mobile app: twrp

Showing posts with label twrp. Show all posts

Monday, 19 October 2015

How to resurrect a broken TWRP Installation

Most of using Kit Kat Roms on our Picos thank thewisenerd for aw3som3 and its successor awesom3. Also we know that it requires specially patched versions of TWRP to function. Sometimes you may try to flash a non awesom3 ROM on the awesom3 based recovery which, in my case, sends TWRP into a boot loop (Ironic, considering we use recoveries to get OUT of bootloops). This got so extreme that my Pico stayed dead for nearly a MONTH, which completely stalled development on my PAC ROM port.

Now as they say, when you're a hardcore Android nerd, you don't wait for things to go right, you make them right. I managed to flash Philz 5 and get a working SlimBean on it. Flashing twrp killed both the recovery AND the ROM. Hmmm, interesting....

I then hit upon an idea which fortunately worked. It is :

Flash the kernel before the recovery.

That's it ! All that blabber gets down to this. Take the boot.img outta your ROM zip, flash it in fastboot then the recovery, and come over and thank me here before TWRP opens up in all its glory.

Sent from a Cool Phone stuck with crappy KingUser

Sunday, 18 October 2015

Android M TWRP Backup, what is "System Image?"

First time using the backup feature in TWRP and I've been searching through guides for info. From what I've found, all I need for a complete backup is system, data and boot. However, I noticed there is also an partition called "System Image" that I can't find mentioned in any backup guides or info.

Anyone know what that is?

Options:

System (1952MB)
System Image (2048MB)
Data (5083MB)
Cache (0MB)
Boot (16MB)
Recovery (16MB)
EFS (3MB)

Thanks!

Nexus 6 With No OS, Just TWRP & ADB Access

I accidentally deleted the OS on my Nexus 6 when trying to flash a new rom via TWRP.

Now I can't flash any rom including stock rom due to error message that says "unable to mount storage".

I have access to adb com with the device, but don't know how to complete process of returning phone to stock based on current problem.

Any help would be greatly appreciated.

PS: My machine is a Mac

Friday, 16 October 2015

TWRP sideload problem.

Sorry for off topic but what recovery is everyone using? I just made a switch from CWM to TWRP since development for CWM is dead but I can't get TWRP to sideload. It recognizes device until I go to Advance > ADB sideload, then it PC stops recognizing device. I've tried many different drivers, I just can't get it to work. Help, anyone using TWRP.

TWRP reboot when flashing

When I try to flash a zip in TWRP, it starts to do it's thing, but then my phone reboots. Flash didn't complete at all. I'm using twrp-2.8.7.1_CPTB-B1-hima.img but I've also had this problem with 2.8.7.0. I've disabled zip verification in settings and also on the confirm screen.

Only thing I did before this problem happened is flash elementalx kernel. I did a nandroid restore after I was unhappy with how hot the new kernel was making my phone, and then this problem started. I hope someone knows a solution to my problem. Thanks.

Bootloader is unlock and twrp coming soon

I unlocked the bootloader and working with another dev to get twrp with superuser power this weekend for you guys. Then we will start building roms for this device..

Sent from my ASUS_Z00A using Xparent BlueTapatalk 2

Help me understand File structure information when using TWRP

I've used twrp a couple times now don't understand the basic file structure of Android and what folders contain what.

If someone direct me to explanation of this it would be greatly appreciated.
I want to know the folder structure and be explained there basic content.

When using TWRP, to backup up or restore, I'm not sure what folders to select to be backed up or to restore and the concequence of selection the wrong ones.

Thursday, 15 October 2015

[FIX] Fingerprint doesn't register after TWRP restore

Hello everyone. I have figured out how to remove registered fingerprints without having to factory reset your device. So, when you create a backup and forget to delete them, you're not SOL when you restore.

Flash this file in recovery and you should be good.

What does it do? Simple, it removes /data/validity/template.db

NOTE: If you have your lock screen set up for fingerprints, this will not reset the lock screen. Upon boot, it will still think you're set up to unlock with fingerprints. You can simply use your backup password to get into your phone then go into settings and set up your fingerprints again. OR if you want, you can remove locksettings.db, locksettings.db-shm, and locksettings.db-wal from /data/system/ while in recovery.

Will this device have the twrp recovery??

First I do think flash it by computer is annoying!!!
I had read some Threads about the recovery on X86 devices,but I still failed in compiling it...
Will some one want to help me to make the recovery?
Thanks!:):):)

Heimdall For Flashing TWRP To Note 3

