Database Info

Need help rooting and/or flashing twrp

Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.

Shad0w32 said:
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Click to expand...
Click to collapse
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.

cmendonc2 said:
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
Click to expand...
Click to collapse
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance

Shad0w32 said:
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Click to expand...
Click to collapse
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.

graphdarnell said:
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
Click to expand...
Click to collapse
For first, I downgraded my device, so I could root it with motochopper. Then I flashed recovery with the way explained here:http://forum.xda-developers.com/showthread.php?t=1845377
Now twrp seems to be working, i can start it, but it cant mount anything, so i cant flash anything from the device. Both 2.5 and 2.4.4 does this. Goo manager cant find a recovery for this device, so i cant use that either. Fastboot still cant see my tab. Im on windows 7, with proper drivers

Nevermind my stupidity, I installed the wrong recovery, not the one for the 4.2 bootloader. By now I'm a proud owner of a tf300t with cyanogenmod on it Thank you both though, for trying to help

[q] help!!! Wiped os

Okay,
So I'm an idiot. I finally unlocked the bootloader on my opo, but then I accidentally wiped everything including the system folder. So now I have no OS installed on my phone. I have TWRP installed, but when I click mount, there is no option to mount usb storage. Please tell me there is something I'm not thinking of!!!

Go into ADB sideload and adb sideload a ROM zip of your choice.
Google on how to use ADB sideload if you're unsure.

This is what I am going to suggest and it has always worked 100% for me.
1) Install a OPO tool box that will let you flash the factory image
2) Connect the phone in fastboot and flash the CM factory image
3) Let it complete and then flash your favorite recovery. I chose CWM.
4) Load your own custom rom and flash it.
Be happy.

Or you could do all of that without a toolbox and gain some experience and confidence in using fastboot manually.
Transmitted via Bacon

^^ This. I second that... Toolkits are great, but knowing what they do exactly is better...

I did same when I got mine. I unlocked bootloader and installed TWRP recovery. I forgot to backup and wiped after thinking I'd copied a custom ROM and gapps to the device.
I used sideload with no problem. Just ensure you install adb on a windows PC and all required drivers. just search adb sideload in xda or Google.
If you're a Mac user the Mac OPO toolkit will do it all in moments if you have the phone in fastboot mode

I agree with no toolkit. It's not that hard, you're just downloading files to use the fastboot, have drivers and then type three words or four words in command prompt.
A toolkit is automatic, but it can also backfire and get you into bad situations and then you're not sure how to recover since it did it for you. A toolkit is like math homework, a toolkit will solve your answers and whatnot. But come next time on the math test when you don't have the toolkit you won't know what to do, so chances are you're going to ask someone for help (I know you can't ask for help on a exam but... Let's just assume you can lol)
Sent from my One using Tapatalk

[Q] Problems with recovery and updating to 5.0.2

Hey,
I'm new to all of this so I really don't know what I'm doing wrong.
I got the normal Moto G running on 4.4.4, unlocked bootloader and rooted.
I've read that if no system files are changed I can just normally update the phone. So I flashed stock recovery (I had CWM before) using MotoTool AiO. But when I want to enter recovery it just gives me the "No Command." screen.
Only other thing I have different is, that I deleted some preinstalled Google and Motorola apps.
When I try to update the phone it just reboots after about 10 seconds telling me the update failed. (I always have to download the update again.)
I hope you guys can help me get to 5.0.2.
Thanks

You need certain Motorola Apps on your phone before the OTA update will work. Also, it's best to be unrooted.

Is there a way to restore the Motorola Apps? With the app i deleted them I can't, because I deleted them completely. (I didn't thought I would need them again.)

I'm not sure if you can find the proper APKs.
It may be easier to just flash back to stock and take the OTA update.

Okay, so I tried to get back a custom recovery so I can flash 4.4.4, but the problem is I still only get the no command screen when entering the recovery.
First I tried flashing CWM with the MotoTool AiO, but I still couldn't enter recovery, so I tried Philz Recovery, but I got the same problem there.
How the hell can I get a recovery, so I can flash 4.4.4?

You need to flash a completely stock ROM, including recovery.
You should download the stock 4.4.4 ROM for your phone and manually flash each partition using fastboot or mfasboot commands.

