hello everyone i need help with my mediapad 7 lite , i been searching for months and have not been able to install a single recovery like cwm twrp etc. would someone tell me what is going on , most guides stuck at fastboot and waiting for device . why is there so much shadyness would anyone post a good solution with tools etc? mediapad 7 lite s7-932u. well i hope i get a solution , i want install android lollipop , and by anymeans is there a rom for the bios to make the processor quad or dual . as simple as formating windows 98 or xp please.
I am sorry if you don't like my answer as I know your device is not the same as this TWRP but you may like to port it? or compile it?
I think you need to root your device as well otherwise you may struggle.
http://forum.xda-developers.com/showthread.php?t=2693100
Note this is tested on S7-931W while your post shows you are keen to get s7-932u.
If you use Linux you can download that TWRP, unpack it with imgRePackerRK
http://forum.xda-developers.com/showthread.php?t=2257331
then use Android to get info on where your recovery is and take a backup image of it
copy your stock recovery to Linux, unpack it with same tool as above, then swap in your kernel into TWRP and adjust the fstab and a few text files to match your ids
repack modified TWRP with imgRePackerRK and flash it.
making sure you have kept a backup on your removable sdcard.
good luck
Hope that sounds enough interesting to get you here
to my problem:
I have a Huawei MediaPad 10 Link+ and theres NOTHING out there for it. So i decided to make it on my own.
belive me theres no recovery or rom for this tablet.
i had a long journy so dont think this is my first problem
i dumped my boot.img, recovery.img and system.img
i used this tool to unpack my recovery modified it, repacked it and flashed it. but the recovery wont boot up. just stuck at the first mediapad logo.
Even if i NOT touch it. ( just unpack / repack )
my problem is not to restore it. i want a modifyd recovery. maybe sobody here can help me.
thanks in advance
PS: the best would be if somebody could port me CWM or TWRP
i tried to make it on my own but ubuntu says no and punchd me in the face
The Author of the tool stated, that it won't work on every device.
But if you plan to build cwm or twrp for your device, you will need ,sooner or later, linux.
So save yourself some trouble and time and install linux in a virtualbox.
It will make numerous things easier for you :good: .
Hello all,
My problem is I have a phone with null development (AFAIK), a LG K4 K-120E, running Android 5.1.1 with root access, and I need to find a compatible custom recovery in order to create Nandroid Backups and, logically, restore them.
I've tried Online Nandroid Backup (previous discussion in this forum here), but my device is not supported. This app generates a device code for my phone (me1) but is not on the device list. I've sent an automated support request to the developer to identify my phone but an user of this forum told me that this app is no longer mantained. Other apps such as ROM Manager and TWRP Manager are also not supported.
All in all, I wonder if it could there be a compatible custom recovery for my model, for example a K5 or K10 recovery image, and if not, how to adapt it. And if this is not possible, how could I make full system backups and restore them?
Thank you very much in advance. Regards.
Given the "success" of my post, I will try a different approach to my issue.
Since it's possible to boot a recovery image without flashing it, by connecting the phone to the computer and typing
Code:
fastboot reboot <downloaded img>
there goes my new question: Could I harm my device if I boot from several images for different LG Kx devices? For example, with K5, K8 and K10 TWRP images.
Thanks again.
I am trying to install TWRP on my phone, but there is no official or unofficial release.
I tried to flash the one for BV9900, but that wont work.
Help with customizing the recovery to suit?
Hello, I also have a BV9900E and I join the petition. Thanks in advance.
there is a forum hov...tek... that you can find a MEDIATEK tool for porting TWRP. its not perfect, and you still need to do some tweaking, but it can produce a working TWRP. (i believe a few FLAGS are not correct, so these need edited for using the MICRO SD or OTG)
ive used a few of the port tools, and they can work, but it takes some adjustments to have a FULL TWRP recovery.
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.