Database Info

TWRP doesnt seem to be working.. and dual screens..

Tried to boot in to recovery to flash a root zip..
When i volume up to enter recovery, screen goes black. I hit power button and TWRP opens but its unusable and dual screen..top and bottom. Slide to unlock is on the screen but nothing works. Only way out is to hold down power and reset.
Help!

Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!

DatacomGuy said:
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
Click to expand...
Click to collapse
What bootloader are you on (its in settings app)

cmendonc2 said:
what bootloader are you on (its in settings app)
Click to expand...
Click to collapse
10.6.1.8-20130225

DatacomGuy said:
10.6.1.8-20130225
Click to expand...
Click to collapse
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.

cmendonc2 said:
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
Click to expand...
Click to collapse
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?

DatacomGuy said:
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
Click to expand...
Click to collapse
I know you can use that firmware to install KitKat ROMs as shown here (http://forum.xda-developers.com/showthread.php?p=49028315).
Use the 10.6.1.27.5 firmware with this:
Tylorw1 said:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Click to expand...
Click to collapse

Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?

DatacomGuy said:
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
Click to expand...
Click to collapse
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app

cmendonc2 said:
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Alright..
fastboot -i 0x0B05 flash recovery firmwarefile.zip
Click to expand...
Click to collapse
Is that the right syntax?

DatacomGuy said:
Alright..
Is that the right syntax?
Click to expand...
Click to collapse
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.

cmendonc2 said:
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
Click to expand...
Click to collapse
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
fastboot -i 0x0b05 flash US_epad-user-10.6.1.27.5.zip"
Click to expand...
Click to collapse
and i get:
Unknown partition 'US_epad-user-10.6.1.27.5.zip'
error: cannot determine image filename for 'US_epad-user-10.6.1.27.5.zip'
Click to expand...
Click to collapse
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.

DatacomGuy said:
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
and i get:
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
Click to expand...
Click to collapse
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob

cmendonc2 said:
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
EDIT2: Is this the right one?
openrecovery-twrp-2.6.3.0-tf300t-JB.blob

DatacomGuy said:
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
Click to expand...
Click to collapse
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.

cmendonc2 said:
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
Click to expand...
Click to collapse
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?

DatacomGuy said:
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
Click to expand...
Click to collapse
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.

cmendonc2 said:
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
Click to expand...
Click to collapse
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?

DatacomGuy said:
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
Click to expand...
Click to collapse
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1

cmendonc2 said:
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
Click to expand...
Click to collapse
i dont want to flash any rom right now, i just want to stick with stock 4.2.1...
Last time i flashed TWRP.. albeit incorrectly.. it didnt ask anything when i rebooted into recovery. I'm assuming thats when it asks....

CWM to TWRP

How do I convert from CWM to TWRP properly?
I searched around and it seems that I should just be able to use goomanager and install open recovery script. I do that, I see it download TWRP and then it says recovery installed, but when I reboot recovery, it still takes me to CWM.
If I go into ROM Manager, it looks like both recoveries are installed and then clicked to use TWRP and it still booted in CWM.
Then I used ROM Installer to install TWRP and now it reboots into TWRP when I reboot into recovery.
But, when I go into ROM Manager, it still says that CWM is installed. Do I need to get rid of that? If so, how?

I would try this. Odin to CWM, uninstall ROM Manager, and then use Goomanager to update to TWRP.

sfobrien said:
I would try this. Odin to CWM, uninstall ROM Manager, and then use Goomanager to update to TWRP.
Click to expand...
Click to collapse
Not exactly sure what Odin to CWM means. Odin is software on my PC? Will that be destructive in any way? Right now, it does all seem like it's working fine except that ROM Manager sees CWM there too.
Any other ideas?

Install flashify from the play store.
Download your recovery .img of choice.
Flash .img using flashify, reboot to recovery.

GideonX said:
Install flashify from the play store.
Download your recovery .img of choice.
Flash .img using flashify, reboot to recovery.
Click to expand...
Click to collapse
I don't think I need that. I have TWRP installed and it boots to it, but ROM Manager says that CWM is also installed. Is it really there? Do I need to get rid of it and if so, how?

lexluthor said:
I don't think I need that. I have TWRP installed and it boots to it, but ROM Manager says that CWM is also installed. Is it really there? Do I need to get rid of it and if so, how?
Click to expand...
Click to collapse
If you reboot to recovery, what recovery does it take you to?
If it's TWRP, disregard the notice from Rom Manager.

GideonX said:
If you reboot to recovery, what recovery does it take you to?
If it's TWRP, disregard the notice from Rom Manager.
Click to expand...
Click to collapse
TWRP.
Ok, I'll just ignore that then.

lexluthor said:
TWRP.
Ok, I'll just ignore that then.
Click to expand...
Click to collapse
Uninstall Rom Manager while you're at it.

lexluthor said:
Not exactly sure what Odin to CWM means. Odin is software on my PC? Will that be destructive in any way? Right now, it does all seem like it's working fine except that ROM Manager sees CWM there too.
Any other ideas?
Click to expand...
Click to collapse
I meant install CWM with Odin. Uninstall ROM Manager first.

SuperSU needs to update binary

Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.

What if you upgrade it using the "normal" method?

If I do a normal install i get the following:
Installation failed!
Please reboot and try again.

brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?

rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.

brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.

rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?

brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards

rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app

brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.

can't update to the lase update (xnph44s)

hi,
i just received the lastest update of the oneplus one (my one is rooted and i have twerp recovery) and when i click on "install update", the phone reboot to recovery and then a window open like when i flash a zip and it fails and i get redirected to the twerp menu and then i don't know what to do. i tried to find the file and to flash it and it still didn't work.
do you have an idea?
thank you

bigben14 said:
hi,
i just received the lastest update of the oneplus one (my one is rooted and i have twerp recovery) and when i click on "install update", the phone reboot to recovery and then a window open like when i flash a zip and it fails and i get redirected to the twerp menu and then i don't know what to do. i tried to find the file and to flash it and it still didn't work.
do you have an idea?
thank you
Click to expand...
Click to collapse
where did you get this file from? what Rom?

gd6noob said:
where did you get this file from? what Rom?
Click to expand...
Click to collapse
i used the file from oneplus, the one i got from the over the air update
https://www.dropbox.com/s/1x5qr4xgto4276u/Screenshot_2014-11-16-13-07-39%5B1%5D.png?dl=0

bigben14 said:
i used the file from oneplus, the one i got from the over the air update
Click to expand...
Click to collapse
I flashed the stock recovery to get the update to install. Then just flash twrp again after that. It is easy and fast.

tech_baggie said:
I flashed the stock recovery to get the update to install. Then just flash twrp again after that. It is easy and fast.
Click to expand...
Click to collapse
still doesn't work, i get the same fail as the one from twerp (i put a picture of it in the last post

bigben14 said:
still doesn't work, i get the same fail as the one from twerp (i put a picture of it in the last post
Click to expand...
Click to collapse
That is weird, hmmm. Maybe if you return to stock via fastboot? There is a how-to thread explaining how to do that. Otherwise I am not sure. It worked when I did it. Will check if there is another way.

i did get back to stock recovery via flashboot and with OPO Toolbox
i'd love it if you can find a solution, i'll try to look for one too on my side
thank you

try the lastest TWRP v2.8.1.0?

I went back to stock recovery so there shouldn't be any problem of update of the recovery right?

Just updated to XNPH05Q - help

So I lost twrp and root, Whats the easiest way to get root back or twrp as I cant get into twrp recovery to try and flash supersu.

SysAdmNj said:
So I lost twrp and root, Whats the easiest way to get root back or twrp as I cant get into twrp recovery to try and flash supersu.
Click to expand...
Click to collapse
You'll probably need to flash a custom recovery via fastboot/toolkit, you can root at the same time or flash a supersu zip once you have your custom recovery.

gsmyth said:
You'll probably need to flash a custom recovery via fastboot/toolkit, you can root at the same time or flash a supersu zip once you have your custom recovery.
Click to expand...
Click to collapse
Dammit, I should of asked first before updating lol. Thanks, I guess I'll have to go that route.

SysAdmNj said:
Dammit, I should of asked first before updating lol. Thanks, I guess I'll have to go that route.
Click to expand...
Click to collapse
Same thing happened to me, but at least its simple enough to sort. Doesn't help if you're not near a PC and can't wait though!

For future reference remember and untick update CM recovery in developer options

gsmyth said:
Same thing happened to me, but at least its simple enough to sort. Doesn't help if you're not near a PC and can't wait though!
Click to expand...
Click to collapse
Yup, gotta wait till this evening.
bombadier said:
For future reference remember and untick update CM recovery in developer options
Click to expand...
Click to collapse
Jeez, missed that as well. Thanks.

Re-Install TWRP through Play Store no PC needed

Cholerabob said:
Re-Install TWRP through Play Store no PC needed
Click to expand...
Click to collapse
But you need root to do that, no?

SysAdmNj said:
But you need root to do that, no?
Click to expand...
Click to collapse
That's right, the TWRP app is really unreliable anyway so don't bother with it. Why don't you just flash TWRP the normal way, with fastboot?
Transmitted via Bacon