Related
TeamWin Recovery for the Lenovo Ideapad A1. The main motivation for this is to be able to backup the kernel, and to support Openrecoveryscript for Goo Manager. This is just experimental for the time being - I thought I'd try it out and see what it's like. I may or may not carry on developing it to a usable release quality. However, it's all open so feel free to fork it and fix things up!
What works
It compiles and boots
The touch screen seems to work, but gets confused if you touch the capacitive buttons
Backups appear to succeed, as long as you check the right options
What's untested
Restoring backups
Installing zips
Pretty much everything
Building
Code:
repo init -u https://github.com/gmarkall/android.git -b twrp-a1
lunch full_A1_07-eng
make recoveryimage
Once you've built it, you can flash it with fastboot:
Code:
fastboot flash inand-recovery out/target/product/A1_07/ramdisk-recovery.ub
Pre-built flashable image
Will be uploaded later - I'm on the train at the moment and it's on my other computer.
I just want to say thanks. You have done so much for A1 users you have made this device a dream to use.
Compiled version
Took me a little longer than I hoped, but here's a compiled experimental version: www.doc.ic.ac.uk/~grm08/ideapad/twrp-a1-alpha-0.ub
Flash with:
Code:
fastboot flash inand-recovery twrp-a1-alpha-0.ub
Usual warnings apply for stuff that's in development. If you try it, please let me know of any problems/what works for you/what doesn't work for you.
Many thanks!
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
How it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* This must work on all devices model quark (XT1250 and XT1254) or quark_umts (XT1225) * custom ROM may display only quark
To know you device model just open the app Terminal Emulator for Android and see the quark after the @ like below.
Main download folder
Mirror download folder
The folder contains the Mod TWRP version base on the latest official with proper support to all android versions (The one from TWRP site doesn't have the proper support For Nougat, Oreo or newer OS's, I tryed to push the changes so the one from they site can be updated they did not answer me so I give it up), the mod other than having the proper support for all OS that prevent bug as the "Bootloop to TWRP after a Factory Reset" it has extra backup option (Radio/Modem, boot logo etc), NTFS support for USB-OTG devices, all possible TWRP languages, full encryption support (For Nougat and earlier, Oreo and up encryption is not suported) and etc improves...
All the extras featuring can be seen in the Changelog click here
Big thanks:
A big thank for those that donating to thanks for my work on TWRP.
@ChazzMatt for his donation, and his help on many other threads of Moto Maxx on XDA.
Renan R. R. for his donation
And all the other users that I contribute.
On the developer side, thanks to:
@Dees_Troy for his work on TWRP, for the tutorial and help to bring the official support...
@Skrilax_CZ for his hard work on building the first stable CM to this device
@Aadi for a tutorial.
@respider for his original work on TWRP for quark.
Developer donation link:
To donate via paypal click here
No other donation option is available.
XDA:DevDB Information
TWRP For all Quark(Moto Maxx/Turbo and Droid Turbo)
Contributors
fgl27
Source :
Android :
omnirom M source
LineageOS source
Device :
Device tree for omnirom source
Device tree for LineageOS base source
Kernel tree for LineageOS source
TWRP Version: 3.3.1
Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-08-16
Last Updated Check changelog (click here)
I use many tutorial to make this TWRP, here some to help those who want to do the same.
tags: how to port TWRP recovery, how to compile TWRP recovery, how to make TWRP recovery.
http://forum.xda-developers.com/showthread.php?t=1943625
http://forum.xda-developers.com/showthread.php?t=2294800
http://wiki.cyanogenmod.org/w/Build_for_quark#Build_CyanogenMod_and_ClockworkMod_Recovery
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://source.android.com/source/building.html
https://source.android.com/source/building-running.html
https://source.android.com/source/initializing.html
http://review.cyanogenmod.org/#/c/89474/1/recovery.te
Check Changelog click here
How to install it.
Using Fastboot:
Download mfastboot
The fastboot I share is need replace fastboot with mfastboot in the commands below...
Copy the file you download form OP to the folder of fastboot and use the command in the bootloader screen
Code:
fastboot flash recovery recovery_name.img
! replace recovery_name with the name of the file, example:
Code:
fastboot flash recovery twrp-3.0.2-0-quark.img
Via app Flashify (for root users)
If you have root, try Flashify is really simple.
Install the app, download the recovery to the phone internal memory, open the app, chose recovery image, chose from file, confirm and flash, after you will go straight to the new recovery.
Via TWRP:
Yes TWRP can flash images recovery and boot image.
- install
- images... (is in the bottom right of the screen)
- select the image and image type (boot or recovery)
- swipe
- reboot to test, to recovery if flash a recovery or to system if is a boot...
...............................................................................
keep system read only?
This will be asked in the first time you boot to recovery after flash the recovery, if you not accepts it TWRP may be replace by the previously recovery of your device, but read way...
Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
..............................................................................
Note about restore from Stock 5.x.x to 4.4.4 and vice versa:
The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.
I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.
TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.
That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.
To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>
For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS
Swipe to change
Now restore.
But be aware that the data partition is were internal memory is, so if you change the file system you will loose all the files in internal memory
The wipe of internal memory doesn't happening if you only wipe data partition without change file system.
This will not affect custom ROM, but i recommend to use f2fs.
.....................................................................................
Note about encrypt
Test done in Nougat in the link below
Last Nougat test
Test done in Lollipop below
TWRP supports backup a encrypted system, but i only test this on lollipop stock ROM.
This is a simple description how to encrypt backup and restore the encrypted system.
Stock ROM
You can only encrypt if you have stock recovery and no modification to yours ROM, that means no root or rooted app like xposed modules etc, so if you have uninstall everything and do a full un-root.
To encrypt go to setting>secure>encryption the process take a while...
If you already have stock encrypted ROM you can flash TWRP and make a backup of it.
To remove the encryption you need to flash back the stock recovery and do a factory reset in Settings>Backup & Reset>Factory Reset
Factory Reset will deleted all the files of the device! so make a copy of important data...
Wiping all the partition in TWRP will not remove the encryption.
After the device finish the factory reset all the data of you phone will be deleted and the encryption will be gone.
Now you can flash back TWRP again and have fun...
If you need to restore that encrypted backup you can but after it finish restoring you will see that it is un-encrypted.
Custom ROM
I tested encrypt on custom Marshmallow AOSP base ROM (all the CM's), it is not need any recovery the only thing that is need to encrypt is that the encryption block of data be clean before encrypt.
Cleaning the encryption block of data
TWRP can't clean that so if the user encrypt the device the only way of clean that is by erasing the data via fastboot:
Code:
mfastboot erase userdata
The down side of it is that the partition will be erased lost every file of data and internal memory + when the system boot the data partition will be formatted as EXT4 that have a small performance lost over F2FS, to have it back to F2FS is need to give the command then start the OS, after the device finish boot and optimized it will format the partition and is need to go back to recovery and format the data as F2FS, going on wipe > advanced > select data > "repair change..." >change file sys> F2FS... then boot to the device and use it...
Note about official TWRP, USB driver via USB-OTG work, but your driver need to be formatted as FAT32(small drivers) or exFAT (big drivers), on the Mod version I have update the NTFS support and it now works
...........................................................
Collection of "Special_flash_zip" to go with the Mod TWRP
As some things are not directly attainable through TWRP menus, but they can be achieved via extra zips...
Clean_modem_status.zip
Logo_Flasher.zip
Modem_Flasher.zip
Clean_modem_status.zip
as the name implies this will erase the modem status partition, and erase any bad modem status, this can help in situations were the users is with some radio problem, one most famous on Quark is when user can get a GPS lock...
I test the GPS after flashing this and it works... (I did not had a GPS problem, but will test after I get one...)
Logo_Flasher.zip
This is a zip that can flash logo.bin via TWRP, is need of the user to have the logo.bin then place it inside of the root of the zip, then flash it over TWR.
Modem_Flasher.zip,
This is a zip made to flash the Radio.img + Clean modem status, thus achieving the update of Radio and clean any bad old radio status.
This zip is empty need the user to add the files on the future I will make a zip with the radio image inside... the below explain how to put the files inside.
As on Quark the radio.img is complex image that can't be flash via TWRP it is need to have a special zip, this zip contains the content of radio image after the user have flash it via fastboot, then for that I made this tutorial in how to use the zip, see the below hide...
Tutorial how to make this zip to work...
This zip must be used with a full backup of stock Modem image that can be achieve via app using apk called partition backup or via ADB
1# APP process... config the app Click on the tool, then in backup formats section, mark only Raw partition image
The partitions name to backup are
modem
mdm1m9kefs3
the file must be in sd/Partitionsbackups, the file names need to be just like describe below
before you put they on the zip so rename the files according the below...
modem.img
mdm1m9kefs3.img
make no modifications to the files, and place it on the root of this zip
The just flash the zip via TWRP
#############
2# ADB process, you must have SuperSu from Chainfire installed before making this, CM root will not work.
use the commands "adb devices" to check if the device is connected it will show the device serial number if it is...
then do the next two lines
Code:
adb shell
su
* after command "su" press enter 3 or more times... until the cmd displays
[email protected]:/ #
then... do the next 4 lines
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
dd if=/dev/block/mmcblk0p32 of=/sdcard/mdm1m9kefs3.img
the files will be on the internal memory, the file names need to be just like describe below before you put they on the zip
modem.img
mdm1m9kefs3.img
make no modifications to the files or to the file name, and place it on the root of this zip
The just flash the zip via TWRP
The recommendation is to make a modem backup of yours device after you get a GPS lock, and store it to use whenever you need because you have a radio related problem, or make one to share on XDA with other users, be aware to share Radio zip and describe from with device model and ROM you pull it from, because flashing other device Radio may cause problem...
............................................................
This TWRP is theme-able, go to the tread to change the looks:
[THEME][TWRP] TWRP Materialised - Dark / Light / Play
Support, any bugs and errors just post in here, I will answer as soon as possible.
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
icondeg said:
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
Click to expand...
Click to collapse
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
baybutcher27 said:
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
Click to expand...
Click to collapse
It works fine!!!
Thanks for all
Enviado desde mi Moto MAXX mediante Tapatalk
omg great work! congrats
muito obrigado!
Awesome work! Thanks man! Can't thank you enough!!
Thank you!
Paypal donation sent.
Confirmation number: 08S12817NX2219226.
Thank you guys i really appreciate the supporter. Of every one.
Small, but big improvement change.
Change log in the 2° post. The TWRP now is much faster to wipe, restore or install a ROM, no more lag to format...
Ok
I believe in you men
If you say that this no affect anything, that's fine by me
Regards
Enviado desde mi Moto MAXX mediante Tapatalk
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
baybutcher27 said:
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
Click to expand...
Click to collapse
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Jejejeje
Regards
Enviado desde mi Moto MAXX mediante Tapatalk
icondeg said:
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Click to expand...
Click to collapse
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
ChazzMatt said:
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
Click to expand...
Click to collapse
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
##W4TCH0UT## said:
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
Click to expand...
Click to collapse
I don't know much about Kernel yet so i cant see what is going wrong in yours...
But i find a workaround, to compile the recovery.img without compile the boot.img i generated a boot.img but use pre build dt + kernel.
That way i can compile recovery in under 13 min and without a kernel folder in the source, before it take over 30, and when i'm resolving bug and error, how much fast i can produce a image better.
The workaround i copy from victara and put in the omni folder of my device source, is need the mkbootimg.mk + dtb (dt image renamed) + kernel.
Then check BoardConfig.mk kernel lines, the dt and kernel i use from a previously build of my on, after you have one no need to compile the kernel every time...
Don't know if this will help but this way you may grub a previously working dt + new kernel or vice versa, and combine to see what works.
My CM source folder is working but not update do to that yet but i believe will work in others source other then omni.
if something work or not let me know.
I finished all the tested with TWRP compile in omni source, i update the download link.
No need to change TWRP unless you use a encrypted device, or you wanna to test it.
Put a note about encryption on 2# post.
If any bug found let me know.
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
respider said:
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
Click to expand...
Click to collapse
too bad bro
i hope you're ok
regards!
This recovery will work ONLY for the Snapdragon 615 version of Oppo R7 Plus!
Here is an update to my UNOFFICIAL TWRP 3.0.2
Everything works well, with one caveat: It will reboot as soon as the display times out. The workaround is simple: Go to settings and disable Screen Timeout.
The -C revision is just to remind me that the recovery it is build on CyanogenMod.
If you don't need encryption and don't care about wrong date/time in your backups, then the official twrp will be all you need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full Source: Github.Old stuff:
My goal with this UNOFFICIAL twrp recovery is to enable encryption on Oppo R7Plus-f(Snapdragon) version.
Tested with AICP on MarshMallow. Full encryption support.
All hard work was done by the TWRP Team and the R7 kernel gurus at CyanogenMod.
I just made a few additions and changed the official TWRP kernel to the CM kernel using the AICP build system.
To get your Oppo R7Plusf encrypted, there are a few points you must follow.
Note1: This wil not work with ColorOS. The ROM must support encryption. ColorOS does not!
Note2: You will LOOSE ALL DATA if you choose to encrypt your R7Plusf.
Here is a small howto:
1. Boot to bootloader and flash TWRP-3.0.2.u
2. Boot to recovery
3. Choose A or B to backup your data
....A: Backup Data and copy it to PC (Internal Storage - TWRP/BACKUPS/xxxxxxxx/BackupName)
....B: Backup Data to the Micro SDcard (Now, be careful not to format the Micro SD)
4. Wipe -> Format Data (type YES and tap the OK/Enter button)
....This command is slow, have patience!
5. Reboot to android. The install wizard should show - be sure to create a PIN or Pattern kode during the setup.
6. Charge the phone to 90-100%
7. Open Settings/Security and -> Encrypt phone
8. Follow instructions
Click to expand...
Click to collapse
Now the device will reboot a few times and finally it will boot to the login screen and ask for your pin code.
All this will take time, have patience.
On my AICP ROM it sometimes "hang" when Finishing boot and make some tick sounds. Turning the screen off and on a few times will make it boot to the login and you can enter the PIN or Pattern. It will boot again and quickly get into your Android system.
Once booted to Android, everything is smooth and there are no more issues (at least not encryption related )
This is an issue with my AICP ROM only, CM13 start without issues.
...reserved...
Please share your experience here, if you choose to check out encryption on the R7+. Thanks.
Major Props ! Great job and you actually fulfilled a request of mine ! Thanks
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
midterm_2003 said:
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
Click to expand...
Click to collapse
It is 6 months since I tried. At that time I was asked for the pin. Don't know if that is different for the latest cm.
Note that this recovery is not perfect. It handles encryption well, but has a few issues. To avoid these, you can flash the official twrp from http://twrp.me, but don't format data - it will break encryption.
Maybe CyanogenMod recovery is fully functional now, then it might be a better choice. @maniac103 ?
Yes backup is optional. It is always your choice.
It was my mistake I selected wipe instead of format , it works now ! :good: do you know what other issues this recovery have as I want to keep
Thanks
Small update - read OP.
teemo said:
Small update - read OP.
Click to expand...
Click to collapse
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
celoxocis said:
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
Click to expand...
Click to collapse
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
teemo said:
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
Click to expand...
Click to collapse
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
celoxocis said:
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
Click to expand...
Click to collapse
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
teemo said:
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
Click to expand...
Click to collapse
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
celoxocis said:
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
Click to expand...
Click to collapse
For the filemanager, I feel it is a little smoother than before. Might be my imagination though.
It is very picky about how you scroll with your finger, sometimes mistaking it for a "tap". But old adf did the same.
I can say definitely, that the slider is much much better now. Not supersmooth as my HTC, but good enough for a recovery tool. Don't see any downsides yet.
EDIT: Funny, the slider animation is the same as on my 3.0.2-C. I made a video and compared. It's the same. I may have seen the slower animations on an older recovery, I am sure it was much more choppy before.
Is there any chance that this would be updated.?
kishd said:
Is there any chance that this would be updated.?
Click to expand...
Click to collapse
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
x
Help please...I'm stucked at the unlock bootloader...
First to say I have root but I got root only with kingroot app...is this a problem?
I have installed the color os r7plusfEX_11_151225 (didn't do full wype data, installed over the latest color os version), but with the oppo tools it didn't do nothing so I got root with kingroot.
I can go into fastboot but when I type "fastboot oem unlock" it always say this:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.053s"
where I was wrong or where I miss something?
thanks for replies I really will to intall a custom rom on this phone........
celoxocis said:
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
Click to expand...
Click to collapse
I hate to be a nuisance, but have you had a chance to look at this?
kishd said:
I hate to be a nuisance, but have you had a chance to look at this?
Click to expand...
Click to collapse
Yes i decided not to bring another unofficial release.
There will be an update for TWRP for the entire R7 series.
It will be made official soon.
The Kernal Source has been released by Razer.
Links to the source is at the bottom of this page:
http://support.razerzone.com/mobile/razer-phone
Here are the links to the source just in case:
MR1 Releases:
Build 853
Build 851
Production Releases:
Build 822
Build 813
It has been talked about already but not in this section. This is where it belongs and nice job posting direct links to it.
https://forum.xda-developers.com/razer-phone/how-to/source-code-posted-t3719665
MedicStuder said:
Surprised no one else posted in the section with this. The Kernal Source has been released by Razer which means modding can start.
https://www.xda-developers.com/razer-phone-kernel-source-code/
http://www.androidpolice.com/2017/12/15/kernel-source-code-just-released-razer-phone/
https://www.gizchina.com/2017/12/16/razer-releases-kernel-source-files-razer-phone/
Links to the source is at the bottom of this page:
http://support.razerzone.com/mobile/razer-phone
Here are the links to the source just in case:
MR1 Releases:
Build 853
Build 851
Production Releases:
Build 822
Build 813
Click to expand...
Click to collapse
I mentioned it in the factory image thread 5 days ago
Mods, can we pin this in the dev section since it contains the links to the needed source code for development purposes. Seems appropriate to have it pinned in this thread. thanks.
I've also got the kernel source going with CAF history included (based on LA.UM.5.7.r1) at https://github.com/jcadduono/android_kernel_razer_msm8998/tree/android-7.1
Fixed a minor bug and added some build scripts to simplify the process of configuring and building.
Added qcacld-3.0 sources into the kernel build for WiFi drivers but I appear to be missing something so it doesn't build. :/
I'm sure someone here can figure that out!
For TWRP support, essentially you'll need to build the stock kernel with additional options like f2fs and exFAT if desired. The OS and TWRP will be sharing the same kernel binaries due to the A/B setup so you *will* need to build the WiFi driver, even for recovery.
If someone is daring enough, they can simply build TWRP normally (ex. for a non-A/B device), flash it to boot_b or boot_a partition (depending what's active), boot up TWRP, and make backups of the opposite A/B partitions.
This can't actually be too hard to do, Dees_Troy has already done most of the work by supporting A/B on Pixel devices already.
I suppose I'm willing to give it a try if anyone is willing to possibly lose the ability to get into the OS until Razer releases factory images.
The chance of that happening is pretty slim, as long as we're only flashing the *active* boot partition (we'll check that in OS using mount command), we should be able to simply grab a copy of the opposite boot partition and restore it to how it was.
YOU CAN simply use fastboot to swap to the other boot partition, restoring your OS to bootable even if TWRP fails to work. (we will test this first to make sure Razer has enabled this option...)
Probably safe, but there's just that risk.
As I'm unsure exactly how to compile the WiFi drivers right now, I'll do this:
Create a normal TWRP image, which you can flash to your *active* boot partition.
Create a TWRP flashable zip that will take the ramdisk from the active boot partition and flash it to the inactive boot partition's boot image, then flash the inactive boot partition's image to your active boot partition.
Result: Both partitions contain the original stock kernel image with TWRP support and a fully working OS.
Slight issue: F2FS won't be supported because the stock kernel will have module signing enabled and TWRP won't be able to load it.
I'm also fairly certain I'll never get decryption working myself for this device...it looks like the vendor partition may be required and it is already encrypted itself? (not encrypted on the Pixel 2 so this is new)
Dees_Troy will be getting his Razer Phone next week. If anyone can get TWRP working it's him. No need to worry ?
MishaalRahman said:
Dees_Troy will be getting his Razer Phone next week. If anyone can get TWRP working it's him. No need to worry ?
Click to expand...
Click to collapse
No way! :victory:
That's the best news I've heard yet
---------- Post added at 04:44 AM ---------- Previous post was at 04:30 AM ----------
jcadduono said:
I've also got the kernel source going with CAF history included (based on LA.UM.5.7.r1) at https://github.com/jcadduono/android_kernel_razer_msm8998/tree/android-7.1
Fixed a minor bug and added some build scripts to simplify the process of configuring and building.
Added qcacld-3.0 sources into the kernel build for WiFi drivers but I appear to be missing something so it doesn't build. :/
I'm sure someone here can figure that out!
For TWRP support, essentially you'll need to build the stock kernel with additional options like f2fs and exFAT if desired. The OS and TWRP will be sharing the same kernel binaries due to the A/B setup so you *will* need to build the WiFi driver, even for recovery.
If someone is daring enough, they can simply build TWRP normally (ex. for a non-A/B device), flash it to boot_b or boot_a partition (depending what's active), boot up TWRP, and make backups of the opposite A/B partitions.
This can't actually be too hard to do, Dees_Troy has already done most of the work by supporting A/B on Pixel devices already.
I suppose I'm willing to give it a try if anyone is willing to possibly lose the ability to get into the OS until Razer releases factory images.
The chance of that happening is pretty slim, as long as we're only flashing the *active* boot partition (we'll check that in OS using mount command), we should be able to simply grab a copy of the opposite boot partition and restore it to how it was.
YOU CAN simply use fastboot to swap to the other boot partition, restoring your OS to bootable even if TWRP fails to work. (we will test this first to make sure Razer has enabled this option...)
Probably safe, but there's just that risk.
As I'm unsure exactly how to compile the WiFi drivers right now, I'll do this:
Create a normal TWRP image, which you can flash to your *active* boot partition.
Create a TWRP flashable zip that will take the ramdisk from the active boot partition and flash it to the inactive boot partition's boot image, then flash the inactive boot partition's image to your active boot partition.
Result: Both partitions contain the original stock kernel image with TWRP support and a fully working OS.
Slight issue: F2FS won't be supported because the stock kernel will have module signing enabled and TWRP won't be able to load it.
I'm also fairly certain I'll never get decryption working myself for this device...it looks like the vendor partition may be required and it is already encrypted itself? (not encrypted on the Pixel 2 so this is new)
Click to expand...
Click to collapse
I'm willing to temporarily sacarfic my device for this. I will message you tomorrow morning and we can give it a shot.
We have lift off! @jcadduono you were right :highfive:
Waiting on you for further instructions on how to proceed.
Even if this leads to no where it sure feels damn good to see the twrp logo.
Everything is going well, we're getting copies of each partition and I'm working on making factory restorable images right now.
I am fairly certain I can even support encryption on this device with no issues.
The device itself actually supports hardware Qualcomm full-disk encryption like most non-Google Qualcomm devices so it's nothing new!
However, the Razer Phone supports HW encrypted SDcards like LG does, so TWRP needs support in the actual crypto code used in the project to work with encryptable sdcards. Maybe Dees_Troy will be up to that task when he gets his phone.
TWRP images will be distributed like so:
- A twrp.img file that you flash to your active boot partition
- A zip file that copies the TWRP ramdisk from your active boot partition into your inactive boot partition, then copies your inactive boot partition to your active boot partition
The zip file will effectively install TWRP and the next time you boot TWRP it will be relying on your ROM's kernel instead of the TWRP kernel.
jcadduono said:
Legend!
Mad props to you, can't wait to see more! :good: This will be a good Christmas, can I ask whether being carrier or not will matter for installation?
Click to expand...
Click to collapse
@jcadduono Legend!
Mad props to you, can't wait to see more! :good: This will be a good Christmas, can I ask whether being carrier or not will matter for installation?
P.s I'll take a pop if you want a second test
thread stuck like Chuck for now, hopefully we can get some dev going for this device.
yeahh !!!!!!! wake up dev teams !!
Any information regarding Franco kernel?
I wanna compile TWRP for SM-A700H(2015) and I have several problems:
1) I can't find my device's BoardConfig.mk
If there is something with kernel, then I couldn't compile kernel due low RAM. See this post. (Check comments too)
2)I just want TWRP itself. Should I do that fstab part too??