This is just my guide for updating. i wrote it down because i tend to forget how i did things when i want to do it again.
i am no expert. there could be better ways to do it.
Update after twrp
This includes a factory reset.
Root, TWRP and all your DATA is gone after this.
Do a backup before you do this!!!
1.
Activate usb debugging
Power off the phone completely.
Press and hold the Volume Up and Power button to enter Fastboot mode.
2. fastboot flash recovery stockrecovery.img
3. boot into recovery (volume down+power)
install from SD: UL-ASUS_Z01KD_1-WW-14.1064.1711.96-user.zip
4. start system.
Factory reset
than shut down.
5. boot into recovery (volume down+power)
install from SD: latest update
You could share the file link to flash user.zip?
matracapx said:
You could share the file link to flash user.zip?
Click to expand...
Click to collapse
What do you mean? The firmware? You can download it from the Asus website.
Does anyone know the current procedure for updating the ROM stock via TWRP. It looks like we should download the full updated firmware and the Magisk. Restart on TWRP, and flash the ROM and then the Magisk, one by one. Can anyone confirm?
-------------------------------------------------------------------------------------------------------------------------------------------------------
Alguém sabe o procedimento atual para atualizar a stock ROm via TWRP. Parece que devemos baixar o firmware atualizado completo e o Magisk. Reiniciar na TWRP, e flashear a ROM atulizada e depois o Magisk, um por um. Alguém pode confirmar?
Following...
badvag said:
Does anyone know the current procedure for updating the ROM stock via TWRP. It looks like we should download the full updated firmware and the Magisk. Restart on TWRP, and flash the ROM and then the Magisk, one by one. Can anyone confirm?
-------------------------------------------------------------------------------------------------------------------------------------------------------
Alguém sabe o procedimento atual para atualizar a stock ROm via TWRP. Parece que devemos baixar o firmware atualizado completo e o Magisk. Reiniciar na TWRP, e flashear a ROM atulizada e depois o Magisk, um por um. Alguém pode confirmar?
Click to expand...
Click to collapse
You just answered your own question. That's how it's always been done, doesn't matter whether you got a ASUS Zenphone or a Galaxy S phone from Samsung for that matter.
urbanman2004 said:
You just answered your own question. That's how it's always been done, doesn't matter whether you got a ASUS Zenphone or a Galaxy S phone from Samsung for that matter.
Click to expand...
Click to collapse
I do not know the procedure for updating the ROM by TWRP, do you know? Can you tell me more details?
I want to say that in the normal way I know how to do it, but I'm still not sure how to update the ROM via TWRP without losing Magisk and Xoosed (if you're using it)
badvag said:
I do not know the procedure for updating the ROM by TWRP, do you know? Can you tell me more details?
I want to say that in the normal way I know how to do it, but I'm still not sure how to update the ROM via TWRP without losing Magisk and Xoosed (if you're using it)
Click to expand...
Click to collapse
I use Magisk, but not Xposed. These instructions are based on the assumption that the bootloader is unlocked, and that TWRP is already installed on your device, and that the Rom in question has already been copied to a USB Stick via OTG cable:
01. Boot into Recovery Mode (hold down Volume Down + Power Buttons)
02. Always make a [Nandroid] backup (via USB-OTG, saving data on USB Stick preferably) when going from one Rom to another; Save separate important data (texts, call logs, documents)/apps prior to Rom Install using backup utility apps, e.g., Titanium Backup.
03. Sideload your Rom (via USB-OTG, copied onto USB Stick preferably)
04. Hit WIPE – Do a Factory Reset: Wipe Data /Cache/ Dalvik. Hit Back
05. Hit MOUNT – Mount USB-OTG. Select the storage device. Hit Back
06. Hit INSTALL – Browse for the Rom (zip file). Install Rom
07. Remember to Flash Google Apps
08. REBOOT the System
09. Complete the startup wizard and give the phone a 10 to 15 minutes before the next step.
10. Now reboot into Recovery and flash any mods/theme or kernel compatible with your new ROM.
a. Remember to 'wipe cache/dalvik' after flashing kernel
urbanman2004 said:
I use Magisk, but not Xposed. These instructions are based on the assumption that the bootloader is unlocked, and that TWRP is already installed on your device, and that the Rom in question has already been copied to a USB Stick via OTG cable:
01. Boot into Recovery Mode (hold down Volume Down + Power Buttons)
02. Always make a [Nandroid] backup (via USB-OTG, saving data on USB Stick preferably) when going from one Rom to another; Save separate important data (texts, call logs, documents)/apps prior to Rom Install using backup utility apps, e.g., Titanium Backup.
03. Sideload your Rom (via USB-OTG, copied onto USB Stick preferably)
04. Hit WIPE – Do a Factory Reset: Wipe Data /Cache/ Dalvik. Hit Back
05. Hit MOUNT – Mount USB-OTG. Select the storage device. Hit Back
06. Hit INSTALL – Browse for the Rom (zip file). Install Rom
07. Remember to Flash Google Apps
08. REBOOT the System
09. Complete the startup wizard and give the phone a 10 to 15 minutes before the next step.
10. Now reboot into Recovery and flash any mods/theme or kernel compatible with your new ROM.
a. Remember to 'wipe cache/dalvik' after flashing kernel
Click to expand...
Click to collapse
That way I would lose the Magisk, XPosed and phone settings. When flashing the original ROM, it will overwrite custom recovery (TWRP). I would like to know a way to update the original ROM without losing anything, understand? It is possible?
badvag said:
That way I would lose the Magisk, XPosed and phone settings. When flashing the original ROM, it will overwrite custom recovery (TWRP). I would like to know a way to update the original ROM without losing anything, understand? It is possible?
Click to expand...
Click to collapse
Did you not just read what I took the time to write? If not, you're on your own
urbanman2004 said:
Did you not just read what I took the time to write? If not, you're on your own
Click to expand...
Click to collapse
I read, I should not have understood. Does the procedure you passed do not lose the settings and root (Magisk)?
badvag said:
That way I would lose the Magisk, XPosed and phone settings. When flashing the original ROM, it will overwrite custom recovery (TWRP). I would like to know a way to update the original ROM without losing anything, understand? It is possible?
Click to expand...
Click to collapse
badvag said:
I read, I should not have understood. Does the procedure you passed do not lose the settings and root (Magisk)?
Click to expand...
Click to collapse
I can tell English is not your native language. If you notice under instruction #2:
Always make a [Nandroid] backup (via USB-OTG, saving data on USB Stick preferably) when going from one Rom to another; Save separate important data (texts, call logs, documents)/apps prior to Rom Install using backup utility apps, e.g., Titanium Backup.
Click to expand...
Click to collapse
That implies that your settings will not be saved, and refers you to other means to backup/restore them; a) creating a Nandroid backup within TWRP will backup the OS/Rom (and installed apk's) but no settings, data, files, etc., b) Titanium Backup does a number of things, if not all of what you inquired a/b. I would highly implore you do your research and due diligence before plunging into something blindly that you're not well-versed in which seems to be the case here. Just b/c I mentioned here what is it that I would do in your situation doesn't mean it works best based on your use case scenario. Hope that provides you more, and better clarity.
urbanman2004 said:
I can tell English is not your native language. If you notice under instruction #2:
That implies that your settings will not be saved, and refers you to other means to backup/restore them; a) creating a Nandroid backup within TWRP will backup the OS/Rom (and installed apk's) but no settings, data, files, etc., b) Titanium Backup does a number of things, if not all of what you inquired a/b. I would highly implore you do your research and due diligence before plunging into something blindly that you're not well-versed in which seems to be the case here. Just b/c I mentioned here what is it that I would do in your situation doesn't mean it works best based on your use case scenario. Hope that provides you more, and better clarity.
Click to expand...
Click to collapse
Of course, English is not my native language.
But I had read, I really did not have much practice in doing this by Titanium backup and recovering these settings. My initial question was: Is there any way to flash the updated ROM without losing anything? I realized that there isn't.
how can i find stockrecovery.img ?
euojunior said:
how can i find stockrecovery.img ?
Click to expand...
Click to collapse
i added stock recovery to the first post
https://forum.xda-developers.com/attachment.php?attachmentid=4694253&d=1548542582
joeblond999 said:
i added stock recovery to the first post
https://forum.xda-developers.com/attachment.php?attachmentid=4694253&d=1548542582
Click to expand...
Click to collapse
Thanx Guy God Bless U !!
Thank you ! all happened normally here God bless you !
I'm coming back here to explain how to update the ROM stock using TWRP and the Asus Flash Tool.
Some guys who are experts say it does not work, but there are videos on Youtube showing that it is possible to do the firmware flash directly through TWRP, I did not do it because of the risk of the softbrick.
These are the videos:
https://www.youtube.com/watch?v=HebmIzuAfS0&t=194s
https://www.youtube.com/watch?v=thEDEvA5UUs
https://www.youtube.com/watch?v=nzBQz1x4xfg
It may also be possible for "adb sideload xxxx" in the sideload option of TWRP (use TWRP version 3.2.3, which is hard to find on the internet), I have not tested it.
In my procedure the TWRP will be lost:
1) Download RAW firmware ZE554KL
2) Install ASUS Flash Tool (in version v2.0.1 does not seem to work), I used version v1.0.0.45.
3) Now, with your phone turned on and your debug mode enabled.
4) Open ASUS Flash Tool ((it does not matter if the model of the device is not listed)
5) Select the RAW firmware you've downloaded.
6) Click on the Serial Number of your device.
7) Click Start. I do not remember, but I think now the phone starts with TWRP or you start custom recovery and then put it in FASTBOOT mode (if you do this before Asus FlashTool will not recognize the device).
8)Start the process on the start button (I can not remember if it has to start again), and then the RAW firmware will start to be copied. The phone will reboot again through TWRP, do nothing until the process is finished (check for TWRP and Asus Flash Tool), then just start the device. Recovery will be back to normal and the device will have the firmware updated.
*I could not attach twrp3.2.3 and Asus Flash Tool (v1.0.0.45) because of the size of the files.
badvag said:
I'm coming back here to explain how to update the ROM stock using TWRP and the Asus Flash Tool.
Some guys who are experts say it does not work, but there are videos on Youtube showing that it is possible to do the firmware flash directly through TWRP, I did not do it because of the risk of the softbrick.
These are the videos:
https://www.youtube.com/watch?v=HebmIzuAfS0&t=194s
https://www.youtube.com/watch?v=thEDEvA5UUs
https://www.youtube.com/watch?v=nzBQz1x4xfg
It may also be possible for "adb sideload xxxx" in the sideload option of TWRP (use TWRP version 3.2.3, which is hard to find on the internet), I have not tested it.
In my procedure the TWRP will be lost:
1) Download RAW firmware ZE554KL
2) Install ASUS Flash Tool (in version v2.0.1 does not seem to work), I used version v1.0.0.45.
3) Now, with your phone turned on and your debug mode enabled.
4) Open ASUS Flash Tool ((it does not matter if the model of the device is not listed)
5) Select the RAW firmware you've downloaded.
6) Click on the Serial Number of your device.
7) Click Start. I do not remember, but I think now the phone starts with TWRP or you start custom recovery and then put it in FASTBOOT mode (if you do this before Asus FlashTool will not recognize the device).
8)Start the process on the start button (I can not remember if it has to start again), and then the RAW firmware will start to be copied. The phone will reboot again through TWRP, do nothing until the process is finished (check for TWRP and Asus Flash Tool), then just start the device. Recovery will be back to normal and the device will have the firmware updated.
*I could not attach twrp3.2.3 and Asus Flash Tool (v1.0.0.45) because of the size of the files.
Click to expand...
Click to collapse
Please upload files to google drive? thank you!
matracapx said:
Please upload files to google drive? thank you!
Click to expand...
Click to collapse
Link: https://drive.google.com/open?id=1s6O3RMVqNe3K-mFzzo2k5vFZByABi0YF
*Reminder: you can recover the original recovery easily. The stock recovery file is also on the link.
Related
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
joaomPT said:
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
Click to expand...
Click to collapse
As you are already familiar with adb and other stuff so will write a short post for you.
To download latest firmware, head to
http://forum.xda-developers.com/hon...tock-firmware-packages-honor-7-t3448747/page1
Google, download and install Huawei update extractor and open UPDATE.APP in it (obtained after extracting firmware).
You can see all the images. Just extract recovery and boot to platform-tools folder.
Meantime, do the unlocking command again, with
Fastboot OEM unlock xxxxxxxxxxxxxxxx
Followed by fastboot reboot
And press and hold the vol down button again until you reboot in bootloader.
Flash the recovery and boot you extracted using
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
(I got a habit of extracting and flashing system and Cust using
Fastboot flash system system.img
Fastboot flash Cust Cust.img
But they are not necessary)
Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again).
Please do report back if it comes to life.
To root, just flash twrp and then use SuperSU 2.62 (no other version) and update it later using play store.
Sent from my PLK-L01 using XDA Labs
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
joaomPT said:
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
Click to expand...
Click to collapse
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
joaomPT said:
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
Click to expand...
Click to collapse
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said » version 2.62 «
I cant thank you enough!! Can I pay you a coffee?
Thank you!
joaomPT said:
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said �?�» version 2.62 �?�«
I cant thank you enough!! Can I pay you a coffee?
Thank you!
Click to expand...
Click to collapse
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
You can find him somewhere in this thread
http://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554/page1
Decision is yours
muradulislam said:
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
Whichever you like...
Click to expand...
Click to collapse
Alright man, cheers
joaomPT said:
Alright man, cheers
Click to expand...
Click to collapse
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
joaomPT said:
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
Click to expand...
Click to collapse
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
tgergo said:
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
Click to expand...
Click to collapse
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
I'll try... But seems too simple to be true...
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
Hi again,
I'm doing this OS installation now. It starts fine but stucks at 90%, (I'm trying to install the latest stock ROM which can be downloaded from Huawei site, B220 or221). Did you have the same issue? I waited more than half an hour at 90% but did not go on.
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Maybe formatting, Flash stock Android 5 recovery using Honor multitool , and then Flash a Android 5 firmware
Not sure it Will Work without rollback..
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
tgergo said:
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
Click to expand...
Click to collapse
Is this really work? i cant rollback to any version.
Yuaru said:
Is this really work? i cant rollback to any version.
Click to expand...
Click to collapse
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
tgergo said:
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
Click to expand...
Click to collapse
Thanks for the answer. Im gonna try this method. I can't reflash any region rom.
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
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 ?????
Hey guys , i have been looking on the forum ,i already have a rooted s9+ but on 8.0, i want to go over to 9.0 but i cant find a guide how to and what i need for it , maby im oberlooking the threads but maby someone can hel me out ?
Wesley_NL said:
Hey guys , i have been looking on the forum ,i already have a rooted s9+ but on 8.0, i want to go over to 9.0 but i cant find a guide how to and what i need for it , maby im oberlooking the threads but maby someone can hel me out ?
Click to expand...
Click to collapse
Just use the method you used on Oreo.
spawnlives said:
Just use the method you used on Oreo.
Click to expand...
Click to collapse
though i forgot its been a while , and somehow i can remember little doing with odin3 i needed serval fiiles
Wesley_NL said:
though i forgot its been a while , and somehow i can remember little doing with odin3 i needed serval fiiles
Click to expand...
Click to collapse
Yes you will need Odin. If you are going to use magisk then either flash twrp or use the patch method. Either way require Odin.
Personally I use twrp. You can copy all files needed ( on to SD card ) and flash within twrp.
spawnlives said:
Yes you will need Odin. If you are going to use magisk then either flash twrp or use the patch method. Either way require Odin.
Personally I use twrp. You can copy all files needed ( on to SD card ) and flash within twrp.
Click to expand...
Click to collapse
yes that was my plan stay magisks with twrp ,
altough i dont remember i did this when i installed twrp on mines
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
Wesley_NL said:
yes that was my plan stay magisks with twrp ,
altough i dont remember i did this when i installed twrp on mines
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
Click to expand...
Click to collapse
Basically yes. I would first do a backup ( I know but the amount of people not doing it and then wanting to know how to retrieve the lost data ).
In download mode check kg/rmm state is NOT in prenormal state.
Step 5 - allowing system to be modified - that's up to you. I normally allow modifications.
Then format data reboot back into twrp.
Flash/install - no verity zip, rmm bypass zip, magisk .
Hey i have a problem, i downloaded latest rom but my bt wont save bt pairings, what can i do about it
Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5