Hi, my name is Apurv
I was looking for a TWRP recovery for my Mediatek MT6580 phone Homtom Ht3.
I came across a boot image which said that it is for only mediatek phones and can be flashed using flashify only.
Sorry since I am new, I can't insert outside links and images.
I followed all the steps given on the site and flashing the boot image was successful.
When I checked whether this new recovery works or not, my phone directly booted to Factory mode
with following options:- Auto Test, Manual Test, Item Test, Test Report, Debug Test, Clear eMMC, Version, Reboot.
I don't recognize this recovery. Is it TWRP? Because I believe it is CWM. And if it is CWM then how can I go to the Recovery mode?
I do have Kernel and Stock backups on flashify, if I install them, is it going to reinstall my original recovery?
Please help!!!!!!!!!!!
Hi !
the "boot.img" file you have flashed is not a recovery , it is a kernel
The messages you have seen are most probably related to a recovery , maybe stock recovery
Restore the boot img and stock ( I`m not sure what "stock" is ) if you have saved it and if you`re able to restore it
Good luck !
Related
Hi Guys,
I had CM 10 on my phone and I was able to use CWM successfully. But, then I flashed Pandroid 4+ (CM 11 based) Kitkat 4.4 ROm on my phone.
Now, I am not able to boot into recovery mode. As i try to enter into recovery mode, My phone gets stuck in the boot screen and does not boot up. After so many attempts of pressing power button, it starts. It's so painful.
I want to revert back to CM 10 stable rom, but I can't boot in to recovery mode.
I did some research and found a CWMFixed.zip as a solution. It contains a boot.img file. Please let me know how can i flash this file without entering into CWM.
Or if there is any other solution for this problem then please let me know.
It urgent.
@tysonraylee I hope you can help me in this as you had posted a similar query in other thread.
Thanks in advance.
My friend, If you would have only read the PA thread properly you would know that beta 5 has the bug where it breaks the recovery you would have avoided the problem altogether but anyways i would suggest that you flash an odin format (.tar) kernel using PC Odin which will get you a working recovery and from there it should be pretty easy, if you took a nandroid backup before you will be able to restore your previous rom and if you didnt you have to flash a different rom of your choice
flash this TW PC odin format (.tar) kernel by bauner https://www.androidfilehost.com/?fid=95784891001607164
make sure once you flash this to not let the phone boot into ROM, after flashing successful take off the battery and then insert back and boot into recovery.
Once you have a recovery then you need a SE Linux compatible recovery so for that connect the device to PC and mount the usb storage through recovery then transfer
This Bauner's KK kernel if you require CWM https://www.androidfilehost.com/?fid=95784891001608504
and this GeeckoDev Raw kernel if you require TWRP recovery http://forum.xda-developers.com/showpost.php?p=53978758&postcount=583 (download raw_kernel_r6_k44.zip)
once transfered to your device flash the one you require and remember we are flashing these kernel just for temporary use and once a rom is flashed they will get overwritten with the recovery that comes with the rom kernel so you dont have to worry about these kernels
Once flashed remember to reboot to recovery and not system, once the device boots into your desired recovery then either restore your previous rom from backup or falsh a new one
hope this helps and remember next time before flashing a rom read the OP and atleast 4-5 last pages. Believe me this will save you a lot of trouble in your future flashing endeavours
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
Hello
I could not find support of twrp and cyanogen mod recovery for my phone. But i installed twrp and cyanogen from playstore.
Whenever i go to recovery, it alsways boot into default recovery of android and not going into custom recovery. I have tried everything.
Help meer...
Please, post which phone model you have and the Android version. Also, make a backup of your stock recovery (I use Rashr Flash Tool, you need root) before installing another.
To install the recovery you have to flash it, the TWRP app just tells you if there exists a recovery for you (and some models are not listed in the app either).
If you haven't found any custom recovery, you could try and adapt the recovery of a similar phone to yours (similar processor, resolution...), but it is risky and can turn your phone into a stone. It implies replacing the .ks modules and testing. I don't know enough about it, but there are threads on XDA where you can get hints on how to do these things.
Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.
Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!
How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579
dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.
If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app
you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1
Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.