Database Develop

CWM is available to flash through Rom Manager

Rom Manager was just updated to version 5.0.2.4 and allows you to flash to CWM 6.0.1.6 recovery. Booting to recovery just gives me the Android with a red flag though. Just a FYI till it gets sorted.
Pressing and holding the pwr button will boot you back to the OS. Not a huge deal as we don't have anything to flash at the moment.
If you need to get back to the stock recovery in the meantime which can be found in this thread
http://forum.xda-developers.com/showthread.php?t=1993331
Edit:
Don't Flash this yet, you'll have to re-install the stock recovery or wait for a fix and could possibly brick your phone if you don't know what you're doing.

Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?

I get the same thing as you, says flash successful then the red flag.

F4M0U569 said:
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
Click to expand...
Click to collapse
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.

kchino said:
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
Click to expand...
Click to collapse
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.

F4M0U569 said:
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
Click to expand...
Click to collapse
i did it last night and it was quite late, but if i remember correctly i had the same problem but just had to reselect USB debugging
Sent from my Nexus 7 using xda app-developers app

[Q] HTC One having touch issues in recovery

i posted this in the att section but maybe ill get some help here as well. ill delete my other one.
I just bought a rooted/bootloader unlocked/s-off HTC one from someone. I went to flash TWRP via goo manager and the touch screen does not work in TWRP. i installed CWM and that worked...until the rom i was flashing went to the aroma installer. Then the touch function in recovery stopped working again. Any ideas and help please?

cwhitney24 said:
i posted this in the att section but maybe ill get some help here as well. ill delete my other one.
I just bought a rooted/bootloader unlocked/s-off HTC one from someone. I went to flash TWRP via goo manager and the touch screen does not work in TWRP. i installed CWM and that worked...until the rom i was flashing went to the aroma installer. Then the touch function in recovery stopped working again. Any ideas and help please?
Click to expand...
Click to collapse
you have ols version of TWRP installed....
you need install 2.6.0.1
http://forum.xda-developers.com/showthread.php?t=2173870
and you have to install that via fastboot NOT goo manager

99piotrek said:
you have ols version of TWRP installed....
you need install 2.6.0.1
http://forum.xda-developers.com/showthread.php?t=2173870
and you have to install that via fastboot NOT goo manager
Click to expand...
Click to collapse
Thanks,,,and luck me i dont have SDK tools/ADB installed on this laptop yet. This is going to be a long night...

thanks again. got it fixed

[Q] Stuck in TWRP

Hi, I have a ATT HTC One I got yesterday. Was rooted, had an old ROM on it, unlocked, s-off, hboot 1.44. I tried to flash a PGe rom on it and it became stuck in TWRP. I can get adb, but sideloading a rom doesn't work. It says it flashes but will not boot. Can get into the bootloader, but can't get fastboot. Really frustrated, any help would be much appreciated. Thanks!

i was also got same problem with you
and to boot to TWRP i use CMD : Fastboot boot recovery.img
and then i can successfully go to TWRP settings

fndfendy said:
i was also got same problem with you
and to boot to TWRP i use CMD : Fastboot boot recovery.img
and then i can successfully go to TWRP settings
Click to expand...
Click to collapse
I can get into TWRP no problem. And I can get adb there, but can't flash a rom, always fails. Anyone else have any ideas?

schufly said:
I can get into TWRP no problem. And I can get adb there, but can't flash a rom, always fails. Anyone else have any ideas?
Click to expand...
Click to collapse
have you tried pushing rom instead of sideloading it??
got to recovery and try this
adb push rom.zip /data/media/0/
or
adb push rom.zip

Harish_Kumar said:
have you tried pushing rom instead of sideloading it??
got to recovery and try this
adb push rom.zip /data/media/0/
or
adb push rom.zip
Click to expand...
Click to collapse
I will try that. I am also using a windows 8 laptop, which may be part of my issue in getting the phone recognized in fastboot. I am trying to locate a windows 7 computer to use. I am also downloading the correct Guru file for it, but can't try it till I get home tonight because I can't install HTC drivers on my work computer.
I have been rooting phones since I had my HTC Hero and never had this much trouble or bricked a phone, let alone had to leave one down overnight. I am humbled......lol

I was also considering trying to load a nandroid backup. IF I do, and I can push it, what location does it need to go to??

schufly said:
I was also considering trying to load a nandroid backup. IF I do, and I can push it, what location does it need to go to??
Click to expand...
Click to collapse
what TWRP version are you using, and what are you installing?
If you're flashing a 4.4 ROM, then you will need TWRP 2.6.3.3, otherwise it will bootloop.
and for GPE 4.4 you also need S-Off.

nkk71 said:
what TWRP version are you using, and what are you installing?
If you're flashing a 4.4 ROM, then you will need TWRP 2.6.3.3, otherwise it will bootloop.
and for GPE 4.4 you also need S-Off.
Click to expand...
Click to collapse
Was about to say same, except if it's a 4.4 ROM it will fail install, not bootloop...........TWRP 2.6.3.4 is available now also.