Hello, everybody. I just wanted to pass something on that more knowledgeable folks might already know, but I didn't know until now, so maybe someone else doesnt know and might benefit from something I just found out. I was under the impression that you couldn't use heimdall to install a custom recovery on a sammsung galaxy note 3 sm-n900t (tmo model) but had to use Odin instead. Well, what a PITA to borrow a windows puter for flashing and rooting when you are a ubuntu user! Yeah odin probably runs under vmware just fine and possibly wine too, but do I really want to try to make my linux laptop more windows-like? Nevertheless that is how I had been doing it until today.

last week I took my old tab 2 for a spin and decided it could use a more modern recovery and OS. I followed instructions (darn... i cant post the url! but just google for the title, "How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 (GSM) ("p3100")") on the CyanogenMod Wiki for installing recovery using heimdall and it went off swimmingly. I already had 3 sm-n900t devices all on CM12 and just got another one for trying other ROMs. Well, that meant I had a totally expendable note 3 to experiment with, so I thought I would give heimdall a stab at it even though I was doubtful of the outcome.

I had just bought this phone on a certain popular auction site, and rushed into flashing it without doing my homework. I stuck a TWRP 4.4 recovery in it and it took just fine, but the stupid phone wouldn't boot into recovery. Okayyyyyy... looked in About Phone and noticed the android version was 4.3. The 4.4 TWRP couldnt boot with the 4.3 bootloader onboard. So I downloaded a 4.3 TWRP, flashed, and wa lah! Now it boots right up into TWRP recovery! Just to kind of check it out and make sure it was fully functional, I flashed a CM12 nightly, a GApps package, and the most recent SuperSU straight from the sd card using TWRP and it works just fine! And it all started with flashing TWRP to the Note 3 with Heimdall on Linux instead of the usual Odin on Windohs.

So fellow linux users, don't despair. Apparently heimdall v1.4.0 will work with the Note 3. At least it did for me.

I would be most interested in anybody's results, or lack of results, of attempting to install custom recovery on the Note4 or Note5, or the latest S phones., using Heimdall/Linux.

TWRP unable to mount cache

Hello,

I'm trying to preform a factory reset, however it always fails with TWRP unable to mount the cache. I'm running TWRP 2.7.1.0 and the Hyperdrive rom. The tablet is stuck booting now as well.

Does anyone know what might be the case?

[Q] - Unlocking the bootloader, TWRP, rooting and (OTA) updates

Hi folks,
I recently got a Moto G 2nd gen. LTE that came shipped with 5.0.2 installed (the exact model is XT1072).
Now my plan is to unlock the bootloader, flash TWRP and root the phone using this tool. As far as I can see this should work fine as the device is supported and there's a TWRP version available.
My question now is: As Marshmallow is officially confirmed and I already found out that flashing a custom recovery will "break" OTA, how could I get the update once it will be released, hence will I be able to obtain further updates once I run a custom recovery and "am" rooted - as far as I know the unlocked bootloader does not affect the OTA/update functionality.

THX in advance :fingers-crossed:

Root & TWRP Lenovo Tab 2 A8-50F (MT8161)

Root & TWRP Lenovo Tab 2 A8-50F (MT8161)

Ok so this is a in depth tutorial on obtaining root and installing twrp for the device in the title. Anything in "quotes" eg, type in cmd "adb devices" quotes should be ignored. This guide is for those who know what root is and know there way around windows and Linux. If you did something wrong i am not liable and maybe you should have read things before trying.

REQUIREMENTS/DOWNLOADS:
-Windows PC & Linux (Ubuntu. virtual box would be fine although i have my pc dual booting both os's)
-Driver Signing Disabled on Windows 7 and above
-Device Drivers
-SpFlash Tool (including scatter file)
-Adb Tools
-TWRP + SuperSU Files
-Insecure Boot.img

LINK FOR ALL REQUIRED FILES >> DOWNLOAD << DOWNLAOAD AND EXTRACT TO DESKTOP

Downlaod all of the above and extract/move everything to a folder which for this guide i will assume will be called ROOT on your DESKTOP

SOME READING:
The Lenovo Tab 2 A8-50F is a rather locked down device with the ability to reflash the stock rom on every reboot if required. In this guide you can only do things in a specific order to be able to get it rooted and stop the stock recovery reflashing. It took me a few times of (soft)bricking my device before i could get it sorted to a stable rooted system with twrp installed. TWRP recovery was not built from source by me personally (it was obtained from a russian website) although i have had to modify the TWRP image as it was boot looping but its sorted and working now. So roughly this is how things are going to go, we will use SpFlash tool to readback the system partition, then use linux to modify a file in the system.img the use SpFlashtool to refalsh the modified system.img. Then we are going to unlock the bootloader and then flash an insecure boot.img along with twrp and then root using chainfire's latest binarys.

THE GUIDE:
STEP 1 - installing the drivers

STEP 2 - backing up system partition

STEP 3 - editing the system.img

STEP 4 - unlocking bootloader

STEP 5 - flashing insecure boot.img

STEP 6 - flashing modified system.img

STEP 7 - flashing TWRP recovery

STEP 8 - flashing Supersu by Chainfire

After following the above steps you will have a fully rooted device wich can be backed up via twrp and flashed via twrp. now i have figured this out, i think its someone elses turn to build a rom for it :) preferably Cyanogenmod :P Thanks for reading this guide and all the best luck with your new rooted device. please remember to click thanks.

