Hi guy
I recently got the bluboo s1 , I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the bluboo S1
Anyone knows if I can use the TWRP for the bluboo S1 or is there any other way to root my phone?
the phone runs pretty good , but when i listen music by bluetooh is always cutting off sound when is screen off. i think that is powersaver that set cpu to very low frequency .. so i need to root to change governador
thanks , sorry for my bad english
Root bluboo S1
Yes please... I want to root it too.
I need root my bluboo s1 too. Thx
You have to try this, Same processor, Same android v. We need to tey allways
bbfsonic said:
Hi guy
I recently got the bluboo s1 , I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the bluboo S1
Anyone knows if I can use the TWRP for the bluboo S1 or is there any other way to root my phone?
the phone runs pretty good , but when i listen music by bluetooh is always cutting off sound when is screen off. i think that is powersaver that set cpu to very low frequency .. so i need to root to change governador
thanks , sorry for my bad english
Click to expand...
Click to collapse
Try this please, my S1 is upcomming and i want to solve it before unbox hhhhb... (Madrid, airport barajas. Im on Toledo, spain.)fkng 32dys.. waiting it
"foro.root4ever/Tema-Tutorial-Elephone-P8-root-recoverys-roms-4443"
Its . Com
Root found!!! Bluboo s1 magisk v.14!!! 1rst im doned
bbfsonic said:
Hi guy
I recently got the bluboo s1 , I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the bluboo S1
Anyone knows if I can use the TWRP for the bluboo S1 or is there any other way to root my phone?
the phone runs pretty good , but when i listen music by bluetooh is always cutting off sound when is screen off. i think that is powersaver that set cpu to very low frequency .. so i need to root to change governador
thanks , sorry for my bad english
Click to expand...
Click to collapse
The 12 of OCT i will post a Guide for it.
Super easy.
Only need a patched stock boot.img image
And unlock the phone before flash it.
Fastguide:
Requisites...
Fastboot/adb tools and drivers
Firmware V10 (lastest update)
Unlock Bootloader
Start!!
Connect bluboo S1 on fastboot mode.
With adb/fastboot tool.
Write:
fastboot oem unlock.
Take your phone and press vol+ (same as accept unlock process)
Now your bootloader its free and your phone will FORMAT.
(Only keeping the system base)
Now with your bootloader open... Wait for reboot android UI.
Download the lastest Magisk Manager.apk (search on ggle "V5.3.0" works on my own) and install IT.
Download this file on mega. And remove ESPACES from-the-link (MOST IMPORTANT)
mega. nz /#!xQtwnR7S!h1vylwQd3u_lUZ4Cbkw_S8YOsL2VskIDuVfbNTTkEis
(Img Patched with magisk v14/stock boot.img from Bluboo S1 Compilation V10, android 7.)
Now if u have the .img from MEGA.. Rename it "boot.img" and place it on the "adb/fastboot" Folder
Open adb/fastboot tools, write:
adb reboot fastboot
And simple...wait for fastboot and write:
fastboot flash boot boot.img
Blablabla, OKAY!
And reboot it:
Fastboot reboot
And keep sure all has been doned on magisk manager check it.
Hi !
My S1 is not detected by ADB...But my Windows 10 did it, so i can't update the boot.img, can somebody help me please ?
Unlock bootloader
Mr.N0S said:
The 12 of OCT i will post a Guide for it.
Super easy.
Only need a patched stock boot.img image
And unlock the phone before flash it.
Fastguide:
Requisites...
Fastboot/adb tools and drivers
Firmware V10 (lastest update)
Unlock Bootloader
Start!!
Connect bluboo S1 on fastboot mode.
With adb/fastboot tool.
Write:
fastboot oem unlock.
Take your phone and press vol+ (same as accept unlock process)
Now your bootloader its free and your phone will FORMAT.
(Only keeping the system base)
Now with your bootloader open... Wait for reboot android UI.
Download the lastest Magisk Manager.apk (search on ggle "V5.3.0" works on my own) and install IT.
Download this file on mega. And remove ESPACES from-the-link (MOST IMPORTANT)
mega. nz /#!xQtwnR7S!h1vylwQd3u_lUZ4Cbkw_S8YOsL2VskIDuVfbNTTkEis
(Img Patched with magisk v14/stock boot.img from Bluboo S1 Compilation V10, android 7.)
Now if u have the .img from MEGA.. Rename it "boot.img" and place it on the "adb/fastboot" Folder
Open adb/fastboot tools, write:
adb reboot fastboot
And simple...wait for fastboot and write:
fastboot flash boot boot.img
Blablabla, OKAY!
And reboot it:
Fastboot reboot
And keep sure all has been doned on magisk manager check it.
Click to expand...
Click to collapse
When i press vol up to accept , it fails
Says
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 4.480s
:crying::crying:
bbfsonic said:
When i press vol up to accept , it fails
Says
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 4.480s
:crying::crying:
Click to expand...
Click to collapse
YEEEEES !!! it works Finnaly, i couldn't do it because is needed to go and activate OEM unlocking on developer options and follow the rest of tutorial !
Minimal ADB & Fastboot 1.4.3
JaMaYe said:
Hi !
My S1 is not detected by ADB...But my Windows 10 did it, so i can't update the boot.img, can somebody help me please ?
Click to expand...
Click to collapse
I get the job done using Minimal ADB & Fastboot 1.4.3 download/install it , drivers is included :good: Press (Y) key for everything
Sure itswork, but is a SYSTEMLESS Root, only for wifi tests, adblock works... Rarelly almost on 75% of apps allow it
but works
We need DEVELOPERS. CAN I HELP, but im not a rom chef.
---------- Post added at 06:46 PM ---------- Previous post was at 06:46 PM ----------
Sure itswork, but is a SYSTEMLESS Root, only for wifi tests, adblock works... Rarelly almost on 75% of apps allow it
but works
We need DEVELOPERS. CAN I HELP, but im not a rom chef.
Thank you all. I successfully unlock my S1.
And now, I want to remove FreeTouch and SCWeather. Because they are malware reported by Malwearbytes.
Please tell me how to do it?
rr0909 said:
Thank you all. I successfully unlock my S1.
And now, I want to remove FreeTouch and SCWeather. Because they are malware reported by Malwearbytes.
Please tell me how to do it?
Click to expand...
Click to collapse
You can remove them with malwarbyte, for exemple, or others applications which uninstall systems apps.
Can you give us a feedback of your unlocking please ? Everythings works great ? (wifi, caméra, 4G, ...)
I'm also struggling to remove the system apps after rooting. When I try to uninstall SCWeather or Freetouch using System App Remover (root) I get uninstall failed. Any other ideas for removing these apps.
Any ideas for now, i have disabled it... But this virus i think is made by bluboo and allow with it some apk's ad-works
For example some app downloaded in playstore got secrets, mirrors and redirections... Fckng ads jeje
I said it because... Some ads-apps will create on your screen more than a one **** with a cross in the upper corner.
Yesterday i have downloaded one apk on play store by the name
"navbar apps"
Its a great app for modify tha n.bar
Working by systemless root (our owned root) by great and patched with Lucky.P with buggy selinux permissons
It ask me for root permisson but we cant install busybox
And lucky patcher saids "no busybox found, lucky patcher its not working"
we have one thing or something wrong... Bluboo dont post any homemade development post's, any unlock for boot users or usefull guide's.. Anything guys...
WE Made IT - We SKATE it.
We can work for now, by testing our progress.
For now we are... 3, or 4 users with this great phone on this great forum.
Search somehelp.
We can made some progress.
Ty for all, ask for help guys if anyone know a romchef, scripter for selinux...
With experience on chinese mtk's helio tree devices.
And
If any modder, kitchen or...lool are bored, help us with this fantastic device.
here is a CWM recovery for our device https://www.androidfilehost.com/?w=search&s=bluboo+s1 can be flashed easily via fastboot, I get some issues with touchscreen trying to porting a TWRP, it`s not responsive and I don`t know much about nougat. This CWM don`t take a backup of rom but anyway...waiting for a TWRP.
For those who want root completely can install in recovery via adb sideload last version of Magisk v14.0 or supersu v2.82 too.
And to uninstall undesired apps just do it manually with a root file explorer like ESFile deleting corresponding files in /system/app, /system/priv-app, /data/app and deleting all cache files (just all) in /data/dalvik-cache/arm and arm64, reboot device. Be carefully selecting; Free Touch, CZWeather and launcher can be removed (put other) with their four themes
SubwayChamp said:
here is a CWM recovery for our device https://www.androidfilehost.com/?w=search&s=bluboo+s1 can be flashed easily via fastboot, I get some issues with touchscreen trying to porting a TWRP, it`s not responsive and I don`t know much about nougat. This CWM don`t take a backup of rom but anyway...waiting for a TWRP.
For those who want root completely can install in recovery via adb sideload last version of Magisk v14.0 or supersu v2.82 too.
And to uninstall undesired apps just do it manually with a root file explorer like ESFile deleting corresponding files in /system/app, /system/priv-app, /data/app and deleting all cache files (just all) in /data/dalvik-cache/arm and arm64, reboot device. Be carefully selecting; Free Touch, CZWeather and launcher can be removed (put other) with their four themes
Click to expand...
Click to collapse
Hi ! When I use adb sideload to root the phone with Magisk v14.0 or supersu v2.82 i have a message "Installation aborted" and off course i dont know why...
JaMaYe said:
Hi ! When I use adb sideload to root the phone with Magisk v14.0 or supersu v2.82 i have a message "Installation aborted" and off course i dont know why...
Click to expand...
Click to collapse
Be sure follow next: go to recovery, connect to device, go to install zip menu, install via adb sideload, then type in terminal to check if device if recognised: adb devices put and rename for short file magisk. zip inside adb folder and type adb sideload magisk. zip don'forget file extension
'Normal its same doogee mix you need decrypt your data for the root is in system and all apps work with supersu ,for adb you can use this programm adb automotic 0 command all its automatic just replace your file
Link: https://www.needrom.com/download/root-twrp-toolkit-doogee-bl5000/
Regards
PS: when you say decrypt data its easy
Envoyé de mon MIX en utilisant Tapatalk
The sheer amount of different android devices will make it really hard to get things rooted with one tap in the future. Most one tap roots already stoped working for a lot of my stuff.
I successfully unlock my S1, but it´s a SYSTEMLESS ROOT!
How do I get full root? I want delete some privates apk
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
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent ?
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Rooted using same method but SP Flash Tools worked in my tablet.
Waiting for a TWRP ....
Yes, can confirm that method works for root.
Also tried the T10 TWRP and it's not working on the T8, just a black screen.
Don't need TWRP yet, some bugs in the ROM are more annoying than that
hi all
somebody tried the new rom v1.10 on needrom ??
marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
HI quick question what rom have u installed in ur T8, mine came with 1.01, i see in needrom have 3 versions: 1.06. 1.08, 1.10, have u updated to any of these?
Thanks
Polo19 said:
Hi everyone,
This is what I have done to root my Teclast T8 with Magisk (based on this chineese forum: http://tieba.baidu.com/p/5449087481)
1-First download the official firmware from Needrom.com (You need to register): https://www.needrom.com/download/teclast-t8-e8c1/
2-Go to the Firmware folder and copy the “boot.img” file to the root directory of your tablet
3-Download and install MagiskManager on the tablet, click on Install, then choose to patch the boot image file. Choose the boot.img you’ve just uploaded to your tablet and it will start to automatically patch it.
Then go into the File Manager and go to the MagiskManager folder and find the “patch_boot.img“ and copy it to the root directory (without copying it to the root directory, you can not find the file from your pc…), then sends the file from the tablet to your computer.
4-For me the method with SP Flash Tool don’t work, because it says the scatter file is wrong (don’t know why…)
So i have to do it with adb and unlock the bootloader first:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
-reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Your bootloader is now unlock.
-then copy the “patched_boot.img” in the adb folder and tap in command prompt “fastboot flash boot patched_boot.img”, then “fastboot reboot”.
Your tablet should be rooted.
I think you can relock bootloader after... don't try yet.
PS: This is my first thread, so be indulgent
Don’t ask me technical questions because I am not a developer , just a simple user …
Hope this will help.
If someone find a way to find and flash a TWRP or how to install Xposed, please tell me, thx.
Click to expand...
Click to collapse
Flashing ROM with SP flashtool - Teclast Master T8 (E8C1)
Fossxp13 said:
Hi guys i jus download v1.10 rom but have no idea how to flash, everything in chinesse... even recovery, how do you flash? the tablet have a TelcastOTA apk installed, this have a local update option allow to load firmware from sd, anyone used this app? what files should i put in SD?
thanks in advance
Click to expand...
Click to collapse
Hi! I haven't used in built update app so I'll try to explain how to update using flashtool. Follow the steps with your device disconnected from the pc and take into account your files will be erased.
First of all, I recommend you to install ADB and fastboot drivers: 15 seconds ADB Installer
As OP said download the rom from NeedRom and unzip it: You will have three folders:
升级工具, which contains flashtool
固件程序, with the rom
驱动程序, with the drivers
Rename all of them as flashtool, rom and drivers, for example. If you don't, you may have troubles launching flashtool or loading the scatter file.
Launch flashtool as administrator (升级程序, you could rename it too), if you get the message "The scatter file cannot found, please make sure the file exist before download" ignore it. In flashtool make sure MTK_AllInOne_DA.bin is selected as Download-Agent and select the scatter file inside rom folder as Scatter-loading file. Choose firmware upgrade from the list and click the Download button (the one with the green arrow).
Finally, switch off your device and connect it to your pc. Flashtool should do the rest, wait untill "Download Ok" message is displayed. Close flashtool, disconnect your device and switch it on.
IF your computer doesn't load needed drivers automatically, flashtool won't start the process as expected. You will need to open device manager on windows, right click on your device - update driver - choose manually - browse "inf" folder inside drivers folder (choose x86 or x64 according to your OS).
Hope it works! Good luck.
Prevent Brick and Xposed for Teclast Master T8 (E8C1)
Polo19 said:
OP
Click to expand...
Click to collapse
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Just need TWRP and I'm happy.
There's a chinese TWRP but it's not working decently.
Rotiaiso said:
Hi Polo19!
Thanks for your post, I rooted my tablet following it! But since I encountered some issues in the process I wanted to share my experience.
IMPORTANT: For a few hours I thought I hard bricked my device, so I hope I could help somebody.
When patching boot.img with MagiskManager IF the app automatically tics "Keep force encryption" choose "Keep dm-verify" aswell!
I don't know why but this was the only way to make it work on my device, I kept getting a encryption error after flashing the patched boot.img, despite the fact that I have never encrypted my device.
After getting that error I tried to flash the clean rom again, but flashtool gave an error and the tablet completely died! Well, it seemed so.
It's pretty stupid but the only way to make it work again was pushing the reset button on the top right corner of the tablet for a few seconds and flashing the rom again.
About Magisk: use the OFFICIAL MAGISK XDA THREAD to download it, as https://magiskmanager.com/ is NOT the official website.
In step 3, I couldn't find the patched_boot.img file even after moving it to the root directory. So I had to (let the patched_boot.img file in the default directory):
Install ADB drivers in the computer: https://forum.xda-developers.com/showthread.php?t=2588979
Enable USB debugging in developer options in the tablet, connect it to the computer and accept the connection.
Open command prompt / powershell: "shift + right click" wherever you want to copy the patched_boot.img and open cmd or power shell.
Run the command:
In step 4: you won't encounter that problem if you rename downloaded folders and get rid of chinese characters. Simply open flashtool, choose the scatter file, untick all options except boot and change the default boot.img with the patched one (I renamed it to boot.img, I don't know if it's necessary)
Xposed: you can install xposed using MagiskManager.
Install Xposed Installer for Magisk, go to download tab in MagiskManager and install Xposed SDK24 (for android 7.0) and reboot
Sources:
15 SECONDS ADB INSTALLER
MAGISK
SYSTEMLESS XPOSED
CHINESE FORUM
Click to expand...
Click to collapse
Yes, i also install Xposed using MagiskManager and it works. Now i am able to use all fonctions of Greenify, Amplify, Powernap and get a pretty decent standby batterylife.
marinero57 said:
hi all
somebody tried the new rom v1.10 on needrom ??
Click to expand...
Click to collapse
Hi, I tried to follow the procedure but in ROM 1.10 doesn't work
---------- Post added at 01:37 PM ---------- Previous post was at 12:44 PM ----------
With the news roms doesn't work...
What is the rom that was working this WA??
Thanks!
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install MagiskManager-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting MagiskManager update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Kerrnel said:
I just did this to a tablet that had OTA'd the 1.10 - using the 1.10's downloaded boot and latest Magisk Manager 5.5.4 / Magisk 15.3 beta
OEM Unlock, patching boot image and patched boot image flashing worked
BUT - the included Magisk Manager does not launch after installing upon reboot...
HOWEVER - V5.5.3 of the manager did work.
$ adb -s 0123456789ABCDEF install *************-v5.5.3.apk
Success
$ adb -s 0123456789ABCDEF shell
t8_e8c1:/ $ su
t8_e8c1:/ #
Notes
1. Tablet is wiped
2. Boot delay of 5 seconds is added with "can't be trusted" warning in white text
3. Fails safetynet
Letting ************* update itself to 554 also worked - so I think my method of just installing the apk from the Magisk zip's common folder was wrong.
Click to expand...
Click to collapse
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
i have the ota 1.10 update and the rooting was successful. magisk and xposed working flawlessly.
another point:
i have closed the bootloader after flashing the patched boot.img with "fastboot oem lock".
the device boot up is faster and the warning "...5 seconds" is gone.
now, i wait for twrp.
You dont need to unlock bootloader.
Just flash patched_boot with flash tool.
Zaphodb69 said:
Hi,
My T8 arrived yesterday and I've used OTA to update to 1.10.
Is the sptools method working with 1.10 or do I need to use this process?
Also where to the numbers 0123456789ABCDEF come from in the instructions I've quoted?
Thank is advance
Click to expand...
Click to collapse
I had multiple devices attached to the PC.
No -s ABC... needed if you only have the one.
Sent from my T8(E8C1) using Tapatalk
The suggested worked for me. I will also mention that you must be connected to the internet to patch the boot.img file with magisk manager (otherwise, the option will not be presented in the magisk manager GUI).
Were there made any changes for the fingerprint? Soimebody mentioned, it isn´t that good. Maybe the last updates change something...
Hi everyone
I have been trying to root my cubot rainbow with no success, I have trier every way possible on which I will list.
King root - apk and PC version
Kingo root - apk and PC version
Iroot - apk and PC version
Towel root - didn't Evan let me open this app
Root genius - apk and PC version
Then I tried custom recovery, I got the tools of needrom and I got to it I did everything right I -
Unlocked my boot loader (I think) as once I accepted to unlock it there was no way to check if it actually was unlocked because everytime I did "fastboot OEM device-info" it returned something like "Failed(no controller)" < something like this anyway so with me not really knowing if IRA unlocked or not I went onto the next step.
With the scatter file and recovery.IMG to hand I opened up sp flash tools and then tried to flash the recovery. It then told me everything went okay and it was done. But when I boot to recovery it's still at stock.
I then tryed flashing with fastboot and same thing happens it tells me its all okay but its actually still stock
This leads to is my bootloader acc unlocked then? (I did try multiple times and uninstalled and reinstalled drivers)
So anyway is there any way to root my phone?
Instruction here http://4pda.ru/forum/index.php?showtopic=741031&st=1000#entry54800941
but on russian
Thank you for your reply I have had a look and from what I can understand it looks positive, but.... I can't find the instructions or translate them properly for the actually rooting
Here google translate of first post, bold below it is what you need:
1. Fully comply with the instructions for the firmware of custom recovery
2. Download and put in the root of the SD card archive SuperSU
3. Turn off the smartphone, hold down the + volume and power buttons simultaneously, select "Recovery Mode"
4. Select "Installation" and select the previously downloaded archive.
5. Reboot the phone.
After enabling, Root-rights and SuperSU will appear.
Click to expand...
Click to collapse
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
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Try this
Planet Indigo said:
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Click to expand...
Click to collapse
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
KIBS2173 said:
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
Click to expand...
Click to collapse
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Planet Indigo said:
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
Click to expand...
Click to collapse
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Karamarov1 said:
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Click to expand...
Click to collapse
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
KIBS2173 said:
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Click to expand...
Click to collapse
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Try this
Planet Indigo said:
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Click to expand...
Click to collapse
Hi there,
So i was researching more about this tablet, turns out you can root by installing a custom recovery (TWRP) and from there you can install SUPERSU to achieve root for your tablet. I am not sure if this method works, but if your able to get the stock firmware and the stock recovery and the software to flash the firmware i think you might as well go ahead using that method.
THIS IS THE ARTICLE I FOUND ONLINE :
https://www.getdroidtips.com/how-to-install-twrp-recovery-on-teclast-t30-and-root-it-easily/
*MAKE SURE YOU FIND OUT IF THIS TABLET HAS A TWRP RECOVERY BEFORE DOING ANYTHING ELSE*
Thank you for looking into it, unfortunately that guide is for the Teclast T30 and the guy advises to only use it for that model. I don't own that tablet yet so I can't try any of the steps myself but I'm very interested in this particular model (16/9 ratio, hdmi out, dc charger in, etc...) so I was really hoping to find a tested working method to root it before I go ahead and purchase it.
i found this: https://www.getdroidtips.com/root-teclast-m16/
I rooted my Teclast M16 using Magisk. Simply unlocked the bootloader through adb/fastboot commands, then have magisk manager patch the boot image from firmware download and then flash it using adb/fastboot command line fastboot flash boot magisk_patched_boot.img reboot system and its rooted.
I haven't found a twrp recovery yet, but I'm thinking about trying my hand at building my own, despite being a noob.
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Hi. Have you got you on working twrp recoberto?
fdsafggg said:
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Click to expand...
Click to collapse
Hi.
I tried to unlock the bootloader .
adb devices command shows the m16.
I send the command "adb reboot bootloader" - the device enter in bootloader.
next I send the command "fastboot devices" and I get this:
PS E:\modified_fastboot> fastboot devices
???????????? fastboot
any help to make fast boot see the device?
Thank you
dcoelho said:
Cześć.
Próbowałem odblokować bootloader.
Polecenie urządzeń adb pokazuje m16.
Wysyłam polecenie "adb reboot bootloader" - urządzenie wchodzi w bootloader.
następnie wysyłam polecenie „urządzenia fastboot” i otrzymuję to:
PS E:\modified_fastboot> urządzenia fastboot
???????????? szybki start
jakakolwiek pomoc, aby szybki rozruch zobaczył urządzenie?
Dziękuję Ci
Click to expand...
Click to collapse
Hi, You bad comand when bootloader. When bootloader after comand: " fastboot oem unlock" , luck on skreen, push volume up, wait moment, after next comand:"fastboot reboot". After this command, the tablet will reset to factory settings with unlocked bootloader.
Hello everyone. I have TWRP for M16, everything is almost fine, after uploading it normally work on M16, except for touch not working, I did not check if it works with the mouse. Maybe someone will find it to correct it so that the touch works? I upload the file, it may be useful to someone. Regards RW
reupload boot.img