CaelanT said:
Was about to say same, except if it's a 4.4 ROM it will fail install, not bootloop...........TWRP 2.6.3.4 is available now also.
Click to expand...
Click to collapse
havent had a chance to check, but is .4 stable? iirc it didnt work for someone for 4.4 but .3 did.

nkk71 said:
havent had a chance to check, but is .4 stable? iirc it didnt work for someone for 4.4 but .3 did.
Click to expand...
Click to collapse
I flashed Insertcoin with 2.6.3.3, but haven't tried 2.6.3.4 with 4.4 as it was released after. Using 2.6.3.4 on my phone now with no other issues though. I know to never assume, but I did assume that later revisions than 2.6.3.3 should also work. Maybe someone can clarify.
<edit> Here ---> http://forum.xda-developers.com/showpost.php?p=48364016&postcount=1107

CaelanT said:
I flashed Insertcoin with 2.6.3.3, but haven't tried 2.6.3.4 with 4.4 as it was released after. Using 2.6.3.4 on my phone now with no other issues though. I know to never assume, but I did assume that later revisions than 2.6.3.3 should also work. Maybe someone can clarify.
<edit> Here ---> http://forum.xda-developers.com/showpost.php?p=48364016&postcount=1107
Click to expand...
Click to collapse
Thanks, downloading
---------- Post added at 06:23 PM ---------- Previous post was at 06:10 PM ----------
CaelanT said:
I flashed Insertcoin with 2.6.3.3, but haven't tried 2.6.3.4 with 4.4 as it was released after. Using 2.6.3.4 on my phone now with no other issues though. I know to never assume, but I did assume that later revisions than 2.6.3.3 should also work. Maybe someone can clarify.
<edit> Here ---> http://forum.xda-developers.com/showpost.php?p=48364016&postcount=1107
Click to expand...
Click to collapse
so i checked, but it doesn't say why it's under m7ul now. any reason it wouldnt work with an m7u?

I'm stuck with TWRP 2.6.3.0 unfortunately.....

Solved my problem. Used a Windows Vista computer, and a different cable, was able to get fastboot to work and used a RUU to get back to stock. Got rid of TWRP and put on the newwest CWM recovery and a new rom. Thanks to all that helped!

Flashed a TWRP Recovery but can't boot into recovery...

Everytime I install the TWRP Recovery and try to boot into recovery mode it just reboots to the regular phone framework.
Whats going on and what do I do now?
HTC Desire 626s
Bootloader Unlocked
using this twrp recovery from here
Edit: So I rooted my phone using the Cyanogenmod recovery since I had gaven up and just tried the next best thing,I got SuperSU Binaries & APK installed so I'm all good. However I would like to know if there is anything I should know when using a recovery and why in the above forum thread they said to use the TWRP method instead of Cyanogenmod ("Highly recommended")
Thank you for your time XDA (aprox. 14minutes replies and 18minutes views)!

EDIT: just realized you incluided your twrp source. Try mine from here
i had the same issue, it means the twrp you used isnt right for your phone. is the twrp you used mine? if so, you need to go into bootloader mode and tell me what the hardware model of your phone. should start with a32XXX i developed for the a32eul and tmobile.
If you grabbed it from captain_throwback that is meant for the sprint variant. there are no other twrp for any other carriers.

Jmingels said:
EDIT: just realized you incluided your twrp source. Try mine from here
i had the same issue, it means the twrp you used isnt right for your phone. is the twrp you used mine? if so, you need to go into bootloader mode and tell me what the hardware model of your phone. should start with a32XXX i developed for the a32eul and tmobile.
If you grabbed it from captain_throwback that is meant for the sprint variant. there are no other twrp for any other carriers.
Click to expand...
Click to collapse
Just an FYI, captain throwbacks version worked on my MetroPCS variant.
To the OP, did you ever have any custom recovery flashed? Like the partially working CM recovery ? If you have root access already you could use rashr or flashify to flash a recovery .img

Jmingels said:
EDIT: just realized you incluided your twrp source. Try mine from here
i had the same issue, it means the twrp you used isnt right for your phone. is the twrp you used mine? if so, you need to go into bootloader mode and tell me what the hardware model of your phone. should start with a32XXX i developed for the a32eul and tmobile.
If you grabbed it from captain_throwback that is meant for the sprint variant. there are no other twrp for any other carriers.
Click to expand...
Click to collapse
Thank you for replying anyway,unfortunate I can't use it anymore (or don't have to),
Used the Cyanogenmod method from the same thread mentioned in OP's Post.
My carrier is TMobile (comes with the app & stuff).
If I tried the Sprint variant should I be worried I tried (and failed)?
talksickisil said:
Just an FYI, captain throwbacks version worked on my MetroPCS variant.
To the OP, did you ever have any custom recovery flashed? Like the partially working CM recovery ? If you have root access already you could use rashr or flashify to flash a recovery .img
Click to expand...
Click to collapse
The partially working CM recovery? Perhaps you are referring to Cyanogenmod?
I didn't try anything but this TWRP,but now I used the Cyanogenmod and installed the SuperSU v2.52 binaries and everything,so its fine now,but if you are referring to Cyanogenmod then why is is partially working and should I be aware of any problems?