Want to update to lollypop a rooted Twrp installed and bootloader unlocked mobile

Hii guys sorry if I post it in wrong place. I was unlocked the bootloader recently by htc dev and install twrp... Then I flashed SuperSU to gain root. Now an update come of 990 mb of size and this is clearly mention that this is lollypop update. My mobile is S-ON. I want to update my mobile to lollypop but don't want to become a brick maker. :).... So pls guide me.... My mobile is htc desire 820 Indian version

help please twrp not installing anything lenovo a526

no os installed flashing on my phone on twrp v 2.5.0.0. i installed custom rom to
lollipop and i have no back up. it turns some laggy thing. and i factory reset it. and boom. no os installed. what should i do? please help me.. its lenovo a256:crying::crying::crying:

[Q] TWRP

Hello, everyone, I am using D5833
After the Sony service centre maintenance (change Motherboard)
I use TWRP to installing the pre-root zip(23.4.A.1.232) on 23.4.A.1.200, then it die, here is my step:
1. use PRFCreator_v1.0 to create the pre-root zip(23.4.A.1.232_HK, SU2.49, XZDR_2.8.21)
2. Flash the 23.0.A.2.93_HK (KK) ftf using FlashTool
3. Root using giefroot_v3.1 then install recovery with XZDR_2.8.21
4. wipe dalvik cache, system, cache,date, internal storage using TWRP
5. restore the backup(23.4.A.1.200_TW) data and installing pre-root zip(23.4.A.1.232_HK) with xposed_v75 (power 99%)
6. reboot to system

then it power off, I cannot boot into the bootloader, recovery or system, and red LED flashing when usb port connect
red LED open when usb connect and push power in the same time
no respond when charging power(not usb port)

and 5 hour later, Sony service centre change another motherboard
it can boot on 232, but when I root it in to step5 without xposed and reboot...........it have same problem

is the motherboard change, then the data cannot use again in TWRP? something missing in the step? or the version cannot 200TW up 232HK?

thanks

Sunday, 4 October 2015

Materialized TWRP theme by z31s1g

I love the material theme for TWRP by z31s1g, so posting a link to the material thread and downloads folder. No mirrors please as requested by the developer.

Link to the Downloads:
1080 Download folder

Link to the original post
http://forum.xda-developers.com/andr...-play-t2915584

Just one thing more:
I couldnt put the theme zip using file manager neither through terminal emulator. As a work around I used the file manager in TWRP to move the zip and reloaded the theme. Hope to confirm this from others whether this is a bug or just one off trouble just affecting me.

Un-Official Breadcrust's TWRP 2.8.7.0 Recovery for ZUK Z1

Quote:

/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards and so on. YOU are choosing to make these modifications.
* Bug reports or confirmation of working things are welcome.
*/

There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.

FAQ

What will I need?

First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.

Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.

Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type

Code:

adb devices

It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.

Code:

adb devices

You will also need to download the TWRP image from the spoiler below.

Download

If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!

Guide

Type:

Code:

adb reboot bootloader

You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with

Code:

-i 0x2b4c

.

Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.

To check type:

Code:

fastboot -i 0x2b4c oem get-device-info

If it returns:

Quote:

(bootloader) Device unlocked: true

Then you are ready to begin the flashing process.

Move the downloaded file to your platform tools folder and type:

Code:

fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust.img

If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.

Help Needed Bad on TWRP password

Password wanted by TWRP and I rooted my phone with Click To Root, I never gave them a password and when I try to do a Factory reset their screen comes up. to wipe, restore, and other utilities such as that. As far as the pass word goes I cant remember that and don't ever put one in just for this reason. Click to root support sucks because if I want to chat with an analyst it cost like .00 and they have a email support which I have heard nothing back from. also my screen is saying I have an available system update, I don't know if this has anything to do with the password?

Kindle Stuck At TWRP BootScreen

Help! I tried to factory reset my Kindle Fire HD 7 (2012) running CM 12.1. When I clicked factory reset the Kindle said rebooting and rebooted in TWRP's loading screen and flashes every 3 seconds or so. I tried to boot it into fast boot mode using ADB but it keeps saying device unauthorized. I don't know what to do from here now.

P.S I live in a place where it would be very hard to obtain a fastboot cable and I don't have the necessary tools to build one

Any amount of help would be greatly appreciated :good: