*******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
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
Last edited: