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:
Just got a notification for OTA to 5.0.1. Anyone know if this will break root? And if it will install with CWM custom recovery?
Hello, I tried to install in my WiFi model and rooted and I got and error during the installation, so I'm waiting for the opinion of other users. ?
Sent from my SHIELD Tablet using XDA Free mobile app
I kiddy got it too, I'll wait for the zip file lol.
Ya think it is really better to install from the zip file?
Sent from my SHIELD Tablet using XDA Free mobile app
I'll be the guinea pig
I downloaded the OTA but can't find where is the ota file. Any idea where is it?
Sent from my SHIELD Tablet using XDA Free mobile app
Get an error in cwm . shucks
Does someone can post change log please?
Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
Same. My bootloader is locked and tried flashing via cwm and got error. Pls teach me how to update?
Sent from my SHIELD Tablet using XDA Free mobile app
Judge584 said:
Does someone can post change log please?
Click to expand...
Click to collapse
Android Central has the log change. It's bug fixes really.
Also, in this thread a user states that apparently only with the full 5.0.1 can you install it with CWM.
http://forum.xda-developers.com/shi...p-nvidia-shield-tablet-ota-android-5-t2982677
You will lose root and CWM after the reboot but those took about 3 minutes to get back .. easy peasy. I'm now at 5.0.1 on my shield with root and CWM.
Cheers.
Hello aegern,
deletes the full update all the data? can you give me the recovery and root attach files?
Thanks
Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
d4m45cuz said:
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
Click to expand...
Click to collapse
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
l0ud_sil3nc3 said:
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
Click to expand...
Click to collapse
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
GMrMadrigal said:
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
Click to expand...
Click to collapse
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
l0ud_sil3nc3 said:
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
Click to expand...
Click to collapse
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
GMrMadrigal said:
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
Click to expand...
Click to collapse
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
dgjenkins said:
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
Click to expand...
Click to collapse
Hi dgjenkins, sorry answer so late. So, answering you first, not, it did not work for me. I actually did give up, the bad was that I tried so many ways to do it that I freezed the tablet and did not start again. Well, looking out there, I found this amazing video who saved my tablet of bust it again the wall and start from the original firmware.
https://www.youtube.com/watch?v=GsMo1tPlIFU
I did intal the Minimal ADB and Fastboot
Copy the image files in to the Minimal ADB and Fasboot directory c:\Programs Files (x86)\Minimal ADB and Fastboot
Ope Minimal ADB and Fastboot
-Type: fastboot flash recovery recovery.img
-Type: fastboot flash boot boot.img
-Type: fastboot flash system system.img
-Type: fastboot flash userdata userdata.img
-Type: fastboot flash staging blob
-Type: fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
And done . I can now install the updates from the stock firmware. Maybe I will root it again once a stable way to root the shield tablet appear out there. :cyclops:
Happy Holidays and Thanks for the interest! :good:
Nvidia updates definitely trump Android ones. These days, Google is in the habit of pretending that a nexus 5 camera bug is worthy of a new Android version (that was KitKat) or that an update is a great place to break functionality (App Ops, also with KitKat). Anything that's not a minor version with updates you know you want... Avoid on a non Nexus unless you have a great reason for it.
Manufacturers besides Google, see, they do this thing I like to call quality control. They generally release an OS that is ready for the hardware and software*. Crazy, right?
* unless that hardware is, say, the pen
The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk
I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.
Hi! Has the modem changed?
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.
maybe, for getting OTA should we just get unroot? How to do it properly?
If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk
Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!
should be an easier way. Did u see some changes to the radio?
Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.
ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.
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.