*******thread is dated, i do not own the device any more*********
Thank you Senior Member: starkly_raving for a break through with a working TWRP recovery and of course Team Win Recovery Project (TWRP) for there awesome recoveries! PLEASE READ, READ AGAIN AND WHEN YOU THINK YOU'VE GOT IT, READ AGAIN! And remember kiddies no one is responsible FOR WHAT YOU DO BUT YOU! Ill be trying to update this opening post as new info comes about, 2nd post will be dated info for reference.... starkly_raving has also mentioned that when a source built TWRP is complete development on this one will stop.
ROOT
Copied from post #22 Senior Member: starkly_raving
Disclaimer!!!
This is the method I used for the Metro PCS variant running 5.1.1 LMY47V. I can't verify this process for any other model or firmware use at your own risk.
All commands are without quotes.
First you have to unlock your bootloader and root...assuming you haven't here are the steps...
Requirements:
1. SDK installed with fastboot. (Minimal adb and fastboot will work also)
2. ADB/USB drivers
1. Enable developer options.
(a) Enable USB debugging
(b) Allow OEM unlock
2. Boot your device into bootloader mode.
(a) Open a cmd prompt in SDK or minadb fastboot.
(b) Connect device via usb
(c) In the cmd prompt type "fastboot devices" this will show if your device is connected.
(d) Then type "fastboot oem unlock" this will wipe all data including internal storage so backup to your PC or cloud.
(e) Once complete type "fastboot getvar" this will give you confirmation that your bootloader is unlocked.
(f) Finally enter "fastboot reboot" this will reboot you back to Android and you you will be greeted with the "bootloader unlocked" splash screen.
Rooting...
Requirements:
Reenable & Keep USB Debugging On!
Reenable & Keep OEM Unlock On!
Enable Unknown Sources!
Install the Kingroot apk from here...
http://www.kingroot.net/wap
Replace Kingroot with supersu:
http://www.w0lfdroid.com/2015/05/How...perSU.html?m=1
At this point you can update SuperSU binary if needed and install busybox.(always helpful)
Now for you (Boost users) to supply the needed files here's what to do.
1. We need the build.prop...
(a) Use a root explorer and copy system/build.prop to your SD card
(b) Via ADB "adb pull /system/build.prop"
2. We need your fstab and partition info... "cat proc/partitions" this will spit out your partition info.
3. We need your stock recovery.img and boot.img
(a) Use a GUI based app like flashify and backup your stock recovery and kernel.
(b) ADB method..
1.If you are using ADB, connect your device to your computer via USB, launch a command prompt window on your computer and enter the following command:adb shell
2. Enter the following command:"cat proc/mtd" You will get an output similar to this. Note that your result may differ from this one and you must proceed according to the output that you get, rather than the example that you see example here.
dev: size erasesize name mtd0: 000a0000 00020000 "misc" mtd1: 00480000 00020000 "recovery" mtd2: 00300000 00020000 "boot" mtd3: 0fa00000 00020000 "system" mtd4: 02800000 00020000 "cache" mtd5: 093a0000 00020000 "userdata"
To dump the recovery image to your SD card, make note of the first word of the line which says “recovery” in the end. It is ‘mtd1’ in case of this example but may be another entry for you.
3. Now use this command, replacing ‘mtd1’ with the term that applies in your case, if different: "dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096" Similarly, to dump the boot image to your SD card, make note of the first word of the line which says “boot” in the end, which is ‘mtd2’ in our case but may differ for you. Use this command now, replacing ‘mtd2’ with the term that is applicable in your case, if different:"dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096"
That’s it – you now have recovery.img and boot.img backed up on the root of your SD card.
RECOVERY
partial copy from post #42 Senior Member: starkly_raving
Prerequisites:
1. root
2. unlocked bootloader
3. knowledge of fastboot commands.
cmds
To test and not replace your recovery
fastboot boot twrp-image-new.img
If you feel its safe for daily use....
fastboot flash recovery twrp-image-new.img
DOWNLOADS:
Beta1:
https://drive.google.com/file/d/0B46...p=docslist_api
Alpha2:
https://drive.google.com/file/d/0B46...p=docslist_api
Alpha1:
https://drive.google.com/open?id=0B4...WNfMm9sQy1RVmM
dated info for reference only. Original opening post....
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/show...php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching. Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
Please help
reemobeens19 said:
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/showthread.php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching.
Click to expand...
Click to collapse
I rooted my lg k7 with kingroot thought i would try putting xposed on it manually with root browser yes i am a noob at this sorry so yes i replaced files in system\bin, system\lib, and the other places xposed requires now it is stuck on the metro pcs screen i tried the factory reset on the phone like 10 times its not working and my pc only is detecting my phone as LGE Android Net MTP or something like that can you please help I just got it last night :'(
BeLOWME1992 said:
I rooted my lg k7 with kingroot thought i would try putting xposed on it manually with root browser yes i am a noob at this sorry so yes i replaced files in system\bin, system\lib, and the other places xposed requires now it is stuck on the metro pcs screen i tried the factory reset on the phone like 10 times its not working and my pc only is detecting my phone as LGE Android Net MTP or something like that can you please help I just got it last night :'(
Click to expand...
Click to collapse
my advice is take it back, while its still under warranty. i wouldnt tell them you rooted it though. as of right now im having driver issues and cannot help.
do you get a security error indicating modification? can you get into recovery? if so try a wipe
Lg k7 metro pcs
Lg k7 metro pcs cant find a custom recovery yet has anyone found one if so please let me know I can't do anything cool on my phone without one
Rooting the device voids warranty i believe.. and theirs no support for this phone at all...
Frustrated.
I rooted mine with KingRoot, then installed Link2SD and moved all of my downloaded apps to the second partition of my external SD. Shortly afterward, all of my applications began crashing, even system ones like Phone, Settings, Contacts, etc. Like an idiot, I performed a factory reset on my device. After the reset, it wanted the original Gmail account that was linked prior to the reset, but LG Keyboard crashes and I can't proceed. Thought maybe I could sideload Google Keyboard but of course USB debugging was disabled after the reset. Luckily, I took it back to the MetroPCS store I purchased it from and was able to get them to order me a replacement. I still have the "bricked" device in my possession, and hopefully I won't have to exchange it to get the new one.
Now that I've explained my situation, is there anyone out there with the KDZ image for this model? I'm thinking that's my only hope to restore this poor thing. I know I've got another one coming, but it'd be nice to have a working backup phone just in case.
mine wont let me reset it need help
Guys I know this is off topic but could you share the stock wallpapers of the K7 please????
reemobeens19 said:
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/showthread.php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching.
Click to expand...
Click to collapse
Be sure to update when a custom recovery is available i just don't feel safe with my lg k7 rooted without a recovery. i mess things up quite often and custom recovery's CWM or TWRP have always got me out of sticky situations
ermond012 said:
Guys I know this is off topic but could you share the stock wallpapers of the K7 please?
Click to expand...
Click to collapse
All of them?
Atelear said:
All of them?
Click to expand...
Click to collapse
Yeah, if possible...?
I'm not sure how to upload the file where I put them
---------- Post added at 08:20 PM ---------- Previous post was at 08:13 PM ----------
ermond012 said:
Yeah, if possible...
Click to expand...
Click to collapse
There. These are all the wallpapers excluding the live wallpapers.
PM me for the link
Is the tribute 5 the same phone as the lg k7?
Migue9088 said:
Is the tribute 5 the same phone as the lg k7?
Click to expand...
Click to collapse
Yes they are the same. I think Boostmobile just named it something else
I can try to port a recovery to it if someone can point me to the right direction
I don't think there any custom recovery yet
Hey guys,
I've rooted and unlocked the bootloader on the Metro PCS variant. I have also got in contact with a developer and provided him with the fstab, stock recovery, boot.img and build.prop...what's this mean? We will have a custom recovery very soon. :thumbup:
---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------
Also could someone who's rooted post the adapt folder/apk? I accidentally lost mine when I moved it to SD and when I unlocked the bootloader it wiped my storage. Thanks guys.
starkly_raving said:
Hey guys,
I've rooted and unlocked the bootloader on the Metro PCS variant. I have also got in contact with a developer and provided him with the fstab, stock recovery, boot.img and build.prop...what's this mean? We will have a custom recovery very soon. :thumbup:
---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------
Also could someone who's rooted post the adapt folder/apk? I accidentally lost mine when I moved it to SD and when I unlocked the bootloader it wiped my storage. Thanks guys.
Click to expand...
Click to collapse
Can you tell the person if he could make one for the tribute 5 please
Migue9088 said:
Can you tell the person if he could make one for the tribute 5 please
Click to expand...
Click to collapse
Once we have the one for the K7 finished I'll submit the files for the Tribute 5 if some one can provide them.
Related
Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.
One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.
Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page
ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...
Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.
Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.
So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!
This thread is out of date since there is my new thread with an easier method: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
However i keep this one for troubleshooting and deeper understanding...
This description was originally made for the k8, however it seems to work on k10 k430 devices
LG K8:
OS Android v6.0 (Marshmallow)
Chipset Mediatek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB of RAM
8GB ROM
LG K10 K430...:
quite similar to k8
Rooting the k8 (and the k10) is rather difficult since it's using "lz4" compression for the partition images not the usual "gzip" method.
Systemless supersu is still unable to patch lz4 boot images so we need to have a little trick. Not to mention porting a working TWRP is also a pian in the ass...
Before posting any questions/errors please read the troubleshooting guide and also read back in the thread!
Steps:
0.
Remove the back panel of the phone because you'll have to be able to reach your sd card, watch out for your battery - must not fall out!
If your TWRP supports mtp connection under "mount" you can skip this part and you don't have to put your sd card in and out - maybe you have to fix the driver in windows!
1.
Unlock your bootloader (all your data will be lost!!!) via ADB then boot up normally
http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
if there is no warnning message during boot up after unlocking your bootloader read this:
http://forum.xda-developers.com/lg-k10/how-to/rid-shutting-device-corrupt-message-t3517879
2.
Boot to TWRP (you have to stay in TWRP during the whole process!!!) via ADB and fastboot
3.
Mount sd card
Backup your boot image (find boot.emmc.win in TWRP folder on your sdcard - rename it on PC to bootlz4_0.img)
or use your boot image taken from your kdz as it is written in the end of this thread:
http://forum.xda-developers.com/lg-k10/how-to/rid-shutting-device-corrupt-message-t3517879
4. Tweak bootlz4_0.img with Carliv Image Kitchen (Carliv download: http://viid.me/qe7BDp)
-Unpack it, open "boot.img-ramdisk-compress" file with a text editor (notepad++) and change the first (and only) line from "lz4" to "gz"
-Repack image - rename the repacked image to bootgz_0
5. Flash bootgz_0.img in TWRP
6. Install SuperSU (and xposed if you wish or you can istall xposed later) - do not quit TWRP from now until last step - that would brick your device
7. Backup boot image again - you need to remove sd card (unmount first) and put it in PC - it means you have to remove the usb cable from the phone and remove back panel - maybe before getting into TWRP!
- or enable mtp in TWRP and copy/paste the boot image from sd card.
8. Tweak boot image in Carliv
-Unpack it, open "boot.img-ramdisk-compress" file and change the first line from "gz" to "lz4"
-Repack image
9. Flash boot image in TWRP
10. Restart (this will take a bit longer and also expect bootloop a few times)
you can find a rather detailed description here:
http://viid.me/qe7Zoh - don't forget that you can use mtp connection instead of taking in and out the sd card if your TWRP supports it.
If you prefer using adb/fastboot commands instead removing your sdcard all the time you can use salaigeethan666's guide:
http://forum.xda-developers.com/showpost.php?p=69415205&postcount=34
but some reported problems with flashing the boot image and getting back to TWRP this way.
If you have problems booting up after installing supersu maybe you can force boot described by cpatrick3000:
http://forum.xda-developers.com/lg-k10/how-to/root-lg-k10-mtk-chipset-95-method-t3498166
or the problem might be:
http://forum.xda-developers.com/lg-k10/how-to/rid-shutting-device-corrupt-message-t3517879
If you ever lose root and try again consider Darkos333's guide: http://forum.xda-developers.com/showpost.php?p=69713043&postcount=99
or use lg up to get back to full stock:
http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
Unbrick guide by Berkantkz:
http://forum.xda-developers.com/lg-k10/how-to/guide-unbricking-flashing-firmware-due-t3380529
Unbrick by lg up:
http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
TWRPs for the different models:
TWRP of the k8:
http://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894
As for the k10 TWRP 3.0.0 you should use http://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434 by berkantkz.
or TWRP 3.0.2 by Singular777: http://forum.xda-developers.com/showpost.php?p=69381986&postcount=126
In case of k10 430dsy try 123xdagsm's recovery: http://forum.xda-developers.com/showpost.php?p=69706581&postcount=154
Please, before you proceed read and practice the methods of each steps! A few hours of preparation (google + xda + tests) might save your device getting hard bricket and it's also better for you to know what you're doing! Look for fastboot commands, systemless supersu, TWRP usage, Carliv image kitchen, ... (google + xda)! You better not leave TWRP during the whole process! Keep in mind that after the supersu is installed you must be able to recompress your boot image to "lz4" otherwise you get soft bricked and you need to use lg up to refirbish...!!!
Read each steps twice and follow them stricktly!
Also keep in mind that if you want to uninstall supersu/remove root you have to reflash stock firmware with lg bridge + hard reset or lg up.
Troubleshooting
"your device is corrupt. It can't be trusted and may not work properly"
- this message is normal when you have an opened bootloader
- phone shuts down right after this message: http://forum.xda-developers.com/lg-k10/how-to/rid-shutting-device-corrupt-message-t3517879
no ADB connection (command: "adb devices" - your device is not in the output list):
- turn-on USB Debugging (settings - developer opions)
- install drivers
no fastboot connection (command: "fastboot devices" - your device is not in the output list):
- install drivers
- check device manager
- you may try to install android SDK if the connection is not working
unable to unlock bootloader (command "fastboot oem unlock"):
- allow oem unlock (settings - developer opions)
device is not booting into TWRP:
- unlock bootloader
- the TWRP is not compatible with your device (there is a list of TWRPs for different devices, if you cant find yours you can try the next guide: http://www.chinaphonearena.com/foru...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial)
unable to unpack boot image in carliv
- your TWRP is not compatible with your device (at least it didn't backup your boot image properly)
unable to repack boot image in carliv
- check the unpacked boot image "ramdisk" folder, if there are all the necessary files and folders, find a list attached at posts #107 and #124: (doesn't have to be the exact same since k8 and k10 migth differ - there is no "boot" folder in case of the k8 and also before installing supersu the su folders are not to be there - normally 5+ folders and 20+ files)
- see if "boot.img-ramdisk-compress" file exists
- maybe you messed up something in carliv
supersu failed to patch the ramdisk (even if it sais installed succesfully)
- you can try just unpack and repack your stock boot image install/flash it and see if it boots up - so you can be sure you are a "master" of carliv and TWRP
- your boot image is not gzip compressed - open "boot.img-ramdisk-compress" as text. It should only have one line: "gz"
supersu failed to install
- you can try just unpack and repack your stock boot image install/flash it and see if it boots up - so you can be sure you are a "master" of carliv and TWRP
- your TWRP is not compatible with your device (or you need a newer version)
device is not booting up after the final step (boot loops for more then 2 minutes)
- http://forum.xda-developers.com/lg-k10/how-to/rid-shutting-device-corrupt-message-t3517879
- use Berkantkz guide to flash back the original firmware: http://forum.xda-developers.com/lg-k10/how-to/guide-unbricking-flashing-firmware-due-t3380529
- after getting back to stock you can try just unpack and repack your stock boot image install/flash it and see if it boots up - so you can be sure you are a "master" of carliv and TWRP
- duble check your final boot image (uncompress and compare files and folders to the one attached in posts #107 and #124 - has to be reasonably/more or less the same)
- consider step 6 in Darkos333 guide: http://forum.xda-developers.com/showpost.php?p=69713043&postcount=99
- also consider cpatrick3000's force boot guide: http://forum.xda-developers.com/lg-k10/how-to/root-lg-k10-mtk-chipset-95-method-t3498166
if none of these helps make a recovery log (in TWRP under advanced menu) before final restart and post it or send it to me
This method works for the LG K10 k430Y as well. Thanks very much brah, so far I have changed a couple of thing in the build.prop like activating the multi window setting and so far it is functioning properly besides the annoying 'device is corrupt' message everything seems to be fine thanks a lot bro :good: :good:
Judroidz said:
This method works for the LG K10 k430Y as well. Thanks very much brah, so far I have changed a couple of thing in the build.prop like activating the multi window setting and so far it is functioning properly besides the annoying 'device is corrupt' message everything seems to be fine thanks a lot bro :good: :good:
Click to expand...
Click to collapse
"device corrupt" message cames rigth after unlocking the bootloader (in my case at least...) however i believe there is a way to tweak boot logo and remove the message, Ill look into it.
Anyways your welcome
Judroidz said:
This method works for the LG K10 k430Y as well. Thanks very much brah, so far I have changed a couple of thing in the build.prop like activating the multi window setting and so far it is functioning properly besides the annoying 'device is corrupt' message everything seems to be fine thanks a lot bro :good: :good:
Click to expand...
Click to collapse
Can i ask whitch TWRP you used? Did you maybe tried it with the one i ported for the k8 or is this the one by berkantkz?
I used the twrp made by berkantkz, do you think it would be safe if I flashed it on my k10.
Judroidz said:
I used the twrp made by berkantkz, do you think it would be safe if I flashed it on my k10.
Click to expand...
Click to collapse
Actually the recovery partitions size is approx. 16Mb. Berkantkz's TWRP is almost 17Mb so there is little chance you can flash it. There is no problem if you try it would give you an error message if the size is too big and nothing's gonna change. I recompressed berkantkz's TWRP to gzip (https://drive.google.com/open?id=0BwyMOazoSp8TdnhBbWpobEk0V0E) so it is smaller, you can try to flash that but you have to try it before. I mean just boot into it (fastboot boot ...) don't flash it first.
Keep me updated please!
About the multiwindow, did you use "ro.build.type" -> userdebug or "persist.splitwindow.support_all" -> true ?
I flashed back to stock with lg bridge and also did factory format with hard buttons. There is no way to root again and boot up succesfully. Somehow lg bridge and also factory format leaves some partions untouched that still have something from supersu. So i erased all partitions in fastboot...
I shouldn't have cause now my phone can't connect at all. Not even in download mode.
I suggest if anyone tried any method to root unsuccesfully that should not try this method. It will not boot up...:S
Thats all for now. I'll try to exchange my phone and then start again...
I can't make lg up to work with the k8. There is no lgup...dll.msi to install. Any ideas?
Maybe the boot image is not turned back to stock not by factory format nor by lg bridge... this migth cause the mess with Supersu install after turnig back to stock... With lg up we could reflash the full stock system and try rooting again...
If anyone plans to root save your stock boot image first, might come handy later...
hilp for root lgk10 439dsy
ha118814kh said:
hilp for root lgk10 439dsy
Click to expand...
Click to collapse
439? Are you sure? I guess it must be 430... however i belive the only method is the above described one. If you ever attempted rooting the device i suggest not to do that unless you can flash it back to fully stock.
Theese might help for unsuccesful root attempts... i wish i found this before erasing all my partitions...:S
http://forum.xda-developers.com/showpost.php?p=63816659&postcount=2769
and
http://forum.xda-developers.com/apps/supersu/unroot-systemless-root-t3249542
Are there any easier ways to root it? It seems a bit of difficult to me(k430)
xdarootxda said:
Are there any easier ways to root it? It seems a bit of difficult to me(k430)
Click to expand...
Click to collapse
I'm afraid until SuperSU is not "lz4" compatible there is no easier method. I't not so difficult anyways as long as you can make a fastboot connection. There is always download mode and lg bridge if anything goes wrong...
PS. if you ever attempted to root this device before then most likely it's not gonna work... unless you can make LgUP see your k430 and reflash the whole firmware.
gottlasz said:
I'm afraid until SuperSU is not "lz4" compatible there is no easier method. I't not so difficult anyways as long as you can make a fastboot connection. There is always download mode and lg bridge if anything goes wrong...
PS. if you ever attempted to root this device before then most likely it's not gonna work... unless you can make LgUP see your k430 and reflash the whole firmware.
Click to expand...
Click to collapse
Thanks for the information, but i'm new to bootloader and recovery, so are there any video guides about this process?
xdarootxda said:
Thanks for the information, but i'm new to bootloader and recovery, so are there any video guides about this process?
Click to expand...
Click to collapse
There are many video guides on youtube but not for this particular case. I guess you can search each step separately and put the whole picture together.
gottlasz said:
There are many video guides on youtube but not for this particular case. I guess you can search each step separately and put the whole picture together.
Click to expand...
Click to collapse
Thanks, I'll have a look.
I'm so glad to see people working on this phone. Has anyone gotten this method to work?
Sent from my VS500 using XDA Free mobile app
chopperchez said:
I'm so glad to see people working on this phone. Has anyone gotten this method to work?
Sent from my VS500 using XDA Free mobile app
Click to expand...
Click to collapse
Guys,root is successfully received!
see details on the Russian forum
4pda in the subject LG K10 LTE.
Sent from my LG-K430 using xda premium
lg_l7_p700 said:
Guys,root is successfully received!
see details on the Russian forum
4pda in the subject LG K10 LTE.
Sent from my LG-K430 using xda premium
Click to expand...
Click to collapse
Unfortunately i speak no russain.. Is it somewhat similar to the method described in the OP?
It also uses carliv so i guess its basically the same, isn't it?
lg_l7_p700 said:
Guys,root is successfully received!
see details on the Russian forum
4pda in the subject LG K10 LTE.
Sent from my LG-K430 using xda premium
Click to expand...
Click to collapse
The principle of obtaining root.
Install SuperSU via TWPR.
We have the boot ramdisk
compression in lz4,it is not
supported so first comes the
installation boot with
compression gz,then install SuperSU,
and boot back lz4
Sorry for my bad English.
Sent from my LG-K430 using xda premium
I would love to try this.. but I tried flashing the supersu package previously and it didn't work.. my phone boots up properly.. but my usb isn't working anymore. I can't get into fastboot anymore cos there is no hardware shortcut to enter into that and Without ADB i can't go into fastboot. is there any way to fix this? pls help
Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay
jortiz31877 said:
Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay
Click to expand...
Click to collapse
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system
Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?
jortiz31877 said:
Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?
Click to expand...
Click to collapse
you said u were good w/ that step so I didn't mention....fastboot is not an option in the menu, it's a tool...you need to use fastboot command to unlock bootloader & also to flash twrp
install this for fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.
jortiz31877 said:
Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.
Click to expand...
Click to collapse
after unlocking bootloader, you will need to flash twrp (fastboot flash recovery nameofrecovery.img), the twrp.img needs to be in you sdktools folder on pc, after flashing, then boot into twrp...from download mode, choose reboot to bootloader, then reboot to recovery. once in twrp, you should probably leave /system read only, then copy either supersu or magisk to sd card, and choose install from main menu of twrp....once done, boot device. if using magisk, update from store
u only need to connect to pc when entering fastboot cmds
will this root work with boost mobile HTC bolt or is there a root that will work for this phone
Chrism1971 said:
will this root work with boost mobile HTC bolt or is there a root that will work for this phone
Click to expand...
Click to collapse
Either should work fine
Sent from my unknown using XDA Labs
Question
OMJ said:
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system
Click to expand...
Click to collapse
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.
craftingatic said:
I am scared to lose my warranty on my phone.
Click to expand...
Click to collapse
You will lost your warranty anyway, if you open the bootloader via HTCdev.
craftingatic said:
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.
Click to expand...
Click to collapse
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look
OMJ said:
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look
Click to expand...
Click to collapse
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up
roadkill42 said:
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up
Click to expand...
Click to collapse
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then
OMJ said:
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then
Click to expand...
Click to collapse
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
Click to expand...
Click to collapse
No triangle just HTC in gray then flashes red letters under it
roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
No triangle just HTC in gray then flashes red letters under it
Click to expand...
Click to collapse
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode
OMJ said:
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode
Click to expand...
Click to collapse
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow
roadkill42 said:
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow
Click to expand...
Click to collapse
Is there a complete in full detail way of flashing tarp in download load mode?
roadkill42 said:
Is there a complete in full detail way of flashing tarp in download load mode?
Click to expand...
Click to collapse
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html
OMJ said:
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html
Click to expand...
Click to collapse
OK thanks there is a lot out there I might did wrong one I try this way and let u know thanks again is there a special key combo to get into twrp after flashing ?
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
HT7120403511 device
when i try to reboot to recovery under the htc says this build for devloping purpose only im on n with no updates installed this phone came to me like this bran new
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
sending 'recovery' (8156 KB)...
OKAY [ 1.782s]
writing 'recovery'...
(bootloader) HOSD CL#821651
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.311s]
finished. total time: 4.096s
C:\Program Files\Minimal ADB and Fastboot>adb reboot
error: device not found
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.004s
C:\Program Files\Minimal ADB and Fastboot> I'm on 7.0
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Your first link for the userdata image says file not found when you go to that link.
UPDATED USERDATA
freedomwarrior said:
Your first link for the userdata image says file not found when you go to that link.
Click to expand...
Click to collapse
Sim unlock
Hey guys,
has anyone managed to find a way to simunlock this phone? I bought one on blackfriday for $49 and since then its been sitting in my closet because it does not accept any other network's sim.
aslezak said:
UPDATED USERDATA
Click to expand...
Click to collapse
That one don't work either
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
The problem with this seems to be, at least for me, that a .bz2 file is not recognized by the recovery as an installable zip.
The dd trick worked for me, but the system image here, is not full stock. IT seems to have a mix of super_su and magisk in it.
Root is working, but I can't seem to mount system as r/w
So trying to figure this out. I used this image to do a restore, and my phone was rooted with magisk.
First time a program tried root, it said that super su was installed. When I went to another one, it said that magisk was installed.
Anyrate, at one time I was able to mount system r/w and make changes. Now it seems that I can't for whatever reason. I don't know exactly how I got it
to the state to be able to modify the system.
I actually pulled an entire copy of the rom at one time, with a dd command. Of course that can't be reflashed from twrp. But I'd like to be able to mount it somehow on a pc so I could do a stringsearch for all files that have an ro, in them to find the master files where the filesystems are mounted, and edit those....
crashburn833 said:
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Click to expand...
Click to collapse
the system.img requires a monthly membership, could an updated link using something like mega or mediafire be created please?
one789 said:
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
Click to expand...
Click to collapse
what custom rom?
HELP PLEEEASE! Bricked h1711
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Hard bricked Dreaded QHSUSB_BULK issue. Need mmcblk0.img PLEASE PLEASE HELP!!!! I've lost recovery and fastboot! Nothing but a black screen and a blue light.
Click to expand...
Click to collapse
divineBliss said:
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Click to expand...
Click to collapse
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Whit3Rabbit said:
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
Click to expand...
Click to collapse
divineBliss said:
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Click to expand...
Click to collapse
That's what I was afraid of Thank you for the quick response.
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
Click to expand...
Click to collapse
What is the link to the info you found?
I have the image you need, but it is 15 GIGs in size, and there is no practical way to send that. I also have a system image, and a boot image with magisk in it, as per the OP.
P.M. me.
I don't see how you can recover this if you don't have recovery or fastboot, and can't boot into the phone. If the bootloader is corrupted, well I just don't know.
Can you get into twrp?
You do know that there are two recoveriess, one erecovery and another recovery.
It seems that POWER and VOL up may get you into one, and POWER and VOL down may get you into another one.
NOTE: I KNOW you can't flash the image via fastboot, cause I tried it. it is just to big.
The files are all to big to post here....
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 I put this up 6 days ago for someone else. I don't know how long the link is good for.
This is the system image from the non-working link. You will need to untar it.
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 <<<<<<<<<< file from Original Post
https://nofile.io/f/vTRffT3CM0s/erecovery.zip <<<<<<<<<< erecovery is same as stock recovery
https://nofile.io/f/3DRA4bYjdsq/twrp-xt2.7z <<<<<<<<<< Hweng's original twrp
https://nofile.io/f/uAET5bTqQVk/patched_boot.zip <<<<<< bootloader patched with magisk for a root that does not touch the system partition.
I'll try to put the 15 gig mmblockp0 up here if it will take it, but it is at the office.
I hope this helps.
I now also have a virgin system image, stock. The image given above appears to also have supersu installed it int.
at least it has a su in the system image. Where magisk, just patches the boot image as I understand it.
Any luck on that stock system.img? I formatted mine like an idiot and now sitting on a phone with no OS
same as above, i will even take the rooted system.img i have all other files needed.
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
littletech said:
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
Click to expand...
Click to collapse
step by step root > https://forum.xda-developers.com/hu...ooting-restoring-huawei-elate-h1711z-t3764391
the files for root are the same for the Elate and the XT2
Blue light black screen fix
Whit3Rabbit said:
That's what I was afraid of Thank you for the quick response.
Click to expand...
Click to collapse
My device suffered the same fate, only a blue light black screen unable to enter boot or recovery. I slowly removed the back cover using my fingernails and removed the two screws holding the metal plate above battery on the right. Popped the left most plug to disconnect the power flow and allow phone to power off completely. Be careful not to touch any of the metal near the plug or you will short. I plugged it back in and held volume down while I inserted USB connected to computer. Tada!! Back in action fastboot ready... So OK now what?? I can't seem to be able to flash an update. Zip just keeps saying failed to load, and system image is too big. Can someone point me to the correct files I need to get her working again? Thanks in advance.
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
How much can we expect to speed this tablet up with just root?
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
marcdw said:
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
I have not added other module.
I root this table so I can install CF.Lumen to fix that muddy tint.
Ahh thanks for this!! I haven't had root in any device for awhile. hoping for twrp soon. Let me know if I can assist in any way!
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
ice5192 said:
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
Click to expand...
Click to collapse
Yeah, that does sound kind of odd.
What it means is type in (no quotes) "fastboot flash boot " ( note the space after) and then you are to drag the patched_boot.img file into the cmd window to complete the line.
Not necessary if the file is in the same directory as fastboot. So full line is
"fastboot flash boot patched_boot.img"
I too had to reread that line of instruction a couple of times.
LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5
Is anyone using TWRP? What version?
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
beymapwrd said:
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
Click to expand...
Click to collapse
Did you install the LG driver's? Happened to me because I forget to install the LG unified drivers. Link in OP
Sent from my [device_name] using XDA-Developers Legacy app
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Drivers installed, had to run first:
adb kill-server
adb start-server
then the rest of the commands..
coolchris305 said:
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Click to expand...
Click to collapse
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
itzmehotsauce said:
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
Click to expand...
Click to collapse
Download twrp builder...but even then i still can't boot into it...
coolchris305 said:
Download twrp builder...but even then i still can't boot into it...
Click to expand...
Click to collapse
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
itzmehotsauce said:
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
Click to expand...
Click to collapse
Yeah. Rootchecker confirms I have root on mines
I've run into the same issue. The image seemed to have been flashed, but whenever I try to boot into recovery it just goes to fastboot (bootloader).
Canadian Variant
Anyone know if there's any general rule to modifying stuff to work with other models? Other than build.prop edits to v533 instead of v530 I'm at a loss, and I'm guessing the boot image is specific to T-Mobile variants..
There's gotta be a way to work off this framework, but again I've got no idea, and it may be way beyond my skill level
So I've had this tablet since March but really haven't used it much. My question is once I root it using your written guide do you recommend a app to use for getting Free Hotspot Tether on it? I am a 11 year tenure TMO Customer & have a legacy grandfathered rate/data plan.
Even tho my data plan says I have unlimited hotspot tether it is blocked by TMO. I have reached out to T-Mobile on Twitter & even the executive resolutions team of the president office but they just said that at one point it was allowed but that TMO took it away for whatever reason.
So rather than fighting tthem further or getting the FCC or FTC involved for false advertising I figured I'll just use an app once rooted to bypass root. Just wondering if anyone knows what is the best app to use to achieve this once rooted. Thank you very much & have a wonderful day!! ?
All the best,
Ron.
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
mingkee said:
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
Click to expand...
Click to collapse
Hello would you happen to know of a app to use with this to get Free Hotspot Tether for TMO once I Root it. Hotspot is currently blocked on my legacy grandfathered data plan even tho my plan shows I have unlimited hotspot tether.
So rather than fighting T-mobile regarding this I figure I'll just root & use an app to get my free hotspot tether back. Thank you very much & have a wonderful day!! ?
@QkTreasures, I use WiFi Tether Router. Had it a few years. It works for the most part. Sometimes I can go hours tethering without using my hotspot data but there's been a time or two where it didn't hide the tethering.
LG G3 D851, PAC-MAN LP ROM, MultiROM, XDA Legacy