Related
The droid Eris Root:
forum.xda-developers.com/showthread.php?t=647707bccc
is what i followed, when it came time to finish step II and install the driver, vista is a bi*ch and has a maze of options.
SO: click device manager, select the device with the exclamation point, update driver software, browse my computer, LET ME PICK FROM A LIST, have disk.... then select that driver.
once that is done, i tried to complete step III
it couldnt complete the commands for some reason.
I skipped down to step 4 to try that and went through the factory reset process, and then tried to flash from the sd card for the second half of the step and it would not complete.... it went through the boot screen and actually said "blah blah not completed..." any advice on this, or a better write up of step 3?
here is my current software info after completing step I:
Firmware V: 2.1
Baseband V: 2.41.04.02.02
Kernel V: 2.6.29-5cf233c2
Build Number: 2.26.605.2 CL134869
why is this not working for me? I just want to overclock this and have the live wallpapers/ new unlock screen style...
Thanks in advance from a new user that HAS searched.
explain the part where the command prompt didnt work. did you get stuck on the last one?
vista's wack try on something more reliable,
asv4k8 said:
here is my current software info after completing step I:
Firmware V: 2.1
Baseband V: 2.41.04.02.02
Kernel V: 2.6.29-5cf233c2
Build Number: 2.26.605.2 CL134869
why is this not working for me? I just want to overclock this and have the live wallpapers/ new unlock screen style....
Click to expand...
Click to collapse
Your software info provided above strongly suggests that you installed the Leak-V1 ROM, rather than the Root ROM. (That's one of the reasons that reputable sources of instructions will tell you to check the MD5 signature of stuff after you download it.) This could have happened because you followed someone else's instructions or download link, or because you previously installed Leak-V1 (and neglected to mention that in your post).
You can compute the MD5 signature of the PB00IMG.ZIP file you downloaded and compare to the listings in this XDA thread.
The correct way to check your phone's rootability would be to inspect the version of the bootloader on your phone - if you did the correct thing in "Step I", you will have 1.49.2000; and if you did the wrong thing (either recently or previously), you will have 1.49.0000. (You can check this by powering off the phone, and then powering it up by holding down the Send and End buttons simultaneously until the phone comes on.)
If you have 1.49.0000, the method of rooting you were trying is no longer available to you; welcome to the club of "leakers".
There is another method available to leakers, detailed in this XDA Eris thread. It is even more complicated - and less successful - than the root method you mentioned in your post. Using best available info, it seems that only 1 out of 3 people that try this succeed at it (sometimes right away, sometimes after hours and hours of trying).
Good luck
bftb0
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Zoandroid said:
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Click to expand...
Click to collapse
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
My concern, being still in the middle of researching just how to root the A500, was whether the update would have a similar effect as, for example, the more major update from 3.0 to 3.2, which, as I understand it totally changes the procedure used to achieve root. But if it won't matter one way or the other, I might as well take the update in the interim. I keep hoping to see a more simple 'one-click' style of root made available before I tackle this task. So far I've found something like 3 different ways to root the tablet between this forum and another. But each is a rather involved process.
Thanks!
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
I downgraded, rooted, and then flashed the stock ROM without wiping. If going to any other rom, you might need to wipe.
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
timmyDean said:
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
Click to expand...
Click to collapse
Hi, and thank you VERY much for posting such a nice explanation, especially in addition to all the work you have done posting your thread rooting 3.2. I understand, and completely agree with your explanation, as well as your position on taking control of what we bought and paid for. I take even stronger offense with this tablet's bootloader being locked than I do on my phones. This is not a discounted phone with a service plan tied to a cell provider. It has WiFi, but " I " am the only one providing its data (it never leaves my home). There is no justification here that I am 'leasing' a provider's technology . It was a gift, so I can't speak to choosing the vendor. But I like your wheel lug analogy.
I've been reading the threads on rooting, and both my Android phones are rooted and ROMed, so I've been around the block a couple times from the rooting aspect. But thus far I have been rather confused as to which route to take with the tablet. I don't want to be limited to using terminal for su access, so I want to 'fully root' the tablet. My goal is to allow apps like Titanium Backup, Root Explorer, and others I use on the phones, as well as having Clockworkmod Recovery, or similar recovery capable of working with nandroid backups. But for now I don't have plans to use a custom ROM. So having rooted stock 3.2 would suffice.
Although I do fully understand the need to research these kinds of things before jumping in, I also know that often times information evolves, and lengthy threads which were once considered current info end up not getting updated during that evolution. This can lead to wasted time reading information which can no longer actually be used . So in the spirit of pursuing the most current info, could you recommend which thread I can use to get the best results while rooting this 3.2.1 OS Tablet with the above goals in mind?
Used Timmydean's method, it is pretty easy as long as you follow his instructions with in the zip file he has made with all the tools you need inside of hat zip file. You root, install super user and busybox then download Acer recover installer and that will install cwm...
http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
Good luck and thanks again timmydean for this method.
Sent from my A500 using xda premium
Thanks, that sounds like the way to go. I'll head over to the link you provided.
I've got a couple of questions about the zip file at that post. I want to download that to my PC, and will be using ADB from there, right? I have the choice of doing so from either Windows XP SP3, or Windows 7 Home Premium. I read in older threads that many of the problems people had were only when they used XP, but were avoided by using Windows 7 (which was exactly opposite of what people experienced rooting the LG Ally), so it seems that in this case it is desirable to use Win7?
I presume I'll need to install a driver so the PC can 'see' the tablet. Is one provided in the tools, or do I need to download that somewhere?
I used windows 7. Yes the driver is in the zip file. I unzipped the file to a folder on my desktop and went from there.
In the zip there is a folder called usbpcdriver. Run the set up from within the fooder to get your driver... please read the instructions that say read me..
Sent from my A500 using xda premium
Thanks. I intend to read everything I can get my hands on before I actually start this. I definitely don't want any trouble or, heaven forbid, to brick the tablet.
pretty easy i think... good luck and let us know when you get rooted
I'm not finding any actual instructions on the steps to take for this procedure. The readme file in version 3 zip file only talks about "changes" from whatever the original procedure was.
Where can I get the actual instructions for the entire procedure?
Edit: I just downloaded version 2 of the zip file. In that one there is an additional PDF called "Steps". It is a little more detailed, and says at step 20 that "you should now have 3.2 with a SU shell installed". Does the DotNetDetector step actually ROOT the device? That seems simple enough, but it still has no mention of things like installing ADB and the PC driver. I located the actual thread from which the single post was derived (the target of the URL above, where it is suggested I use TimmyDean's procedure). I am now looking through that entire thread to try to sort out where the instructions are.
AHA! Post 119 of that main thread says "Also the instructions and everything you need are in earlier posts.".
It appears this procedure needs an instruction manual written to consolidate all the gathered information. Having a link to only the download zip files isn't telling me the whole picture. I'll try gleaning the thread and see if I can put together all the steps needed from start to finish to make this work. Looks like ROOT ain't happening tonight.
http://www.multiupload.com/SLR6XSV841
---------- Post added at 05:14 AM ---------- Previous post was at 05:11 AM ----------
thats the link to read me file.. I about to jail break an Iphone 4... Wish me luck
I edited the above post while you were replying. I'll check out that link, thanks.
Good luck on jailbreaking the DemonSpawn 4.
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
OK, so it looks like the file you just sent me a link to is the same one as the "Steps.PDF" file that was released in Version 2. It appears to me that what I need to do is blend the changes (detailed in version 3's readme file) into that original Steps file, to make a single contiguous set of instructions, and then start at the top. I notice it does mention installing the PC driver and ADB.
Do I have this right so far?
rdnkchevy said:
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
Click to expand...
Click to collapse
That was fast! Wanna do my tablet?
The link you sent just now is to the version 3 zip file posted on 12/25, which is what I had initially downloaded. It does appear he streamlined the procedure, but it is that readme file which leaves out the part about installing the PC driver and ADB in the beginning, and also leaves out the part at the end telling you that you should now have 3.2 with a SU shell installed.
Please understand that I want to be "fully" rooted, not just have the ability to gain an SU prompt in terminal. Will this procedure "fully root" the tablet? I'm confused by what he means saying "SU shell installed".
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
rdnkchevy said:
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
Click to expand...
Click to collapse
OK, thanks!! Rooting went well without incident. I just installed Root Explorer and Titanium Backup, and made a backup to SD of my apps and data. Then installed Acer Recovery Installer, and let it install CWM Recovery. But what is considered the "home" button on the tablet?? Is it the reset button? The only buttons on this thing are the Volume rocker and the Power button. ( I got brave and found out it is the POWER button ).
Edit: To clarify, I meant to ask which button serves as the Home button while you are IN the CWM Recovery environment, not while in the Android OS home screen.
[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?
I just got a brand new K1. Fresh out of the box with 3-3 pre-installed, I downloaded and used TimmyDean's permanent root tool, flashing a rooted 2-2 firmware. I then enabled the backdoor and ran all the OTA updates up to 14-14. This took several hours in all. I then ran the BusyBox and SU Tools install script. Everything was looking okay. I selected the choice to exit the script with reboot. The K1 turned off and came back on with the Lenovo logo, but, at the top of the screen was red writing:
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002).
It stops there and goes no further. No bootup.
Attempting to research the error, it seems this is not an error too many people encounter or know about, so my guess is that my only way of fixing this problem is to flash the whole thing over again from the beginning. (Unless someone here knows something about this problem. That would be tremendously helpful.)
Having already experienced what it took to go from 2-2 to 14-14 the first time with the permanent root package, I'd certainly like to shortcut it however possible. In this thread, http://forum.xda-developers.com/showthread.php?t=1404351 , TimmyDean posted a rooted 13-13 that we can start from. However, the link to the download file for it is Multiupload.com, and Multiupload.com does not seem to be up for me. Does anyone know where else I can go to try and download a copy?
I'd have posted directly in that Development thread, but, since I am an XDA noob, the forum system only allows me to post in this General section.
After experimenting with the "permanent root" package several times now, each time ending up with the "Unsupported menu option selected: 1" error after any OTA update, I have to believe there is an incompatibility between the K1 I have and the bootloader files in the "permanent root" package. I do not know if my K1 is recently manufactured and they are now doing something different with them that causes this incompatibility or what, but I felt I should warn you all that flashing the "permanent root" package could cause your K1 to not take official updates or to otherwise brick it with the "unsupported menu option" error. Perhaps the 13-13 package, which I don't have and can't test, didn't have this problem.
My serial number is CB1245XXXX. Manufacture date is "11/11/27."
I have now given up on getting root on my K1 and would just be happy to get it back to a working condition that can take Lenovo's OTA updates without bricking. I am currently trying these instructions and will update as to whether or not that resolves the problem: rootzwiki.com/topic/13877-guide-ideapad-k1-restore-to-mostly-stock-with-ota-updates/ (The forum software will not allow me to post hot links, so copy and paste that to browser.)
The rootzwiki procedure did not work to correct the problem. After any update, the tablet is bricked with the error. There are a few threads on the Lenovo support forum on this issue now, and there is no solution.
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Unrecoverable-Boot-Loader-Error/td-p/683633
I believe these old bootloader files will not work and will brick newer K1's, so my warning is:
DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
This might only apply to more recently manufactured K1's, but, since we do not know when this problem begins, it is not possible to know beforehand whether or not you will brick yours.
To be on the safe side, DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
Unfortunately, there was no backup option in the rooting packages, so I could not get a copy of the stock bootloader or any other files, if they are indeed of a different and newer variety. If someone has a recently manufactured K1, perhaps you can get those files and share them, because a lot of people are starting to see this problem now.
I have one with sn#1250xxxx, mfg dt 11/11/29. I wasn't even trying to root the thing. I happened during an OTA update. I tried probably all the recovery/rooting option out there. None of them worked. I have the tablet booting at lenovo screen. But I think you are right about the bootloader. If we can get the correct bootloader, we might be able to the the tablet back to life.
fix?
Has anyone come out with the fix for your issue.. I have the same issue . Used TImmy Dean's method.. and anything updating past the 02_02 (loaded from the tool I get the error... Anyone here have access to contact JimmyDean to ask him for help?
I see that he updated the tool to K1_A301_13_13_111209_US and maybe K1_A301_14_14_111209_US but all the links are dead.. anyone have a good place to download the files?
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
those are just OTs.. not image files.. If you don't have a compatable boot loader, you can't load those files.. We don't have a compatable bootloader.. so this is why we need ver 13 of timmy dean..
rezapatel said:
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
Click to expand...
Click to collapse
Can someone who's getting this bootloader error send me a pm. I put together a stock 120109 update that may work around the issue and I need someone to test.
Was this issue ever resolved, I didnt attempt to root mine, only attempted to wipe it clean and got this..
No, no real resolution. What I ended up doing was NVFlashing one of khanning's ROMs, like this one: http://forum.xda-developers.com/showthread.php?t=1560441
I don't know what's going to happen when I have to update again, such as the upcoming Ice Cream Sandwich update promised by Lenovo.
Hello,
I’ve been browsing these forums endlessly in an effort to find an answer to my problem, however I feel like I am at my wit’s end so I am trying to find anyone that could help me here.
I have Samsung A5 (2016) with Android 7.0 and October 1, 2018 Security patch level.
I’m trying to flash an older version of 6.0 Android with an older Security update level, however I am facing the “SW REV CHECK FAIL ERROR” - from what I understand I cannot downgrade to a version that has lower security patch. Is there ANY way around this besides trying to flash 6.0 with newer security patch?
I’ve been browsing here a lot and found a few mentions of this being possible by unpacking the .tar.md5 file and removing all files ending with .bin and packing it up as .tar.md5 again, however my attempts at this have failed - Odin will still give me “Fail” and I will still get the same SW REV CHECK FAIL error. I’ve found a post saying that removing the .bin files from the .tar.md5 file that I want to flash and replacing them with newer .bin files should work as to trick the bootloader to think the version is the same as my current one and essentially leaving the newer version of bootloader still on my phone but with downgraded android version of a lower sec. patch. I’m a bit skeptical about this approach and I fear it will not work - I am afraid to try.
I have been trying to find an anwser for days - any help will be truly appreciated! ^^
Armageddon8 said:
Hello,
I’ve been browsing these forums endlessly in an effort to find an answer to my problem, however I feel like I am at my wit’s end so I am trying to find anyone that could help me here.
I have Samsung A5 (2016) with Android 7.0 and October 1, 2018 Security patch level.
I’m trying to flash an older version of 6.0 Android with an older Security update level, however I am facing the “SW REV CHECK FAIL ERROR” - from what I understand I cannot downgrade to a version that has lower security patch. Is there ANY way around this besides trying to flash 6.0 with newer security patch?
I’ve been browsing here a lot and found a few mentions of this being possible by unpacking the .tar.md5 file and removing all files ending with .bin and packing it up as .tar.md5 again, however my attempts at this have failed - Odin will still give me “Fail” and I will still get the same SW REV CHECK FAIL error. I’ve found a post saying that removing the .bin files from the .tar.md5 file that I want to flash and replacing them with newer .bin files should work as to trick the bootloader to think the version is the same as my current one and essentially leaving the newer version of bootloader still on my phone but with downgraded android version of a lower sec. patch. I’m a bit skeptical about this approach and I fear it will not work - I am afraid to try.
Is there any way to do this?
Click to expand...
Click to collapse
The fifth character from the right end of your firmware build number is the Binary version.
You are getting that failure error because the firmware that you are trying to flash has a Binary version that is lower than the Binary version of the firmware that you had on the device before you tried to downgrade it. You can not flash any firmware that has a lower Binary version, you can flash a firmware that has the exact same Binary version as what was already on the device or a higher Binary version. You can't go backwards, you can only stay where you are or go forward, but, if you go forward, you also can't go back to what you had before you went forward, and so on and so on....
Yes, you can try to swap the .bin files, but, that may not be the only things that need to be swapped or modified. You'd have to do some research for yourself and use a little trial and error.
Sent from my SM-S767VL using Tapatalk
Yeah I know about all that, apparently my bootloader is 7.
What I’m trying to do is to find a workaround for the “can’t go back to older version” roadblock.
I was hoping someone here might be experienced in this regard as to help me with the editing process. I’ve also heard that flashing custom ROM and then flashing the old version Android might work.
Anyone with any ideas? :/
Armageddon8 said:
Yeah I know about all that, apparently my bootloader is 7.
What I’m trying to do is to find a workaround for the “can’t go back to older version” roadblock.
I was hoping someone here might be experienced in this regard as to help me with the editing process. I’ve also heard that flashing custom ROM and then flashing the old version Android might work.
Anyone with any ideas? :/
Click to expand...
Click to collapse
Flashing a custom ROM then trying to flash the older version isnt going to work either because even though you would have a custom ROM installed, the bootloader that is blocking the downgrade is still there "under" the ROM.
As I stated, swapping files between the older version and the newer version "might" work. But, the problem is, there is no definitive guide that works for every user or every device. It is always a case by case scenario where the modifications required depend on but are not limited to exactly which device you are working with, what android versions are you working with, what bootloader versions you are working with and whatever other software security measures may be incorporated into your device.
As I said, on this subject, you will have to do your own research and use trial and error. In other words, you will have to try for yourself and experiment until you find something that works. There are no instructions or guides that any of us can specifically give you and say "do this" that will 100% work for you because results are different from one device to the next.
I realize that this doesn't help you as much as you would like it to, but, it is the reality whether you choose to accept it or not.
All I can say is do some searches for how to modify Samsung firmware in order to downgrade or how to modify Samsung firmware in general. Then it's a matter of using trial and error to find the right recipe of firmware parts to get a firmware that will successfully flash on your device. It isn't easy because it doesn't always come down to just the bootloader or its binary version, sometimes, the bootloader or the binary is also looking for(for example but not limited to) a modem, system and kernel that has the same binary version as the bootloader that is being flashed. No one can definitely say which parts you can or can't use together from the different firmware available for your device. This makes it very hard to help you to the extent that you are hoping for.
This website really functions by the user searching for answers and doing the work for themselves. We answer questions here, but we don't spoonfeed anyone, we don't hold anyone by the hand and lead them step by step nor will we do it "for" you. You must be willing to put the time and the work into it for yourself, after all, it is your goal to achieve, not ours.
Sent from my SM-S767VL using Tapatalk
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Waiting for someone to shed some light in to this matter. I tried all the possible procedure I found on google, but no luck.
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
If your still interested in rooting this device go to @Austcool post it worked for me.
custom-sm-t380-sm-t385-boot
Edit: 2022 I have tested it it fully works as of this year!!!. 😁 disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk. to flash it simply open up settings enable developer options and enable OEM...
forum.xda-developers.com
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
Its Defex use my boot.img it's related to Samsungs new Defex anti root privileges security feature you must build the kernel from source; I already built Defex disabled kernel Prerooted with magisk.
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Sure I'll pull them from my device on pie.
Austcool said:
Sure I'll pull them from my device on pie.
Click to expand...
Click to collapse
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Austcool said:
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Click to expand...
Click to collapse
Thank you so much!!!
And sorry it wasn't your build it was zfk110's build https://forum.xda-developers.com/t/...android-9-bloatware-free-twrp-backup.4243589/
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I am piggy backing too because you are someone recently (last week) were messing with this thing too...
I was given a SM-T380 and am trying to make it "useful"
So far I have had fine luck with both oreo and pie (using the build you mentioned T380DXS4CUD3 via twrp restore... and it is fine, but seems slower than I recalled 8.1 being...
Anyway, I have been flashing the v19.0 of magisk (and a v7.1 of magisk manager) and then flashed v21.4 (and v8.x of manager).
Anyway, if you install a newer magisk manager it will show the device as unrooted (N/A) but updating further seems like I would need to extract the boot.img from the twrp backup (which is above my head...) and patch it with newer magisk...
I am not sure that it's needed for what I will be using the tablet for.. but I haven't had luck with safetynet (using magiskhide props) so I am looking into other methods.
Anyway, I'm not sure if I sould go back to oreo 8.1 or not just because pie 9 seems sluggish in comparison..
Anyway, I am going to tinker with it in my spare time over the next few days, so if you want to connect about anything particular I am around.
-g
cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I root mine by just loading pie.tar from @Austcool post on odin. We have the same build no.