Related
TWRP 2.8.5.0 YotaPhone 2 recovery imageAfter the bare bones modded stock recovery for YotaPhone 2 it's time for something more advanced. The TeamWin Recovery Project 2, or TWRP2 is just that: a fully fledged, graphical, touch enabled, custom recovery.
This recovery image for YotaPhone 2 is still an alpha version, so expect some rough edges. Which leads me to:
Disclaimer
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device. You are likely to void your warranty by doing so, and on a bad day you might even damage or brick your device.
What is it?
It's a recovery image for YotaPhone 2 based on TWRP2 custom recovery, and the stock kernel from Yota Devices. You can boot it ad-hoc, or flash it permanently to the recovery partition. Use it to root, install software, make backups, update ROMs etc.
What can you do with it?
- adb root & shell access
- All TWRP 2.8.5.0 functionality (except MTP)
- install update zips (signed with testkeys (e.g. SuperSU), Yota Devices software, and also unsigned zips like Xposed framework.
- You can sideload packages, but also install them from internal storage (e.g. Download folder)
- make partition backups
- root your device
What can it NOT do?
- In this recovery image the MTP functionality of TWRP is disabled, it doesn't play nice with YD's kernel.
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0
- Some technical confidence to cope with quirks that come with an alpha version
- USB cable with a PC or laptop on one end
Steps overview:
NOTE: I used less detail in this post than the previous recovery thread, please look there for more detail.
1) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
2) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
3) Unlock the bootloader if you haven't done so before (read warning below!)
4) Download recovery image: recovery_twrp_yd201_alpha2.img
5) boot or flash the recovery image
Unlocking bootloader:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
See stock recovery thread for unlock steps
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
You should see a black screen with a tiny white: downloading...
b) Boot the recovery image:
Code:
fastboot boot path/to/recovery_twrp_yd201_alpha2.img
Alternatively, flash the recovery image (overwriting the stock recovery):
Code:
fastboot flash recovery recovery_twrp_yd201_alpha2.img
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly. TWRP has it's own logfile that you can copy to (virtual) SD card, and access from there.
Kernel sourcecode:
In this recovery image is Yota Device's version of the Linux kernel v3.4.0 for YotaPhone 2. Yota Devices are required by the GPLv2 license to release the source code for this kernel, but so far they haven't taken that step or even shown intention to do so as far as I know. The YotaPhone firmwares and also this recovery image are in effect violating the GPLv2 license if the situation does not change. Attempts to contact Yota Devices on the subject through support, press departement, and an attempt to contact Yota Device's management, have gone pretty much unanswered as of writing. I'm hoping they're just busy making great devices instead of being unwilling.
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info & credits::
TWRP2 is created and maintained by TeamWin. Please donate through their site if you enjoy their work!
Recovery image for YP2: SteadyQuad
Version: alpha2 based on TWRP 2.8.5.0 with Yota Devices kernel (1.39 EU1)
Thanks to: TeamWin for TWRP, @Dees_Troy for hints for getting it up and running, @Jeopardy for testing, @Chainfire for SuperSU and lastly Yota Devices for a great device.
Linking to this recovery image:
Please don't link directly to the download image, link to this post instead. That way users can get the most recent version and any updated info. (It's an alpha version after all)
Created: 2015-06-23
Last Updated: 2015-06-24
SteadyQuad said:
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Click to expand...
Click to collapse
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Yeah, I got the same boxed response and replied that it was not relevant, and explained why. Their SDK (for app development) has nothing to do with the kernel sourcecode, and at the moment their developer pages do not mention anything about kernel sources. I think that their support page tickets are handled by an external company (quicksupportlink.com), that is dependent on Yota for definitive answers, and they're probably instructed to send this reply. At least Yota will get reports from them, with hopefully lots of requests for kernel source. On the press page there's email addresses of 2 press ladies, you could try those too (as I did).
So nice to see this! Looking forward to trying, once mine comes.
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
zencooler said:
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
Click to expand...
Click to collapse
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Jeopardy said:
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Click to expand...
Click to collapse
Hi again,
Soory for the mistake (I just replied not for the first post). Once again sorry SteadyQuad and congrats for you again!
Jaopardy, thanks for the quick info and confirmation it works on 1.44 EU firmware! It's a good news
Regards!
Jeopardy said:
...Yotaphone 2 kernel's source code...
Click to expand...
Click to collapse
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
elatllat said:
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
Click to expand...
Click to collapse
Thanks, this archive was already known, it contains a kernel snapshot of end of june 2015. I put it on github with some small adjustments to make it build initially. (and it actually boots
I've also put up an initial device and vendor tree there, although both are pretty far from complete/correct at this point.
BTW @elatllat where did you get the link from?
SteadyQuad said:
...where did you get the link from?
Click to expand...
Click to collapse
I did a xda forum search and found that link, this thread, and thought I should link them up.
(as it's not widely known)
so anyone tried xposed??
varun.gid said:
so anyone tried xposed??
Click to expand...
Click to collapse
Yeah. It works as expected. No problems for me.
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
adamo86 said:
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
SteadyQuad said:
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
Click to expand...
Click to collapse
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
adamo86 said:
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
May be my phone is dieing?
Sent from my YD201 using Tapatalk
SteadyQuad said:
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
Click to expand...
Click to collapse
Your right my phone is bust does anyone have yota contact details
Sent from my YD201 using Tapatalk
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
zute333 said:
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
I got rid of it I tried everything downgraded wiped data etc clean install then did ota still freezes after a while. I did clean install of Rom twice. I think the screen is dying or something inside it is loose because the epd started off as freezes then moved to very light grey instead of black and would refresh but old pics and widget would be visible and it started to flicker from one side then it would start to work after a while then fade again etc. When these freezes happened I would get a blue screen when phone was rebooted and it would slow device down then reboot it self until the screen got unfrozen. I noticed even after installing rom new the screen would some time be frozen. It's only sometimes the screen would be reseted if I did a new installation.
I will miss my yotaphone. I will be getting a nexus 6p or v10.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Im trying to build cm13 unofficial from source i downloaded and im following this guide: http://xda-university.com/as-a-devel...id-from-source
And i used this guide to get source code and some others downloaded: https://nathanpfry.com/how-to-setup-...-android-roms/
Im using openjdk 8.
I got it to compile and it said "done" but when i flash the rom.zip it gets stuck at manufactor logo. i did not install anything else. thats all. ideas?
Phone is Nexus 4 8GB MAKO.
Bump
You're going to need to get some sort of logs to troubleshoot such as dmesg or kmsg. Unfortunately in order to get that without being able to boot the rom and enable root/developer mode settings, I believe you will need a modified kernel.
Sent from my SM-T350 using Tapatalk
Koognod said:
You're going to need to get some sort of logs to troubleshoot such as dmesg or kmsg. Unfortunately in order to get that without being able to boot the rom and enable root/developer mode settings, I believe you will need a modified kernel.
Sent from my SM-T350 using Tapatalk
Click to expand...
Click to collapse
Ideas where to find that?
You'd have to either make one yourself or find a developer who will do it for you. sorry I cannot help you more than that. here are a few more pages I found when googling https://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging , http://bootloader.wikidot.com/linux:android:kmsg
could possibly be a reference
https://github.com/ResurrectionRemix/android_frameworks_base/issues/139
hi,
this was the first time compiling a kernel from android source. I'm actually a java and app dev, so this was actually new to me.
I wanted to have full ntfs support and maybe some other features on my shield so i thought i'll give it a try.
the first thing i tried was pulling the whole android source code from the nvidia git server. Then I followed the instructions except i changed "mp dev" to "mp bootimage -j5" to just build the kernel. (I also did no modifications to the kernel). All went well and I got the boot image.
I used this repo: rel-24-uda-r1-partner.
I flashed the boot image with fastboot, but when it boots up, the nvidia sign comes and after some time I get a message with a red exclamation mark, which says that the partitions are corrupted or something like that. Then I get a black screen.
I also dont want to open up the device to access the uart to read out the kernel messages.
I dont know what else to do. Am I missing something? Does the open source kernel even work on stock android rom?
have u tried wiping the data partition?
yes i have
Take a look at the last few posts on this thread https://forum.xda-developers.com/sh...ecovery-twrp-shield-android-tv-t3510456/page4
so do you mean i have to use a another toolchain?
Jahusa said:
so do you mean i have to use a another toolchain?
Click to expand...
Click to collapse
I believe so
It works now. I copied the kernel from the repo into a another folder, set the env variables for the cross compilers and compiled it.
With the help of some threads in the nvidia forum and google, i got everything compiled.
The kernel boots now. But there's still the red sign at boot. I have to figure it out later.
Edit: OK, i think I got it now. To remove the annoying sign, I have to somehow disable the boot verification.
@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image
That warning pops up once you unlock bootloader.
Jahusa said:
@AndroidUser00110001 did you sign your trwp recovery image when you created it. If you didn't, then it would also trigger the boot verification. That's what I think.
Also thanks for your recovery image
Click to expand...
Click to collapse
Just wondering if anyone has looked into this, and what it could possibly mean for our device if we could be merged. Apparently there's no need for special kernel modules, bootloader edits, or KEXEC, and I think it would be pretty cool to be able to use multi ROM to boot back and forth between stock and AOSP.
Why don't you explain what this is and provide a few links?
lafester said:
Why don't you explain what this is and provide a few links?
Click to expand...
Click to collapse
https://www.xda-developers.com/efidroid-is-a-second-stage-bootloader/
This article was the first I'd heard of it. But it does seem like it might be something easy to implement. It's basically multi ROM, but without all the requirements.
Looks interesting.
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
gecko702 said:
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
Click to expand...
Click to collapse
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
This is very, very interesting. I love the thought of just using LineageOS or RR for everyday things and then just switching to stock when I want to use media and enjoy the fantastic sound.
I'm not a developer, but I'd like to help/contribute in any way possible if someone's working on bringing unofficial support to the Axon 7.
jimbo77 said:
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
Click to expand...
Click to collapse
Very true. However, it makes ROMs easier to port and for more people to test, as then people can try them out without wiping their phone each time they want to try.
I was able to port and build right up until the last step where you generate lk.img and fastboot it to the phone. I'm running Linux inside a virtual machine and it doesn't seem to want to communicate, though adb does work.
I might try on the weekend to boot linux off a hard drive and see if it will work..
In the mean time, if someone else wants to try to build, it's really simple just follow these two guides:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
twoi said:
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
Click to expand...
Click to collapse
Did you try this fix for arm64 devices?
https://github.com/efidroid/projectmanagement/issues/89
Seems you need to dump aboot to check what's the correct address for LK to boot.
Edit: also did you try using freeza Beastmode boot.img? Probably that's better
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
Yeah that's he creator of Efidroid... Why don't you reply to that issue tracker and add the Axon 7 to the list of devices that don't boot because of the arm64 arch
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
yes you are on right track
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Druboo666 said:
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Click to expand...
Click to collapse
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
twoi said:
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
Click to expand...
Click to collapse
you should contact with the dev he may help you OP3 and A7 got same chipset so yeah it will help
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
twoi said:
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
Click to expand...
Click to collapse
you can contact @npjohnson or @m1cha with your compiled LK or boot maybe they can help
as they have fix Nexus 6P LK with no uefi boot
This thread is presently about the development of a TWRP port to these devices.
The build is not yet working!
I am in the process of porting TWRP to my 3562 mostly out of pure spite for this stupid device. This thread is mostly for collecting my development process, for anyone who is interested, or wants to help.
Presently, TWRP will boot properly, and does function apart from UI issues and generally not being able to mount partitions correctly.
The UI draws in portrait mode (USB port at the top), but the touch interface responds in landscape mode (USB port on the right). This is very annoying, but it is still usable, so I haven't looked too far into it.
It seems to mount boot and userdata partitions okay, /sdcard is full of garbage data (encrypted? bad mount flags?), /system will not mount at all.
First order of business is to get /system mounted. It looks like this is related to vbmeta, so I have to sort out how to properly wipe the vbmeta on this device.
Here is my current image, if anyone is interested in trying it out: https://drive.google.com/file/d/1kMvKvocKY6AWRR-xkXIwisv27TmF6xcP/view?usp=sharing
I'll keep this updated as I keep working. As always, any input is greatly appreciated.
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
rolenthedeep said:
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
Click to expand...
Click to collapse
Thanks for moving, we were a bit OT in other thread. Yes the boardconfig.mk is for building from source. Does no good when using kitchen, I was just showing you an example of where and how rotation was handled. I still haven't followed up on changing rotation and touch input using kitchen, just got home from another heart catheterization. The only way to get a fully working fully functional twrp is to build from source, but without source code AIK is an awesome alternative. I just can't remember if we can change rotation and touch input in de-compiled img. We can ask @osm0sis if it is possible to edit recovery rotation via AIK. If you've not done so already, check out his work here on XDA. There are a lot of useful tools and scripts authored by him and a wealth of android knowledge that you can only benefit from reading.
Haven't ever messed with TWRP rotation myself, sorry. I'm sure it's something you can Google and find out though.
@rolenthedeep look at this may be helpful with rotation
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
mpalpha said:
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
Click to expand...
Click to collapse
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
tek3195 said:
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
Click to expand...
Click to collapse
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
mpalpha said:
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
Click to expand...
Click to collapse
I thought I was replying to someone else, but same applies. You're wanting to port one using kitchen the best place to start is here:
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
Where it gives the different screen resolutions go with largest, if it calls for a file not present in your device just skip it and don't add extras. There are a lot of guides but that one I know works rather well, I've used it on 3 diff devices. Cooking custom recovery in kitchen works but not always correctly. By that I mean that you may not have the ability to backup or restore or install. You may not be able to control brightness or some other setting or it could be that usb does not work. It can be a combination of any of those things and more. It can also be that you never notice something not working because it does everything you want it to. Just letting you know what to expect and saying that building from source is always best, even when it's unavailable.
If you ever get the time can you port TWRP to the 100015685-E?
@rolenthedeep here is a WIP fstab. I have commented out the partitions that were not first_stage_mount If you try it as is to try to get an idea of which parts are needed for recovery there is no sd card in it as it too is commented out for now. Got caught up in some other issues and stopped looking at it for a while. Maybe it will help a little.
Any updates on this? I have the 10.1 3562 version