Related
for Fire 7in 2015 5th Gen Only ( KFFOWI/Ford)
Downgrading Options
If flashing Stock over a custom rom
5.3.1.0 is the safest rootable version, if original firmware is unknown. -25 Oct 2018
Fire OS 5.3.1.0 was the last rootable version for all Fires,
except the HD 10.
Do not attempt to downgrade. 24 Oct 2018
5.3.2.1 cannot be rooted, nor downgraded -28 Dec 2016
5.3.2 can not be rooted, but can be downgraded to 5.3.1.0 - 28 Dec 2016
5.3.1.0 cannot be downgraded, trying will brick - 19 Jul 2016
System version 5.1.4, 5.1.3 & 5.1.2.1 can be downgraded to 5.1.2 - 5 June 2016
System version 5.1.4, 5.1.3, 5.1.2.1, and 5.1.2 cannot be downgraded to 5.1.1 or lower
System Version 5.1.X cannot be downgraded to 5.0.X
Download Firmware
Fire (5th Generation) Software
Note:This Can be done with PC/Mac/Linux but I'm just including PC instructions for now.
Watch
[Video]How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
Mac
How to Downgrade the Firmware on the Amazon Fire 5th gen from 5.3.2 to 5.3.1 using Mac OS
https://youtu.be/iv0VcNM8IAw
PC Steps
Install ADB Drivers and verify they are installed correctly
Setup ADB
Download the Amazon Fire Firmware and place it with your ADB.exe files
Verify that Firmware file is correct version, size, and best to check the MD5 or SHA-1 checksum
Boot into recovery: Hold Volume Down button & Power button at the same time (If it boots to Fastboot mode, use the other Volume button)
Connect to PC via usb cable
Select Sideload in recovery
Recheck Device Manager (PC)
Send adb code (change to filename of firmware)
Code:
adb sideload filename
Its going take 5- 10 minutes so be patient
Once the recovery options come back up, wipe data and cache.
Select Reboot
Reboot is going to take few minutes BE PATIENT!!
Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
A000XXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522054520.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)
saved
how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.
fastcar22 said:
how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.
Click to expand...
Click to collapse
That has been an issue with 5.1.1 after trying to flash a Rom with FlashFire.
Is rom booting?
Sent from my XT1060 using Tapatalk
sd_shadow said:
That has been an issue with 5.1.1 after trying to flash a Rom with FlashFire.
Is rom booting?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
nope got stuck in cyanogen icon mode. thats why ia m trying to recover to factory flash
fastcar22 said:
nope got stuck in cyanogen icon mode. thats why ia m trying to recover to factory flash
Click to expand...
Click to collapse
could try wiping cache and or data in fastboot mode
not sure that is even possible, but worth trying
need to setup adb/fastboot then
fastboot wipe cache command
Sent from my XT1060 using Tapatalk
sd_shadow said:
could try wiping cache and or data in fastboot mode
not sure that is even possible, but worth trying
need to setup adb/fastboot then
fastboot wipe cache command
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Can you give me the fastboot commands? i can get to fastbootcommand prompt to do this?
i even tried the "fastboot install filename.zip" it says it could not find the android-info.txt in the zip file.
Thanks
fastcar22 said:
Can you give me the fastboot commands? i can get to fastbootcommand prompt to do this?
i even tried the "fastboot install filename.zip" it says it could not find the android-info.txt in the zip file.
Thanks
Click to expand...
Click to collapse
Code:
fastboot erase data
fastboot erase cache
Sent from my XT1060 using Tapatalk
sd_shadow said:
Code:
fastboot erase data
fastboot erase cache
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
it does not recognize data in the command i get this message
erasing 'data'...
FAILED (remote: unknown command)
finished. total time: 0.000s
fastcar22 said:
it does not recognize data in the command i get this message
erasing 'data'...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
i was afraid of that, I do not have any ideas how to fix.
could try flashing stock boot.img, then return to Amazon
Sent from my XT1060 using Tapatalk
sd_shadow said:
i was afraid of that, I do not have any ideas how to fix.
could try flashing stock boot.img, then return to Amazon
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
i even tried that it says flashing not allowed
target reported max download size of 134217728 bytes
sending 'boot' (4348 KB)...
OKAY [ 0.140s]
writing 'boot'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.156s
is there anythign else in fastboot commands to delete the files?
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
can you tell me how to get to adb mode using volume up and power button, some are sayiing that it does not show recovery command but remove finger from power button when u see logo and side load?
fastcar22 said:
i even tried that it says flashing not allowed
target reported max download size of 134217728 bytes
sending 'boot' (4348 KB)...
OKAY [ 0.140s]
writing 'boot'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.156s
is there anythign else in fastboot commands to delete the files?
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
can you tell me how to get to adb mode using volume up and power button, some are sayiing that it does not show recovery command but remove finger from power button when u see logo and side load?
Click to expand...
Click to collapse
there is no button combination, for adb
but it is not possible that adb is available during part of the boot, unlikely though
Power off then power on
try
Code:
adb reboot recovery
Sent from my KFFOWI using Tapatalk
sd_shadow said:
there is no button combination, for adb
but it is not possible that adb is available during part of the boot, unlikely though
Power off then power on
try
Code:
adb reboot recovery
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
i am sorry i meant to ask a different question, is there a way to get to stock recovery mode in 5.1.1 when flashfire is used?
fastcar22 said:
i am sorry i meant to ask a different question, is there a way to get to stock recovery mode in 5.1.1 when flashfire is used?
Click to expand...
Click to collapse
what likely happened is FlashFire moved the wipe option to last task
so the rom was wiped from system, then device rebooted
for some reason those with the 5.1.1 bootloader, lose recovery, for some reason.
if the rom was Bootable, i believe stock recovery would also still work.
right now I have no idea how to fix it.
Sent from my KFFOWI using Tapatalk
sd_shadow said:
what likely happened is FlashFire moved the wipe option to last task
so the rom was wiped from system, then device rebooted
for some reason those with the 5.1.1 bootloader, lose recovery, for some reason.
if the rom was Bootable, i believe stock recovery would also still work.
right now I have no idea how to fix it.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
thanks for your replies, i will wait for a solution until then i will stick with my bricked device
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Nea123 said:
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Click to expand...
Click to collapse
There seems to be a few of us with this problem but all we have is fastboot to work with so it doesn't look good, without adb i don`t know how we can flash anything.
Nea123 said:
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Click to expand...
Click to collapse
All 2015 Fires are within 1 year warranty. Contact Amazon for replacement options.
I think this is not a good idea. The fire hangs on the boot screan with cm12.1 .
For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!
Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate
Change log ? Or its just a security update
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck
m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!
rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button
redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?
dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing
dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.
Just delete this if it's considered in the wrong place. If and when is the the Stylo 2 Plus getting its own forum and has anyone come up with an exploit for rooting this phone yet?
Hiya
Yes this is the wrong place. This is for the g stylo not the stylo 2 plus as can be seen in the name of the forum.
No there is not an exploit yet. Kingroot, kangoroot, one clove root, etc all do not work yet. Soon i would imagine
I even have trouble looking on the web for things because it seems we share a model number ms550 with the lg optimus m. Weird
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Reserved
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
mustangtim49 said:
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Remote: unknown command
Rmontoya83 said:
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Click to expand...
Click to collapse
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Rmontoya83 said:
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
Click to expand...
Click to collapse
[email protected] said:
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Click to expand...
Click to collapse
Then Twrp didn't flash
Flashing
Rmontoya83 said:
Then Twrp didn't flash
Click to expand...
Click to collapse
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
What software version are you running?
[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
Wrong command your trying to boot twrp
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
It was something I found in another tutorial when I started trying other things, since the "fastboot flash recovery recovery.img" was not getting me past the standard Android recovery. I'm about to try the file you sent me last night. I'll let you know the result.
---------- Post added at 10:25 PM ---------- Previous post was at 10:13 PM ----------
Rmontoya83 said:
What software version are you running?
Click to expand...
Click to collapse
Android version 6.0.1
Android security patch level 2016-08-01
Kernel version 3.18.20
Windows 7 Pro x64
The recovery.img you sent also said it flashed, but I got to the same Android factory reset screen after the key press procedure (volume down, power, release power, repress power, release all)
Here's the latest:
C:\Users\Darin\Downloads\platform-tools-latest-windows\platform-tools>fastboot f
lash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15518 KB)...
OKAY [ 0.495s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 0.865s
Once you boot into recovery, let the screen fully dim, do not touch it... once the screen is completely blacked out, turn it back on and all touch features will be up and running... and don't mess with the adoptable storage feature..migrating data.. because TWRP will not recognise any data if you have this enabled.
[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
You have to push the ing to and directory. Fastboot push img
Sent from my LG-K550 using Tapatalk
[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
Are you on the newest firmware for that phone?
If you are downgrade that could be a fix to lock down the recovery
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it? Usbhost mode..mount
Usb pendrive-
Mouse
Usb hub
Keyboard...etc
They say LG STYLO 2 PLUS DOES NOT SUPPORT OTG...LIES....LIES....THEY JUST DISABLED IT...WHY?...WELL..
FOLLOW THESE STEPS TO ENABLE FULL OTG SUPPORT
1-in root explorer go to:
-/sys/devices/soc/78db000.usb/power_supply/usb/usb_otg and edit from =0 to 1save
then-/sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit disabled to enable.. plug in otg cable..
Done
WoodEe23 said:
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it?
Click to expand...
Click to collapse
You enabled it by adding it to the build prop lol
Dig waaayyyy deeper ..like
/sys/devices/soc/78db000.usb/power_supply/usb/ scroll to usb_otg and edit it from disabled to enable.
Then /sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit it to enabled..
VOILA!!!"PLUGIN OTG CABLE AND UR IN THERE LIKE SWIMWEAR
Working On MM-WW-4.21.40.352 Z00A Z00AD And on Latest versions
MM-WW-4.21.40.327 Z00A Z00AD
MM-WW-4.21.40.223 Z00A Z00AD
Latest Stable Magisk : v16.3 Updated 28 March 2018. If there is update you will surely find it in telegram group. I don't visit xda much.
To download, Go to "Magisk" folder In download folder.
If you are using Magisk 12, Then first flash Magisk 12 uninstaller, then flash Latest Magisk from Twrp.
If Safetynet Fails, Then enable "Hide Magisk" in settings from magisk manager.Warning:
Rooting voids warranty. Also If some damage occurs because of wrong steps taken by you, Neither me nor forum is responsible. Do at your Own risk. Though I'm sure If you follow the steps carefully you wont get problem.
Prefer to backup your device apps and data.
First read the post twice carefully then proceed.
I may change name of files in folder. Use common sense to identify them.
If you want to flash stock rom then visit here Flash Stock Rom Zenfone 2
Features:
Magisk ManagerNEW
MagiskLatest Warning: Never update magisk from the app. Flash the latest zip from here, otherwise you will get bootloop.
Systemless Xposed
TWRP Latest
UnRoot (Magisk SuperUser only)
Requirements:
1. Phone should be charged at least 60%.
2. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
3. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
ALL .BAT FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2.
"
There are two parts which should be followed precisely.
1. Unlock Bootloader and Install TWRP.
2. Root and Install Xposed*
*=Though Xposed is not necessary but Xposed is very helpful, so its your choice.
Part 1: Unlock Bootloader and Install TWRP.
Step 1: Connect your phone to PC, make sure usb debugging is "ON".
Step 2: Go to the folder and run "Bootloader Unlocker.bat" .
Wait for command to execute.
When you see "Unlock Successful" in your phone, your phone will shut down. Then keep hold Volume Up button on your phone until you see bootloader again. Then follow the instructions. If You Missed it, the close the application. Boot your phone into fastboot mode and try again..
Step 3: If you are in fastboot/bootloader mode then use "TWRP.bat" otherwise first go to fastboot/bootloader mode and then use "TWRP.bat"
It will install twrp. When you first go to twrp. Tick Always allow modifications.
Part 2: Root and Install Xposed
Step 1: Boot to fastboot mode.
Step 2: For rooting. First use "ROOT UNROOT MAGISK.bat", follow any given instruction in script.
Step 3: If you want Xposed, then use "XPOSED.bat" in fastboot mode and follow any instruction in script.
Step 4: Reboot to system.
Your phone may optimize for 5-10 minutes depending upon number of apps Installed.
YOUR PHONE SHOULD BE ROOTED NOW.
Unroot
Step 1: Boot to fastboot mode.
Step 2: For unrooting. First use "ROOT UNROOT MAGISK.bat", follow any given instruction in script for unroot.
For Any querry or doubt please ask.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
https://telegram.me/joinchat/ESGRD0Erde3o4dRPSzkBCQ
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode.
b) If you can go to recovery mode then you can go to previous state(before starting unlocking) by using adb command
First boot to recovery(it should be the stock one), you'll see dead android logo, keep pressing power -then vol up-then release vol up- now release power. (This should be quick, otherwise pressing power button for too long will shut you down)
When successfull, you'll see options, choose apply update from adb, and follow command
Code:
adb sideload mm.zip
You must rename the downloaded zip to mm.zip . Or you can replace mm.zip to xxxxxxxxxxx.zip (whatever the name of downloaded zip)
Warning Before that you must download same version full firmware from asus website Here
2. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
3. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
4. Want to relock bootloader?
Sol. No possible way for now. The post will be updated if it ever comes.
5. Safetynet Failed?
Sol. 1. Have you enabled Magisk Hide in the settings of Magisk Manager? Try toggle to disable, and re-enable again.
2. If you are using SuperSU, you often need suhide, or maybe other solutions. Developer do not have control of how SuperSU behaves.
3. It might be due to xposed. Either you remove xposed or wait for future updates.
Download files from here
https://www.androidfilehost.com/?w=files&flid=273540 AFH Link
All Files in folder are not useful for this purpose, but are used for other purpose also. You can download them if you want.
File credits.
Giovix92
topjohnwu
Some tools are not made by me. This guide is genuine based on my experience.
Generous Donor(s):
1. Peter Fedorow (20 Canadian Dollar):good:
2. Nicola Roncari (20 Euro):good:
Hi, warranty will be void? Or still usable?
Hi, in the 5th step, installing twrp does not seem to work and my computer cannot find my device (using adb devices computer cannot find the phone)
flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15316 KB)...
OKAY 0.686s
writing 'recovery'...
FAILED (remote: Permission denied)
finished. total time: 0.849s
---------- Post added at 11:11 PM ---------- Previous post was at 11:00 PM ----------
aguywithaname said:
Hi, in the 5th step, installing twrp does not seem to work and my computer cannot find my device (using adb devices computer cannot find the phone)
flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15316 KB)...
OKAY 0.686s
writing 'recovery'...
FAILED (remote: Permission denied)
finished. total time: 0.849s
Click to expand...
Click to collapse
Ah nevermind I found the solution to the problem. From bootloader mode all I had to do was boot into recovery and then I got into twrp. Thanks anyway.
Hi it's me again. Why do I lose root after I reboot/restart my phone?
You bricked your phones 3 times, i also bricked mine can you tell me how to unbrick?? @Kapil Tapsi
biondo_92 said:
Hi, warranty will be void? Or still usable?
Click to expand...
Click to collapse
No. But if you unlock by this method you can get your warranty by flashing clean marshmallow or lollipop.
aguywithaname said:
Hi, in the 5th step, installing twrp does not seem to work and my computer cannot find my device (using adb devices computer cannot find the phone)
flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15316 KB)...
OKAY 0.686s
writing 'recovery'...
FAILED (remote: Permission denied)
finished. total time: 0.849s
---------- Post added at 11:11 PM ---------- Previous post was at 11:00 PM ----------
Ah nevermind I found the solution to the problem. From bootloader mode all I had to do was boot into recovery and then I got into twrp. Thanks anyway.
Click to expand...
Click to collapse
Thanks. Permission denied to write means bootloader is still locked
aguywithaname said:
Hi it's me again. Why do I lose root after I reboot/restart my phone?
Click to expand...
Click to collapse
If you successfully followed these steps then root will persist. Check your steps. I've done this in 3 phones successfully.
ayush.gl said:
You bricked your phones 3 times, i also bricked mine can you tell me how to unbrick?? @Kapil Tapsi
Click to expand...
Click to collapse
Yes, But before that I need to know some things.
1. Your phone can be powered on(meaningless but still want to know.)
2. Can you reach bootloader.? I.e. fastboot mode.
3. Or you cannot see any bootloader while pressing volume + and power, but your phone is only showing asus logo.
Is there any way to access TWRP recovery after all is said and done? When ever I try to go into recovery via fastboot, it just takes me back to fastboot again.
shaza98 said:
Is there any way to access TWRP recovery after all is said and done? When ever I try to go into recovery via fastboot, it just takes me back to fastboot again.
Click to expand...
Click to collapse
Yes but you have to unlock bootloader again using unlock.bat and go to recovery menu flash whatever you want, reboot to bootloader again and run restore.bat.
Working guide as of 9/8/2016
Kapil Tapsi said:
I've been trying to root my Asus Zenfone 2 since the day Marshmallow Launched for it.
I bricked my phone 3 times. And finally I found true working process. I thought to share with you mates.Rooting voids warranty. Also If some damage occurs because of wrong steps taken by you, Neither me nor forum is responsible. Do at your Own risk. Though Im sure If you follow the steps carefully you wont get problem.
Prefer to backup your device apps and data.
First read the post twice carefully then proceed.
There are two process which should be followed precisely.
1. Temporarily Unlock Bootloader.
2. Root and Install Xposed Installer*
*=Though Xposed is not necessary but Xposed is very helpful, so its your choice.
Download all Files given below
Step 1: Enable Usb Debugging
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it says
"You are a developer now". Connect phone to your computer via usb (Make sure you have Installed android drivers in your Pc, If not install pda.net from Here)
Step 2: Copy "Magisk-v6_repack_for_zf2_601.zip","phh-superuser-17-magisk-x86-fix.zip" and "xposed-v86.5-sdk23-topjohnwu_repack_for_zf2_601.zip" to your Internal Memory.
Step 3: Extract "unlock_for_zf2_551ml_6.0_20160703.zip" to your desktop. And run "Unlock.bat". It will restart your device to bootloader and install , and again reboot. Now it will struck at Asus logo with white background.
Step 4: Force Shutdown your phone by pressing power button for 10 seconds. Then start it into bootloader mode by pressing "Vol+"and "Power" buttons simultaneously. When it vibrates leave power button only(keep pressing "Vol+" until you see bootloader mode)
Step 5: Install twrp recovery from fastboot mode (google it if you dont know)
command " fastboot flash recovery twrp.img "
twrp is provided.
after successfull execution of command go to recovery mode by pressing down button on bootloader mode and allow modifications for twrp.
Step6: In TWRP, goto "Install" and browse three files which you copied to Internal Memory, And flash them In same order Which I say
"Magisk-v6_repack_for_zf2_601.zip"
"phh-superuser-17-magisk-x86-fix.zip"
"xposed-v86.5-sdk23-topjohnwu_repack_for_zf2_601.zip"
tap soft button for "Back" and tap "Reboot" And choose "Bootloader"
Step7: When in bootloader mode. Go back to your PC and double click "Restore.bat".
It will again lock your Bootloader(As it is necessary for your phone to boot) and reboot your phone. Your phone will optimize for 5-10 minutes depending upon number of apps Installed.
Step8: Install 3 Apps for accessing root and xposed given in folder.
named: Magisk manager apk
phh super user apk
xposed apk
YOUR PHONE IS ROOTED NOW.
Thanks.
For Any querry or doubt please ask.
Every Suggestion welcomed
Download files from here
https://drive.google.com/open?id=0B6SZRpR9Q7C5RzFDMUx0bFkycEE
Click to expand...
Click to collapse
I seriously thank you for this guide. I have been spending the last 12 hours looking for a working guide; though other guides were correct, it's your guide that lead me right to where I should be. I've completed the guide without problems.:good::highfive::good:
dhogthag said:
I seriously thank you for this guide. I have been spending the last 12 hours looking for a working guide; though other guides were correct, it's your guide that lead me right to where I should be. I've completed the guide without problems.:good::highfive::good:
Click to expand...
Click to collapse
Thanks. When I got my phone rooted after 3 times brick. I thought to help, so no one face problem.
Help others reach this post. And give me suggestion if any.
Kapil Tapsi said:
Thanks. Permission denied to write means bootloader is still locked
Click to expand...
Click to collapse
It can also mean you forgot to disable your lockscreen.
Sent from my ASUS_Z00AD using XDA Premium HD app
is there a way without unlocking bootloader first?
I was wondering with the TWRP provided in this root process, can we install a custom ROM with it? If so, can you provide any steps? (I want CyanogenMod)
I am totally confused, every time, the phone rebooted, it rolled back to unroot...
I had already followed any single instruction, as stated in this thread.
tm_muri said:
I am totally confused, every time, the phone rebooted, it rolled back to unroot...
I had already followed any single instruction, as stated in this thread.
Click to expand...
Click to collapse
Mine does the same.[emoji19]
Sent from my ASUS_Z00AD using XDA-Developers mobile app
any chance you guys didn't unlocked bootloader before upgrading to MM from LP
Thank you very much! I'm a rooted Zenfone owner.
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