Hi,
Trying to dualboot OOS and stock. Anyone got this working on oreo only?
matteosaeed said:
Hi,
Trying to dualboot OOS and stock. Anyone got this working on oreo only?
Click to expand...
Click to collapse
There is not a solution that is confirmed to work on the op5t, multirom was released for the op5 but needs to be ported over to 5t. feel free to work on the port!
Misanful said:
There is not a solution that is confirmed to work on the op5t, multirom was released for the op5 but needs to be ported over to 5t. feel free to work on the port!
Click to expand...
Click to collapse
I came across this and was asking. Seems like it has a few downloads wasn't sure if someone had used it.
https://androidfilehost.com/?fid=745849072291693835
matteosaeed said:
I came across this and was asking. Seems like it has a few downloads wasn't sure if someone had used it.
https://androidfilehost.com/?fid=745849072291693835
Click to expand...
Click to collapse
Hmmm. If you test it please report back here how it worked for you!
matteosaeed said:
I came across this and was asking. Seems like it has a few downloads wasn't sure if someone had used it.
https://androidfilehost.com/?fid=745849072291693835
Click to expand...
Click to collapse
I tried it last night. It works, I was able to dual boot. You must download the custom TWRP by the same guy for the 5t. The custom twrp is outdated so it won't read my ntfs formatted portable hard drive. You must also be decrypted.
cubandanger05 said:
I tried it last night. It works, I was able to dual boot. You must download the custom TWRP by the same guy for the 5t. The custom twrp is outdated so it won't read my ntfs formatted portable hard drive. You must also be decrypted.
Click to expand...
Click to collapse
Hey, thanks for trying this. Did you flash any roms?
matteosaeed said:
Hey, thanks for trying this. Did you flash any roms?
Click to expand...
Click to collapse
Yes. I flashed Omni as secondary, although I had to remove the assert lines in the updater script. Then it failed to install magisk on secondary, so to make it work I had to swap primary and with secondary, Flash what I needed to Omni as primary, then swap it again. Pain sticking but worked.
I wonder how hard would it be to update the custom twrp with the most recent changes in regular twrp.
Sounds interesting, what was your other room?
Any chance you tried to restore a nandroid backup as second rom?
pargas said:
Sounds interesting, what was your other room?
Any chance you tried to restore a nandroid backup as second rom?
Click to expand...
Click to collapse
I was using codename Phoenix as primary. I didn't try backing up or restoring using the customer twrp
Anybody that knows anybody that would be able to use the twrp and multirom source and update the recovery with most recent changes?
Related
This is a source-built version of CWM version 6.0.4.9 for Oneplus ONLY. Do not attempt to use this recovery on any other device.
Tested on Oneplus 64 Gb and 16 GB
Features:
OpenRecoveryScript-compatible
Backup/Restore
Mount/Unmount/Format Partitions
Warnings:
- I am not to be held responsible if you brick your device using this.
Bugs:
I have not managed to find any. If you find one, feel free to let me know.
Additional Notes:
- I will attempt to maintain this in my spare time. If a new release comes out that you are interested in and I have not updated yet, feel free to let me know.
- To flash this unzip files and click on recovery_start.bat
- To flash via fastboot, use only the Recovery Image File.
Download:
Version 6.0.4.9 (June 11th, 2014)
Link
http://d-h.st/XZ9
EDIT: Typo corrected in OP.
dansou901 said:
Kindle Fire HD 7? In Oneplus One section?
Click to expand...
Click to collapse
sorry typo error. Recovery is for oneplus
@acer73 any chance at compiling the touch version?
dmo580 said:
@acer73 any chance at compiling the touch version?
Click to expand...
Click to collapse
This is last ver with swipe (touch)
acer73 said:
This is a source-built version of CWM version 6.0.4.9 for Oneplus ONLY. Do not attempt to use this recovery on any other device.
Tested on Oneplus 64 Gb and 16 GB
Features:
OpenRecoveryScript-compatible
Backup/Restore
Mount/Unmount/Format Partitions
Warnings:
- I am not to be held responsible if you brick your device using this.
Bugs:
I have not managed to find any. If you find one, feel free to let me know.
Additional Notes:
- I will attempt to maintain this in my spare time. If a new release comes out that you are interested in and I have not updated yet, feel free to let me know.
- To flash this unzip files and click on recovery_start.bat
- To flash via fastboot, use only the Recovery Image File.
Download:
Version 6.0.4.9 (June 11th, 2014)
Link
http://d-h.st/XZ9
Click to expand...
Click to collapse
grazie mille
ha qualche bug ?
Don't quote OP and please use English.
good news!thanks!
Dualboot
Hi everyone
I have a Xiaomi M2s right now and the thing i like the most about the device is that it has 2 system partitions and that I can install MIUI on my first partition and CM11 on my second partition. This is ideal if you want to test a ROM but keep one stable system.
Is there any chance that there will be a way to re-partition the one plus to have this? Also CMW would need to have true dual boot right or is this a stock feature?
I don't know if partitioning is common on other devices?
The backups created appear to not have the correct dates for filenames. They start with 1970...
Is this a offical build? Will it be listened on clockworkmod.com anytime soon?
Does anybody have problems with mounting the SD card through CWM? On my device CWM wont backup because of not being able to mount the sd card. I solved this error by reflashing CWM through fastboot, but why does this error occur?
fiz:ik said:
Does anybody have problems with mounting the SD card through CWM? On my device CWM wont backup because of not being able to mount the sd card. I solved this error by reflashing CWM through fastboot, but why does this error occur?
Click to expand...
Click to collapse
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
MontAlbert said:
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Had the problem with Mahdi rom and Philz or cwm ... Hope they will fix this soon !
I found this .. Not really perfect :/ http://forum.xda-developers.com/showpost.php?p=54112729&postcount=24
MontAlbert said:
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm on stock CM11S
I'm try to build a lot of rom but all of these bootloop or take a lot of time to start, or data partition unmount itself after a reboot.
No issue using PA version 20140708
So I think there is some issue in the last sources,otherwise if it was a problem of recovery also paranoid should have bootloop.
Now I'm trying to build PA with last sources
what about an update?touch edition?
blade_ said:
what about an update?touch edition?
Click to expand...
Click to collapse
Would be great, I hate TWRP and Philz, too. CWM is sufficient, but this project here looks abandoned
blade_ said:
what about an update?touch edition?
Click to expand...
Click to collapse
I actually hate recovery touch editions! When I had the ghost touches it f*cked up everything in recovery.
wacky.ddw said:
I actually hate recovery touch editions! When I had the ghost touches it f*cked up everything in recovery.
Click to expand...
Click to collapse
no problems in all my phones with touch
Original Thread by Philz3759:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Recovery Package [Goo]
http://goo.im/devs/playground/trltesku/
This is the CWM-based Philz Touch Recovery with a shiny new kernel, SELinux tweaks, and some other modifications that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Kernel: http://forum.xda-developers.com/note-4/unified-development/kernel-dealers-choice-t2915824
Device: https://github.com/StarKissed/android_device_samsung_trltetmo
[Recovery]Philz Touch Recovery - Ported to North America
The initial version uses a kernel for the N910W8 and SELinux policy settings from the N910T. If that combination works for me, I can almost guarantee it will work on either of those devices because those values would not match up.
re: Philz Custom Recovery
twistedumbrella said:
Original Thread by Philz3759: http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Download from Mega
https://mega.co.nz/#F!l1RBBbDI!KHcF184rkhshJhdF_tO7gw
Download from Goo
http://goo.im/devs/playground/trltetmo/recovery
This is the CWM-based Philz Touch Recovery with a shiny new kernel and some other minor tweak that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Click to expand...
Click to collapse
Thanks for sharing Philz Touch Recovery for our N910T, it's always good to
have a backup custom recovery just in case twrp ever stops working properly.
Misterjunky said:
Thanks for sharing Philz Touch Recovery for our N910T, it's always good to
have a backup custom recovery just in case twrp ever stops working properly.
Click to expand...
Click to collapse
Yeah, I used to just make my own but it's far easier to outsource the core and then replace it with the kernel I'm already working on.
Kernel control apps
twistedumbrella said:
Yeah, I used to just make my own but it's far easier to outsource the core and then replace it with the kernel I'm already working on.
Click to expand...
Click to collapse
Just out of curiosity, in your opinion what is the best app at the play store which
is fully compatible and easy to use with your StarKissed kernels that even noobs
can use without fear of messing anything up when changing the kernel settings?
Thanks!
Thanks.....will wait for corrected upload
louforgiveno said:
Thanks.....will wait for corrected upload
Click to expand...
Click to collapse
It should be uploaded in the next minute or two to Mega and shortly after for Goo
These links not working?
Hanoverfiste said:
These links not working?
Click to expand...
Click to collapse
They should be. I just tried them and they did
twistedumbrella said:
They should be. I just tried them and they did
Click to expand...
Click to collapse
I read back and saw where Tapatalk won't work properly, so I tried through Chrome and that's not working either.
Hanoverfiste said:
I read back and saw where Tapatalk won't work properly, so I tried through Chrome and that's not working either.
Click to expand...
Click to collapse
Mega was the issue on the device, so there is a Goo mirror below it. That should be working.
Or it would have been if I remembered I changed folders on Goo. Now it does.
twistedumbrella said:
Original Thread by Philz3759:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Download from Mega:
https://mega.co.nz/#F!l1RBBbDI!KHcF184rkhshJhdF_tO7gw
Download from Goo:
http://goo.im/devs/playground/trltesku/recovery
This is the CWM-based Philz Touch Recovery with a shiny new kernel, SELinux tweaks, and some other modifications that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Kernel: http://forum.xda-developers.com/note-4-tmobile/orig-development/kernel-dealers-choice-t2915824
Device: https://github.com/StarKissed/android_device_samsung_trltephil
Click to expand...
Click to collapse
Guys, I don`t know if I am doing something wrong.
I have been using Twrp 2.8.1.1, I used it to flash CWM.
I tried to back up using CWM but says error while making a backup image of /data!
please press any key to continue.
I need help please!
sunnyo_ola said:
Guys, I don`t know if I am doing something wrong.
I have been using Twrp 2.8.1.1, I used it to flash CWM.
I tried to back up using CWM but says error while making a backup image of /data!
please press any key to continue.
I need help please!
Click to expand...
Click to collapse
The partition scheme may be off. I assumed there were identical from Europe to NA but I'll verify that tonight
twistedumbrella said:
The partition scheme may be off. I assumed there were identical from Europe to NA but I'll verify that tonight
Click to expand...
Click to collapse
Thank you, I am using US T-Mobile note 4!
Yeah... The partition scheme is off. I'm on T-Mobile and it won't work. Thanks for your efforts and I can't wait to try again.
[Recovery]Philz Touch Recovery[North American Variants]
Edit: nevermind. The issue is obviously deeper than the fstab or SELinux
Thanks for your hard work. I'm happy to test if you need anything.
After a lot of building, rebuilding, reconfiguring, etc some new builds are finally up.
The current version only supports identifying itself as a T-Mobile device until fully tested.
Rather than modifying the existing European version for the US, this now fully source-built.
twistedumbrella said:
After a lot of building, rebuilding, reconfiguring, etc some new builds are finally up.
The current version only supports identifying itself as a T-Mobile device until fully tested.
Rather than modifying the existing European version for the US, this now fully source-built.
Click to expand...
Click to collapse
Thank you I am going to try it right now,
I will you a feedback.
thank you again for the great work always!
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far
I flashed lineage os (latest) and everytime i restart I have to setup the device all over again like a new phone. is this a happening to other users as well or only me?
danielmachado99 said:
I flashed lineage os (latest) and everytime i restart I have to setup the device all over again like a new phone. is this a happening to other users as well or only me?
Click to expand...
Click to collapse
The same thing happened to me too!
Some people say its because of F2FS but im not sure about it.
AcidNoteZ said:
The same thing happened to me too!
Some people say its because of F2FS but im not sure about it.
Click to expand...
Click to collapse
oh because even i am on f2fs
danielmachado99 said:
I flashed lineage os (latest) and everytime i restart I have to setup the device all over again like a new phone. is this a happening to other users as well or only me?
Click to expand...
Click to collapse
This was happening to me as-well, while I was on the official build of TWRP. This is what I did:
1) Flashed @dianlujitao 's custom TWRP recovery from here.
2) Wiped and Formatted all the partitions to Ext4.
3) Changed only the Data partition to f2fs.
4) Adb sideloaded LineageOS and Gapps.
5) Finally Rebooted and all was well.
this happens because the out-dated twrp isn't compatible with 7.1, f2fs always works well
dianlujitao said:
this happens because the out-dated twrp isn't compatible with 7.1, f2fs always works well
Click to expand...
Click to collapse
Is your TWRP compatible atm?
AcidNoteZ said:
Is your TWRP compatible atm?
Click to expand...
Click to collapse
why not?
Mod Edit
Important note: if you going to report a bug plz give the logs also so reporting it actually will done something
Also:
this rom got no bug
Microsd/Sim2 tray Mod?
Hi luiscool,
Thanks for the ROM mate, but can I ask what you did to ensure that Snapchat antiban?
Kind regards,
Nathan
Hello. Thanks, I'm testing it now.
Luiscool Rom
Nolan01 said:
Hello. Thanks, I'm testing it now.
Click to expand...
Click to collapse
Any telegram group for this rom?
baruaberger said:
Any telegram group for this rom?
Click to expand...
Click to collapse
I don't think so. But it would be good.
how to use the prepatched twrp??
I've found two bugs so far. First, you cannot get a backup from Samsung Cloud and second, Magisk Manager won't open just crashes. I have reinstalled both the rom and TWRP to make sure that it wasn't a one off thing.
lambik333 said:
how to use the prepatched twrp??
Click to expand...
Click to collapse
Flash in Odin in the ap slot. If you're using TWRP .7 or .8 already you don't need to use it though.
Regards,
Nathan
Rennert said:
Microsd/Sim2 tray Mod?
Click to expand...
Click to collapse
Please test if it works or not else i add it in the next update
sevsman said:
Hi luiscool,
Thanks for the ROM mate, but can I ask what you did to ensure that Snapchat antiban?
Kind regards,
Nathan
Click to expand...
Click to collapse
I have done a system modification if you want to apply this to another ROM then you can pm me for the fix as i prefer leaving this thread to normal user / ROM feedback not fixes.
Nolan01 said:
Hello. Thanks, I'm testing it now.
Click to expand...
Click to collapse
good luck
lambik333 said:
how to use the prepatched twrp??
Click to expand...
Click to collapse
Do as sevsman said, flash it in ODIN and then flash my ROM
tripping_ said:
I've found two bugs so far. First, you cannot get a backup from Samsung Cloud and second, Magisk Manager won't open just crashes. I have reinstalled both the rom and TWRP to make sure that it wasn't a one off thing.
Click to expand...
Click to collapse
The Magisk thing is a bug because magisk.apk is not included in the ROM, just install latest Magisk.apk and it works and for Samsung Cloud you must sign in first before you can use it as always. although i did not test it so please give logs if it continues to not work so i can fix it
Thanks
thank u
Flashed the Rom. Everything seem to work fine but couldn't get backup from Samsung Cloud as reported earlier by another member. Please fix it.
Thanks
Very nice. downloading. :fingers-crossed::fingers-crossed::fingers-crossed:
Magisk always freeze and not working or I am doing something wrong.
ok next version no more samsung cloud bug i will check it out
"100% camera quality" - can you prove it?
I have flashed the rom, everything works except that Magisk Manager says Magisk is not installed. What did i do wrong and how can i fix this?
Tok12 said:
I have flashed the rom, everything works except that Magisk Manager says Magisk is not installed. What did i do wrong and how can i fix this?
Click to expand...
Click to collapse
You need to select reboot to recovery after flashing the ROM.
sevsman said:
You need to select reboot to recovery after flashing the ROM.
Click to expand...
Click to collapse
I just did a complete wipe, reflashed the rom,held the combination to reboot in recovery. Once in recovery i booted into the system. Still no Magisk?
Tok12 said:
I just did a complete wipe, reflashed the rom,held the combination to reboot in recovery. Once in recovery i booted into the system. Still no Magisk?
Click to expand...
Click to collapse
In recovery you're meant to use reboot/recovery and not system.