Xevioni said:
Thank you for replying anyway,unfortunate I can't use it anymore (or don't have to),
Used the Cyanogenmod method from the same thread mentioned in OP's Post.
My carrier is TMobile (comes with the app & stuff).
If I tried the Sprint variant should I be worried I tried (and failed)?
The partially working CM recovery? Perhaps you are referring to Cyanogenmod?
I didn't try anything but this TWRP,but now I used the Cyanogenmod and installed the SuperSU v2.52 binaries and everything,so its fine now,but if you are referring to Cyanogenmod then why is is partially working and should I be aware of any problems?
Click to expand...
Click to collapse
Before captain throwbacks TWRP somebody had uploaded a version of cyanogen mod recovery to work on the desire 626s. But it wasn't fully functional. It didn't read from external storage which also made nandroid backups not an option. But what it did do however, is allow us to flash super SU from internal storage. But if you have flashed superuser and have achieved root you can go ahead and flash the twrp .IMG with rashr or flashify
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
As far as which one you should use, use the one Jmingels posted as he says that works on T-Mobile ... I can only confirm MetroPCS for captain throwbacks version. I'm not sure about if it will work for a t mobile phone or not. But if the recovery you have is the CM one posted in the how to root thread you are definitely going to want to update to twrp for a full featured recovery. Just download jmingels file, download rashr or flashify from playstore, and install the .IMG file you downloaded.. With rashr select recovery from storage, or with flashify select flash a recovery/choose file,flash it, reboot, done. Easy as that

talksickisil said:
Before captain throwbacks TWRP somebody had uploaded a version of cyanogen mod recovery to work on the desire 626s. But it wasn't fully functional. It didn't read from external storage which also made nandroid backups not an option. But what it did do however, is allow us to flash super SU from internal storage. But if you have flashed superuser and have achieved root you can go ahead and flash the twrp .IMG with rashr or flashify
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
As far as which one you should use, use the one Jmingels posted as he says that works on T-Mobile ... I can only confirm MetroPCS for captain throwbacks version. I'm not sure about if it will work for a t mobile phone or not. But if the recovery you have is the CM one posted in the how to root thread you are definitely going to want to update to twrp for a full featured recovery. Just download jmingels file, download rashr or flashify from playstore, and install the .IMG file you downloaded.. With rashr select recovery from storage, or with flashify select flash a recovery/choose file,flash it, reboot, done. Easy as that
Click to expand...
Click to collapse
Alright,Thank you very much for this explanation,I'll keep note of this and go ahead and flash the t-mobile one at some point today or tomorrow.

Recovery Question (Only Santod recoveries work on my phone)

Why is it that only recoveries compiled by Santod will boot (successfully) on my phone? I'm using m7vzw.
The symptom is that the standard recoveries seem to "load" but the screen is blank. However, it does mount the partition in Windows via MTP and it does respond to touch. You just cant see what you're doing. On Santod's, everything works perfectly.

ccsoccer03 said:
Why is it that only recoveries compiled by Santod will boot (successfully) on my phone? I'm using m7vzw.
The symptom is that the standard recoveries seem to "load" but the screen is blank. However, it does mount the partition in Windows via MTP and it does respond to touch. You just cant see what you're doing. On Santod's, everything works perfectly.
Click to expand...
Click to collapse
By "standard recoveries" I guess you mean TWRP for the VZW variant? (i.e no the ones for the U or UL variant?)

alray said:
By "standard recoveries" I guess you mean TWRP for the VZW variant? (i.e no the ones for the U or UL variant?)
Click to expand...
Click to collapse
Yes, nothing I download off of TWRP website for the VZW Variant will load the screen, however, when I flash back to Santod 2.8.3, works like a charm.

ccsoccer03 said:
Yes, nothing I download off of TWRP website for the VZW Variant will load the screen, however, when I flash back to Santod 2.8.3, works like a charm.
Click to expand...
Click to collapse
Try the universal build of twrp by mdmower
https://android.cmphys.com/twrp-m7/

alray said:
Try the universal build of twrp by mdmower
https://android.cmphys.com/twrp-m7/
Click to expand...
Click to collapse
That worked but I'd like to understand why it did. I don't understand why only certain recoveries work on certain version phones and so forth. I get that m7 only works on m7 but why is it different between subversions?