Related
Hi folks! I have a Galaxy S4 GPE, rooted and unlocked, but stock otherwise. When I try to run the OTA update for 4.4.3, the phone reboots into TeamWin recovery and appears to start installing. The install errors out though. Can I not install the OTA update because I'm rooted? If so, would reverting the rooting allow me to install? Thanks in advance for any help you can provide!
Install Stock recovery and then try again
Aamirx12 said:
Install Stock recovery and then try again
Click to expand...
Click to collapse
Is there a thread on how to do that? I seem to remember when I installed this recovery tool to root the phone, it wiped everything. Is it going to do that again? Because I don't want to have to keep wiping my phone every time a new Android update comes out just to be rooted.
1337squirrel said:
Is there a thread on how to do that? I seem to remember when I installed this recovery tool to root the phone, it wiped everything. Is it going to do that again? Because I don't want to have to keep wiping my phone every time a new Android update comes out just to be rooted.
Click to expand...
Click to collapse
Flash it via Odin or simply restore recovery from Nandroid backup..
http://forum.xda-developers.com/showthread.php?t=2265477
this may help you..
1337squirrel said:
Hi folks! I have a Galaxy S4 GPE, rooted and unlocked, but stock otherwise. When I try to run the OTA update for 4.4.3, the phone reboots into TeamWin recovery and appears to start installing. The install errors out though. Can I not install the OTA update because I'm rooted? If so, would reverting the rooting allow me to install? Thanks in advance for any help you can provide!
Click to expand...
Click to collapse
Follow this GUIDE (Method 1: Update Via Custom Recovery).
Joku1981 said:
Follow this GUIDE (Method 1: Update Via Custom Recovery).
Click to expand...
Click to collapse
I went through that method, and it's essentially the same thing, except that I'm downloading the actual update file myself and not letting Android handle it. Needless to say it didn't work. I also updated my TWRP to 2.7.1.0 and tried; no luck. I also uninstalled SuperSU to see if removing root would help. It didn't.
1337squirrel said:
I went through that method, and it's essentially the same thing, except that I'm downloading the actual update file myself and not letting Android handle it. Needless to say it didn't work. I also updated my TWRP to 2.7.1.0 and tried; no luck. I also uninstalled SuperSU to see if removing root would help. It didn't.
Click to expand...
Click to collapse
It's the problem of no read for be vague. It worked perfectly on the GPE of my sister. The update that appears in the website is ready for install it through custom recovery. Read all the guide:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
UPDATE 1: Possible Solution
So, turns out you should be completely stock, means you should have stock recovery and NO ROOT. Stock Recovery can be Installed through 'Wugfresh' and unroot through SuperSu Setting. BUT, if you have modified even a single thing, YOU WILL A FACE ERROR as shown in the second screenshot. SO you will have to 'Fastboot Flash' the system.img from Factory image. I'm downloading The 5.0.0 Factory image right now and it will be downloaded by 2 hours.
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
You can get the stock recovery from the nexus factory images here . I would suggest just flashing the factory 5.0.1 image (don't flash userdata or cache and you should be fine).
I think OTA is only from 5.0.0 to 5.0.1.I'm having the same problem too and nobody seems to have an answer so I'll just get the factory images, flash all except user data
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember
You mean bringing silent mode back, getting a hold on the countless graphical glitches (yes, mine were all clean flashes) and maybe even grace us with a 3.10 kernel?
I was hoping on that as well, but it looks like we really are the rearmost wheel on the Google cart.
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps
parkourz said:
So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember
Click to expand...
Click to collapse
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...
matiamb said:
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...
Click to expand...
Click to collapse
I think it was something with security... but good to know that nothing has changed before flashing it
did we get a new kernel with 5.0 update?
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
EDIT: Recovery update did not help, still getting 4.4.2 fingerprint.
VinceCZ said:
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
Click to expand...
Click to collapse
I don't think I will work. Starting from lollipop, the update process is not like previous versions. It needs the system partitions to be completely unmodified. That includes the recovery partition and root to be hidden (temporary unroot in the supersu app). I tried to flash ota file with adb sideload and twrp and also cwm (both newest version) and failed. It can only be flashed successfully with stock recovery.
I heard what you are saying from more guys so I will try that.
EDIT: I made unroot and flashed stock recovery but getting error 7, which is basically the same as with custom recovery.
hk.happy said:
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps
Click to expand...
Click to collapse
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?
There is no solution yet.
VinceCZ said:
There is no solution yet.
Click to expand...
Click to collapse
Guys, for the ota to work you need to be unrooted and 100% stock recovery, system, and kernel.
Sent from my Nexus 5 using XDA Free mobile app
veketash said:
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?
Click to expand...
Click to collapse
I'm not sure but I think it will break root no matter how you update from 5.0.0 to 5.0.1, and you will have to flash supersu zip again, but again, i'm not sure....
Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.
VinceCZ said:
Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.
Click to expand...
Click to collapse
Flash the system, recovery, and boot images from 5.0 in fastboot. Then try the ota
Sent from my Nexus 5 using XDA Free mobile app
I suppose it will delete user settings and all, will it not?
VinceCZ said:
I suppose it will delete user settings and all, will it not?
Click to expand...
Click to collapse
no, it won't delete anything.
Sent from my Nexus 5 using XDA Free mobile app
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Thalias said:
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Click to expand...
Click to collapse
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
Thanks. I am downloading again. Hope it works this time.
bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Thalias said:
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Click to expand...
Click to collapse
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Teet1 said:
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Click to expand...
Click to collapse
I got b29 from zte website. Can I install it with stock recovery?
Thalias said:
Is there a link to download it?
Click to expand...
Click to collapse
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
bkores said:
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
Click to expand...
Click to collapse
Can I install it with stock recovery?
Thalias said:
Can I install it with stock recovery?
Click to expand...
Click to collapse
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
bkores said:
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
Click to expand...
Click to collapse
I got following message at bottom left of screen
Supported API: 3
Sorry, you can't sd upgrade
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
MiMtnBiker said:
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
Click to expand...
Click to collapse
Thanks. I forgot to unzip the file and put it in the root of sd card and I have done what you said too. It is running installation now.
I'm failing now? I went from ZAD v.3 back to stock B29 (I have an unlocked bootloader). I do have the MiFavor recovery (not TWRP)
I got the notification there was an upgrade, it took 6 hours to download... but the update "failed". I tried applying the update via SD card, but I get about 32% in and says "Update failed"......It also lists "Status 8" and "system partition has unexpected contents".
Sounds like y'all are having a hell of a time between the slow OTA speeds and then getting it to actually flash.
So I think I'll hold off for now. Hopefully we can get some TWRP-flashable zips soon enough... I think DrakenFX is already busy with all that
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
gpz1100 said:
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
Click to expand...
Click to collapse
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
tele_jas said:
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
Click to expand...
Click to collapse
No problem upgrading using the OTA on an sdcard here. Flashed the draken stock_system zip, then fastboot flashed the B29 stock recovery. Reboot to recovery (which is now stock) and update from sd card. If you've messed with other partitions, you may need to flash more B29 .img's.
Thalias said:
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
Click to expand...
Click to collapse
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
yosef019 said:
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
Click to expand...
Click to collapse
I don't know Chinese so I prefer Eng community with support and US region always get latest update first.
Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Bill R said:
Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
Click to expand...
Click to collapse
divineBliss said:
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Click to expand...
Click to collapse
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Bill R said:
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
Click to expand...
Click to collapse
divineBliss said:
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Click to expand...
Click to collapse
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Also, if you followed the rooting guides, you should have your own copy of the stock recovery in your first TWRP backup.
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
The roms do NOT include Stock Recovery or any recovery for that matter ...Roms don't flash recovery (none that I have ever flashed anyway)
If you need B140 Stock recovery it's here B140.Stock.recovery.img
The Guide kind of assumes you just did the B130 to B140 update and you already have stock recovery installed
and yes if your phone was B140 when you rooted it you should already have your own stock backup of B140
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Bill R said:
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Click to expand...
Click to collapse
Yes I corrected the Guide
Flash stock recovery before doing the dload/ update.app flash
as soon as the firmware update is done boot to the bootloader
fastboot boot H1611.TWRP.New.img
then mount cust / system and data and flash the B150.Stock.rom
also flash Supersu and reboot
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Bill R said:
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Click to expand...
Click to collapse
It's pretty clear in the guide
When it's done it will reboot the phone so now boot to the bootloader with power + volume down while hooked to the PC via USB
Click to expand...
Click to collapse
Anyway congratulations
I hope you Enjoy the CleanRom
I tried installing TWRP but always failed, the nearest TWRP build I can find is for gtanotexllte, but mine is gtanotexlltedx, so I tried flashing the non dx version (I haven't found the DX one) and It just bricked the tab, any help ?
Edit: My device is the S Pen version (SM-P585Y, Australian ROM, Android Oreo)
Jelly Hero said:
I tried installing TWRP but always failed, the nearest TWRP build I can find is for gtanotexllte, but mine is gtanotexlltedx, so I tried flashing the non dx version (I haven't found the DX one) and It just bricked the tab, any help ?
Edit: My device is the S Pen version (SM-P585Y, Australian ROM, Android Oreo)
Click to expand...
Click to collapse
You need a DEV to fix TWRP for your device because your TWRP you are using is for Android 6, it needs updating for working on android 8.1. Or if you want Twrp, you can downgrade to android 6 and flash it.
I tried downgrading but it says error bootloader binary 1...
raphael mark said:
I tried downgrading but it says error bootloader binary 1...
Click to expand...
Click to collapse
You can use Magisk Manager app to patch boot.img and flash using Odin to root the tablet
Thanks its works....and how can I Install a custom rom without twrp
Hi seniors, please guide me samsung bootloop SM-P585Y tab after trying to install twrp and then I flash the firmware to solve the problem failed to install twrp. after flashing the firmware successfully, I tried installing Twrp again and failed again. When I tried flashing the firmware it failed and "bootloader device 2, binary 1" appeared and finally the battery shutdown. please provide help for me
Guncloudes said:
Hi seniors, please guide me samsung bootloop SM-P585Y tab after trying to install twrp and then I flash the firmware to solve the problem failed to install twrp. after flashing the firmware successfully, I tried installing Twrp again and failed again. When I tried flashing the firmware it failed and "bootloader device 2, binary 1" appeared and finally the battery shutdown. please provide help for me
Click to expand...
Click to collapse
The Twrp is only for android 6 and need a developer to maintain it and fix error with android 8.1. If you want twrp, just downgrade your tablet to android 6 and flash twrp.
Tung Lam said:
The Twrp is only for android 6 and need a developer to maintain it and fix error with android 8.1. If you want twrp, just downgrade your tablet to android 6 and flash twrp.
Click to expand...
Click to collapse
Thanks for answer. i trying downgrade and just success. But always self reboot and stuck at logo samsung .
Mr Tunglam, what step to solve auto reboot?
Guncloudes said:
Thanks for answer. i trying downgrade and just success. But always self reboot and stuck at logo samsung .
Mr Tunglam, what step to solve auto reboot?
Click to expand...
Click to collapse
Make sure that u download right version of 4-file ROM of your tablet. Flash all 4 files with Odin.
Tung Lam said:
Make sure that u download right version of 4-file ROM of your tablet. Flash all 4 files with Odin.
Click to expand...
Click to collapse
Thanks for help.
Now my tab allready flash to android 7.
But after boot to system and phone screen lock ,all screen black just a black line white line.
Tung Lam said:
The Twrp is only for android 6 and need a developer to maintain it and fix error with android 8.1. If you want twrp, just downgrade your tablet to android 6 and flash twrp.
Click to expand...
Click to collapse
This step bring everythings fine. Thank you very much Mr Tung Lam
TWRP issues
Guncloudes said:
This step bring everythings fine. Thank you very much Mr Tung Lam
Click to expand...
Click to collapse
Commonly TWRP will not install if you're using a version incompatible with the device, check to make sure. You should always have the original stock frimware on hand in case anything goes wrong. If you do encounter difficulties such as bootloops you can basically start over by flashing in the stock firmware in download mode via Odin3. Sometimes after flashing it may take a while for the device to fully boot up, I've had some take hours.
Tung Lam said:
You can use Magisk Manager app to patch boot.img and flash using Odin to root the tablet
Click to expand...
Click to collapse
I get Odin fail with this. I'm using the Magisk 20.1 version. Do you have a solution?
Guncloudes said:
Thanks for answer. i trying downgrade and just success. But always self reboot and stuck at logo samsung .
Mr Tunglam, what step to solve auto reboot?
Click to expand...
Click to collapse
You have to wipe data after a downgrade.