Develop Bugs

twrp 2.6.3.1 questions

I heard that data mounting is broken and can't seem to find a file for it...I want kitkat
So...the questions are:
Where can I download it?
Is data mounting broken?and what do they mean by "data mounting?" Am I better off waiting for a new fixed version of twrp? Possibly 2.6.3.2 will be out soon?

bumping for answers. Im looking for the latest TWRP as well.

djkozdefantastico said:
bumping for answers. Im looking for the latest TWRP as well.
Click to expand...
Click to collapse
Thanks for the bump.I really want kitkat on my fire as I haven't got it on my nexus 7 2013 or obviously my 2012 nexus 7 that doesn't respond to touch...

I actually haven't heard anything about the data mounting being broken. I just flashed the newest version with flashify. And I'm running CM11 now.
Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify
The latest TWRP
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.6.3.1-otter.img
After installing TWRP, I flashed the rom and gapps which i got here.
http://forum.xda-developers.com/showthread.php?t=2397942
Hope this helps

VTCruzer said:
I actually haven't heard anything about the data mounting being broken. I just flashed the newest version with flashify. And I'm running CM11 now.
Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify
The latest TWRP
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.6.3.1-otter.img
After installing TWRP, I flashed the rom and gapps which i got here.
http://forum.xda-developers.com/showthread.php?t=2397942
Hope this helps
Click to expand...
Click to collapse
I usually flash twrp in twrp.

Jacobloveskindles said:
I usually flash twrp in twrp.
Click to expand...
Click to collapse
You can flash a recovery in a recovery?

VTCruzer said:
You can flash a recovery in a recovery?
Click to expand...
Click to collapse
I did that with my upgrade from 2.2.2.1 to 2.5.0...

Jacobloveskindles said:
I heard that data mounting is broken and can't seem to find a file for it...I want kitkat
So...the questions are:
Where can I download it?
Is data mounting broken?and what do they mean by "data mounting?" Am I better off waiting for a new fixed version of twrp? Possibly 2.6.3.2 will be out soon?
Click to expand...
Click to collapse
You are correct. Data mounting is broken for me and some others on the KF Sub-Forum. So if I were you, I would wait about a month or 2. If you can't, oh well. You were warned
EDIT: Made a guide. Flash TWRP first but if you have problems with it after you install it like I had (data mount errors), then follow this guide to fix it.

cant get newer twrp to work
I am having trouble with getting the newer versions of twrp to boot up correctly. I have manually flashed all the most recent versions of TWRP with command prompt, I even used flashify but every version would either freeze at the teamwin logo or would not boot into recovery at all. I went down the list (downloaded and installed each version) and the only version of twrp that would work on my kindle is 2.4.0. Even after doing this, I cant seem to get passed the boot animation when flashing roms, the boot animation is off centered and cut off to the top right. The boot animation would play then freeze then would start a boot loop. I wiped all data, cache and everything else needed before and after flashing the rom but no results. Can someone please help me out?

VTCruzer said:
I actually haven't heard anything about the data mounting being broken. I just flashed the newest version with flashify. And I'm running CM11 now.
Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify
The latest TWRP
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.6.3.1-otter.img
After installing TWRP, I flashed the rom and gapps which i got here.
http://forum.xda-developers.com/showthread.php?t=2397942
Hope this helps
Click to expand...
Click to collapse
Flashify did the trick... Thanks a lot!

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

Stuck after Install Rom

Hello to everyone ,
i installed miui v6 to my M8 and after that i cant flash any other rom.
I install a new rom from zip but after the reboot it stucks on the first screen of the new rom.
Waited for 3 hours but nothing.
What do you suggest ?

alexis333 said:
Hello to everyone ,
i installed miui v6 to my M8 and after that i cant flash any other rom.
I install a new rom from zip but after the reboot it stucks on the first screen of the new rom.
Waited for 3 hours but nothing.
What do you suggest ?
Click to expand...
Click to collapse
simple question, do you flashed the boot.img inside the rom using fastboot?(fastboot flash boot boot.img)

Simple answer.
No.
Now what ?

Husky34 said:
simple question, do you flashed the boot.img inside the rom using fastboot?(fastboot flash boot boot.img)
Click to expand...
Click to collapse
This isn't normally required on the M8, unless its some quirk specific to MIUI (which is a ROM I don't a have much knowledge of).
Make sure your TWRP version is up to date.
Make sure your hboot is up to date.
Wipe user data and cache (default wipe in TWRP) before flashing the ROM.
Those are the most common reasons for no boot after flashing multiple ROMs.

I dont use TWRP. I use Philz Touch recovery.
Where can i download latest TWRP ?

alexis333 said:
I dont use TWRP. I use Philz Touch recovery.
Where can i download latest TWRP ?
Click to expand...
Click to collapse
That may be the issue right there. I know some folks are still using it, but Philz hasn't been updated in a long time. And since some newer ROMs have issues with older TWRP builds, I would assume the same would be true with Philz.
You can get TWRP here: https://dl.twrp.me/m8/

alexis333 said:
I dont use TWRP. I use Philz Touch recovery.
Where can i download latest TWRP ?
Click to expand...
Click to collapse
https://twrp.me/devices/htconem8gsm.html

I flashed TPWR and then flashed the new ROM and everything ok.
Thanx for your help men ..

alexis333 said:
Thanx for your help men ..
Click to expand...
Click to collapse
There's a button for that.
Happy it worked for you.

Help- stuck on TWRP after cm14 update

***SOLVED***
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?

lsdream said:
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
Click to expand...
Click to collapse
what version of twrp are you running? do you have a nandroid backup that you could restore? sometimes the partitions can get messed up during an update. if nothing helps, just follow this unbrick guide which will revert your phone completely back to stock, with all the storage partitions intact.

3.0.2-1

lsdream said:
3.0.2-1
Click to expand...
Click to collapse
yeah, everyone's got that one, but there are many versions of it usually a number, like 3.0.2-1 (22) for example, and each one build for specific cases. except you got it from the official twrp web, then there shouldn't really be problems with cm14.1
what about nandroid? can you restore one?

do you have any idea how to boot it?

lsdream said:
do you have any idea how to boot it?
Click to expand...
Click to collapse
please use the quote function so i get a notification when you reply.
i do, right in my first post here is a link to an unbrick guide which will help you because clearly something in your phone's storage is messed up. just follow it and you'll be back at stock with a fully functional phone

bombaglad said:
please use the quote function so i get a notification when you reply.
i do, right in my first post here is a link to an unbrick guide which will help you because clearly something in your phone's storage is messed up. just follow it and you'll be back at stock with a fully functional phone
Click to expand...
Click to collapse
Thanks, I just flash the stock rom and it boot normally.

lsdream said:
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
Click to expand...
Click to collapse
I had the same situation. You get out of this by fastboot flashing cm recovery, booting to it, then flash twrp back in fastboot. I think the ota doesnt fully work with twrp.

Flash the modified twrp from the second post in this forum
http://forum.xda-developers.com/oneplus-3/how-to/rom-community-build-3-5-5-t3490939

Device turns off randomly after root

Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?

cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom

niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..

cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me

Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!

If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!

cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.

Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.

cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.

Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.

cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.

Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display

the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!

cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.

the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do

cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.