Develop Bugs

Update TWRP

I bought a used phone that already has TWRP 2.3.3.1 installed. I'm trying to update the rom in used, but first need to update TWRP to 2.7.0.0 (since I receive a set_metadata_recursive failure). I tried with goomanager, it says it updated recovery sucessfully, but when booting, still have 2.3.3.1. I tryed using dd, but still have the old version. Seems the only solution left is Odin, which require windows ? That I don't have.
Any other solution to update TWRP ?
Kristian

Try flashify root
Sent from my LG-D800 using Tapatalk

In goo change your download directory to external SD been the only way I have gotten goo to install twrp on any of my phones
Making the iPhone jealous one user at a time.

kbenoit said:
I bought a used phone that already has TWRP 2.3.3.1 installed. I'm trying to update the rom in used, but first need to update TWRP to 2.7.0.0 (since I receive a set_metadata_recursive failure). I tried with goomanager, it says it updated recovery sucessfully, but when booting, still have 2.3.3.1. I tryed using dd, but still have the old version. Seems the only solution left is Odin, which require windows ? That I don't have.
Any other solution to update TWRP ?
Kristian
Click to expand...
Click to collapse
Have you tried mobile odin? Also lots of people having problems with latest twrp, but the most recent 2.6 (can't remember the whole version #) works fine

Thanks
mkfryan said:
In goo change your download directory to external SD been the only way I have gotten goo to install twrp on any of my phones
Click to expand...
Click to collapse
Thanks I did exactly that and it worked ! I dont dont know what might be screwed by dd on /dev/mmcblk0p18 ?
That was great help !

kbenoit said:
Thanks I did exactly that and it worked ! I dont dont know what might be screwed by dd on /dev/mmcblk0p18 ?
That was great help !
Click to expand...
Click to collapse
Awesome glad that helped you!
Making the iPhone jealous one user at a time.

dualrecovery not working after using EasyRootTool ?

Hello folks,
I just spend a couple of hours trying to get some new software on my Z1C. My inital plan was to flash PA 4.4 final, but that didn't really work out. Here's what happend:
1) I received the 108 update OTA. I used EasyRootTool ( ht tp://forum.xda-developers.com/showthread.php?t=2784900) with option 2 to regain root access. That seemed to work so far. Afterwards I tried to installed lockeddualrecovery using the Z1C-lockeddualrecovery2.7.129-BETA.installer, and here things started to get strange. I couldn't boot into CWM, so I made a backup using TWRP.
2) I unlocked my bootloader
3) I flashed PA following the instructions given in the thread: ht tp://forum.xda-developers.com/showthread.php?t=2764775
4) I was stuck with a bootloop, showing the PA start screen.
So I tried to roll back using the TWRP backup I made before unlocking the bootloader, but TWRP won't recognize the backup. I tried putting it in a folder named TWRP, directly into the root folder, interal SD, external SD...all the same, it just doesn't show up. I also can't install one of my older CWM backups, as trying to boot into CWM leads to a bootloop showing the "SONY" screen.
So I decided to flash a stock ROM (D5503_14.4.A.0.108_GenericDE_(1279-6978)) using flashtool and repeated the procedure. Again, I'm stuck with a TWRP that won't recognize its own backup and a broken CWM. Same if I start with D5503_14.3.A.0.757_GenericDE_(1279-6978).
Finally I managed to install CWM using the older version Z1C-lockeddualrecovery2.7.128-BETA.installer.zip. My question therefore: Was I doing something wrong or could this be a bug in Z1C-lockeddualrecovery2.7.129-BETA.installer.zip?

matt.s said:
Hello folks,
My question therefore: Was I doing something wrong or could this be a bug in Z1C-lockeddualrecovery2.7.129-BETA.installer.zip?
Click to expand...
Click to collapse
It`s a bug, you didn´t made something wrong!

czrtst said:
It`s a bug, you didn´t made something wrong!
Click to expand...
Click to collapse
Thanks, so if I'm using Z1C-lockeddualrecovery2.7.128-BETA and follow the instructions from the PA 4.4 thread, it shouldn't matter if I come from 108 or 757 right? Right now I'm on 757, so I would prefer to upgrade from here straight to PA 4.4

czrtst said:
It`s a bug, you didn´t made something wrong!
Click to expand...
Click to collapse
I have the same problem. Somebody tried it with new version (Z1C-lockeddualrecovery2.7.130-BETA.installer)?

lovasjoe said:
Somebody tried it with new version (Z1C-lockeddualrecovery2.7.130-BETA.installer)?
Click to expand...
Click to collapse
Doesn`t work with CWM:
http://forum.xda-developers.com/showpost.php?p=53783354&postcount=2378

Use 128 beta and you'll be fine. 129 didn't work for me either.

crótach said:
Use 128 beta and you'll be fine. 129 didn't work for me either.
Click to expand...
Click to collapse
It works with Z1C-lockeddualrecovery2.7.132-BETA! :laugh:

lovasjoe said:
It works with Z1C-lockeddualrecovery2.7.132-BETA! :laugh:
Click to expand...
Click to collapse
confirm Z1C-lockeddualrecovery2.7.132-BETA

[Q] TWRP on Note 10.1 2014 WiFi - Touchscreen not working

