Database Info

Issue After Flashing CM 10

I went through unlock, and root with no issue. After installing CM and gapps, I'm now just getting the spinning CM boot image.
I wish I could just pull the battery
Any help would be appreciated.

dgwphotography said:
I went through unlock, and root with no issue. After installing CM and gapps, I'm now just getting the spinning CM boot image.
I wish I could just pull the battery
Any help would be appreciated.
Click to expand...
Click to collapse
Which hboot do you have?
Which recovery are you using?

pbelcomp said:
Which hboot do you have?
Which recovery are you using?
Click to expand...
Click to collapse
I have CWM touch.
I also tried running reboot through fastboot, and just got "Waiting for device"

dgwphotography said:
I have CWM touch.
I also tried running reboot through fastboot, and just got "Waiting for device"
Click to expand...
Click to collapse
Which hboot?

I'm not sure - it must be the latest stock version. I just got this phone from Assurion this week as replacement for my daughter's Amaze.

dgwphotography said:
I'm not sure - it must be the latest stock version. I just got this phone from Assurion this week as replacement for my daughter's Amaze.
Click to expand...
Click to collapse
Did you flash the boot.img via Fastboot?
http://forum.xda-developers.com/showthread.php?t=1752270

I flashed CWM touch via fastboot, and then flashed CWM 8.2.3 zip before I flashed CM and gapps

dgwphotography said:
I flashed CWM touch via fastboot, and then flashed CWM 8.2.3 zip before I flashed CM and gapps
Click to expand...
Click to collapse
Read this thread and the cm10 op...you didn't install correctly and have ignored several relevant questions trying to help...

You have to extract the boot image from the ROM .zip file. Then you have to flash it with either fast boot ( on computer) or flash image GUI( On your phone In Android itself).
That is why your phone will not boot because the boot image has not been flashed correctly or at all.
You don't need to pull the battery obviously you can't. What you do is just hold down volume down and power and keep holding it until you see the bottom lights flashing keep keep holding it eventually your phone will turn off.
Sent from my HTC One S using xda premium

Thanks everyone for your help.
I extracted the boot image from the ROM and flashed it. For good measure I also rewiped, and flashed CM10 and gapps again. Everything is working great now - this phone is really a beast without sense.
Thanks again!

[Q] Clockwork Mod Recovery Failure

