Related
A firend of mine got a problem with his Lenovo, so we thought about reflashing it.
Unfortunattely we are not sure if it is CN or Row version.
The rom flashed on it is VIBEUI_V1.5_1423_9_P780_baralajbiV7
However reading the forum I'm not only not able to choose between CN and Row, but what are CN+ and Row+ versions?
ch3mn3y said:
A firend of mine got a problem with his Lenovo, so we thought about reflashing it.
Unfortunattely we are not sure if it is CN or Row version.
The rom flashed on it is VIBEUI_V1.5_1423_9_P780_baralajbiV7
However reading the forum I'm not only not able to choose between CN and Row, but what are CN+ and Row+ versions?
Click to expand...
Click to collapse
Hi. Your firmware is based on Chinese firmware.
CN+ or ROW+ are modified layout firmware so you can flash latest kernel and latest TWRP.
Partitions are modified to be bigger. TWRP has grown from 6.1 mb to 12 mb and dont fitt in original recovery partition. Kernel its allmost the same thing.
Read here for + versions. Its the post of original developer.
Link: http://forum.xda-developers.com/lenovo-p780/development/kernel-twrp-2-8-4-0-2-8-6-0-custom-t3141171
Hope this helps you.
He is not into modding stuff (to much, coz he too know that You cannot have full Android experience without Root). I just wanted to know which firmwares I can safely flash on this device.
Sent using XT1562 - Resurrection Remix/Ultra Kernel
ch3mn3y said:
He is not into modding stuff (to much, coz he too know that You cannot have full Android experience without Root). I just wanted to know which firmwares I can safely flash on this device.
Sent using XT1562 - Resurrection Remix/Ultra Kernel
Click to expand...
Click to collapse
For me is MIUI from USNKREAL.
Stable. Still developed. OTA updates.Patched with latest Android Security Patches.Easy to use. Rooted with original MIUI Root manager.Developed specialy for this phone Lenovo P780.
Here is the post. There are the screenshots too.
Link: http://forum.xda-developers.com/lenovo-p780/development/miui-lenovo-p780-t2976347
I love MIUI (however moved to Resurrection Remix, coz their LP build made me love it more) and, between Roms available here on XDA, would probably choose it. But It's not my choice. I'm here to repair NVRAM, but cannot do it on this build, so first need to reflash it, but as it;'s my first time with this device, I wasn't sure about this CN, Row, CN+ and Row+, and preferred to ask than looking for ways to unbrick it later.
ch3mn3y said:
I love MIUI (however moved to Resurrection Remix, coz their LP build made me love it more) and, between Roms available here on XDA, would probably choose it. But It's not my choice. I'm here to repair NVRAM, but cannot do it on this build, so first need to reflash it, but as it;'s my first time with this device, I wasn't sure about this CN, Row, CN+ and Row+, and preferred to ask than looking for ways to unbrick it later.
Click to expand...
Click to collapse
If your NVRAM is corrupted on Lenovo P780 here is the tools you need.
Link: http://forum.xda-developers.com/lenovo-p780/help/imei-nvram-restore-tools-t3174563
Yep. I saw it, but there is 4. Flash STOCK Firmware. and that's why I created this thread
ch3mn3y said:
Yep. I saw it, but there is 4. Flash STOCK Firmware. and that's why I created this thread
Click to expand...
Click to collapse
Ok. But let me tell you one thing!
I have ROW version of the phone.
I am using CN based firmware.
Only i have to change was the modem software!
Works like charm!
MIUI is updated with latest Android Security Patches.
Your phone is ROW but have installed CN based firmware.
Sooo... you can use any of CN or ROW firmware. Modem software makes the diference.
You can try to get the phone in META MODE by powering down the phone, then power on with the buttons POWER and VOL - pressed together.
If the message: YOU HAVE BEEN IN META MODE TOO LONG.... appears you can flash ahain your IMEI, ofcorce respecting that tutorial.
Good Luck.
So if I flash CN modem on Row phone, all the problem will be no signal, and than flashing right modem will make it OK? It won't brick the device?
But how do You recognized that it's Row mode? It was bought form Aliexpress so as well he could bought CN model. It doesn't have LTE modem to make so big difference.
ch3mn3y said:
So if I flash CN modem on Row phone, all the problem will be no signal, and than flashing right modem will make it OK? It won't brick the device?
But how do You recognized that it's Row mode? It was bought form Aliexpress so as well he could bought CN model. It doesn't have LTE modem to make so big difference.
Click to expand...
Click to collapse
Flashing modem software for this kind of phone wil not brick your phone or signal.
In china phones dont use 800 mhz frequency. It is forbidden. So in hardware they dont have seccond chipset on modem, row phones have the seccond chipset for 800 mhz frequency.
Flashing cn modem software will not afect the phone, only the gsm signal received. In some area where your gsm provider antenna works on 800 mhz your phone will not have signal.
That is it.
Thought that there is more risk
But got confirmation that it's Row, as it had Google Play OOTB and CN ones don't have it.
stympy said:
Ok. But let me tell you one thing!
I have ROW version of the phone.
I am using CN based firmware.
Only i have to change was the modem software!
Works like charm!
MIUI is updated with latest Android Security Patches.
Your phone is ROW but have installed CN based firmware.
Sooo... you can use any of CN or ROW firmware. Modem software makes the diference.
You can try to get the phone in META MODE by powering down the phone, then power on with the buttons POWER and VOL - pressed together.
If the message: YOU HAVE BEEN IN META MODE TOO LONG.... appears you can flash ahain your IMEI, ofcorce respecting that tutorial.
Good Luck.
Click to expand...
Click to collapse
What if i flash row based rom on a cn base device ? And Is this apply to p780 only ? Tq sir
daftsslr said:
What if i flash row based rom on a cn base device ? And Is this apply to p780 only ? Tq sir
Click to expand...
Click to collapse
Hi.
If you FLASH Row based firmware, over CN based firmware, nothing will happen. FLASH mean, using SP Flash Tool. The phone will start normal with Chinese software. After this you can use CN zip file firmware, like MIUI.
If you INSTALL Row zip file over CN based firmware, you will softbrick the phone.
This applies only to P780. Maybe there are phones that use the same technology, and i do not know the precise brand.
Hope this will answer your question.
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Hi,
I still don't understand how to check the phone version. It's not my phone, so can You just point me a stable rom without preinstalled chinese apps etc. ?
This one is installed: VIBEUI_.V2.0_9439_7.10.1_DEV_P780
Thanks
gunlok said:
Hi,
I still don't understand how to check the phone version. It's not my phone, so can You just point me a stable rom without preinstalled chinese apps etc. ?
This one is installed: VIBEUI_.V2.0_9439_7.10.1_DEV_P780
Thanks
Click to expand...
Click to collapse
Hi. Your layout is CN.
Look if you have custom recovery TWRP Installed.
If you have TWRP installed you can go to this post and install latest MIUI MINOVO.
Good luck.
I have P780 with VIBEUI_V2.0_1443_7.25.1_ST ROM, it also has TWRP installed.
Is this CN or ROW?
borda01 said:
I have P780 with VIBEUI_V2.0_1443_7.25.1_ST ROM, it also has TWRP installed.
Is this CN or ROW?
Click to expand...
Click to collapse
All firmware that contains VIBEUI is CN based.
stympy said:
Ok. But let me tell you one thing!
I have ROW version of the phone.
I am using CN based firmware.
Only i have to change was the modem software!
Works like charm!
MIUI is updated with latest Android Security Patches.
Your phone is ROW but have installed CN based firmware.
Sooo... you can use any of CN or ROW firmware. Modem software makes the diference.
You can try to get the phone in META MODE by powering down the phone, then power on with the buttons POWER and VOL - pressed together.
If the message: YOU HAVE BEEN IN META MODE TOO LONG.... appears you can flash ahain your IMEI, ofcorce respecting that tutorial.
Good Luck.
Click to expand...
Click to collapse
I have read a lot of articles in 3 days on XDA for my P780.
And the most of them are of you Stympy, but I'm a bit of mess.
I Bought my device from China "Minideal", I asked it rooted but now with serch on it I saw that its not. I don't know wich recovery mode it has. But for sure its not TWRP.
My ROM version is VIBEROM_V1.0_1347_3_ST_P780 so I must serch for CN or ROW to install on it. The diference on that 2 is from what I read the frequency only or the languish too. CN has only Chinise and English? ROW is multilanguish? This moment I have multilanguish on phone because I use Greek.
The phone had 3 years the same ROM and has launched not working properly.:cyclops:
As I have said above I have read enough articles and I'm confused about the upgrade process. Others are older versions, other files there are no longer on posts. The process is not written so clear. HELP PLEASE...
AlexTsi said:
I have read a lot of articles in 3 days on XDA for my P780.
And the most of them are of you Stympy, but I'm a bit of mess.
I Bought my device from China "Minideal", I asked it rooted but now with serch on it I saw that its not. I don't know wich recovery mode it has. But for sure its not TWRP.
My ROM version is VIBEROM_V1.0_1347_3_ST_P780 so I must serch for CN or ROW to install on it. The diference on that 2 is from what I read the frequency only or the languish too. CN has only Chinise and English? ROW is multilanguish? This moment I have multilanguish on phone because I use Greek.
The phone had 3 years the same ROM and has launched not working properly.:cyclops:
As I have said above I have read enough articles and I'm confused about the upgrade process. Others are older versions, other files there are no longer on posts. The process is not written so clear. HELP PLEASE...
Click to expand...
Click to collapse
Hi.
Your firmware currently installed is Chinese for sure. Its old allright! All stock firmware is old because Lenovo builders gived up on this nice phone.
So... first thing first...
You must upgrade your system first in order to install one custom firmware. I think is what you want.
To upgrade your system you must work with SP FLASH TOOL. SP Flash tool is not a program to play with if you dont know what are you doing. 99% of people who used this tool and did not know how to... corupted NVRAM and lost their IMEI.
So... lets begin.
A. Tool to be downloaded:
1. SP Flash Tool V.5 and v.3. This 2 tools are made for Lenovo P780.
2. Divers like zip file and exe file.
3. Firmware multilanguage for your phone. This firmware is CN Based but dont wory to mutch, is custom made and compiled for multilanguage and is working well. I used very long time.
4. TWRP custom recovery.
B. Drivers installation procedure.
1. First drivers instalation. This small tutorial is for installing drivers if you never installed on your device:
1.1 First install the .exe file. Reboot PC.
1.2. After reboot plug the phone (powered on) to the PC and new hardware wizard will appear. Install driver if windows will wants too.
1.3. Now power off the phone. And open the Device Manager.
1.4. Again plug the phone to the PC or laptop this time powered off.
1.5. At this time in Device Manager appeared for a second or two not in PORTS area something with.. MTK65xx...
1.6. Click very fast on it because that will dessapear very fast.
1.7. After you clicked on it all you have to do is update driver. Browse for the driver unzipped. Install.... yes yes... next next... blah blah.... Finnish. . And voila you have drivers installed and now all you have to do is to flash you ROM.
C. Flashing procedure:
1. now... turn off your phone
2. plug your USB cable in your computer
3. do not plug your USB cable in your phone
4. open Flash Tool and unzip the firmware. Remember the adress of your folder where you unzipped the firmware. Load scatter file from that folder.
5. check DA,DL WITH CHECKSUM (NOT OPTIONAL)for v.3 not for v.5. Version 5 is allready checked. Look at those 2 pictures attached.
6. press Firmware Upgrade button (NOT DOWNLOAD BUTTON). For version 5 select FIRMWARE UPGRADE. Look at those 2 pictures attached.
7. now... just now plug usb cable to your phone.
8. firmware flash should start.(some red and other color lines should appear)
9. iff the firmware is not starting remove the back case of your phone and hold pressed the little red button from the right side, for about 20 seconds then release. All this must be done with cable pluged in to your phone.
9. after flash is done a green circle or some ok should appear
10. disconect your phone and power on your phone
11. lenovo logo should appear. then you should be pacient because it will took some time before android boots for the first time.
12. Reboot at least once, then your phone is ready to work HARD.
D. Installing TWRP. This custom recovery is good for custom firmware and full system backup.
Power Off your phone.
1. After power off your phone open Flash Tool and browse for the scatter file your folder where are the recovery.img and scatter file.
2. Now comes the tricky part . Creeate a new folder on your Desktop. In that new folder copy TWRP recovery and scatter file from your firmware folder.
3. Now load the scatter file and mark DA DL with check sum in SP Flash Tool v3. In SP Flash Tool v 5 dont need. They are allready selected. Recovery.img should appear checked. If not, checkit.
4. Press Download NOT FIRMWARE UPGRADE.
5. Now, just now plug the cabble on your phone. Download should start and a green circle should appear.
6. After this you should have custom recovery TWRP installed.
7. Then boot directly to recovery your phone by pressing power with vol + and vol - butons together. Not Optional because TWRP will overitten by some files and stock recovery will appear.
8. After you entered in TWRP look arrownd to see what is there and after your curiosity is satified reboot to system.
E. After all this steps are done your firmware and your phone is ready to install custom firmware, i mean CN based custom firmware.
This is it. You have a custom firmware ready phone.
------ SAGA CONTINUES -----
F. There is some new form of layout for this phone appeared recently in order to prepare the phone for more bigger custom firmware like MIUI.
This new form called "+" layout is developed by Andreya108 and is made specialy for this P780.
You can see Andreya108 work here.
Based on his work i have creeated this firmware.
Remember this firmware is creeated to support newer firmware released by this magic developers.
You can find this firmware here.
To install this firmware you must follow all the steps except D point steps. Those firmware are prepared allready with TWRP.
Hope this tutorials will help you.
If you have another questions just quote me.
Good luck.
stympy said:
Hi.
Your firmware currently installed is Chinese for sure. Its old allright! All stock firmware is old because Lenovo builders gived up on this nice phone.
So... first thing first...
You must upgrade your system first in order to install one custom firmware. I think is what you want.
To upgrade your system you must work with SP FLASH TOOL. SP Flash tool is not a program to play with if you dont know what are you doing. 99% of people who used this tool and did not know how to... corupted NVRAM and lost their IMEI.
So... lets begin.
A. Tool to be downloaded:
1. SP Flash Tool V.5 and v.3. This 2 tools are made for Lenovo P780.
2. Divers like zip file and exe file.
3. Firmware multilanguage for your phone. This firmware is CN Based but dont wory to mutch, is custom made and compiled for multilanguage and is working well. I used very long time.
4. TWRP custom recovery.
B. Drivers installation procedure.
1. First drivers instalation. This small tutorial is for installing drivers if you never installed on your device:
1.1 First install the .exe file. Reboot PC.
1.2. After reboot plug the phone (powered on) to the PC and new hardware wizard will appear. Install driver if windows will wants too.
1.3. Now power off the phone. And open the Device Manager.
1.4. Again plug the phone to the PC or laptop this time powered off.
1.5. At this time in Device Manager appeared for a second or two not in PORTS area something with.. MTK65xx...
1.6. Click very fast on it because that will dessapear very fast.
1.7. After you clicked on it all you have to do is update driver. Browse for the driver unzipped. Install.... yes yes... next next... blah blah.... Finnish. . And voila you have drivers installed and now all you have to do is to flash you ROM.
C. Flashing procedure:
1. now... turn off your phone
2. plug your USB cable in your computer
3. do not plug your USB cable in your phone
4. open Flash Tool and unzip the firmware. Remember the adress of your folder where you unzipped the firmware. Load scatter file from that folder.
5. check DA,DL WITH CHECKSUM (NOT OPTIONAL)for v.3 not for v.5. Version 5 is allready checked. Look at those 2 pictures attached.
6. press Firmware Upgrade button (NOT DOWNLOAD BUTTON). For version 5 select FIRMWARE UPGRADE. Look at those 2 pictures attached.
7. now... just now plug usb cable to your phone.
8. firmware flash should start.(some red and other color lines should appear)
9. iff the firmware is not starting remove the back case of your phone and hold pressed the little red button from the right side, for about 20 seconds then release. All this must be done with cable pluged in to your phone.
9. after flash is done a green circle or some ok should appear
10. disconect your phone and power on your phone
11. lenovo logo should appear. then you should be pacient because it will took some time before android boots for the first time.
12. Reboot at least once, then your phone is ready to work HARD.
D. Installing TWRP. This custom recovery is good for custom firmware and full system backup.
Power Off your phone.
1. After power off your phone open Flash Tool and browse for the scatter file your folder where are the recovery.img and scatter file.
2. Now comes the tricky part . Creeate a new folder on your Desktop. In that new folder copy TWRP recovery and scatter file from your firmware folder.
3. Now load the scatter file and mark DA DL with check sum in SP Flash Tool v3. In SP Flash Tool v 5 dont need. They are allready selected. Recovery.img should appear checked. If not, checkit.
4. Press Download NOT FIRMWARE UPGRADE.
5. Now, just now plug the cabble on your phone. Download should start and a green circle should appear.
6. After this you should have custom recovery TWRP installed.
7. Then boot directly to recovery your phone by pressing power with vol + and vol - butons together. Not Optional because TWRP will overitten by some files and stock recovery will appear.
8. After you entered in TWRP look arrownd to see what is there and after your curiosity is satified reboot to system.
E. After all this steps are done your firmware and your phone is ready to install custom firmware, i mean CN based custom firmware.
This is it. You have a custom firmware ready phone.
------ SAGA CONTINUES -----
F. There is some new form of layout for this phone appeared recently in order to prepare the phone for more bigger custom firmware like MIUI.
This new form called "+" layout is developed by Andreya108 and is made specialy for this P780.
You can see Andreya108 work here.
Based on his work i have creeated this firmware.
Remember this firmware is creeated to support newer firmware released by this magic developers.
You can find this firmware here.
To install this firmware you must follow all the steps except D point steps. Those firmware are prepared allready with TWRP.
Hope this tutorials will help you.
If you have another questions just quote me.
Good luck.
Click to expand...
Click to collapse
:laugh:You're amazing, so written in detail! Thank you very much for your time and your job!
I will inform you on how to go!:fingers-crossed:
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Hi all,
please find attached the Havoc OS 3.8 custom ROM, Olivelite version, and Magisk 20.4 which you will need for installation also.
I am neither the creator of this ROM or anyhow involved with the team, nor do I take any responsibility for everything which might go wrong during installation.
How I got it to work:
1. Unlock your boot loader (you will find appropriate instructions here in the forum and elsewhere on the web, also on YouTube).
2. Ensure that you have the XiaoMi Flash tool and the latest stock rom available, to be able to recover you phone when you encounter issues.
Both can be found on the Xiaomi website.
3. Get the "minimal ADB and Fastboot" tools. You will find in the web.
4. Get TWRP (you will find out what this is and why you need it here in the forum). Take care that it is a version for your phone model, else worst case it will not work.
5. Put the attached files to an external SD card in your phone.
6. install TWRP. Boot into "Fastboot" mode and install TWRP with command "fastboot flash recovery twrp.img".
7. Boot into recovery mode - if yoiu did everything right, should be TWRP now
7a. Wipe - Format data - confirm with "Yes", then go back to main menu
7b. Wipe - advanced wipe - select all except the last 2 (expecially NOT "external SD" if you put your files on there),
go back to main menu
7c. Install - select location where you've put the "havoc 3.8 update.zip" and select the file, afterwards wipe Cache / Dalvik (TWRP will give you this option after install), DO NOT REBOOT
7d. Install - select location where you've put the "magisk v20.4.zip" and select the file, afterwards wipe Cache / Dalvik and then reboot to system.
Now, hopefully, congratulations and enjoy
If something happens and it will not work at all, search the web first for solutions and, if still does not work and you do not get along with it, do not worry. You can always go back to the Xiaomi original ROM with the XiaoMi Flash Tool. Phone must be in "Fastboot" mode for this. In the flash tool, select your ROM location (ideally in the root of your drive as this tool cannot interpret spaces in paths), then confirm and ensure that you have ticked "Clean all" in the bottom, NOT "clean all and lock" - else you will have to do the unlock procedure again.
Sometimes, you need the "permissiver v5.zip" which you will find on the web. In case the above does not work, you can try to install the Permissiver. I never needed it, and I'm using 2 Redmi Olivelite.
I just tried this and had a success message from TWRP about the Havoc 3.8 flash but the Majisk file had an error from within TWRP first time & then it installed after reboot. But I still go straight into TWRP after rebooting.
Right now I have TWRP on the device & a micro SD card to get files onto the device but no OS on it & no backup as one way or another I want a ROOTed OS & it was the Chinese version when I got the phone so useless to me anyway.
What's the best approach from here to get this thing running again?
Thanks!!! Thanks!!! Thanks!!! after trying to get a GSI rom run on my daugthers olivelite i finally got a new rom working. I don't know why last guides didn'twork for me actually a recently requested a boot.img patch but i managed to patch it myself after dealing with python. Now will try to update it to 3.12 i suppouse it iwll have many improvements. But this worked right out of the box for me. Just followed each step and good to go.
For anyone interested. its de 2Gb/32Gb Global Version. with 12.0.3 latest MIUI updated applied trough fastboot. I used OFOX to test it and it worked fine by now.
If you have guide to update HAVOC please point me in the right direction.
Thanks again
I got off .Havoc precisely because it did not have voLTE support & BT HS 's didn't work. Has anyone had any luck on these 2
I absolutely thank you for this rom, I can now miraculously play Asphalt 9 on high settings at 30ish fps while on miui it struggled on lowest settings, the UI is flawless but I only have one problem I can't send nor receive SMS and the phone sometimes reboots randomly but that cannot make me go back to miui since it's too heavy for my phone.
IS THERE any fix for not being able to receive or send SMS
I have a black screen [FIxed by installing OrangeFox recovery]
So, this is the first time I'm installing a custom rom and I was following along with this guy:
(I found the xda steps to be too confusing to follow) and everything was going just fine until around the 5.20 min mark where after flashing TWERP on the device through Odin I was supposed to press the volume - & the power key to restart the device and as soon as the device went black I was supposed to then press volume + & the power key which I did but then I got this: (attachment)
(btw, even when I don't press the volume + & power key afterwards I get the same result)
Can this still be fixed or have I bricked my device?
Hi @Winter413
I found a wonderful description on the installation of TWRP here .... maybe it's easier to follow though it's for the 8.
Just read the whole story .... your troubles while installing TWRP are not at all new.
It's a kind of trick which you learn as soon as you want to root your phone, or want a good user friendly recovery backup app.
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Hope it might be of help ....
Nice Sunday for you !
Here on the forum you will be able to meet all the specialists you need.
[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hi @xabu
First I'd like to greatly apologise you for answering so late. I did not mean to be rude I just didn't want to reply with "ok, I'll be working on it than" & I actually wanted to get something done first. I decided to do things that way becouse I thought that I'll find some time to do this rather soon however unexpected things happened that kept me from doing it but now I have some time & have done something in this regard so enough of my excuses let's get to what I did & what I want to ask you about:
So first I went onto the s8 thread you suggested & I flashed vbmeta_disabled & to my suprise when I restarted again & pressed volume up + power it actually booted into TWRP "and relief washed over me in an awesome wave" but then I went on to get lineage os on it and it doesn't show up in TWRP. I have also gotten some other stuff (magisk & a few files from NanoDroid) & those show up just fine. I got the file from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/
& the link I got from this thread: https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/
& as far as I'm concerned that is the only thread about lineage os on this phone on xda so that doesn't work I guess.
I have also tried this: http://www.mediafire.com/file/4w6vaq4lu2tbjfj/lineage-17.0-20200110-UNOFFICIAL.zip/file
& this: https://mega.nz/file/gw4QTYSS#IqqswGusWIW5l10LyvSfmtVUoE4gqn6_g6jywH96Z5Q
& got this:
(I've done these sequentially but I hope that doesn't make any functional difference however one important thing is the first one goes 'till the first "done" and the second one is the rest. You surely could figure that out by yourself but I wrote this just for clarity's sake.)
P.S. I know that both of the error messages I got seem to refer in one way or another to the fact that I'm not using an sd card for this operation, however as far as I'm concerned it should also be possible to install lineage os to the internal storage of the phone & that is what I want to achieve with this.
P.S. 2
I forgot to mention that I obviously wiped everything properly before trying to install lineage os so that's not the problem.
Hi Winter ,
it's important to check if you found the right version of TWRP:
Samsung Galaxy A10
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
every other version might get you in trouble.
And then: there is still no official LineageOS for the A10 (this gives problems too)
[ROM] [GSI] [GUIDE] Lineage os A10 A105F
A guide for how to install Lineage OS [ GSI ] on Samsung A10 A105F Notes / Warning! Use at your own risk, I’m not responsible for bricking your device. Make sure to backup your important data before everything. here is a summary of the steps I...
forum.xda-developers.com
should be the place to be, though there is not too much activity there ...
but look at this thread too:
Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot
Improve your Samsung Galaxy A10's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
with many good ideas.
Whatever:
I learned that LineageOS should be installed before other additions like Magisk and G-apps. Do this from internal storage and not from an external sd-card.
In TWRP we always make a Zip queue before installing but always starting with the OS or ROM.
You should be successful now you experienced how to install TWRP.
Always check for the right version or ask in the threads.
Thanks for coming back to me though I just wanted to help you
with installing TWRP and I don't have a A10 at my disposal.
Sincerely @xabu
Ps: I saw that you had courage enough to experiment. Be careful but go for it.
Hi @xabu
So as I mention I made it work by flashing this file through odin while in dowload mode & then restarting & pressing the volume up + power buttons which was supposed to take me to twrp & it did & twrp for me seems to be working just fine so I'm a little hesitant to try & install some different version of it but if you think that's the issue than I will try installing those other versions.
As soon as you are in TWRP and it functions fine, then just look to it's version and go to the link which I gave you for the newest version of TWRP for the A10.
"
If you intend to root your (a10) device, be advised that Magisk will be installed to the recovery partition, not the usual boot partition. Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time.
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery. The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually."
In this website the instructions about flashing TWRP to your device goes further .... so try to understand it step by step.
If you want to install Magisk, then you should know that from some weeks ago, Magisk started a complete new life with new important instructions: look here:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
As you can see .... there is a lot to do and to learn.
Hope you'll enjoy it like your
"and relief washed over me in an awesome wave"
no one could have said it better .
PS:
Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
is especially for your kind of device and certainly not in general.
Alright, so I checked my twrp version with your link & I have the latest one so everything is fine. I also got lineage os 18.1 & it seems to have installed just fine. So now it's time for Magisk. So first I'm also kinda following this guide:
& Wolfgang recommends to not only install the .zip file but also Magisk manager & I couldn't find any link to download it.
"The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP" so does that mean that I have to go back to the download mode & from there flash the root file in odin & then install magisk.apk like here?:
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Also, If you're curious, the "and relief washed over me in an awesome wave" is an almost direct quote (I only changed "washes" to "washed") from my favourite movie - American Psycho.
@xabu
If you liked my previous post, does that mean that I should do the steps I mentioned?
Dearest @Winter413 ....
No, this does not mean that you should do the steps mentioned.
Again read the instructions on the official TWRP where they help you with Magisk. You can always upgrade the moment all works.
I'm not familiar enough with your device. All is working here on the S7.
A complete different device as I noticed while studying your situation.
My like also shows my admiration for your courage to root your phone and try out how to go further and further.
Ps: https://github.com/topjohnwu/Magisk/releases/tag/v24.1
What about Magisk Manager? Do I need that?
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Winter413 said:
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Click to expand...
Click to collapse
Yes you need the new Magisk manager. If you want a rooted phone.
But as I told you....Magisk is changed maybe a month ago .... this means totally new instructions ... so keep this in mind while working with older instructions.
And also regarding the root - If I've gone this far than I might as well go further & attain some more control over my device & also learn a bit about how computers work along the way. This is definitely not the last project of this kind that I'll be doing. I'm already running Pop os on my main computer instead of windows (however I did use windows for this whole process as Odin is unfortunately unavailable for linux). For now I'm also very very slowly learning javascript (I'll try to pick up the pace cuz it's really bad) & once I buy myself a new computer I'll try installing arch on it & using that as my daily driver & yeah, further carrer routes in IT & such are definitely also something that I'll be looking into so while pretty inconmpetent I'm not afraid to play around with computers.
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
So I must admit I haven't looked to much into rooting yet & it seems that It is not required to install a custom rom, however this sounds pretty cool:
Advantages of rooting include the possibility for complete control over the look and feel of the device. As a superuser has access to the device's system files, all aspects of the operating system can be customized with the only real limitation being the level of coding expertise. mmediately expectable advantages of rooted devices include the following:
1. Support for theming, allowing everything to be visually changed from the color of the battery icon to the boot animation that appears while the device is booting, and more.
2. Full control of the kernel, which, for example, allows overclocking and underclocking the CPU and GPU.
3. Full application control, including the ability to fully backup, restore, or batch-edit applications, or to remove bloatware that comes pre-installed on some phones.
4. Custom automated system-level processes through the use of third-party applications.
5. Ability to install software (such as Xposed, Magisk, SuperSU, BusyBox, etc.) that allows additional levels of control on a rooted device or management of root access.
Winter413 said:
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
Click to expand...
Click to collapse
Yes learn about the denylist and Zygisk !
So from my understanding currently the steps left are:
1. installing Magisk.zip & Magisk Manager
2. Installing NanoDroid
3. & perhaps locking my bootloader afterwards to make my device more secure? (I think that's something that should be done but correct me If I'm wrong)
& then I can finally start using my phone on Lineage os, right?