Amazon is downgrading my device to 3.2.3 after a lengthy live chat. Any requests for the downgrade file?
Edit: My device actually got downgraded to 3.2.8. Oh well, it's rootable with Towelroot, /cache/recovery is attached.
You miss the most important thing... the downgrade binary...
veaceslav said:
You miss the most important thing... the downgrade binary...
Click to expand...
Click to collapse
I couldn't get it, the binary was deleted immediately after flashing.
Could That File Be Undeleted ?
bmccoy11 said:
I couldn't get it, the binary was deleted immediately after flashing.
Click to expand...
Click to collapse
Would it be possible to undelete this file immediately after the delete using a previously installed utility like EaseUS Android Data Recovery ?
reggie9 said:
Would it be possible to undelete this file immediately after the delete using a previously installed utility like EaseUS Android Data Recovery ?
Click to expand...
Click to collapse
I'll try!
That file was probably in the top level of the Internal Storage folder. Also there may be better tools than that available.
I noticed when I downloaded the 3.2.5 bin file from Amazon's website and placed into my internal storage folder. When I tried to apply the update, it complained and said the update was older than the 4.5.2 (ugh) I currently have installed. When I looked again the file was gone. SO maybe the way to solve this is to undelete this file. Will try some more this evening. Good luck.
Could Not Be So Easy
bmccoy11 said:
I'll try!
Click to expand...
Click to collapse
So far have not been able to find anything to successfully undelete files. Looks like they are move to a secure folder and deleted. I'm going to learn more about this. One thing I found is that you can view the entire files system with WIFI File Explorer. Anyone been able to SSH into Kindle Fire HDX 3rd Gen 7 with 13.4.5.2?
reggie9 said:
So far have not been able to find anything to successfully undelete files. Looks like they are move to a secure folder and deleted. I'm going to learn more about this. One thing I found is that you can view the entire files system with WIFI File Explorer. Anyone been able to SSH into Kindle Fire HDX 3rd Gen 7 with 13.4.5.2?
Click to expand...
Click to collapse
OTA downloads are stored in /cache. Obviously you won't be able to recover anything.
Also, SSH access is the equivalent of running adb shell.
EncryptedCurse said:
OTA downloads are stored in /cache. Obviously you won't be able to recover anything.
Also, SSH access is the equivalent of running adb shell.
Click to expand...
Click to collapse
That's what I thought. Anyway, there is no way to downgrade to any version below 3.2.8 when running version 3.2.7 or above without tripping the eFuse and bricking your device, so I'm SOL until another exploit is found... At least 3.2.8 is rootable.
I just got mine rolled back to 3.2.8 too, today.
Does that mean that I cannot install a custom rom now as this 3.2.8 version will not allow subsequent downgrade?
johim said:
I just got mine rolled back to 3.2.8 too, today.
Does that mean that I cannot install a custom rom now as this 3.2.8 version will not allow subsequent downgrade?
Click to expand...
Click to collapse
No, you can root it with Towelroot but you won't be able to install any custom recovery or ROMs until another exploit is found. I believe 3.2.8 uses the same bootloader as 4.5.2, which is why you're able to downgrade to 3.2.8 but nothing lower than that.
bmccoy11 said:
No, you can root it with Towelroot but you won't be able to install any custom recovery or ROMs until another exploit is found. I believe 3.2.8 uses the same bootloader as 4.5.2, which is why you're able to downgrade to 3.2.8 but nothing lower than that.
Click to expand...
Click to collapse
Do you think amazon can downgrade further?
johim said:
Do you think amazon can downgrade further?
Click to expand...
Click to collapse
No, they won't be able to downgrade it either without tripping the eFuse.
bmccoy11 said:
No, you can root it with Towelroot but you won't be able to install any custom recovery or ROMs until another exploit is found. I believe 3.2.8 uses the same bootloader as 4.5.2, which is why you're able to downgrade to 3.2.8 but nothing lower than that.
Click to expand...
Click to collapse
bmccoy11 said:
No, they won't be able to downgrade it either without tripping the eFuse.
Click to expand...
Click to collapse
I understand... Btw, i saw a member that wrote about his kindle.. It was 4.x and they rolled back to 3.2.5....
Also, have you tried the xposed framework for hdx? I just want to enable wallpapers but couldn't find any other way to achieve this.
What did you used to install gapps?
johim said:
I understand... Btw, i saw a member that wrote about his kindle.. It was 4.x and they rolled back to 3.2.5....
Also, have you tried the xposed framework for hdx? I just want to enable wallpapers but couldn't find any other way to achieve this.
What did you used to install gapps?
Click to expand...
Click to collapse
Xposed Framework works fine on 3.2.8.
Follow this thread to get Gapps working: http://forum.xda-developers.com/showthread.php?t=2787813
Amazon support said it would be impossible to downgrade below 3.2.8.
bmccoy11 said:
Xposed Framework works fine on 3.2.8.
Follow this thread to get Gapps working: http://forum.xda-developers.com/showthread.php?t=2787813
Amazon support said it would be impossible to downgrade below 3.2.8.
Click to expand...
Click to collapse
"Amazon support" isn't one person. The representative you talked with may claim that it's impossible (as do many others), but it does not mean that it's a uniform response; it all depends on who you talk to. From what I've read and experienced firsthand, it is well within their power to do so.
Amazon is most likely well aware of the flaws in their software, so it's obviously protocol to downgrade the customer to a patched firmware.
Hmm.. Rootrd, and installed xposed. Wallpapers in launchers still don't work... Any idea?
johim said:
Hmm.. Rootrd, and installed xposed. Wallpapers in launchers still don't work... Any idea?
Click to expand...
Click to collapse
Try this: https://kindlecooltricks.wordpress.com/2012/02/01/change-kindle-fire-wallpaper-without-rooting/
Related
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
Getting ROOT rights to Android 5.0 Lollipop (KingRoot) It is not my work. Taken from a russian forum.
1.Download and install latest version of Kingroot to phone.
2.Run the application and get the Root. Important - do not restart the device, because it can lead to failure in obtaining Root.
3.Enable "USB debugging" and "unknown sources".
4.Install the latest version from the PC XZDualRecovery to get full access to reading and writing to the section System (connect your phone to a PC via a cable, run the install.bat to select a number " 1 "on the screen to confirm a request for superuser)
5.Phone will reboot automatically to recovery. Install supersu.
6.Boot
Files to root.
https://mega.co.nz/#!eUgAiSDZ!R1bU-_hIxa2GW11Pjd8ikc-AzfbbJsoAXWkh7DG8j1A
isaekrem said:
Getting ROOT rights to Android 5.0 Lollipop (KingRoot) It is not my work. Taken from a russian forum.
1
Click to expand...
Click to collapse
I've been waiting for a one click root, but everything I'm reading says this is really sketchy and no one is quite sure what it is doing.
Can anyone confirm working on Z3?
For which phone? T-Mobile?
se1zure31 said:
For which phone? T-Mobile?
Click to expand...
Click to collapse
Tested by owner z3c.
And I tested on my phone D6603.
Is everything working good ???
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
gregbradley said:
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
Click to expand...
Click to collapse
Thanks.........for the information.
gregbradley said:
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
Click to expand...
Click to collapse
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
haste75 said:
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
Click to expand...
Click to collapse
AFAIK they are the same
haste75 said:
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
Click to expand...
Click to collapse
Yes they are the same ...
Well, I couldnt resist. I've now got a working root with SuperSU, and have removed all I can find of the KingRoot app.
So far, seems to be working well.
Someone else tried it?
haste75 said:
Well, I couldnt resist. I've now got a working root with SuperSU, and have removed all I can find of the KingRoot app.
So far, seems to be working well.
Click to expand...
Click to collapse
Were you able to remove KingUser and install SuperUser?
scoder said:
Were you able to remove KingUser and install SuperUser?
Click to expand...
Click to collapse
Yes I believe so. I have the Kinguser icon in my app draw, but It wont open. I deleted all files associated with King via ES Root Explorer, and cannot find anything.
I still wouldn't recommend anyone else doing this, god knows what information was sent to China upon installing it, but I really wanted root.
haste75 said:
I still wouldn't recommend anyone else doing this, god knows what information was sent to China upon installing it,
Click to expand...
Click to collapse
But if try to isolate PC and phone from the internet during installing?
artlov said:
But if try to isolate PC and phone from the internet during installing?
Click to expand...
Click to collapse
I tried that, it needs internet connectivity. However, the reason I allowed this was I understand that this root is based on a Ping exploit, which would need internet connecivity to work.
I figured the risk werent THAT high for me. I dont re-use passwords and no bank details stored on my phone.
Can confirm this method works.
You might want to try going in Airplane mode if you're paranoid for the Chinese. In any case, Kingroot + XZDR + SuperSU 2.49 works perfectly.
It works for me I can confirm now.I have root on lollipop locked bootloader so nice haha ? thanks
E66666666 said:
Can confirm this method works.
You might want to try going in Airplane mode if you're paranoid for the Chinese. In any case, Kingroot + XZDR + SuperSU 2.49 works perfectly.
Click to expand...
Click to collapse
did you flash the recovery?
krugu said:
did you flash the recovery?
Click to expand...
Click to collapse
Not yet will do tomorrow, now I accidentally cleared the data of kinguser and now any app can't recognize root on my devices although it's installed, it says root denied, but şu binaries are installed, I will try tomorrow the recovery after school, if it really works I will release my ultimate sound mod I'm working since months and ofc I can test it myself and don't need any testers hope the pc cam.recognize the root on my.device and install the .bat files
Kingroot now roots 5.3.1!
If you are having trouble installng cm 12.1, try the supertool or @wtfjajaja's instructions.
wtfjajaja said:
try it a few times, i encountered the same problems as well
here's what i did
1. factory reset through recovery
2. root with kingroot, (it worked for me after 2 to 3 tries)
3. installed supersu-me 6.7
4. update su binary
it's important here! don't restart yet, my device bricked few times here
5. install flashfire 0.53
6. follow the steps to install cm12.1 under flashfire from here
7. enjoy
Click to expand...
Click to collapse
Supertool: http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Bricked?: http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Fingers crossed! I can't wait to start flashing roms!
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
tonibm19 said:
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
Click to expand...
Click to collapse
Flashfire needs supersu
or Cmsu to work.
hooks024 said:
Flashfire needs supersu
or Cmsu to work.
Click to expand...
Click to collapse
Try rootjunky's supertool after rooting to see if it can install it.
.
tonibm19 said:
Try rootjunky's supertool after rooting to see if it can install it.
Click to expand...
Click to collapse
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
DoctorDark_ said:
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
Click to expand...
Click to collapse
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
marvelous news!!!
DoctorDark_ said:
Kingroot now roots 5.3.1! Hopefully someone can quickly push out a toolkit.
Click to expand...
Click to collapse
Would you add the 5.3.1 version in the title ???
tonibm19 said:
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
Click to expand...
Click to collapse
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Nice I will try it out.
Good chance the latest versions of Kingroot (always evolving) will also work for those on FireOS 5.1.2.1-5.1.4. Worth a try before attempting a rollback to 5.1.2.
I couldn't get super sume to work.
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
ttcontributor said:
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
Click to expand...
Click to collapse
Not good - earlier builds of Kingroot froze around 29% before crapping out. Make sure you have the latest Kingroot app. Also try a factory reset (warning: you will loose personal apps/data) and do not register with Amazon during subsequent device initialization. This proved effective for some in the past. Recognize the community is still learning; expect some failures along the way.
Davey126 said:
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Click to expand...
Click to collapse
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
-Yami- said:
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
Click to expand...
Click to collapse
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Davey126 said:
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Click to expand...
Click to collapse
Come check my browser, I've read every single thread on the forums man, the thing is 5.1.2 is not same as 5.3.1 and device has locked bootloader and anti-rollback.
So it is not like my Motorola with unlocked bootloader, I am not sure if I always can save the device and also I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
So I had to make it clear everything works for 5.1.2 also will work for 5.3.1
Now I have to convert kingroot to supersu somehow (can't find the option under supertool like you mentioned.)
Your approach was a little bit harsh on me m8
It doesn't say "What can be done on 5.1.2 also can be done on 5.3.1" anywhere, it says the opposite everywhere.
So someone had to clear it out. Thank you for your help, It really helped me a lot.
-Yami- said:
Come check my browser, I've read every single thread on the forums man...
Click to expand...
Click to collapse
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
-Yami- said:
I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
Click to expand...
Click to collapse
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Davey126 said:
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Click to expand...
Click to collapse
The reason that I cannot return device to amazon is, shipment will cost more than the actual device from here to amazon, and I got it as a gift.
and Thanks so I missed out the part that Supertool automates the conversion when I click install Flashfire, thank you.
Now after this post everybody jumping right onto 5.3.1 root gonna know it, and the guy on first page have used Super Sume, so he probably would use
Supertool if he knew.
I am on 5.2 rooted. ,2017 model
I know it doesn't take ota updates anymore after a certain version if you are rooted.
I would like to update to the latest version and no longer be rooted.. there really just isn't much point. I don't find myself needing root for anything on the shield in particular.
It used to be easy to update.. you just updated and it would kill your root and then you would have to root all over again. Now though an ota will fail if the system has been modified in any way (aka root)... Even though I have a systemless root and I didn't flash recovery.. just loaded image for purposes of flashing root.
My first shield bricked while flashing a stock recovery... I did nothing wrong it just died.. could have been a fluke.. Nvidia was good enough to send me replacement tho.
I don't want to take that chance again.
Is it possible to do something.... That will enable me to take the ota and get a update and loose my root without having to flash stock recovery image?
I just hate to take that chance if I don't have to. I just really don't trust the flash of stock imsges with previous experience and one getting bricked in the process
adam_ky said:
I am on 5.2 rooted. ,2017 model
I know it doesn't take ota updates anymore after a certain version if you are rooted.
I would like to update to the latest version and no longer be rooted.. there really just isn't much point. I don't find myself needing root for anything on the shield in particular.
It used to be easy to update.. you just updated and it would kill your root and then you would have to root all over again. Now though an ota will fail if the system has been modified in any way (aka root)... Even though I have a systemless root and I didn't flash recovery.. just loaded image for purposes of flashing root.
My first shield bricked while flashing a stock recovery... I did nothing wrong it just died.. could have been a fluke.. Nvidia was good enough to send me replacement tho.
I don't want to take that chance again.
Is it possible to do something.... That will enable me to take the ota and get a update and loose my root without having to flash stock recovery image?
I just hate to take that chance if I don't have to. I just really don't trust the flash of stock imsges with previous experience and one getting bricked in the process
Click to expand...
Click to collapse
Probably a fluke, easiest way I have found is developer image and flash with flashfire takes about 2-3 minutes
I cannot get FlashFire to install even after downloading from apkmirror. On 2015 16 gig Shield.
ghostyroasty said:
I cannot get FlashFire to install even after downloading from apkmirror. On 2015 16 gig Shield.
Click to expand...
Click to collapse
You have to use flashfire 0.73
jionny said:
You have to use flashfire 0.73
Click to expand...
Click to collapse
That's the version I used.
ghostyroasty said:
That's the version I used.
Click to expand...
Click to collapse
what are you using to download it?
I download from apkmirror and upload to Google Drive. Then I use X-Plore to download to the Shield.
ghostyroasty said:
I download from apkmirror and upload to Google Drive. Then I use X-Plore to download to the Shield.
Click to expand...
Click to collapse
Do you know how to use adb link if so send it to the shield via adb link that is how I put all my apps on the shield, also just checking once you downloaded did you go into shield settings, apps and look to see if flashfire was there?
jionny said:
Do you know how to use adb link if so send it to the shield via adb link that is how I put all my apps on the shield, also just checking once you downloaded did you go into shield settings, apps and look to see if flashfire was there?
Click to expand...
Click to collapse
I've never used adb link, but I can look it up. As for trying to install, the option was grayed out so I had no way to install.
ghostyroasty said:
I've never used adb link, but I can look it up. As for trying to install, the option was grayed out so I had no way to install.
Click to expand...
Click to collapse
ok I remember now you need fllashfire 0.57 that works with 5.2 then when you get to 6 you need flashfire 0.73 as 0,73 doesnt work with 5.2 and versa
I have .73 installed and found the ota... It's a beta, but it will not install.
Sent from my SM-G950U1 using Tapatalk
ghostyroasty said:
I have .73 installed and found the ota... It's a beta, but it will not install.
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
ota is on xda do a search for developer image and you will find it also you have to have it on your shield internal and click flash firmware in flashfire, takes 3 min. I do know that before I went to 6 I was using 0.57 and when I tried to flash to 6.2 it wouldnt let me I had to change 0.57 to 0.73 flashfire to work, you . look at this page,,,,https://forum.xda-developers.com/sh...perience-upgrade-6-2-shield-tv-t3708798/page2
jionny said:
ota is on xda do a search for developer image and you will find it also you have to have it on your shield internal and click flash firmware in flashfire, takes 3 min. I do know that before I went to 6 I was using 0.57 and when I tried to flash to 6.2 it wouldnt let me I had to change 0.57 to 0.73 flashfire to work, you . look at this page,,,,https://forum.xda-developers.com/sh...perience-upgrade-6-2-shield-tv-t3708798/page2
Click to expand...
Click to collapse
This ota is a part of their preview program. I have the image downloaded, and when it tries to flash I get an error walking the lines of the partition tables have been modified.
Sent from my SM-G950U1 using Tapatalk
ghostyroasty said:
This ota is a part of their preview program. I have the image downloaded, and when it tries to flash I get an error walking the lines of the partition tables have been modified.
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
The beta you are referring to is preview and not stable its 6.3 I believe the link I sent you is 6.2 it is the same I used to upgrade
My phone keeps bugging me to install OTA update for krack vulnerability. I tried and it sent my phone to boot loop and now I have it restored. My phone has xposed installed. What is the best course of action? I would like to update but if that's not possible can I at least stop having the message show up each time I unlock my phone?
You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.
thorin0815 said:
You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.
Click to expand...
Click to collapse
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.
twoplustwo said:
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.
Click to expand...
Click to collapse
Is it a good idea to avoid security updates? No, it isn't. Is it clever to avoid updated drivers? No, it isn't (at least in most cases).
You should have informed yourself about the backdraws of rooting your phone before you did it. You need to be completely on stock firmware without any changes
to the system files to be able to use an OTA for updating your phone. This is needed to be safe the OTA update works the way it should.
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.
thorin0815 said:
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.
Click to expand...
Click to collapse
How can this be done? I don't know what to search for in these threads?
twoplustwo said:
How can this be done? I don't know what to search for in these threads?
Click to expand...
Click to collapse
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
thorin0815 said:
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.
twoplustwo said:
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.
Click to expand...
Click to collapse
Same procedure as on other stock rom versions): you need ElementalX kernel to be flashed and afterwards your desired root method(magisk is recommended).
Guides like this are valid https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
So as the title says, it is possible to root the Samsung Tab A SM-P580?
My reason for wanting to root is so that I can mount the SD card as internal storage and I can't find much regarding it other than using apps like app2sd which just isn't good enough sadly.
In an ideal world I'd like to get a custom rom like lineage running on the tablet but I need full s-pen functionality.
My Tab A is running android 8.1.0, which I think means I can't root?
Please help.
Thanks
Patch the boot.img file
antoine62 said:
Patch the boot.img file
Click to expand...
Click to collapse
i also got the sm-p580 running android 8.1. how does one go about patching the boot.img file to get root? the rooting of this particlular tablet back when it was on android 7 does not work no more. nor does twrp
tony950 said:
i also got the sm-p580 running android 8.1. how does one go about patching the boot.img file to get root? the rooting of this particlular tablet back when it was on android 7 does not work no more. nor does twrp
Click to expand...
Click to collapse
It still works, but you need to downgrade to Android Nougat 7 then you can root it with TWRP. You cannot root Oreo because TWRP is bugged with a black graphics line screen (looks like a damaged screen).
ya im aware that root still works on android 7. i was wondering about a working root solution for android 8.1
tony950 said:
ya im aware that root still works on android 7. i was wondering about a working root solution for android 8.1
Click to expand...
Click to collapse
If you only need root (no TWRP), you can simply follow the instructions which have been posted here: https://forum.xda-developers.com/showpost.php?p=78373937&postcount=2
I've used the method to root my P580 on 8.1 and it works without any issues.
cyyy said:
If you only need root (no TWRP), you can simply follow the instructions which have been posted here: https://forum.xda-developers.com/showpost.php?p=78373937&postcount=2
I've used the method to root my P580 on 8.1 and it works without any issues.
Click to expand...
Click to collapse
can confirm this works
artaeun said:
can confirm this works
Click to expand...
Click to collapse
Call me an idiot but I'm going to ask... Will doing this allow me to use my SD card as internal storage? Thank you.
JR1979 said:
Call me an idiot but I'm going to ask... Will doing this allow me to use my SD card as internal storage? Thank you.
Click to expand...
Click to collapse
You could use app2sd, but installing app to sd is a REALLY bad idea because sd card can corrupt easily, you can lose all of your data in every app that is on the sd.
But yes, if you want to take the risk, it will works, if you are rooted