I tried it with help of this thread.
But it always says i can't find the command mfastboot and with the command fastboot it tells me it can't find the files and when I'm entering the folder it says it can't find the command. And even if I move the extracted files to the same folder (Where the fastboot.exe is) it tells me the files can't be found...
Like I said I'm new to all of this and little more detailed help would be appreciated
PS:
I still got the same .zip with the stock 4.4.4 I used to flash the first time (After that I deleted the system apps)
And in this .zip is an app folder with all the apks, so is there a fast way to just reinstall all of them?

Enable USB debugging and use the Moto AIO tool's Utilities tab to flash APKs to your phone.
http://forum.xda-developers.com/showthread.php?t=2635706

In MotoTool when I'm in fastboot it tells me device not found (Minimal ADB and Fastboot can find my device, and yestery MotoTool could find it, too. USB-Debugging is active.) and when the phone is normally stared in the cmd window it tells me [failed] ... (Can't read the rest, because the window closes instantly), but MotoTool says the installation worked

You need to be booted into ROM in order to use the APK installer.
When installing an APK, you may be prompted on the phone screen to allow your computer to have access to the phone.

Okay I managed to flash 4.4.4 and then I could update to 5.0.2, thanks for the help.

That's great. Glad I could be of some help.

Help Neeed Putting CM12 on Moto G 2013

EDIT
-------------
Thanks for the support from the people below but I have now solved my origonal issue. TWRP didn't seem to be working with me so I downloaded MOTO G 4G/Peregrine Easy Recovery (Credit to the absolute legend who made that) and then installed ClockworkMod instead, which worked perfectly. I have now succsessfully installed CM12 onto myMoto G 4G. If anyone has the same issue and want's some help, just message me.
I am trying to get CM12 into my Moto G 2013 (xt1032) and have hit a problem which I don't know how to solve. I successful unlocked the biitloader on my phone, and attempted to root it. After many different methods, I finally got my phone rooted (not sure which method actually did this) however, I also tried to install TWRP on my phone, and I now don't have a working recovery on my phone.
I have tried all the root apps of installing a recovery, as well as 3 or 4 similarpc methords and non seem to work. I either get the no command screen, or the failed to boot error. If anymore detail is needed, just ask.
If anyone has any ideas on what I can do, I would be very grateful. My desired outcome is to either have TWRP or the Stock Recovery Working and also a working methord on how to install CM12. This is my first time at rooting a phone so please be considerate of the language used in any responses.
Thanks, Dan

I usually use fastboot and a PC but if you are wanting to use an app and are already rooted I have used TWRP manager available in the play store with out issue

TWRP manager is the solution, but I gnrally recommend you to do it using fastboot on a pc

n0ts0smart said:
I usually use fastboot and a PC but if you are wanting to use an app and are already rooted I have used TWRP manager available in the play store with out issue
Click to expand...
Click to collapse
How would I do this? I have fastboot already installed if that is what I need.
Also, what can I do to get the default 'recovery mode' back onto my phone. At the moment, I just get an 'Unable to Boot' error pop up.
Thanks for the quick reply.

https://wiki.cyanogenmod.org/w/Install_CM_for_falcon#Installing_recovery_using_fastboot
You just need to download recovery file on your computer (I recommend it), boot to bootloader, either by using adb reboot bootloader or by holding Volume Down & Power simultaneously. Then you have to connect phone to your PC (if you haven't done it yet) and flash recovery using fastboot by command "fastboot flash recovery your_recovery_image.img".

Eregus said:
https://wiki.cyanogenmod.org/w/Install_CM_for_falcon#Installing_recovery_using_fastboot
You just need to download recovery file on your computer (I recommend it), boot to bootloader, either by using adb reboot bootloader or by holding Volume Down & Power simultaneously. Then you have to connect phone to your PC (if you haven't done it yet) and flash recovery using fastboot by command "fastboot flash recovery your_recovery_image.img".
Click to expand...
Click to collapse
After doing this with TWRP, using the same method, I get an 'Unable to Boot' message. I have now however descovered MotoTool AIO and Moto G 4G EasyRecovery which I will try. (Credit to all developers who created that software)

UPDATE!!
I have now fixed my issue and have CM12 installed. Please read the edit in the first post for more infomation. Thanks to everyone who helped.

[Q] Google OG Pixel problems soft bricked

Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.

Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image

To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs

Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel

maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).