Related
THESE ARE UNSUPPORTED. YOU ARE RESPONSIBLE TO ANYTHING THAT HAPPENS AS A RESULT OF YOUR ACTIONS.
WARNING: THESE BOOT IMAGES HAVE BEEN CAUSING BOOT LOOPS FOR SOME USERS. THEY INCLUDE PEOPLE WHO ARE USING NON-STOCK FIRMWARE, FIRMWARE FROM ANOTHER DEVICE (such as using "c" firmware on a "i" device) AND THE ONE PERSON WHO'S TRIED THE "8" BOOT IMAGE. INSTALL AT YOUR OWN RISK AND BE SURE YOU HAVE A METHOD TO RECOVER ANOTHER BOOT IMAGE.
ALL QUESTIONS/COMMENTS/REQUESTS SHOULD GO HERE: http://forum.xda-developers.com/note5/help/qa-stock-kernels-selinux-enforcing-t3222324
I've taken the stock boot image (kernel) from a few different devices and repacked them in order to make them safe for use with SuperSU.
These kernels are Samsung stock SEAndroid enforcing. That means higher security (but also the chance that some *root* programs fail.) The ramdisk is modified to allow SuperSU to work, and to prevent boot loops when you're using a modified device. The ramdisk is also modified to work around the samsung kernel bug that would prevent some devices from going into deep sleep.
Other than these changes, they are completely, 100% stock. They will NOT auto-root your device (though it is safe to install SuperSU after installing this kernel), they won't grow new hair on your head, and most certainly won't find you a spouse.
For details on the changes, please read this thread:
http://forum.xda-developers.com/note5/orig-development/kernel-discussion-root-recompiling-t3219990
As these are STOCK kernels (not recompiled), all your hardware should continue to work properly. From my own tests, I have no reboot issues, no NFC issues, etc.
Each file attached here has a file name that reflect the firmware I pulled it from. Read it carefully. Don't use a kernel that shouldn't be used on your device!
Files ending with ".tar.zip" can be unzip'd (they contain only a .tar file) and applied via ODIN (PDA/AP section.) The files must be unzipped before used in ODIN. These ".tar.zip" files can NOT be flashed with TWRP or CWM.
Files ending with just ".zip" are meant to be flashed via TWRP or CWM. You can also extract the .img files from the .tar.zip files mentioned above and flash those directly with TWRP (using the proper options.)
Yes, this will trip KNOX if it's not already tripped...
Enjoy..
Gary
N9208ZTU1AOH4
OP updated to include a big red boot loop warning...
Added N920T (T-Mobile) to the top post.
Added modified boot images for the T-Mobile "M" leak N920TUVU2DOK5. The origin of the boot image is @danon.brown. Thanks to @gharris040604 for testing this...
Added N920LKLU2AOJ6 to the first post.
added N920GDDU2AOJ5 to the first post.
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
Moved here
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
steps
Installation Instructions.
There is never only one way to do anything. The following steps have worked for me.
Before you start, make sure you have rooted the A20
https://forum.xda-developers.com/android/development/root-samsung-galaxy-a20-rooting-guide-t3954872
This part may not be necessary if you're recovering from a crash.
To install TWRP
1. Download the U2 custom recovery from here
https://androidfilehost.com/?fid=1899786940962574261
2. On the PC rename the unpatched recovery as recovery.img
3. Use 7zip to make it into recovery.tar
(right click and choose add to archive)
4. Use 7zip to add your patched boot.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
5. Download vbmeta.tar from here (https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237) and extract vbmeta.img
6. Use 7zip to add vbmeta.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
7. Install recovery.tar to ap slot using Odin.
If you are getting messages about being unable to flash the recovery try this.
https://forum.xda-developers.com/showpost.php?p=80216465&postcount=276
8. Boot the A20 into TWRP and mount everything that you can.
9. Format Data (not just wipe) - this will remove the encryption of the data partition.
10. Flash this zip View attachment Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
11. Reboot into Recovery. It may reboot into download mode. If it goes to TWRP skip step 12. If you already have a backup, you can go to step 16.
12. On the pc install recovery.tar to ap slot using Odin.
13. Reboot phone and re-enter all data.
14. Reboot into Recovery.
15. Backup only 3 parts: boot, data & system (not system image)
16. You can now restore boot, data & system from TWRP after any crash, but you may need to forget your wifi and go back in to it.
You can now move on to installing a new GSI ROM .
It you get stuck you can come back to Samsung by using your backup.
GSI ROMs are here.
https://forum.xda-developers.com/android/development/gsi-galaxy-a20-t3964546
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
jajk said:
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
Click to expand...
Click to collapse
How did you get a copy of the stock recovery?
@physwizz Stock recovery is in the AP image in the ROM.
jajk said:
@physwizz Stock recovery is in the AP image in the ROM.
Click to expand...
Click to collapse
I'll get grab it now.
jajk said:
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
Click to expand...
Click to collapse
After hitting dead ends with Mac and Windows, I succeeded in installing Android Kitchen on Ubuntu and unpack the s9 image.
Next step is to try to modify it to fit the A20
Hmmm...
Look at S10 Exynos TWRP versions also.
jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
Thanks
jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
Now I just need to work out how to repack it.
@jajk
AIK now wants an update-script and I can't repack the recovery.img without one.
Edit: went back to the Mac and worked it out.
Didn't install [email protected]
-deleted-
@TBM 13 Can you help build?
physwizz said:
@TBM 13 Can you help build?
Click to expand...
Click to collapse
I don't actually have the device yet. I will probably buy it in like two weeks (but i won't make nothing to it once i get bored, my parents will kill me if i brick it lol).
I can build TWRP, but i only have LOS 14.1 source (i'm not sure if that version of the source can work for a device with Android Pie).
I'm also a little bit noob on this.
TBM 13 said:
I don't actually have the device yet. I will probably buy it in like two weeks (but i won't make nothing to it once i get bored, my parents will kill me if i brick it lol).
I can build TWRP, but i only have LOS 14.1 source (i'm not sure if that version of the source can work for a device with Android Pie).
I'm also a little bit noob on this.
Click to expand...
Click to collapse
???
Does this device have a Telegram group?
TBM 13 said:
Does this device have a Telegram group?
Click to expand...
Click to collapse
No, not at this stage.
jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
The A30 have 2 versions of twrp.
https://forum.xda-developers.com/galaxy-a30/development/team-win-recovery-project-3-3-1-0-t3940850
@physwizz A30 TWRP appears never to have worked.
Kiss of death to have an off forum Telegram group - should be banned
Helpful Info
Download Odin Flash Tool For Android Phone, Then Extract It
Now Download >> TWRP Recovery
Then Go To Settings >> About Phone >> Tap On Build Number 5 To 7 Times You Will See Developer Option
Now Tap On Developer Option >> Then Enable USB Debugging And Also Enable OEM Unlocking
Now Boot Your Smartphone In >> TWRP Recovery Mode
To Boot Phone In Recovery Mode You Have To Turn Of Your Smartphone Then Press Volume Up + Power Botton Together To Turn On >> Recovery Mode
Then Select >> Reboot To Bootloader, After Some Time You Will See Downloading Mode
Now Cannect Your Smartphone To Computer Using USB Cable, Then Open >> Odin Flash Tool In Your PC
Now ID:COM Tab On Your Odin Will Turn Blue Which Means Your Phone Is Successfully Recognized By Odin Flash Tool, If It Doesn’t Reconnect Your Device And Check Again
Now Tap On >> AP Button On Odin Flash Tool And Select >> TWRP Recovery For Smartphone You Downloaded Earlier
Now Tap On >> Start Button
After Some Time You Will See “Pass” Button On Screen, It Means TWRP Recovery Successfully Installed On Smartphone
Hello I need a little bit of help.
My problem:
I've LineageOS 16 on my Samsung Galaxy S5 (SM-G900F) and I want to change the boot image BUT if I make exaktly that what I saw in a video my phone just boot in the bootloader. So now i want first the stock boot image to have a back up, so that I can make a different boot image. (Btw I need help with that too. Do i just need to go to twrp and install it as "image" "boot" and install it?)
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.