Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Related
Guide to rooting infocus Epic 1 (for windows) for build 00.
This method is only tested on build 00IN_1_360 only. If you are on the older build, first update your phone to build 00IN_1_360 then proceed. Check Build number in settings->about phone.
Proceed at your own risk, I will not be help responsible if your phone bricks, Your warranty will be void after this. Also all phone data will be lost including data on internal memory like photos, etc after these steps so take necessary backups.
Prepare your system
1. Extract and Install MTK Driver Auto Installer v5.1632 (google it)
2. Install Phone F Driver (from phone CD-emulation/driver folder upon connecting your phone)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
4. Download latest SuperSU flashable zip file from here
5. Download twrp-3.0.3-0-epic1-noveritynoencrypt.zip from here, extract in the folder where you have installed adb and fastboot
6. Download noencryptnoverty_boot.zip from attachments and extract to folder where you have installed adb and fastboot
Steps to root:
1. Enable Developer options in phone settings (goto phone settings -> about phone -> tap build number 7 times)
1a. Enable OEM unlock
1b. Enable USB Debugging
2. Connect phone to computer, wait for hardware to auto install
3. open cmd as administrator
3a. goto the directory where adb and fastboot is installed
4. type command:
4a.
adb reboot bootloader
(Wait for phone to come in fastboot)
4b.
fastboot OEM unlock
(press vol up key on phone)
4c.
fastboot flash boot noveritynoencrypt.img
4d.
fastboot flash recovery recovery.img
4e.
fastboot reboot
You will get an phone orange state prompt, do not worry its normal. Phone may reboot once or twice. Wait for phone to normal bootup.
5. open cmd and type command
5e.
adb reboot recovery
Phone will reboot in recovery i.e. TWRP
6. Tap on Keep system read-only. Do not swipe to allow modifications. If TWRP asks for password, don't enter any press back.
7a. Tap Wipe -> Format Data. Come out to main menu, then click reboot and then recovery to restart recovery.
7b. Tap Wipe -> Advanced Wipe -> Select Dalvik /ART, Cache, Data and Internal Storage. This is important step, as these partitions are encrypted at the moment, so if you flash anything the phone rom may corrupt.
8. Come out and then Tap Reboot -> System
9. Once the phone is back, turn off the phone. Then power on with vol up key pressed to boot into TWRP
10. Tap Backup, select all partitions, select phone storage (SD card preferred) and take backup (optional step but highly recommended )
11. Now tap install, goto the location where you had copied SuperSU zip file, flash it.
Congratulations your Phone is rooted. Reboot, see SuperSU icon in app drawer.
Many thanks to @mujammil786 for providing stock files and @Bornstud for testing twrp builds
Special thanks to our devs @DespairFactor for modifying boot.img to disable Encryption and Verity and @kirito9 for creating TWRP for our device. Without their help, it wouldn’t have been possible.
MODS
(Take backup of your ROM/Data before applying any mods)
Viper4Android (Advanced Sound Enhancement)
Hugely Customizable and better than MaxxAudio or Dolby Atmos IMHO
Now working on our device Infocus Epic 1
Need to flash the 2 attached files via TWRP before installing the official app from HERE. Although latest version v2.5.0.5 also works, but i personally prefer v2.4.0.1 (busybox required)
(Note the attached files are not my work, they are picked from here and here. Say thanks to original contributors.)
Good V4A profile: HERE
Extract it to ViPER4Android Directory in internal Storage
Xposed
Needs no introduction. Every android enthusiast should know what it is. Anyway if you are new, xposed opens limitless ROM customization(s) and useful features via 100s of its modules.
Installation:
1. Flash framework xposed-v87-sdk23-arm64.zip from HERE via TWRP. Reboot after installation will take long time (~10 - 15 minutes)
2. Install app XposedInstaller_3.1.1.apk from HERE
Restoring phone back through SUT
If you are stuck somewhere or want to restore the phone factory state (like for when giving to repair), you can restore the phone back via SUT
Link for build 1280: https://firmwarefile.com/infocus-epic-1
Also dont turn off your phone as suggested in sut readme file. It only works when your phone is on. Check below vid for more instructions
https://m.youtube.com/watch?v=eV_cId5fC9E
Reduce battery consumption & phone temperature
Found an interesting thread, mod works on our device also
https://forum.xda-developers.com/red...tings-t3687897
I have tried both flavor 1 and flavor 2 over the past week. Results with flavor 1 were positive in the beginning but for some reason standby drain shot up after 3-4 days, not sure what the reason was.
On flavor 2, I have just disabled MTK perfservice by setting
ro.mtk_perfservice_support = 0 in build.prop
Yes this limits the a72 core to 1.5ghz, but i have noticed phone is heating less and need for charging the phone has reduced. I haven't noticed much drop in performance either, but that might be as I don't use intensive apps.
Mafioso said:
I've managed to unpack nb0 file through a688 tool, however its only successful in unpacking few files before it crashes with some array size error, but the good thing is I was able to extract the scatter file for this phone before it happened.
Anyway, I was hopeful that I would be able to make backup of Stock ROM and Recovery through it via spflash tools however as it turns out, spflash tool is giving me error while doing readback BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
Not sure how to fix it, i've updated my drivers as well as i'm using latest version of spflash tool (SP_Flash_Tool_v5.1628_Win)
Attaching scatter file.
Click to expand...
Click to collapse
From where uve downloaded the stock firmware
Romeotamizh said:
From where uve downloaded the stock firmware
Click to expand...
Click to collapse
http://firmwarefile.com/infocus-epic-1
Mafioso said:
http://firmwarefile.com/infocus-epic-1
Click to expand...
Click to collapse
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Romeotamizh said:
Oh
Click to expand...
Click to collapse
Look in other sites bro for img files
Romeotamizh said:
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Look in other sites bro for img files
Click to expand...
Click to collapse
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Mafioso said:
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Click to expand...
Click to collapse
Ooh bro I'm happy to help but seriously i Duno about these kind of extensions hope u understand
Mafioso said:
I'm trying to root Infocus Epic 1, its a good budget phone with decent specs. Availability is only in India, not sure other regions. Anyway I'm having hard time to root it, since not much support is available. But so far, I have tried below things:
1. Tried to root with Kingroot, doesn't work .Probably because it is very new version of Marshmallow with Oct'16 patch level and kernel dated in dec 16.
2. Tried to generate scatter file via MTK Droid tool v2.5.3, after enable USB debugging in phone. The phone get detected in the tool, however create scatter file option in block map is disabled I've read somewhere, it might be due to MTK6797 (Helios x20) is quite new and is not yet fully supported by tool yet. Not sure if its true though. But if I can generate scatter file, I can extract phone's stock recovery via SPFlash tool readback to try a hand at porting twrp/cwm with some help..
3. Downloaded stock Infocus Epic 1 firmware in hope for recovering stock recovery.img or MTK scatter file, however on unpacking the firmware package, I found it contains unknown image file of nb0 extension which is it to be flashed via SUT Tool. Not sure how to unpack this file
Any more ideas, how can i atleast start with my quest to root/put custom recovery on this phone ? @Romeotamizh Pls help.
Click to expand...
Click to collapse
I can give u stock recovery of epic 1..
mujammil786 said:
I can give u stock recovery of epic 1..
Click to expand...
Click to collapse
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Mafioso said:
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Click to expand...
Click to collapse
I was able to extract it from last update zip
---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------
Epic 1 stock recovery
https://drive.google.com/file/d/0B4FNo4vddleCNmpwcS1hS3FLam8/view?usp=drivesdk
mujammil786 said:
I was able to extract it from last update zip
Click to expand...
Click to collapse
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Mafioso said:
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Click to expand...
Click to collapse
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
mujammil786 said:
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
Click to expand...
Click to collapse
thanks, updated first post.
Mafioso said:
thanks, updated first post.
Click to expand...
Click to collapse
Thanks let's hope for best
I like this phone and the only thing lacking is Root, Hope someone will do it
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Mafioso said:
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Click to expand...
Click to collapse
My device does not get detect in fastboot can u show me screen shot of command u are trying....
mujammil786 said:
My device does not get detect in fastboot can u show me screen shot of command u are trying....
Click to expand...
Click to collapse
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Mafioso said:
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Click to expand...
Click to collapse
Ok will try thanx
bootloder get unlocked and locked too
ok so phone get detected in fastboot mode:victory: .was able to lock and unlock boot loader but without custom recovery it is no useful for us.
unlocked bootloader.
tried flashing Vernee_Apollo_Lite_P6(same spec. as epic 1) twrp recovery.
flashing done but after flashing phone refused to boot.
flashed stock recovery from update zip.
locked bootloader.
phone booted but erased internal memory after boot.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
do you know any guide for making twrp and i think phone will not boot if it detect any change in system partition i think
Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
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.