I have searched and can't find out anything about this, but for some reason I can flash recovery-clockwork-6.0.4.5-hammerhead.img through fastboot and then get into CM recovery. However, if I leave recovery and try to boot into it again, I get the dead droid picture. I can flash CM again and it'll work, but again, for a single use. I've never had this problem before on any Droid I've owned and I can't seem to find anyone dealing with it in this forum. Any help would be greatly appreciated.
No this phone is not rooted. I have unsuccessfully attempted this with CM (upon exiting recovery mode, you are prompted to root your phone if it hasn't been rooted).

It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'

You should also search the rules and list in he correct forum. This is not for questions only development
Sent from my Nexus 5 using XDA Free mobile app

also, clockwork mod recovery is long discontinued and provides no support anymore.

EddyOS said:
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
Click to expand...
Click to collapse
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.

strakajagr said:
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
Click to expand...
Click to collapse
In any case, I can flash something else since CM is no longer supported. Thanks.

strakajagr said:
In any case, I can flash something else since CM is no longer supported. Thanks.
Click to expand...
Click to collapse
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How do I go about locking the bootloader after it's unlocked?

strakajagr said:
How do I go about locking the bootloader after it's unlocked?
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app

First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.

BirchBarlow said:
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
Click to expand...
Click to collapse
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?

strakajagr said:
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
Click to expand...
Click to collapse
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.

simms22 said:
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
Click to expand...
Click to collapse
Word. Thanks.
Next order of business is figuring why there is so much lag when I text/gchat in 5.0. This is the whole reason I got into this mess. I couldn't wait 3 more weeks. Sadly, when I type, the keyboard freezes constantly. I figure I'll install a recovery mode correctly and then try to tackle that problem.

[Q&A] [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]

Q&A for [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

where is the link?

1122qqww said:
where is the link?
Click to expand...
Click to collapse
Here: http://www.teamw.in/project/twrp2/105
I strongly recommend installation using the fastboot method, as the apps are reported to work poorly or not at all.

TWRP 2.8.5.0 Won't Boot
I just installed TWRP 2.8.5.0 on my TF700T via the fastboot method (since TWRP Manager fails to install it). However, when I attempt to boot the recovery, the device locks up. This is different behavior than 2.8.4.0, which had a kernel panic and rebooted the device. Any idea how to go about debugging, or should I simply try older recoveries / wait until a newer one comes out?

N1FFO said:
I just installed TWRP 2.8.5.0 on my TF700T via the fastboot method (since TWRP Manager fails to install it). However, when I attempt to boot the recovery, the device locks up. This is different behavior than 2.8.4.0, which had a kernel panic and rebooted the device. Any idea how to go about debugging, or should I simply try older recoveries / wait until a newer one comes out?
Click to expand...
Click to collapse
My self-built one works fine. Can anyone else reproduce this problem with TWRP 2.8.5?

_that said:
My self-built one works fine. Can anyone else reproduce this problem with TWRP 2.8.5?
Click to expand...
Click to collapse
Nope!
Just dd'd 2.8.5.0 onto tf700. Flashed and works tadellos.

Works Now
das chaos said:
Nope!
Just dd'd 2.8.5.0 onto tf700. Flashed and works tadellos.
Click to expand...
Click to collapse
Naturally, the dd method is the one method I didn't try. So I just did, and it works now. I did have to perform a normal reboot to complete the installation (as opposed to rebooting directly into recovery), but the instructions mentioned that (although they didn't specify that the reboot needed to be a normal one). So all is well now, and I can move on to installing ZOMBi-Pop, my main goal all along.
Makes me wonder why TWRP and fastboot failed, but oh well.

N1FFO said:
Makes me wonder why TWRP and fastboot failed, but oh well.
Click to expand...
Click to collapse
These methods also require reboot to system not to recovery.

das chaos said:
These methods also require reboot to system not to recovery.
Click to expand...
Click to collapse
I can believe that for fastboot, but TWRP Manager claimed that the flashing failed. On my OnePlus One, TWRP Manager flashed the recovery just fine. Is the claimed failure just a caveat of flashing on the TF700T, and the new recovery will actually work despite it if you perform a system reboot afterwards? I think I'll try that next when the next version comes out, just to see.

N1FFO said:
I can believe that for fastboot, but TWRP claimed that the flashing failed. On my OnePlus One, TWRP flashed the recovery just fine. Is the claimed failure just a caveat of flashing on the TF700T, and the new recovery will actually work despite it if you perform a system reboot afterwards? I think I'll try that next when the next version comes out, just to see.
Click to expand...
Click to collapse
Did you try to flash the twrp.blob in recovery?
That won't work unless you put the blob into a flashable zip.
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...

berndblb said:
Did you try to flash the twrp.blob in recovery?
That won't work unless you put the blob into a flashable zip.
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
Click to expand...
Click to collapse
You're right, I meant TWRP Manager. Thanks for pointing that out, I edited the previous post to reflect that.

berndblb said:
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
Click to expand...
Click to collapse
That bricked my first tf300t!
Repeat:
Don't ever use TWRP Manager or Goo Manager for flashing recovery.

das chaos said:
That bricked my first tf300t!
Repeat:
Don't ever use TWRP Manager or Goo Manager for flashing recovery.
Click to expand...
Click to collapse
+1
add Flashify to the list. Or make that: apps in general
Fastboot or dd command is the way to go

Never mind, thanks
Never mind
Bgecko

USB OTG not working on htc one m7
USB keyboards not work on htc one m7 that support USB host mode via a USB OTG cable noooooooot work
openrecovery-twrp-2.8.5.0-m7.img

Can anyone turn this into a zip for me?
TLR - I think if I can get a zip of the latest TWRP I can get myself out of a nasty bootloop
I seem to have gone and bricked my Infinity while under the influence...
Installed new rom.
Decided to factory reset.
During format there was an error, and E: data no longer mountable (didn't realize this at the time)
Bootloop
Read some things online and thought maybe I didn't have the right TWRP
Installed a new recovery that was "compatible" with the rom I was installing
It was Philz cwm (freaked out)
Read a post that said I could force the tablet to re-format the :data partition from TWRP by using the terminal command "mke2fs -T ext4 /dev/block/mmcblk0p8" BUT can't run a terminal command from cwm
Can't find a way to enter fastboot to put twrp back onto transformer (No option for usb)

jbjcurly said:
Can't find a way to enter fastboot to put twrp back onto transformer (No option for usb)
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2688891

Problem solved!
_that said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Thanks _that! I actually used a flashable version of your twrp recovery (2.6.3 maybe?) that I found, followed the plan I outlined above, and all is now well.

Where to get TWRP 2.8.6.0 for TF700T
Does anyone know where a TWRP 2.8.6.0 .img for the TF700T can be found? It's not available on the official website (actually, NOTHING for the TF700T is available on the offcial website).
Alternatively, does anyone know where a patched version of 2.8.50 that supports f2fs can be found? Or should I revert to 2.8.4.0?
Eh, maybe I'll just build 2.8.6.0 myself. How hard can it be?

Slightly harder than finding the Kang TWRP 2.8.6 by lj in the dev section I would think....

TWRP downgrade works but strangely.

Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?

Unnecessary screenshot attached :good: enjoy~

Tiash420 said:
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Click to expand...
Click to collapse
Did you try flashing the recovery img via TWRP itself? And are you using any theme on TWRP 3.x.x.x?

Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.

Tiash420 said:
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Click to expand...
Click to collapse
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk

Renosh said:
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I get the notification quick settings bug, I mean, I can't get quick setting toggles directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that? Meanwhile my friend on the other hand downloaded the same version from the same place and he doesn't face those bugs. :'| Why is this happening to me?

Tiash420 said:
I get the notification quick settings bug, I mean, I can't get quick settings directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that?
Click to expand...
Click to collapse
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk

Renosh said:
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|

Tiash420 said:
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Click to expand...
Click to collapse
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk

Renosh said:
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well doesn't matter, I flashed Sultan's unofficial CM13 build via Kumajaya's TWRP 3.0.0.0 and it works fabulously! jgcaap can wait, I'm sure it's not much different in features and stuff! :3

Custom Recovery's won't install

Other than CM Recovery I cannot get anything to install, not even the stock or TWRP. They all install fine and say that it is all flashed fine regardless of how I flash the recovery, but then when booting into recover I get the boot screen for around 5-10 seconds a brief flash of a plain black screen with some text (though sometimes not even this shows up) and then nothing, the phone is still on however as I have to turn it off before turning it back on again, there is just nothing displayed on the screen.
Also my boot image still shows as FreedomOS however since freedom I have had Paranoid and CM installed so not sure (the boot animation is CM but the image shown with the one plus logo has FreedomOS at the bottom)
Any help would be wonderful
Thank you

Never heard of that rom. What device do you have?
Sent from my A0001 using XDA-Developers mobile app

Did you Root before ?

DerRomtester said:
Never heard of that rom. What device do you have?
Click to expand...
Click to collapse
I have a OnePlus 3

Cholerabob said:
Did you Root before ?
Click to expand...
Click to collapse
I did root yes

McreativeH said:
I have a OnePlus 3
Click to expand...
Click to collapse
Wrong forum bro. Search for OnePlus 3 in search bar. You may get some help on freedom os is there.
It seems like you had a Firmware flash. You can try flashing recovery using a "PC with adb".
Secondly Google and download Firmware for one plus 3 . And flash it using recovery.
Again. Try booting into recovery, if you can't , you have lost recovery while flashing Firmware. Flash the recovery again using "PC with adb".
Hope it helps. Thanks.

shubhaemk said:
Wrong forum bro. Search for OnePlus 3 in search bar. You may get some help on freedom os is there.
It seems like you had a Firmware flash. You can try flashing recovery using a "PC with adb".
Secondly Google and download Firmware for one plus 3 . And flash it using recovery.
Again. Try booting into recovery, if you can't , you have lost recovery while flashing Firmware. Flash the recovery again using "PC with adb".
Hope it helps. Thanks.
Click to expand...
Click to collapse
I see... I clicked the my device section via the XDA app and for some reason it said I have a OnePlus One

McreativeH said:
I see... I clicked the my device section via the XDA app and for some reason it said I have a OnePlus One
Click to expand...
Click to collapse
Hope your phone didn't turned into OnePlus One.
Regards! Delete the thread and start over there. See you