Hi!
Can't figure out how to fix "Recovery is not Seandroid Enforcing". Do I need to compile new kernel?
Tried all versions for this model what I could find on internet:
https://github.com/TwrpBuilderTests/android_device_samsung_heatqlte/releases
https://gitlab.com/HosteBin/Surendrajat_sdliub/-/tree/master/samsung/heatqlte
Thanks.
sorry noob question, are u using custom recovery ?
Hi!
Are TWRP stock recovery images? Of course not. I can't get boot to TWRP custom recovery.
TWRP-3.2.3-TwrpBuilder-heatqlte-2018-09-08_13-05.img - broken image is only one which don't message "Recovery is not Seandroid Enforcing", but have broken fstab and stuck at Galaxy boot logo. You can use adb, but can't execute any commands. Getting "CANNOT LINK EXECUTABLE /sbin/sh: library libc.so not found" error. Fixed fstab and flashed and getting "Recovery is not Seandroid Enforcing" error.
TWRP-3.2.3-TwrpBuilder-heatqlte-2019-03-13_20-24.img - can't flash because Odin complains about size. I think recovery partition is too small for it.
I'm curious does anybody had successfully flashed TWRP and used any custom Android image on this phone? Could use 4.4.4 Android with root, but some apps what I need to use needs at least Android 5+.
Thanks.
Coool_ said:
Hi!
Are TWRP stock recovery images? Of course not. I can't get boot to TWRP custom recovery.
TWRP-3.2.3-TwrpBuilder-heatqlte-2018-09-08_13-05.img - broken image is only one which don't message "Recovery is not Seandroid Enforcing", but have broken fstab and stuck at Galaxy boot logo. You can use adb, but can't execute any commands. Getting "CANNOT LINK EXECUTABLE /sbin/sh: library libc.so not found" error. Fixed fstab and flashed and getting "Recovery is not Seandroid Enforcing" error.
TWRP-3.2.3-TwrpBuilder-heatqlte-2019-03-13_20-24.img - can't flash because Odin complains about size. I think recovery partition is too small for it.
I'm curious does anybody had successfully flashed TWRP and used any custom Android image on this phone? Could use 4.4.4 Android with root, but some apps what I need to use needs at least Android 5+.
Thanks.
Click to expand...
Click to collapse
How do you flash IMG from Odin?
AP checked and select .img file.
Hey
Bit late and not twrp but i got cwm recovery running you still need it
https://github.com/tibixh/android_device_samsung_heatqlte/releases/tag/stable
had several builds of twrp running aswell but the screen doesnt seem to work on them
also had some success building cm11 but somethings bugged with the internal storage and its pretty unusable like that
i would have a better chance building cm12 or LOS13 but somethings up with the device blobs and the display doesnt work on android 5 or up (which it should)
Tibix250 said:
Hey
Bit late and not twrp but i got cwm recovery running you still need it
https://github.com/tibixh/android_device_samsung_heatqlte/releases/tag/stable
had several builds of twrp running aswell but the screen doesnt seem to work on them
also had some success building cm11 but somethings bugged with the internal storage and its pretty unusable like that
i would have a better chance building cm12 or LOS13 but somethings up with the device blobs and the display doesnt work on android 5 or up (which it should)
Click to expand...
Click to collapse
Thanks, I'll test it! I'll let you know if it works or not
Update: works fine
adisskiteam12 said:
Thanks, I'll test it! I'll let you know if it works or not
Update: works fine
Click to expand...
Click to collapse
Glad it works
I hope i can figure out the display drivers in the near future and start working on LineageOS 13/14 but there's still a lot to figure out
https://forum.xda-developers.com/t/recovery-twrp-3-1-1-0-for-sm-g357fz-ace-style.4453469/
Related
Hi guys,
First up here are the details of the phone that I am currently using:
Zeaplus M7
MediaTek MT6752
Android 5.0
Root = YES
Unlocked = YES
Secure = NO
The Problem
I have compiled CWM using the CM-11.0 branch, and TWRP using the OmniRom and TWRP Minimal sources, but I always end up with the same problem, regardless of whether I flash CWM or TWRP.
After flashing either of the recovery.img files to the phone, I can attempt to boot into recovery and what happens is the phone restarts, sits at the splash logo (boot screen) and sits there for around 15-30seconds (using the stock recovery, it will already have booted by this point), and then it will just restart the phone and it will continue to boot to the system as normal.
This happens on both CWM and TWRP. What is causing both the recoveries to hang at the boot screen without actually entering the recovery? Is there a way I can get a logcat or log of what is happening during the recovery bootup so I can check if there are any error messages going on behind the scenes that I am missing out on?
If you need anymore information please let me know!
Thanks
Just committed the most recent files for a CWM (11.0) build. (Also contains some older files used for the TWRP build)
https://github.com/alien-13/android_device_zeaplus_m7
Hopefully that may help out a little bit more. Not 100% sure what could be causing the issue as the P6000 has a working TWRP, and I have based this device tree around the P6000 device tree (with specific changes made to suit the M7).
Not sure if this will help, I also have the z+m7 , have tried the ele p 7000 Rom on it and it works fine, twrp installs fine, but will not download from playstore , both are from needrom made by s7yler, when I go back to m7 Rom with the p7000 twrp package exactly the same happens as happens to your phone, have noticed in m7 Rom and Mijue t500 Rom which are the same, there is a file called Encrypt, which I have never seen in other roms.could this be a problem
There is now a twrp for the zeaplus m7 on the zeaplus forum
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
DJABHipHop said:
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
Click to expand...
Click to collapse
I always disable screen timeout in the settings of TWRP so I haven't run into that issue. Im not sure why you would say its buggy as hell. I dont think a screen timeout bug qualifies it for all that. Just disable screen timeout in twrp settings and move on. Certainly not a reason to downgrade, but to each their own I guess.
some one please port it to t330nu ...
MTP
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Reshan Kariyawasam said:
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Click to expand...
Click to collapse
Let me know if the camera and mic work
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
mrdreamers said:
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
Click to expand...
Click to collapse
Thats really odd!
As of right now I've seccessfuly fixed the microphone but its still really quite witch requird more digging all soulutions are welcome at this time freas build comming today for t530&t530nu user new thread started by to posted all device fixes and rom tweaks to The Samsung Galaxy Tab 4 in general.
https://drive.google.com/drive/folders/1F3qVR2Gy-SCqFwg5El7-aeGn6UhX-_-_?usp=sharing
DJABHipHop said:
Thats really odd!
Click to expand...
Click to collapse
ya i just odin firmware and started over no root no recovery, its a x-mas gift to my sister and law anyway she don't need all that, she's not nerdy like us lol!!!!
How it look?
How's the recovery doing? Is it working fully?
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
PizzaG said:
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Click to expand...
Click to collapse
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
srialmaster said:
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
Click to expand...
Click to collapse
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
nico3dd said:
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
Click to expand...
Click to collapse
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
PizzaG said:
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
Click to expand...
Click to collapse
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
nico3dd said:
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
Click to expand...
Click to collapse
At this point I would probably start over from scratch and flash stock with Odin. How did you try installing updated TWRP?
If you want me to update the tar file with newer TWRP so it can be flashed with Odin, send me the tar file of old twrp and the newer twrp img file and i'll get that done for you.
can you please port the twrp to the t330nu?
zuhero said:
can you please port the twrp to the t330nu?
Click to expand...
Click to collapse
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
PizzaG said:
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
Click to expand...
Click to collapse
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Delete
---------- Post added at 06:12 AM ---------- Previous post was at 06:08 AM ----------
zuhero said:
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Click to expand...
Click to collapse
If you know how to get skype working on the tab 4 for matisse & milet device hit me up on tellgrem @DJABHipHop I can sure use the help with fixing all the little but anoying bugs.
Thenk in advance.
I'm trying to get Magisk to work on a Samsung S2 Tablet SM-T713. I don't think it's relevant, but I'm running LineageOS 16.0 (the 4/5/19 nightly), and TWRP 3.2.3. I had enabled OEM Unlocking before I installed either of those.
I installed Magisk Manager 7.1.1on the tablet. I pulled the stock boot.img from a stock installation image (T713XXU2BRB2_T713OXA2BRA1, which was the same firmware I had before upgrading to LineageOS). I then used Magisk Manager 7.1.1 to create a patched boot.img. I then used TWRP to flash the patched boot image to the boot partition.
The result is that my tablet is now bricked at the initial boot screen (the one that says "Samsung Galaxy Tab S2") with an error in the corner that says "Set Warranty Bit: kernel".
I'm assuming that once the battery runs down I'll be able to boot into either recovery or Odin download mode and re-flash the boot image. Since having a non-removable battery makes trial and error very slow (since I need to let the battery run down before I can reboot), I'd really like to understand what I'm doing wrong before I try installing Magisk again.
All of the threads I've seen about people installing Magisk on the T713 are from last year. Is anyone still using that combination? Even if you're not, I'd appreciate any suggestions!
Thanks in advance for any help.
Dr. Drax said:
I'm trying to get Magisk to work on a Samsung S2 Tablet SM-T713. I don't think it's relevant, but I'm running LineageOS 16.0 (the 4/5/19 nightly), and TWRP 3.2.3. I had enabled OEM Unlocking before I installed either of those.
I installed Magisk Manager 7.1.1on the tablet. I pulled the stock boot.img from a stock installation image (T713XXU2BRB2_T713OXA2BRA1, which was the same firmware I had before upgrading to LineageOS). I then used Magisk Manager 7.1.1 to create a patched boot.img. I then used TWRP to flash the patched boot image to the boot partition.
The result is that my tablet is now bricked at the initial boot screen (the one that says "Samsung Galaxy Tab S2") with an error in the corner that says "Set Warranty Bit: kernel".
I'm assuming that once the battery runs down I'll be able to boot into either recovery or Odin download mode and re-flash the boot image. Since having a non-removable battery makes trial and error very slow (since I need to let the battery run down before I can reboot), I'd really like to understand what I'm doing wrong before I try installing Magisk again.
All of the threads I've seen about people installing Magisk on the T713 are from last year. Is anyone still using that combination? Even if you're not, I'd appreciate any suggestions!
Thanks in advance for any help.
Click to expand...
Click to collapse
any luck?
pointbob said:
any luck?
Click to expand...
Click to collapse
I wound up having to let the battery run out. Then I had to do finger acrobatics to hold down the buttons for download mode while I plugged in a USB cable attached to my computer. That allowed me to use Odin to install a stock boot image.
I ultimately figured out that the problem was that my data partition had automatically re-encrypted itself. I found I had to use TWRP to wipe my data partition, then immediately use TWRP to install Magisk so that my bootloader wouldn't force encryption. A reboot between those two steps screws things up.
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.