Related
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
MrFixit007 said:
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Click to expand...
Click to collapse
Pm me your teamviewer information and I'll help you out.
bigdaddy619 said:
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
Click to expand...
Click to collapse
I am on 1.31. I have tried running the RUU from my PC and I got error 140. I tried looking that up and could not find any solutions to that. I figured it was because I am on 1.31 and not 1.29 and I still had s-on. That is when I tried to get s-off so that I could apply the 1.29. Is it possible to open a fastboot shell? I was going to try to push the revone files to the phone via fastboot and then run the commands via fastboot, but didn't get around to trying that out last night.
Indirect said:
Pm me your teamviewer information and I'll help you out.
Click to expand...
Click to collapse
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
MrFixit007 said:
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
Click to expand...
Click to collapse
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
What do you want to know?
Sent from?
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
im0rtalz said:
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
Click to expand...
Click to collapse
bigdaddy619 said:
What do you want to know?
Sent from?
Click to expand...
Click to collapse
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
MrFixit007 said:
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
Click to expand...
Click to collapse
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
bigdaddy619 said:
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
Click to expand...
Click to collapse
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
MrFixit007 said:
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
Click to expand...
Click to collapse
Check PM
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect is a beast
bigdaddy619 said:
Indirect is a beast
Click to expand...
Click to collapse
yep! Indirect and bigdaddy are both beasts!
theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect and bigdaddy have both helped me out bunches tonight!!! I am completely back in action!!
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
Probably downgraded him from 1.31 to 1.29 so he could RUU
Sent from?
NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
MrFixit007 said:
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
Click to expand...
Click to collapse
I got him fixed up
Hi guys,
I hope you can help me. Sorry if this has been covered somewhere, I tried looking for an answer but nothing has worked so far.
I can get into recovery or hboot but thats all. Phone is not recognised by WIN 8.1. Tried installing drivers and HTC SYNC, still no luck. It's driving me crazy. PLEASE HELP!
Thanks
First of all what did you try and do that has lead you to this? Are you s-off? Is your boot loader unlocked or locked?
Sent from my HTC One using xda app-developers app
stovie_steve said:
First of all what did you try and do that has lead you to this? Are you s-off? Is your boot loader unlocked or locked?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks for quick reply.
I am s-off and unlocked.
I was trying to reinstall because my camera was constantly out of focus. and i read that it maybe a bug since 4.2. So the install failed and then i formated system and whatever I tried since, nothing has worked. Tried all kind of drivers etc. still nothing
silesrap said:
Hi, thanks for quick reply.
I am s-off and unlocked.
I was trying to reinstall because my camera was constantly out of focus. and i read that it maybe a bug since 4.2. So the install failed and then i formated system and whatever I tried since, nothing has worked. Tried all kind of drivers etc. still nothing
Click to expand...
Click to collapse
read FAQ 1 and 5 from here
http://forum.xda-developers.com/showthread.php?t=2541082
bored_stupid said:
read FAQ 1 and 5 from here
http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
OMG!!!!!!!! You are a GENIUS
I installed windows 7 on a different drive and flashed RUU.zip again without any problems.
I was already looking to get a new phone
Thanks again!
silesrap said:
OMG!!!!!!!! You are a GENIUS
I installed windows 7 on a different drive and flashed RUU.zip again without any problems.
I was already looking to get a new phone
Thanks again!
Click to expand...
Click to collapse
Your welcome
stuck
hlo sir,I m really depressed these days bcz I can't find ruu for my htc one as it shows TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp meee....suggest me the perfect ruu
jaspreet4140 said:
hlo sir,I m really depressed these days bcz I can't find ruu for my htc one as it shows TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp meee....suggest me the perfect ruu
Click to expand...
Click to collapse
Unlock your bootloader and try the Guru reset again..
stuck
thx for replyi g sir, but when I try to give command 'fastboot oem get_indentifier_token' it says command error
jaspreet4140 said:
thx for replyi g sir, but when I try to give command 'fastboot oem get_indentifier_token' it says command error
Click to expand...
Click to collapse
Have you still got the identifier token given to you when you first unlocked the phone,
Also check that its not a typographical error on your part.
Sent from my Nexus 7 using XDA Premium HD app
stuck
at first I unlocked using kingo unlock bootloader...so I m not having any bin fioe of token..........and I don't have android sdk does it matter in any way...
jaspreet4140 said:
at first I unlocked using kingo unlock bootloader...so I m not having any bin fioe of token..........and I don't have android sdk does it matter in any way...
Click to expand...
Click to collapse
You really need fastboot and adb.
Download the minimal files from here
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/preview
Create a folder on your desktop and put the files there.
Sent from my Nexus 7 using XDA Premium 4 mobile app
jaspreet4140 said:
thx for replyi g sir, but when I try to give command 'fastboot oem get_indentifier_token' it says command error
Click to expand...
Click to collapse
bored_stupid said:
Have you still got the identifier token given to you when you first unlocked the phone,
Also check that its not a typographical error on your part.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
@jaspreet4140 please keep in one thread so either this thread or http://forum.xda-developers.com/showthread.php?t=2724479&page=2 whichever you prefer, but not both. thanks.
(not to mention the third one, but nobody replied there anyway)
re
extremly sorry sir for wrong posting........I m new here.......thx for providing informaion....
btw I unlocked my bootloader ....
another problem is now when I on phone it directly goes into clockworld recovery....bcz I flashed it before .......help me to fix it.....
jaspreet4140 said:
extremly sorry sir for wrong posting........I m new here.......thx for providing informaion....
btw I unlocked my bootloader ....
another problem is now when I on phone it directly goes into clockworld recovery....bcz I flashed it before .......help me to fix it.....
Click to expand...
Click to collapse
no problem, i was just pointing out that we can't follow your progress if there are multiple posts around.
So now you are able to go to CWM recovery? then just flash the Guru Reset ROM mentioned earlier (can't remember if it was in this thread or the other), and select stock recovery in the installer so you can receive OTAs.
---------- Post added at 07:56 PM ---------- Previous post was at 07:42 PM ----------
jaspreet4140 said:
extremly sorry sir for wrong posting........I m new here.......thx for providing informaion....
btw I unlocked my bootloader ....
another problem is now when I on phone it directly goes into clockworld recovery....bcz I flashed it before .......help me to fix it.....
Click to expand...
Click to collapse
now this: http://forum.xda-developers.com/showthread.php?t=2723504&page=4 is just plain rude!!
EDIT: @jaspreet4140 : I recommend you open your own thread, and start posting the information necessary, such as fastboot getvar all (excluding IMEI and s/n), and everything else that is of relevance, including what you want to achieve.
sry
last time soryyy...now I will only talk to u.......promise......
ya guru reset is my 2nd option...I was thinking of deleting cwm recovery can u tell me how.....or chnging recovery to twrp can solve this problem.............
jaspreet4140 said:
last time soryyy...now I will only talk to u.......promise......
ya guru reset is my 2nd option...I was thinking of deleting cwm recovery can u tell me how.....or chnging recovery to twrp can solve this problem.............
Click to expand...
Click to collapse
you're not understanding my point, you're randomly posting onto different threads which may or may not have the same problem (i'm leaning towards not the same problem)
and i'm not the only one you should be "talking to", both @alray and @bored_stupid have already been helping you, but you can't expect everybody to always be online. we all are in different timezones, and may have other things to do to; for example i have to sign off for a while...
So my recommendation is: open a new thread in Q&A with all the necessary information, and we'll try to help.
xda is a community, it's not about one person, it's about the group... and there are many friendly people here trying to help each other out :good:
http://i.imgur.com/GDZHuuG.png
Can anybody help me too please?
I bought the phone, only to found out it has a crackling top speaker AFTER unlocking bootloader, rooting, custom recovery and custom rom, s-off, removing the 'tampered' status etc...
should I RUU now? (I think I should because I have a custom rom on it)
Been reading all day... very confusing lol..
okkkk...... I will make it tomorrow morning........but tell me how to delete cwm recovery to slove this prob..
MasterThiefGarrett said:
http://i.imgur.com/GDZHuuG.png
Can anybody help me too please?
I bought the phone, only to found out it has a crackling top speaker AFTER unlocking bootloader, rooting, custom recovery and custom rom, s-off, removing the 'tampered' status etc...
should I RUU now? (I think I should because I have a custom rom on it)
Been reading all day... very confusing lol..
Click to expand...
Click to collapse
use my guide (RUU.ZIP method)
with this ruu.zip: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
please read it carefully, and if you have questions post there.
jaspreet4140 said:
okkkk...... I will make it tomorrow morning........but tell me how to delete cwm recovery to slove this prob..
Click to expand...
Click to collapse
it will be gone once you flash the Guru Reset ROM (Guru Reset ROM includes stock recovery)... you cannot "delete" a recovery, only replace it.
Hello,
I am new to xda forum and expecting a helping hand from fellow members, here's the scenario, I have a sprint htc one which was working fine a few days ago before i decided to act smart .
It was rooted when i purchased it so i thought of flashing a new custom rom into it.I tried flashing (HTC_One_-_MaximusHD_53.0.0) and this one (NuSenSeveN-LP-m7-Sprint_v4.02_050715) and ended up being stuck at green HTC logo, even though the physical buttons are performing their respective functions when pressed but the screen shows just the htc one logo and nothing else.
It is unlocked, tampered and s-on and i have twrp recovery on board, hboot 1.57.0000
WHAT I HAVE ALREADY TRIED AND FAILED:
1) tried rum runner to turn s-off because i though may b because of s-on the roms are not being flashed properly but it says adb device not found
2) tried flashing Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0 but stuck at handsfree activation, even though i deleted htcwizard.apk.
Now the bottom line is, I am unable to use my device and in desperate need of your help.
Please respond, awaiting to put my hand back on the device.
Thank You
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Sloth said:
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Click to expand...
Click to collapse
Hey thanks for the response, I am not tech geek so I have no idea how to flash the latest RUU can you please be more specific about how to perform the above mentioned process or can you have a chat on hangouts as I have altready added you on it.
Thanks alot
Try to flash ruu which could be found on other posts do u know how to boot into the bootloader?
problem solved
Update: thanks to @Sloth I have fixed the problem, if anyone out there who owns a sprint htc one and have messed up his phone by flashing an incompatible rom the way i did, first relock your bootloader if you are s-on and then simply download RUU file from htc official website, make sure its for sprint variant.
Once the bootloader is relocked simply run ruu.exe file that you have downloaded and you are done.
Note: if the ruu setup says that you phone is not connected or gets stuck, boot into recovery and perform factory, after that re-try running ruu.
Thanks Sloth, and thanks xda members
Just purchased a second hand HTC One (M8).
Turned out to be a CDMA variant, bootloader shows M8_WHL, which is the Sprint variant.
When I got the device, it had a locked bootloader but was S-OFF with SuperCID (11111111) and running stock ROM.
I rooted it, by unlocking the bootloader and flashing TWRP.
After this, I handed it over to my friend, whom I forgot to tell that it was a CDMA variant, so he treated it as a GSM one.
He didn't notice the M8_WHL part and changed the MID to 0P6B1000 and left the CID as is, downloaded 6.12.401.1 (which is the MM ROM for International M8), flashed the RUU.zip and tried to boot the phone.
Phone will not boot now, if one types the reboot command, it just goes back to Bootloader.
TWRP can not be used correctly since it shows Internal Storage as 0MB, which I think is a bad sign.
So he gave it back to me, I downloaded a Sprint RUU (exe) from the HTC website, didn't detect the device so didn't flash it. I tried copying the ROM.zip from the exe RUU but it turned out to be corrupt.
I downloaded the RUU zip from XDA, also turned out to be corrupt, when attempting to flash it through htc_fastboot, it shows an error:
"remote project does not have sa key to decrypt ROM"
Is the phone bricked, or is there any way I can get it going again?
Please help!
Thanks!
Mods, please close the thread.
Problem has been solved thanks to help from @miggsr.
murtaza02 said:
Mods, please close the thread.
Problem has been solved thanks to help from @miggsr.
Click to expand...
Click to collapse
Glad I was able to help.
Sent from my Family of HTC One devices.
murtaza02 said:
Mods, please close the thread.
Problem has been solved thanks to help from @miggsr.
Click to expand...
Click to collapse
Done
Hello everyone. I'm attempting to assist @arindambag recover his device from a soft brick.
If anyone with a rooted Desire 628 (2PVG) could provide a dump of their hboot or hosd, it would be greatly appreciated.
The version doesn't matter. It is only needed to generate a key file for the RUU extraction tool.
How to root htc desire 628 dual sim?
Tathyajit said:
How to root htc desire 628 dual sim?
Click to expand...
Click to collapse
It seems that some people were able to root with Kingroot on the originally released rom, but, as far as I know, there's no way to root yet after updating.
With no custom recovery (yet), root will not be possible unless another vulnerability is discovered.
CSnowRules said:
It seems that some people were able to root with Kingroot on the originally released rom, but, as far as I know, there's no way to root yet after updating.
With no custom recovery (yet), root will not be possible unless another vulnerability is discovered.
Click to expand...
Click to collapse
Then is there any process to go back to the original rom? I mean revert this update? If we flash the original stock rom before update? Then we will be able to root it with KingRoot
Tathyajit said:
Then is there any process to go back to the original rom? I mean revert this update? If we flash the original stock rom before update? Then we will be able to root it with KingRoot
Click to expand...
Click to collapse
If you can s-off, you should be able to use any RUU for your phone or change regions with a CID change, but I'm not that familiar with the HTC mediatek devices, though.
Any update brother for my case?
arindambag said:
Any update brother for my case?
Click to expand...
Click to collapse
None so far. I really need an hboot for your model. Or images, or anything really...
It is really difficult to support without the phone or images.
CSnowRules said:
None so far. I really need an hboot for your model. Or images, or anything really...
It is really difficult to support without the phone or images.
Click to expand...
Click to collapse
Since Tathyajit has the same model and also in working condition, can we extract the hboot or system image file from his phone and check? Just a thought. In that case, we need to guide Tathyajit how to do that, if required.
Without root permission,is it possible to extract hboot and system image file.
@Tathyajit: Please share your getvar info so that we can know the model and version of your phone.
arindambag said:
Since Tathyajit has the same model and also in working condition, can we extract the hboot or system image file from his phone and check? Just a thought. In that case, we need to guide Tathyajit how to do that, if required.
Without root permission,is it possible to extract hboot and system image file.
@Tathyajit: Please share your getvar info so that we can know the model and version of your phone.
Click to expand...
Click to collapse
No, root or custom recovery would be required to get an hboot image.
Still not able to restore my phone, any help please......
arindambag said:
Still not able to restore my phone, any help please......
Click to expand...
Click to collapse
Tell me if i can help in any way
Tathyajit said:
Tell me if i can help in any way
Click to expand...
Click to collapse
If you can find a way to get root on your device, I'll be able to provide instructions to extract what I need to decrypt the RUUs for all Desire 628s. Unfortunately, without root and no custom recovery available at this point, the only way to fix @arindambag's phone is via a RUU that is not available (yet).
Need help please, could able to install the RUU for version 1.17.400.1 and the phone also started successfully, but suddenly the phone went off and now it's not starting. I tried all combinations of Volume Up, Down, Power, etc. but could not able to start. Once the charger is connected, pressing the Power button shows the Battery icon once and then again the phone goes off. Pressing combinations of hard buttons, I could able to listen in my PC that connecting/disconnecting sound is coming but nothing getting displayed in the screen.
At one point of time,the HTC logo screen did come but the phone again going to the black screen.
Any suggestions would really help me.
Check this if you could find what you need
I have root via kingroot on a purchased outright medtech HTC desire 628. If you tell me how to go about getting any info that would help let me know.
Sent from my htc_v36bml_uhl using XDA Labs
Hey guys! I'm using this desire 628 and I have successfully unlocked bootloader, rooted and also flashed custom recovery (TWRP). If you need any assists.. leave a reply!?
DKrbD235 said:
Hey guys! I'm using this desire 628 and I have successfully unlocked bootloader, rooted and also flashed custom recovery (TWRP). If you need any assists.. leave a reply!?
Click to expand...
Click to collapse
Yeah man, how did you do it?
cinimod666 said:
Yeah man, how did you do it?
Click to expand...
Click to collapse
Its really simple mahn... Just download TWRP builder. Grant root access and upload your boot image. Make sure you have backed up your current boot.img . When the custom twrp recovery is ready, the app will let you know. For me, it didn't work. Then I contacted the developer and he did some tweaks and sent the recovery for the second time. And it worked!