Related
hi I tried to root my att lg g2 and this is what I get in command prompt after I run the root file
Determining device model...
Found ATT phone!
Checking OTA version...
We don't have an unlock for this OTA version yet.
Your phone is running D80020c .
Please try the manual root method or
post your full device info in the thread
This program will now exit.
Press any key to continue . . .
my phone running the latest android version 4.4.2
sofare vesion d80020c
is there a way to root the phone please help
thank you
antonov225 said:
hi I tried to root my att lg g2 and this is what I get in command prompt after I run the root file
Determining device model...
Found ATT phone!
Checking OTA version...
We don't have an unlock for this OTA version yet.
Your phone is running D80020c .
Please try the manual root method or
post your full device info in the thread
This program will now exit.
Press any key to continue . . .
my phone running the latest android version 4.4.2
sofare vesion d80020c
is there a way to root the phone please help
thank you
Click to expand...
Click to collapse
Go here droidviews.com/root-lg-g2-after-recent-ota-update/
Press "Thanks" if it helped you
jamesclassy said:
Go here droidviews.com/root-lg-g2-after-recent-ota-update/
Press "Thanks" if it helped you
Click to expand...
Click to collapse
@jamesclassy You might want to re-read a post before you reply to it with a recommendation. He specifically stated that he received the OTA update for 4.4.2 (KitKat); and if you read the description on the website link you provided, not only does it show that the article was last updated in January of 2014, (while KitKat was only recently pushed to the LG G2's in the past couple weeks) it also says the root they provide only works for 4.2.2
Thanks for your attempt to help though.
Download Framaroot app... I think it will work...
N'ayam Amarsh'e said:
Download Framaroot app... I think it will work...
Click to expand...
Click to collapse
@N'ayam Amarsh'e You just did the same thing. Try Googling your own recommendation or list something that's confirmed to work, not something you think will work.
If you go here:
http://forum.xda-developers.com/showthread.php?t=2130276
You'll see that the LG G2 is not a supported device.
Mine was not listed too.. But I tried and it worked... I have tried it on 3 phones which are not officialy listed but it works on them...
Here I Think It Would definitely Work...
Download This
Code:
Drivers :http://bit.ly/18EPHZN
IOROOT24: http://bit.ly/1iadnJP
1.Ensure you have the proper USB drivers installed, and your phone is in the proper mode
2.Enable Developer Mode on your phone and enable USB Debugging
3.Extract the zip file somewhere on your PC
4.Run root.bat
5.The phone will ask you to disconnect USB, disable USB debugging, then re-enable it and plug the phone back in, do so when prompted
6.You will then be asked if you would like to have a superuser package installed, which you can accept or decline...
Press Thanks if I helped...
Nope. It did not work. I've already tried that myself.
Here is the response from the root.bat script:
**************************************************
Automated root for LG Optimus G, G2, G Pro 2, G Flex
Original idea by IOMonster (thecubed on XDA)
Original linux script and Sprint root by Shelnutt2
Original LG root backdoor idea by giantpune
Current IOroot by autoprime
**************************************************
**************************************************
Unlock phone and lock screen.
Turn on airplane mode.
Set USB mode to charge only mode.
Verizon users must use ethernet mode instead!
**************************************************
Press any key to continue . . .
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Determining carrier...
Found TMO phone!
Checking OTA version...
We don't have an unlock for this ATT OTA version yet.
Your phone is running D80120a .
Please try the manual root method or
post your full device info in the thread
This program will now exit.
Press any key to continue . . .
Now, as you can see, oddly the phone initially says "Found TMO phone!" which is correct considering I'm on T-Mobile, but then as indicated it says they don't have an unlock for the "ATT OTA" version. Whether this is simply a typo in some sort of if/then statement in the script causing it to feed the wrong response line, the end result is still that the root is not successful.
For anyone else reaching this thread I just wanted to provided an updated link to the most recent IORoot for LG G2.
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
However, if you're on a T-Mobile variant G2 trying to root after taking the 4.4.2 update, members have shifted to a dedicated post for it as it seems to not want to work like the other G2 variants with IORoot 25.
T-Mobile G2 thread: http://forum.xda-developers.com/showthread.php?t=2706308
Hi all, and firstly I think I need to apologize in advance for what I'm about to ask, as it seems to be a common problem that must be simple to fix but I'll be darned if I can figure out how to do it or find out how to do it.
I've just got my first Android phone, a Moto G (a Tesco's 8G XT1032). It's updated to KitKat 4.4.2, it's been successfully unlocked from the Tesco's network, and I've got the bootloader unlocked based on Motorola's guide.
However, in order to install a privacy app (xprivacy is my current choice, I'm open to suggestions if there are other better ones) I need to complete the rooting on the device. However, despite trying to follow a few of the various guides out on the internet (including Modaco's, and one in Swedish) I don't seem to be able to get the adb command in the Windows Command Prompt window to see the device when fastboot-ed ('adb devices' just comes up blank). I believe this might be down to the drivers that Motorola supply in their 2.4.5 package, but I can't figure out how to get the device recognized.
So finally I've come here to see if anyone might be able to help out.
TIA
Ian
OK, I'm booted and rooted.
Turns out that this page http://theunlockr.com/2014/02/17/root-motorola-moto-g-running-android-4-4-2/ was basically right, but now the two bits to do with 4.3 and 4.4 can be 'ignored' and just the CWM and SU bits are required, as per this thread here: http://forum.xda-developers.com/showthread.php?t=2563599
Zte N9515 Boost Mobile.
I rooted the zte n9515 warp sync from boost mobile about a year ago, I received an OTA update one day, unrooted the phone and the phone still is stuck in a bootloop. I am able to get to stock recovery, but, my issue is I have done everything I could think of to unbrick that phone. Zte updates don't work, stock firmware doesn't work, zte open gives me a partition mbn error, all kinds of flash tools using .pit files bin files IMG files.... I haven't found a way to fix it yet... I'm not too familiar with adb commands and I've done the research.. Using android SDK I only receive an adb rejected shell command error and adb sideload continuously gives me E:2 footer[2]=0x00 footer[3]=0x00 E:signature verification failed error message... No matter what I sideload. I need help fixing this issue if anyone has a suggestion or the answer to this I would really appreciate it....
trysten711 said:
Zte N9515 Boost Mobile.
I rooted the zte n9515 warp sync from boost mobile about a year ago, I received an OTA update one day, unrooted the phone and the phone still is stuck in a bootloop. I am able to get to stock recovery, but, my issue is I have done everything I could think of to unbrick that phone. Zte updates don't work, stock firmware doesn't work, zte open gives me a partition mbn error, all kinds of flash tools using .pit files bin files IMG files.... I haven't found a way to fix it yet... I'm not too familiar with adb commands and I've done the research.. Using android SDK I only receive an adb rejected shell command error and adb sideload continuously gives me E:2 footer[2]=0x00 footer[3]=0x00 E:signature verification failed error message... No matter what I sideload. I need help fixing this issue if anyone has a suggestion or the answer to this I would really appreciate it....
Click to expand...
Click to collapse
My question should've been more direct, what adb commands can I use if fastboot commands won't work?
Wow! A year Later and No takers?
I Have the same issue as of 3 Days ago My ZTE N817 Quest Assurance mobile (Virgin Mobile) received a notice to OTA from Google... It Downloaded just fine.. at the Pause of Install screen I was busy with Grankids so hit Install...
Phone Booted into Recovery Mode (Bootloop)
and all sub flders/files in /fota... /etc... and /system... are Somewhere in the Ether, as far as i can tell.
Used ALL types of recovery methods... [Except oem Firmware... {it's a UNICORN}
unavailable from every ZTE site that claims *ALL ZTE ROMS*
And they often do have over 795 roms ... Just NOT that 1 i need ( ZTE N817 Quest 4.4.4 kitkat Qualcomm MSM8610 sdk19 )
I have Rooted it successfully and unlike so many Zte n817-s mine doesn't unroot @ reboot...
ANYWHO!
Hope ya find a solution i don't want to have to pay for anymore Forensic Applications to deep Force this Crap Box... Jes Sayin
I was told i could get a Forensic App from ZTE China by ZTE china and had to register as an Advocate tester/developer for the Company, and all discovery would be proprietary to them, and them Only!... OoooK!
I'm not gonna fix the issue then have someone else profit on it if i cannot SHARE IT!
CmeL8r
sent from acer 5250 laptop without keyboard
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
Currently this link https://forum.xda-developers.com/tm.../nougat-h90130b-boot-img-img-upgrade-t3638750 suggests that this can be flashed on the H900.
I am starting this thread so that people can share their experiences of what they have tried so far and declutter the above thread so that all H900 related discussion can take place here.
I am currently on Marshmallow with no root and have experienced the same issues as many others
The instructions on the above thread read as follows
* adb reboot recovery
* adb push boot.img /sdcard
* adb push system.img /sdcard
* adb push modem.img /sdcard
* adb push rpm.img /sdcard
* adb shell
* cd /dev/block/bootdevice/by-name
* dd if=/sdcard/boot.img of=boot
* dd if=/sdcard/system.img of=system
* dd if=/sdcard/modem.img of=modem
* dd if=/sdcard/rpm.img of=rpm
* exit
* adb reboot system
The challenges :
1. 'adb reboot recovery' when we do this on H900 on MM we get a green droid with red triangle and can no longer see the device over adb.
2. 'cd /dev/block/bootdevice/by-name' gives permission denied.
What I tried was the following :
1. Copied boot.img to /sdcard
2. Copied system.img to /sdcard
3. I then installed dirtycow and managed to get the root icon in the terminal '#'
running dirtycow in the terminal gave this :
[INFO] Complete. Installed package "run-as" on device.\n[INFO] Cleaning up workspace...Done
[INFO] Starting shell in 3 seconds...
[email protected]:/ $ run-as -exec sh
uid run-as 2000
uid 0
0 u:r:runas:s0
context 0 u:r:shell:s0
[email protected]:/ # ls /dev/block
/dev/block: Permission denied
1|[email protected]:/ #
So my questions are as follows:
1. If we cannot reboot into a useful recovery are we screwed?
2. Am I using dirtycow correctly?
3. Is this a complete non-started as H900 has a locked bootloader?
Cheers,
Trev
3. If this a complete non-started as H900 has a locked bootloader?
Click to expand...
Click to collapse
If you enable developer mode, and then enable OEM unlock, are you able to adb reboot bootloader and then fastboot oem unlock?
If you are not able to unlock your bootloader, then yes it is a non-starter.
What was the root procedure for LP on the H900?
-- Brian
runningnak3d said:
If you enable developer mode, and then enable OEM unlock, are you able to adb reboot bootloader and then fastboot oem unlock?
If you are not able to unlock your bootloader, then yes it is a non-starter.
What was the root procedure for LP on the H900?
-- Brian
Click to expand...
Click to collapse
Hi Brian,
OEM unlock was enabled. Issuing adb reboot bootloader merely reboots the phone.
I foolishly upgraded to MM when I got the phone. There was a rooted Lollipop ROM on here but it is not possible to go back to L once on M.
It looks like AT&T have really locked this phone down. Being in the UK it is also not possible to get AT&T upgrades from their server.
Looks like we are stuck on MM. I cannot even uninstall an app. The phone simply soft reboots.
The root procedure for L was this : https://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317
Cheers,
Trev
Thanks for starting up a dedicated thread for this. AT&T have really messed this device up! We can't even roll it back to LP, those who've tried bricked! I'm happy to do some testing, just can't do anything too risky until I get my wife another phone since she's using this one.
trevt said:
Hi Brian,
OEM unlock was enabled. Issuing adb reboot bootloader merely reboots the phone.
I foolishly upgraded to MM when I got the phone. There was a rooted Lollipop ROM on here but it is not possible to go back to L once on M.
It looks like AT&T have really locked this phone down. Being in the UK it is also not possible to get AT&T upgrades from their server.
Looks like we are stuck on MM. I cannot even uninstall an app. The phone simply soft reboots.
The root procedure for L was this : https://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317
Cheers,
Trev
Click to expand...
Click to collapse
Hi
I am also in UK but I bought my H900 from HK and it came with MM already installed (can't remember which) but I loaded LG Bridge and selected software update and low and behold it updated me to H90021w. I would love to get root on this phone and am willing to test as necessary.
Sent from my LG-H901 using Tapatalk
Hi Stransky,
Do you have any problems with the H90021w update, for example unable to uninstall apps, broken finger print sensor etc?
trevt said:
Hi Stransky,
Do you have any problems with the H90021w update, for example unable to uninstall apps, broken finger print sensor etc?
Click to expand...
Click to collapse
No, no problems at all. The firmware updated as an upgrade as I retained all my apps and settings.
Sent from my LG-H901 using Tapatalk
Hi Stransky, interesting yours already came with MM. I think this is why your update went fine without issues. I upgraded from LP so that could be where something broke.
A friend is in the US at the moment and took my H900 with him and he upgraded it using an AT&T OTA update with an AT&T sim card installed. When I get it back I will report back if this solved the problem.
Cheers,
Trev
Our ATT phone in general does not have an unlockable bootloader, which means we can not (openly) root our device on MM. This also means we can not install a custom recovery onto our device, of which is needed in order to execute adb commands onto the phone. I don't think this device will ever see a custom recovery or root, and I would be surprised if we even see official nougat at this rate.
bkman08 said:
Our ATT phone in general does not have an unlockable bootloader, which means we can not (openly) root our device on MM. This also means we can not install a custom recovery onto our device, of which is needed in order to execute adb commands onto the phone. I don't think this device will ever see a custom recovery or root, and I would be surprised if we even see official nougat at this rate.
Click to expand...
Click to collapse
I would tend to agree with your assessment. Such a waste of a great phone.
H900 at&t USA Holiday.
Hi Trev,
I just read you post about a friend taking your phone to the US and with an at&t Sim was hoping for an Android upgrade.
Did it work? I love the phone and a nougat upgrade would be a dream but the thought to download/upgrade manually is tempting but I am not too confident I will be successful and will no doubt damage the phone.
Cheers
Bert
bertiebro said:
Hi Trev,
I just read you post about a friend taking your phone to the US and with an at&t Sim was hoping for an Android upgrade.
Did it work? I love the phone and a nougat upgrade would be a dream but the thought to download/upgrade manually is tempting but I am not too confident I will be successful and will no doubt damage the phone.
Cheers
Bert
Click to expand...
Click to collapse
Hi Bert, no it did not work.
it hurts, I'm in marshmello and I have the same problems, I can not uninstall apps: c ... nougat and apparently never arrived.
Is there any hope that official nougat for the h900 will come out? .... I update it to mm and the device is almost unusable of the errors it has: c, and it can not be returned to Lollipop either.
trevt said:
Hi Bert, no it did not work.
Click to expand...
Click to collapse
Me too! I sent it to my brother living in the US. He tried to update it to the latest security patch (Kernel version: 3.10.84
Build number: MRA58K /Software version: H90022b) which is stated in the AT&T website:
(To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
BUT unfortunately, even he succeeded to connect to their servers he couldn't get any update. Simply it didn't work!! He tried with AT&T customer service to get some technical quote or advice, but they knew nothing about the issue or how to solve it! the efffing At&t and LG!!! are both held responsible for the H900 variant mess!!!
Fakalus77 said:
Me too! I sent it to my brother living in the US. He tried to update it to the latest security patch (Kernel version: 3.10.84
Build number: MRA58K /Software version: H90022b) which is stated in the AT&T website:
(To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
BUT unfortunately, even he succeeded to connect to their servers he couldn't get any update. Simply it didn't work!! He tried with AT&T customer service to get some technical quote or advice, but they knew nothing about the issue or how to solve it! the efffing At&t and LG!!! are both held responsible for the H900 variant mess!!!
Click to expand...
Click to collapse
Have you try to do factory reset before trying to update? also fresh LG up flashing may help..