Related
I am S OFF, UNLOCKED.
When I boot into bootloader and into fastbootmode, as soon as i connect the cable to my phone, the fastboot USB mode freezez... No keys work that time...I have to press and hold power button for a few seconds in order to reboot the phone. This happen always with me.
I wanted to backup my Stock recovery by booting into custom recovery using this command fastboot boot name_of_your_custom_recovery.img . It sends the recovery and everything is okay on the PC, but nothing happens on the phone.
But I did flash the unlock.bin via fastboot, that way it works....I am not getting what the problem is.
I need to backup my STOCK RECOVERY (HTC CID_J15) before flashing CWM.
ANy help would be appreciated.
mathrania said:
I am S OFF, UNLOCKED.
When I boot into bootloader and into fastbootmode, as soon as i connect the cable to my phone, the fastboot USB mode freezez... No keys work that time...I have to press and hold power button for a few seconds in order to reboot the phone. This happen always with me.
I wanted to backup my Stock recovery by booting into custom recovery using this command fastboot boot name_of_your_custom_recovery.img . It sends the recovery and everything is okay on the PC, but nothing happens on the phone.
But I did flash the unlock.bin via fastboot, that way it works....I am not getting what the problem is.
I need to backup my STOCK RECOVERY (HTC CID_J15) before flashing CWM.
ANy help would be appreciated.
Click to expand...
Click to collapse
Not sure about your fastboot issue, but just an FYI if you have upgraded your firmware and now have hboot 1.54 you can no longer use the command
Code:
fastboot boot name_of_your_custom_recovery.img
to boot to a non installed recovery. That can only be done with the older 1.44 hboot.
Since you have s-off, if you can get fastboot working, you should be able to flash hboot 1.44 if you the need the ability to boot a non installed recovery.
crushalot said:
Not sure about your fastboot issue, but just an FYI if you have upgraded your firmware and now have hboot 1.54 you can no longer use the command
Code:
fastboot boot name_of_your_custom_recovery.img
to boot to a non installed recovery. That can only be done with the older 1.44 hboot.
Since you have s-off, if you can get fastboot working, you should be able to flash hboot 1.44 if you the need the ability to boot a non installed recovery.
Click to expand...
Click to collapse
Yes, hboot 1.54....so how do i ensure i have stock recovery backup before flashing CWM?
Sent from my HTC One using xda premium
mathrania said:
Yes, hboot 1.54....so how do i ensure i have stock recovery backup before flashing CWM?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Could go a few different routes. First there are tons of users who posted the stock recovery on XDA and other sites. Also it could be pulled from the RUU if you device has one or one of the posted nandroid backups. (http://forum.xda-developers.com/showthread.php?p=39588860)
This site has the original retail dump which has the stock recovery:
http://www.modaco.com/topic/361407-htc-one-retail-release-dump/
You have s-off, so you can downgrade back to hboot 1.44 and boot a custom recovery. Just flash the stock 1.44 hboot from here:
http://forum.xda-developers.com/showthread.php?t=2316726
When finished you can leave hboot 1.44 or flash back up to 1.54.
Lastly if you have root you can look around (Will have to search) for how to pull the recovery.img like a system dump.
Best of luck.
crushalot said:
Could go a few different routes. First there are tons of users who posted the stock recovery on XDA and other sites. Also it could be pulled from the RUU if you device has one or one of the posted nandroid backups. (http://forum.xda-developers.com/showthread.php?p=39588860)
This site has the original retail dump which has the stock recovery:
http://www.modaco.com/topic/361407-htc-one-retail-release-dump/
You have s-off, so you can downgrade back to hboot 1.44 and boot a custom recovery. Just flash the stock 1.44 hboot from here:
http://forum.xda-developers.com/showthread.php?t=2316726
When finished you can leave hboot 1.44 or flash back up to 1.54.
Lastly if you have root you can look around (Will have to search) for how to pull the recovery.img like a system dump.
Best of luck.
Click to expand...
Click to collapse
Is the stock recovery same for all HtC One?? I mean also the 1.29.x.x and 2.24.x.x are same too?
Sent from my HTC One using xda premium
mathrania said:
Is the stock recovery same for all HtC One?? I mean also the 1.29.x.x and 2.24.x.x are same too?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
No there are differences for some of the different models and carriers. You will have to match your CID to one of the nandroids or find the proper RUU.
The stock recovery was updated in 2.24 I think, but I am not positive since I didn't ever use it.
It will only take a few minutes to flash the hboot to 1.44 so that you can boot a recovery and take a backup for yourself. I would recommend that method.
crushalot said:
No there are differences for some of the different models and carriers. You will have to match your CID to one of the nandroids or find the proper RUU.
The stock recovery was updated in 2.24 I think, but I am not positive since I didn't ever use it.
It will only take a few minutes to flash the hboot to 1.44 so that you can boot a recovery and take a backup for yourself. I would recommend that method.
Click to expand...
Click to collapse
Yes, but i am afraid to do it.... Might brick my phone....
Sent from my HTC One using xda premium
mathrania said:
Yes, but i am afraid to do it.... Might brick my phone....
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Um, not sure where your getting that but just flashing stock hboots will not brick your phone. I have switched my hboot around between like 4 different versions 10+ times to test some things after the firmware upgrades.
Even the modified one are no problem.
Oh well. Good luck.
I know, two very bad mistakes. I was excited. First thing I did wrong was install a GE kernel when I should have installed a sense one..then I used fast boot to write TWRP to my boot image by accident instead of recovery. I tried to update RUU using fastboot, but I keep getting errors. I cant mount my internal storage, can't side load either.
Whenever I reboot, I boot into TWRP instead of system now. I probably have to restore, but not being able to RUU or side load, I dont know what to do. Please help!
j2sun said:
I know, two very bad mistakes. I was excited. First thing I did wrong was install a GE kernel when I should have installed a sense one..then I used fast boot to write TWRP to my boot image by accident instead of recovery. I tried to update RUU using fastboot, but I keep getting errors. I cant mount my internal storage, can't side load either.
Whenever I reboot, I boot into TWRP instead of system now. I probably have to restore, but not being able to RUU or side load, I dont know what to do. Please help!
Click to expand...
Click to collapse
Just boot into fastboot and flash a new boot.img which matches your ROM
Thanks! But where do I get a boot.img file? I tried looking but couldn't find one. I could just find ZIP ROMs and RUUs
j2sun said:
Thanks! But where do I get a boot.img file? I tried looking but couldn't find one. I could just find ZIP ROMs and RUUs
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/showthread.php?t=2316726
Choose the 2.24 firmware file, this one which includes the kernel
https://mega.co.nz/#!iVJEWLBD!T3fwwlKNRTq_f1ls50jicDMQ5ysOG_Y6iMhO78zwrSA
Extract boot.img, flash it, then reflash TWRP correctly also
EddyOS said:
Just boot into fastboot and flash a new boot.img which matches your ROM
Click to expand...
Click to collapse
dgtiii said:
Go here http://forum.xda-developers.com/showthread.php?t=2316726
Choose the 2.24 firmware file, this one which includes the kernel
https://mega.co.nz/#!iVJEWLBD!T3fwwlKNRTq_f1ls50jicDMQ5ysOG_Y6iMhO78zwrSA
Extract boot.img, flash it, then reflash TWRP correctly also
Click to expand...
Click to collapse
Thanks a lot!
Is this the boot.img that I should flash:
hboot_signedbyaa.img
Also, after that, should I RUU?
Thanks!
j2sun said:
Thanks a lot!
Is this the boot.img that I should flash:
hboot_signedbyaa.img
Also, after that, should I RUU?
Thanks!
Click to expand...
Click to collapse
Yes. You also should flash stock recovery before you flash the RUU, just to make sure everything goes right.
kibmikey1 said:
Yes. You also should flash stock recovery before you flash the RUU, just to make sure everything goes right.
Click to expand...
Click to collapse
The RUU flashes the stock recovery so you don't need this. You don't even need the boot.img if you're going to flash an RUU. Just connect the phone in fastboot mode and then run the RUU. So long as you're S-OFF it should run fine
Your phone doesn't need a kernel to boot to recovery or fastboot, recovery has its own kernel built in... Just goto fastboot and flash a new boot.img
Fastboot flash boot boot.img
Hboot_signedbyaa.img isn't a boot.img it's a hboot
Sent from my One using xda app-developers app
how did a do that?
EddyOS said:
The RUU flashes the stock recovery so you don't need this. You don't even need the boot.img if you're going to flash an RUU. Just connect the phone in fastboot mode and then run the RUU. So long as you're S-OFF it should run fine
Click to expand...
Click to collapse
Hi mate, in your signature I red OS 2.24.4018 / HBoot 1.54.0000 and now "tadaaaa" S-OFF and so on.
How did you do that? I've damaged my brain and gnawn down my nails but nothing works ....
Have you installed the 1.54.0000 on top of the 1.44.0000 (unlocked + S-OFF) and your HBOOT is still unlocked and S-OFF?
Or are u using the black&beauty ONE?
Then ou are a lucky man I guess.
God bless you.
I was S-OFF on 1.44 and then did the OTA so I kept S-OFF - sorry to get your hopes up!
EddyOS said:
I was S-OFF on 1.44 and then did the OTA so I kept S-OFF - sorry to get your hopes up!
Click to expand...
Click to collapse
EddyOS said:
The RUU flashes the stock recovery so you don't need this. You don't even need the boot.img if you're going to flash an RUU. Just connect the phone in fastboot mode and then run the RUU. So long as you're S-OFF it should run fine
Click to expand...
Click to collapse
Uhm...I don't have S-OFF. I tried pushing it in recovery , but when I do ./revone -P but I'm stuck with error code = 1
j2sun said:
Uhm...I don't have S-OFF. I tried pushing it in recovery , but when I do ./revone -P but I'm stuck with error code = 1
Click to expand...
Click to collapse
I know, I was replying to another post in this thread...
EddyOS said:
I was S-OFF on 1.44 and then did the OTA so I kept S-OFF - sorry to get your hopes up!
Click to expand...
Click to collapse
Oh yeah, I got it. I decided to buy a new ONE and wait for the exploid to fix my device. Then I'll give it to my wife. I know she will be happy about this....
Sent from my HTC Sensation XE with Beats Audio using XDA Premium 4 mobile app
Hi There,
I searched the threads available to the best of my ability, but im not sure exactly what im looking for. Purchased an HTC one used, flashed with cyanogenmod 10.2. When I tried to update it to 11, it soft bricked (im assuming) as it cant get past the recovery mode. I factory wiped it, in my ignorance thinking this would be able to fix the issue, boot up the stock rom. This cleared the OS so I was more stuck then I previously was.
I figured out how to push roms onto it, and I got the new android revolution rom on there, and when i install it, it says its successful as it goes through all the rom specific steps, but when it system reboots it goes back into this loop.
Are there any suggestions to get out of this? Should i somehow flash the latest RUU?
Thanks a lot I appreciate any help
bronsonb said:
Hi There,
I searched the threads available to the best of my ability, but im not sure exactly what im looking for. Purchased an HTC one used, flashed with cyanogenmod 10.2. When I tried to update it to 11, it soft bricked (im assuming) as it cant get past the recovery mode. I factory wiped it, in my ignorance thinking this would be able to fix the issue, boot up the stock rom. This cleared the OS so I was more stuck then I previously was.
I figured out how to push roms onto it, and I got the new android revolution rom on there, and when i install it, it says its successful as it goes through all the rom specific steps, but when it system reboots it goes back into this loop.
Are there any suggestions to get out of this? Should i somehow flash the latest RUU?
Thanks a lot I appreciate any help
Click to expand...
Click to collapse
what recovery are you using? what version?
also post a fastboot getvar all wihout imei/sn
alray said:
what recovery are you using? what version?
also post a fastboot getvar all wihout imei/sn
Click to expand...
Click to collapse
Im using TWRP 2.5.0.0, and im trying to run the fastboot getvar but its stuck on <waiting for device> ill post an update if that changes, thank you for your response!
bronsonb said:
Im using TWRP 2.5.0.0, and im trying to run the fastboot getvar but its stuck on <waiting for device> ill post an update if that changes, thank you for your response!
Click to expand...
Click to collapse
You must use latest twrp version to flash arhd rom! 2.5.0.0 is very outdated.
Are you using a windows 8.1 computer? If yes then you miht have issue with fastboot.
and make sur your phone variant is M7_U or M7_UL in bootloader screen. (not a sprint version M7wls)
What is the hboot version in bootloader screen?
from the OP of arhd thread:
Android Revolution HD 51.0
--- MD5 Checksum: 1F9253A64D5B0A0566C8B40EC809D05F ---
You need TRWP 2.6.3.3 recovery!
Flashing KitKat F.A.Q. - click here
Click to expand...
Click to collapse
alray said:
You must use latest twrp version to flash arhd rom! 2.5.0.0 is very outdated.
Are you using a windows 8.1 computer? If yes then you miht have issue with fastboot.
and make sur your phone variant is M7_U or M7_UL in bootloader screen. (not a sprint version M7wls)
What is the hboot version in bootloader screen?
Click to expand...
Click to collapse
I had no idea, Ill figure out how to do that right away I really appreciate that.
Im using a mac actually, so i understand everything isnt really made to work with it, though i can use parallels windows 7 if necessary
it shows:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT - 1.44.0000
bronsonb said:
I had no idea, Ill figure out how to do that right away I really appreciate that.
Im using a mac actually, so i understand everything isnt really made to work with it, though i can use parallels windows 7 if necessary
it shows:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT - 1.44.0000
Click to expand...
Click to collapse
ok so flash twrp 2.6.3.3 and reflash your rom.
Code:
./fastboot flash recovery <name_of_file>.img
./fastboot erase cache
./fastboot reboot-bootloader
then flash arhd again.
alray said:
ok so flash twrp 2.6.3.3 and reflash your rom.
Code:
./fastboot flash recovery <name_of_file>.img
./fastboot erase cache
./fastboot reboot-bootloader
then flash arhd again.
Click to expand...
Click to collapse
is there a line of code to flash the rom through fastboot, rather then rebooting recovery and installing it?
bronsonb said:
is there a line of code to flash the rom through fastboot, rather then rebooting recovery and installing it?
Click to expand...
Click to collapse
No, you'll need a custom recovery to flash a rom.
or
Use a ruu to restore back to 100% stock but you will need to post a ''fastboot getvar all'' to determine if this is possible.
What is going wrong?
You can also post screenshots of you terminal window when you get errors.
alray said:
No, you'll need a custom recovery to flash a rom.
or
Use a ruu to restore back to 100% stock but you will need to post a ''fastboot getvar all'' to determine if this is possible.
What is going wrong?
You can also post screenshots of you terminal window when you get errors.
Click to expand...
Click to collapse
Actually, I just installed it through the newly flashed recovery and it worked perfectly (Android Revolution)
Thank you so much! Saved me a lot of time
bronsonb said:
Actually, I just installed it through the newly flashed recovery and it worked perfectly (Android Revolution)
Thank you so much! Saved me a lot of time
Click to expand...
Click to collapse
np
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
KoalaSuccess said:
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
Click to expand...
Click to collapse
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
7ftnick said:
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
Click to expand...
Click to collapse
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
KoalaSuccess said:
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
Click to expand...
Click to collapse
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
I took a look and I'll try it! Do you know if my device is Bell? I'm not sure how to tell.
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
KoalaSuccess said:
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
Click to expand...
Click to collapse
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
alray said:
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
Click to expand...
Click to collapse
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
KoalaSuccess said:
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
Click to expand...
Click to collapse
well that is strange, you should have kept s-off and try other things first but well, its to late. At least your phone is working now
Hi guys i got an htc one in placw of my samsung grand
I managed to unlock the bootloader using cmd and tried flashing a recovery. However after the flash when i try booting into recovery mode from bootloader, it first gives the entering recovery screen but then screen blacks out and then it reboots as normal.
Now htc just got a lollipop update and i want to update, but when it enters recovery, it blacks out and then reboots as normal due to the fail recovery
Before i tried flashing each and every reocvery and the same happened... Then i just left it at a version of cwm ( didnt work also) .
Now shall i flash stock recovery? What if that dosent work? Is there any way to do it without a pc or any other computer?
arushawasthi said:
Hi guys i got an htc one in placw of my samsung grand
I managed to unlock the bootloader using cmd and tried flashing a recovery. However after the flash when i try booting into recovery mode from bootloader, it first gives the entering recovery screen but then screen blacks out and then it reboots as normal.
Now htc just got a lollipop update and i want to update, but when it enters recovery, it blacks out and then reboots as normal due to the fail recovery
Before i tried flashing each and every reocvery and the same happened... Then i just left it at a version of cwm ( didnt work also) .
Now shall i flash stock recovery? What if that dosent work? Is there any way to do it without a pc or any other computer?
Click to expand...
Click to collapse
no .. you will need a PC to restore stock recovery / or RUU back to stock
Darn
clsA said:
no .. you will need a PC to restore stock recovery / or RUU back to stock
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
I tried RUU, turns out theres no file for my cid (HTC_039).
I also tried alternate methods, turns out i cant use Guru reset as i need functioning recovery, and i have S-ON so no Nand.
pl help.
arushawasthi said:
Hi,
Thanks for the reply.
I tried RUU, turns out theres no file for my cid (HTC_039).
I also tried alternate methods, turns out i cant use Guru reset as i need functioning recovery, and i have S-ON so no Nand.
pl help.
Click to expand...
Click to collapse
Did you use the correct version of the recovery you flashed? I mean are you sure it wasn't a Sprint or Verizon recovery?
Secondly did you fastboot erase cache after flashing recovery?. This is the no.1 reason for recovery bootloop. Flashing recovery should be done like so.
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
Then select recovery from the bootloader for the first time load.
Sent from my M7 ARHD 84-Kitkat
arushawasthi said:
I tried RUU, turns out theres no file for my cid (HTC_039).
Click to expand...
Click to collapse
Yes there is one. 7.19.980.5 posted in the general section
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
see post #2.
If your phone is already on a 6.xx.980.x or 7.xx.980.x firmware you can flash it.
Danny201281 said:
Did you use the correct version of the recovery you flashed? I mean are you sure it wasn't a Sprint or Verizon recovery?
Secondly did you fastboot erase cache after flashing recovery?. This is the no.1 reason for recovery bootloop. Flashing recovery should be done like so.
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
Then select recovery from the bootloader for the first time load.
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Hi,
i didnt do the exact thing. Ill try like you said.
And how do i find out my firmware version? In settings?
arushawasthi said:
Hi,
i didnt do the exact thing. Ill try like you said.
And how do i find out my firmware version? In settings?
Click to expand...
Click to collapse
To find your firmware version it's best to use command
Code:
fastboot getvar all
this will show you a list of your devices version information.
You can post the list here if you need help but please remove your imei and serial number before posting for your own security.
There are 3 models of HTC One.
Sprint = m7_wls Downloads here http://techerrata.com/browse/twrp2/m7wls
Verizion = m7_vzw Downloads here http://techerrata.com/browse/twrp2/m7vzw
International = m7_ul or m7_u Downloads here http://techerrata.com/browse/twrp2/m7
There are also more model numbers for dual sim variants.
You must have the correct version of recovery depending on your model. The getvar info would be very helpful for me to make a recommendation :good:
Sent from my SM-T230 using Tapatalk