Related
You want to update your device, you have the OTA zipfile, but you don't know how to use it, you don't want to bricked your device!
That's why I've wrote this guide. I'm not the writer, just an adaptor for xda member
By downloading, flashing these files and use this guide you agree to the following:
Your warranty is now void.
We are NOT responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this guide before use it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you with all of my teeth.
Support is limited. I do this as a hobby in our free time. I'll do my best to help you if you state your problem in clear English, with as much information as you can (what mods you selected, have you wiped, when exactly does the error occur, what type of phone you have, what carrier, logcat and so on. The more information you offer, easier for me to help you. If you do not ask for support in clear English and with no information what-so-ever we will ignore your issue
Click to expand...
Click to collapse
Before to flash or use fastboot lines command, you need to read quietly this guide. Download all files in one folder (it's easier to find all files in the same folder).
Prerequisite: Your Nexus 7 LTE should be running Android 4.4.2 (KOT49H) or (KVT49L -for Verizon). You will not lose your data using this method
Step 1.
Download the update zip
=> Download link for almost of users => cac1a204d3770a20fdce28f6ed3418fdd36abd5d.signed-razorg-KTU84L-from-KOT49H.cac1a204.zip - md5: 34adc31c6647de18547c405133072381
=> Download link for Verizon users => f0c2187ff1dba772cff3fa7f99f0e6bd38ecb62b.signed-razorg-KTU84L-from-KVT49L.f0c2187f.zip - md5: 663b29478d60babb2f0cbb6fc506f111
Charge your Nexus 7 to at least 60% battery level
Don't forget to enable USB debugging
Don't forget - Backup your tab’s storage,
you can choose to change the file’s name to ‘update.zip’. take care
Be sure to read the instructions and carry on...
Step 2.
Reboot your Nexus 7 LTE and hold the Vol+Down button while it's booting up.
Once you see the fastboot menu and the word Start, press Vol+Up a few times until you see Recovery and then press the Power button to enter recovery
You will see an Android with a red exclamation point.if you have stock recovery
Now press Vol+Up+Power together, and you should see the menu below:
Select the 2nd option called apply update from adb.
Step 3.
Connect your Nexus 7 LTE to your computer with your USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Place the update.zip package from Google in the Android SDK/platform-tools folder on your computer, but do not unzip it. And open up a command prompt
(cmd in Windows)
(regular shell in Linux and Mac) in the same directory as the zip file.
and type
Code:
adb sideload <the name of the zip file that you've done>.zip
if you have changed the name of the update file to ‘update.zip’, then enter: adb sideload update.zip
You should see the progress bar go up to 100%, like so:
sending: 'sideload' 100%
Click to expand...
Click to collapse
At this point, the device should have started installing the update 4.4.3 OTA :victory:
Step 4.
Reboot - you're done.
Enjoy Android 4.4.3 on your Nexus 7 LTE... we just need to waiting the next release for KK4.4.4
Just in case
Reserved for me
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Hizpanick said:
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Click to expand...
Click to collapse
I've tried before to install my OTA update and the install is failed. I'm with TWRP also
That's why I'll edit my OP without this process. I have rename the zip file to update.zip
For info I have this result:
Code:
- verifying current system
"/system/bin/debuggerd" has unexpected contents
E:Error executing updater binary in zip '/sdcard/update.zip
Error flashing sip '/sdcard/update.zip
Updating partition details
So if you haven't received the OTA update for 4.4.3, use the adb sideload process.
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Hizpanick said:
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Click to expand...
Click to collapse
I haven't been able to get this to install either. Does root or custom recovery cause the installation to fail?
Sent from my Nexus 7 using Tapatalk
i am getting a status 7 error in /tmp/update.zip
help?
I don't know exactly what is the problem. I've used this process for updating my N7.
After the flash with adb sideload, I am back completely stock, unlocked, rooted but stock recovery, not twrp.
Sent from my N7 LTE from XDA Assist and use TapatalkPro
So I found out why I was getting my particular error and it was because I had Xposed framework installed. I uninstalled that and was able to flash the OTA. However, I lost root, but kept TWRP. So I flashed the updated SuperSU.zip (http://www.androidfilehost.com/?fid=23501681358555830) and I had root back. Re-installed Xposed Framework and now everything is updated and working
So you got the update to flash in twrp?
I uninstalled xposed and it still doesn't work with stock recovery and kernel. Got too much setup to redo it all
Sent from my SCH-I605 using Tapatalk
worked for me.
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...
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
Ah, So You've rooted your 6.1 Plus/X6 but don't know how to Install stock or having troubles with it? I'm here to help!
*All of the instructions and procedures below requires an unlocked bootloader. If you do not have an unlocked bootloader, Please refrain from asking about it here.
*Not having an unlocked bootloader and following this will definitely brick your phone. You have been warned.
Installing Stock ROM - Method 1A(Nost) --
1. Get NOST from here - NOST
2. NOST ONLY SUPPORT OREO FIRMWARE, USE OST LA FOR PIE(Not sharing cause its a patched app, Search on Google and get it from TechMesto)
3. Download unpacked oreo firmware, You can get it from - Here
4. Extract the zip on your PC
5. Put your phone in bootloader mode, Power off - Press Volume Down+Power Button.
6. Now connect it to your PC
7. Open NOST, Select the .mlf file from the folder where you extracted the Firmware
8. Now select, Normal download and Erase User data option.
9. Now click on next and wait for NOST to flash the phone. (It takes 258 seconds or 2.3 - 2.5 minutes on my laptop)
Installing Stock ROM - Method 1B(OST LA) --
Same as NOST, It has the same UI.
Except You might have to change some values in the .mlf file.
An appropriate guide for the same - Here
Installing Stock ROM - Method 2(Hikary's Generic Flashing Script) --
I recommend this method more than NOST and OST LA.
1. Get Hikary's script from - Here
2. Get unpacked Firmware from - Here
3. Extract the Firmware
4. Put the .exe file you got from Github into the folder where you Extracted the firmware
5. Run the script
6. Follow instructions on screen
7. Profit!
Thanks alot to member - Hikary for this easy to use scipt!
You've installed Stock, Now let's add some magisk to it !
*Please disable Automatic System Updates through developer options to make taking OTA .zips easier.
Installing Magisk - Method 1A(Fastboot method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Extract ADB to a Folder
2. Get Magisk patched boot images from - Here Don't worry, Boot images for Nokia 7 Plus will work on DRG(6.1 Plus/X6) and PL2(6.1)
3. Open adb(Type cmd in the address bar of the folder where you extracted adb)
4. Put your device on Download mode
5. type the command
Code:
fastboot boot 'nameofbootimage'.img
6. Now your phone will boot
7. Install Latest Magisk Manger from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
8. Open Magisk Manger, You will see Magisk is installed, But there will also be an Install Button next to it. Tap on Install.
9. Let Magisk Install and re-boot the phone
10. Viola Magisk is now permenantly available
Installing Magisk - Method 1B(TWRP method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Get the latest TWRP for 6.1 Plus
2. Get the Latest Magisk Installer from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
3. Put the .zip file to your Internal Storage/SD Card
4. Open adb and pass the command
Code:
fastboot boot "nameofrecoveryfile.img"
5. Now TWRP will open on your phone
6. Install Magisk through TWRP
7. Wipe Dalvik
8. Reboot
9. Profit
Now you've got magisk. Follow the next post to see how to take an OTA update with Magisk Installed.
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
CarbonGTR said:
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
Click to expand...
Click to collapse
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Hymix said:
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Click to expand...
Click to collapse
Open Magisk Manager, Tap on Uninstall. You will see 2 options, Complete Uninstall and restore stock images.
*Nevar tap on the complete uninstall option, It will throw your phone into bootloop
To install to inactive slot, Tap on install, You will get 2 options, Release Notes and Install. Tap on Install again and select install to inactive slot, Reboot from within Magisk Manager.
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Hymix said:
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Click to expand...
Click to collapse
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
CarbonGTR said:
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
Click to expand...
Click to collapse
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Click to expand...
Click to collapse
It's easy. Get an OTA .zip file, Re-Boot to recovery and flash it. Or Use the ADB Sideload method.
Most likely installing the OTA would fail if the device is rooted because, Magisk will patch the boot.img.
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Click to expand...
Click to collapse
I just took an OTA with Magisk installed it went fine. (September patch)
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Hymix said:
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Click to expand...
Click to collapse
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
CarbonGTR said:
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
Click to expand...
Click to collapse
Really? I did the restore via Magisk and that seemed fine, but then the update part didn't work. It downloaded then gave the error so I quit and started again with a fresh installation, minus Magisk.
Sent from my Nokia 6.1 Plus using Tapatalk
Have you guys modified the system/vendor partition in any way? If you did, Then it will obviously fail.
@Bluebriz and @Hymix I agree. It's the september security patch causing the installation issue.
It fails for me no matter what, Unless I completely un-root. But this method works perfectly fine on the August update.
Lets see for the October patch.
Okay, I can specifically narrow this down to way the September patch. The september patch requires the August security patch as a precondition to install. And that's where something funky is happening.
Guys a quick update. October update has been released but it also fails to install. This time I've managed to find the cause, Apparently some service that needs to be used for the update is being blocked/used by Magisk. (I could be wrong here)
The error code according to the recovery is 20(kDownloadStateInitializationError)
Is there any update to this issue?
Tried removing Magisk, didn't help.
Yesterday I got November security update ..iam using magisk...so it is showing installation problem...I tried in recovery and ADB method both didn't work.. finally I ended in bootloop ...so I again installed stock ROM...any solution is there without resetting each time how to install security updates..coz each time my data balance was wasted??
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