Develop Bugs

[Q] TWRP

I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?

MColbath said:
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
Click to expand...
Click to collapse
Do you still have root? What was the error?

There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app

MColbath said:
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you outline the exact steps you are doing to flash?

mdamaged said:
Can you outline the exact steps you are doing to flash?
Click to expand...
Click to collapse
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.

MColbath said:
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
Click to expand...
Click to collapse
In the process of resetting back to factory, did it relock your bootloader? I ask only because some tools do this automatically. I had to ask.

mdamaged said:
In the process of resetting back to factory, did it relock you bootloader? I ask only because some tools do this automatically. I had to ask.
Click to expand...
Click to collapse
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.

MColbath said:
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
Click to expand...
Click to collapse
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it (a suggestion to use goo was here, but forget that).
If you can boot into twrp using the above suggestion, you can at least root and get some stuff done while waiting for a fix or update or someone more knowledgeable than I to solve your issue.
The only thing I can think of is that the bootloader changed and we are back to where you started, waiting for them to update it for your bootloader.

mdamaged said:
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it and try using...goo manager (never used this myself heard some good, some bad things, about it YMMV etc etc).
Click to expand...
Click to collapse
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.

MColbath said:
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
Click to expand...
Click to collapse
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.

mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Okay seems good.

mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.

MColbath said:
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
Click to expand...
Click to collapse
No problem, thanks for the update.

mdamaged said:
No problem, thanks for the update.
Click to expand...
Click to collapse
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.

MColbath said:
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
Click to expand...
Click to collapse
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or location or added a new one (with a diff name) or did something with the permissions so it could not be renamed, and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.

mdamaged said:
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or added a new one (with a diff name), and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
Click to expand...
Click to collapse
Yeah there are new backup files all over the place in System partition.

MColbath said:
Yeah there are new backup files all over the place in System partition.
Click to expand...
Click to collapse
Stupid providers.

mdamaged said:
Stupid providers.
Click to expand...
Click to collapse
I'm checking the developer block section of recovery right now.
I'll upload the log for the recovery too. Hold on.

Here it is.

MColbath said:
Here it is.
Click to expand...
Click to collapse
Is there a file in /system named recovery-from-boot.p?

dualrecovery not working when coming from D5503_14.4.A.0.108 ?

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 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)) and repeated the procedure. Again, I'm stuck with a TWRP that won't recognize its own backup and a broken CWM. Therefore my question: Am I doing something wrong? Did this tool chain (upgrade to 108 -> EasyRootTool -> lockeddualrecovery) work for anybody else?

matt.s said:
Hello folks,
1) I received the 108 update OTA. 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,
Click to expand...
Click to collapse
You should use search function or read a bit more in the Recovery thread:
.129 beta doesn´t work with 14.4.A.0.108.
Use instead .128 beta recovery and everything runs fine!

czrtst said:
You should use search function or read a bit more in the Recovery thread:
.129 beta doesn´t work with 14.4.A.0.108.
Use instead .128 beta recovery and everything runs fine!
Click to expand...
Click to collapse
Thanks, I read a lot but somehow this skipped my attention... :-/

matt.s said:
Thanks, I read a lot but somehow this skipped my attention... :-/
Click to expand...
Click to collapse
No problem

czrtst said:
You should use search function or read a bit more in the Recovery thread:
.129 beta doesn´t work with 14.4.A.0.108.
Use instead .128 beta recovery and everything runs fine!
Click to expand...
Click to collapse
Hmm strange, im on 14.4.A.0.108 and .129 Beta work like a charm....

ThreeMMM said:
Hmm strange, im on 14.4.A.0.108 and .129 Beta work like a charm....
Click to expand...
Click to collapse
Yes, only TWRP but not CWM.

how about 131?

acme64 said:
how about 131?
Click to expand...
Click to collapse
Try it with .132 and let us and @[NUT] know if it works !
http://forum.xda-developers.com/showpost.php?p=53809938&postcount=2392

14.4.A.0.108
for me been exactly same,i still on 757

OP3 TWRP not Booting

Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.

Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it

SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Thanks for the reply.
Are you sure what happened to is exactly what happened to you? Because I tried the ToolKit and it is not working. I tried both the versions of the TWRP and Stock recovery.
If you know anything else about this issue that would help me. I'd love to hear it.

SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Also. Does encryption affect this in anyway, because I did it. I don't want to factory reset my phone because this is my primary phone and I don't have another phone. And I don't want to risk it, at least for a few days.

malachiseelam said:
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Click to expand...
Click to collapse
Modified TWRP version should do it

Same, when I flashed cm 14.1 I also got blank TWRP.

michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Then, what did you do?

LS.xD said:
Modified TWRP version should do it
Click to expand...
Click to collapse
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.

malachiseelam said:
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
Click to expand...
Click to collapse
Thanks it worked!

Please try the modified TWRP, 3.0.2-22

[TUTORIAL][ROM][CM14.1] OFFICIAL CyanogenMod 14.1 for Android One 2nd Gen on WF Swift

Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.

Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ

Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms

DonQuichotte said:
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Click to expand...
Click to collapse
Flash the factory image.

[email protected] said:
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
Click to expand...
Click to collapse
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?

seb5049 said:
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
Click to expand...
Click to collapse
Yeah I would like to know too

VivaLaVent said:
Flash the factory image.
Click to expand...
Click to collapse
I'm not sure this is enough, cause with the GM4G rom some partitions (.img) get flashed, that are not in the swift factory rom...oem.img, devinfo.bin. I think about switching to seed, cause no more nigthlies and seed has official CM14.1 already. But there has to be a bullet-proof way to return to stock...just in case.
bye DonQ

twrp patched by Arvin Quilao
VivaLaVent said:
Yeah I would like to know too
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....

[email protected] said:
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
Click to expand...
Click to collapse
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.

Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....

Twrp version status...
VivaLaVent said:
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Click to expand...
Click to collapse
Yeahhh it isnt the latest i know. The latest is 3.0.2-1 but isnt patched for cm ota updates like that shared by me later. The dev stated the official version patched from twrp website will come later. Using it dnt create any prblm.

piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I'm having the same problem.

seb5049 said:
I'm having the same problem.
Click to expand...
Click to collapse
I'm starting to think I made an error, can anyone confirm they successfully used this method?

VivaLaVent said:
I'm starting to think I made an error, can anyone confirm they successfully used this method?
Click to expand...
Click to collapse
I was unsuccessful with your method. I even tried two times then I gave up and restored my backup with cm-13

How is it running on CM 14? Is there noticeable lag and such?

If you want CM14, try crDroid, it works great. I'm using it for two weeks now, no FC errors, good battery performance, no serious lags.
When I read the bricks of some users trying to flash a ROM that is meant for a clone with ALMOST the same hardware - I won't try this.

I am considering doing this update. But I have an issue. Since Android 6 has integrated sdcards, I had to reformat the sdcard on every update which is a pain in the ass. I using mixed mode. Is there any way to do an update which allows to reintegrate the sdcard without reformatting the sdcard?

piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I seem to have the same problem as you, device doesn't respond, no boot or whatever.
Could you link me to the solution you used to unbrick the device?

Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.

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