I installed TWRP on my Note 10.1 2014 through the play store app. Once I installed the recovery image, I tried rebooting into recovery and it would only boot to the OS.
I went into the app and rebooted to recovery from there and it did go into TWRP, however, there is no response on the touchscreen or any other button but power, which causes it to reboot back into TWRP.
I haven't been able to find a way to get back to the OS or do anything else.
Can anybody help me out? I'm very new to this, I had it rooted and tripped the warranty bit a while back but that's all I've done. I just want to upgrade to KK, which I can't do since the warranty bit has been tripped. (I'll go to Lollipop if I can, but I have a few apps I want that need at least KitKat.)
Thanks in advance for any help you can provide!!

2.8.7.0?
Sent from my SCH-R530U using Tapatalk

Orion116 said:
2.8.7.0?
Sent from my SCH-R530U using Tapatalk
Click to expand...
Click to collapse
Yes, it was 2.8.7.0. After doing some more searching, I found out how to flash TWRP with Odin and got 2.8.6.0 working. I now have it fixed running Lollipop.

jbrewer8 said:
Yes, it was 2.8.7.0. After doing some more searching, I found out how to flash TWRP with Odin and got 2.8.6.0 working. I now have it fixed running Lollipop.
Click to expand...
Click to collapse
Thank you sir. Exactly the same problem here: No touchscreen on SM-P600, stuck on recovery boot loop, and had to flash TWRP through ODIN to get out. Now in 2.8.6.0 and everything is working now.

Hi.
Anybody could tell me how solve this problem?. Me too installed TWRP 2.8.7.0 in my Samsun SM-P600 but touchscreen does not work. Shutdown the tablet doesn't work, only return to TWRP.
Ashade mentioned: "had to flash TWRP through ODIN", but, if there is a guide let me know, because I don't wanna break my tablet more.
This of root and flash is new for me.

sanyick said:
Hi.
Anybody could tell me how solve this problem?. Me too installed TWRP 2.8.7.0 in my Samsun SM-P600 but touchscreen does not work. Shutdown the tablet doesn't work, only return to TWRP.
Ashade mentioned: "had to flash TWRP through ODIN", but, if there is a guide let me know, because I don't wanna break my tablet more.
This of root and flash is new for me.
Click to expand...
Click to collapse
Go here and read thread #6 and #7. After you flashed twrp 2.8.7.0, you need to use your spen to navigate and it's very sensitive so be careful not to click on the wrong option. Good luck.
http://forum.xda-developers.com/gal...-easily-root-modifying-kernel-how-to-t3242644

Ashade said:
Thank you sir. Exactly the same problem here: No touchscreen on SM-P600, stuck on recovery boot loop, and had to flash TWRP through ODIN to get out. Now in 2.8.6.0 and everything is working now.
Click to expand...
Click to collapse
There is a version of 2.8.7.0 with fully working touch and other tweaks. This one: https://basketbuild.com/devs/Joshndroid/TWRP/lt03wifi which is compiled to support F2FS, but works just fine.

Thanks all... I never thought to use the Spen. I gonna follow your tips. regards.

buhohitr said:
Go here and read thread #6 and #7. After you flashed twrp 2.8.7.0, you need to use your spen to navigate and it's very sensitive so be careful not to click on the wrong option. Good luck.
http://forum.xda-developers.com/gal...-easily-root-modifying-kernel-how-to-t3242644
Click to expand...
Click to collapse
I stuck on it for almost half an hour keep on reflash different version twrp..hahahaha..
thank for your help. bro happy new year

Root not working on m9 with twrp 2.8.7.0 using chainfire, need help.

I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.

Jerry060599 said:
I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Click to expand...
Click to collapse
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.

LLegion said:
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
Click to expand...
Click to collapse
tks for the help . will be trying it out.

Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance

LLegion said:
Of u still have issues i can give whatsapp and help you with further assistance
Click to expand...
Click to collapse
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.

Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance

Jerry060599 said:
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Click to expand...
Click to collapse
Look at post 3 in this thread. Best is you read all information in the first three posts.

Here u havebaccess to my personal folderhttps://drive.google.com/folderview?id=0B--58xBx8PTOfmYyeDdXeFJ1ZnRSdGJTVnVhQTJQZUZiMG5uRWl0blNackNWMVU1NUNoVjg&usp=sharing

Flippy498 said:
Look at post 3 in this thread. Best is you read all information in the first three posts.
Click to expand...
Click to collapse
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.

Jerry060599 said:
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Click to expand...
Click to collapse
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now

dragonesdenano said:
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
Click to expand...
Click to collapse
Sorry for the (extremly) late reply. I had not been home for the past week. I tried restoring to stock system image and flashin su binaries before. It didnt work. At this point, I suspect that the only reason why I can't flash supersu is because of my firmware version. So I'll be wimpering in a corner untill some kind devs at htc decide to release the source for my version.

My GX8 is starting TWRP automatically at every start

Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx

dg89 said:
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
Click to expand...
Click to collapse
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79

tiklmypikl said:
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
Click to expand...
Click to collapse
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working

dg89 said:
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
Click to expand...
Click to collapse
What verison of TWRP are you on?

tiklmypikl said:
What verison of TWRP are you on?
Click to expand...
Click to collapse
right now it is on v2.8.7.0 and i tried to install the new version but it's not working