Related
Hi all,
I just finally got my KitKat OTA update on Sprint, my bootloader is unlocked (with stock recovery) and I'm rooted. I tried updating and got an error while installing, do I have to be unrooted? If yes, it needs to be done via RSD, correct?
Please someone answer quickly, I'm waaaaay too excited :beer:
Sent from my XT1056 using Tapatalk
I'm in the same boat. Except I have twrp recovery. I've done research, but I'm still confused. Can someone point me in the right direction. Thanks
Sent from my XT1056 using Tapatalk
shloho said:
I'm in the same boat. Except I have twrp recovery. I've done research, but I'm still confused. Can someone point me in the right direction. Thanks
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
You have to be on stock recovery, I don't remember right now where you can get it, but I believe this thread can help you
I was rooted with cwm recovery and unlocked bootloader and managed to update last night. All I did was fastboot flash the stock 4.2 recovery, then stick the update zip from the sprint kitkat thread in my /sdcard folder, then go to settings, check for updates and it installed just fine.
momentary said:
I was rooted with cwm recovery and unlocked bootloader and managed to update last night. All I did was fastboot flash the stock 4.2 recovery, then stick the update zip from the sprint kitkat thread in my /sdcard folder, then go to settings, check for updates and it installed just fine.
Click to expand...
Click to collapse
I got the OTA, I wanna do it the real way
Sent from my XT1056 using Tapatalk
I also got the ota and I'd rather go that route. But what you're saying is that I don't need to reflash any firmware I just need to flash stock recovery and then update?
Sent from my XT1056 using Tapatalk
shloho said:
I also got the ota and I'd rather go that route. But what you're saying is that I don't need to reflash any firmware I just need to flash stock recovery and then update?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I'm not absolutely positive, I'll let someone smarter than me answer that
Sent from my XT1056 using Tapatalk
I'm under the impression that you need to flash the stock firmware and recovery in order to get the OTA. I can't post links, but here is what I did to successfully get the OTA on my rooted, unlocked Sprint X:
1. Unroot via SuperSU.
2. Download your firmware from sbf droid developers.
3. Download the updated fastboot file that is linked in the 4.4 update Q&A/FAQ thread.
4. Place the new fastboot file in your platform-tools folder, and rename it so it doesn't get overwritten if you update the SDK.
5. Extract system.IMG, boot.IMG, and recovery.IMG from the firmware zip.
6. Fastboot flash recovery.IMG, then boot.IMG, then system.IMG.
7. Reboot and let sprint reinstall the stock app config.
You should then be able to take the OTA without losing any of your data. Steps may vary depending on whether or not your bootloader is unlocked/you used jcase's root methods instead of rooting via twrp or cwm.
Sent from my XT1056
---------- Post added at 12:38 AM ---------- Previous post was at 12:21 AM ----------
If you didn't uninstall any of the stock apps, you may just need to flash the recovery. The aforementioned thread is located in the General section and is entitled [FAQ] for Kit kat and How to prepare for it (All Carriers). It contains more detailed instructions, a few more options for regaining a state that will take the OTA, and it's written by someone who appears to be much more knowledgeable than myself. If I were you, I'd take a look at that thread before trying anything.
Sent from my XT1056
Deadboots said:
I'm under the impression that you need to flash the stock firmware and recovery in order to get the OTA. I can't post links, but here is what I did to successfully get the OTA on my rooted, unlocked Sprint X:
1. Unroot via SuperSU.
2. Download your firmware from sbf droid developers.
3. Download the updated fastboot file that is linked in the 4.4 update Q&A/FAQ thread.
4. Place the new fastboot file in your platform-tools folder, and rename it so it doesn't get overwritten if you update the SDK.
5. Extract system.IMG, boot.IMG, and recovery.IMG from the firmware zip.
6. Fastboot flash recovery.IMG, then boot.IMG, then system.IMG.
7. Reboot and let sprint reinstall the stock app config.
You should then be able to take the OTA without losing any of your data. Steps may vary depending on whether or not your bootloader is unlocked/you used jcase's root methods instead of rooting via twrp or cwm.
Sent from my XT1056
---------- Post added at 12:38 AM ---------- Previous post was at 12:21 AM ----------
If you didn't uninstall any of the stock apps, you may just need to flash the recovery. The aforementioned thread is located in the General section and is entitled [FAQ] for Kit kat and How to prepare for it (All Carriers). It contains more detailed instructions, a few more options for regaining a state that will take the OTA, and it's written by someone who appears to be much more knowledgeable than myself. If I were you, I'd take a look at that thread before trying anything.
Sent from my XT1056
Click to expand...
Click to collapse
Awesome thanx!!!
Sent from my XT1056 using Tapatalk
Deadboots said:
I'm under the impression that you need to flash the stock firmware and recovery in order to get the OTA. I can't post links, but here is what I did to successfully get the OTA on my rooted, unlocked Sprint X:
1. Unroot via SuperSU.
2. Download your firmware from sbf droid developers.
3. Download the updated fastboot file that is linked in the 4.4 update Q&A/FAQ thread.
4. Place the new fastboot file in your platform-tools folder, and rename it so it doesn't get overwritten if you update the SDK.
5. Extract system.IMG, boot.IMG, and recovery.IMG from the firmware zip.
6. Fastboot flash recovery.IMG, then boot.IMG, then system.IMG.
7. Reboot and let sprint reinstall the stock app config.
You should then be able to take the OTA without losing any of your data. Steps may vary depending on whether or not your bootloader is unlocked/you used jcase's root methods instead of rooting via twrp or cwm.
Sent from my XT1056
---------- Post added at 12:38 AM ---------- Previous post was at 12:21 AM ----------
If you didn't uninstall any of the stock apps, you may just need to flash the recovery. The aforementioned thread is located in the General section and is entitled [FAQ] for Kit kat and How to prepare for it (All Carriers). It contains more detailed instructions, a few more options for regaining a state that will take the OTA, and it's written by someone who appears to be much more knowledgeable than myself. If I were you, I'd take a look at that thread before trying anything.
Sent from my XT1056
Click to expand...
Click to collapse
I successfully updated, thanx again
Sent from my XT1056 using Tapatalk
No problem!
Sent from my XT1056
Those that are flashing and posting success are you getting root access again after the update?
Sent from my XT1056 using Tapatalk
What exactly did you do to update successfully
Sent from my XT1056 using Tapatalk
shloho said:
What exactly did you do to update successfully
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I followed this posts option 2, didn't lose any data and was extremely easy
Sent from my XT1056 using Tapatalk
shaya4207 said:
I followed this posts option 2, didn't lose any data and was extremely easy
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Were you able to regain root?
Sent from my XT1056 using Tapatalk
robbi24r said:
Were you able to regain root?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Didn't attempt yet, but with TWRP it should be fairly easy, I'll keep you posted as soon as I do it
Sent from my XT1056 using Tapatalk
shaya4207 said:
Didn't attempt yet, but with TWRP it should be fairly easy, I'll keep you posted as soon as I do it
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Appreciate it.
Sent from my XT1056 using Tapatalk
Thanks
Sent from my XT1056 using Tapatalk
robbi24r said:
Were you able to regain root?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Yep, it was very easy...
PLEASE KEEP IN MIND THAT THIS IS WHAT I DID, AND IT WORKED PERFECTLY FOR ME. I CAN'T FULLY GUARANTEE THAT IT'LL WORK FOR YOU THOUGH!!!
Step 1: Download TWRP Recovery for KitKat here and mfastboot from here and put them in the same folder
Step 3: Power off phone, and power on to bootloader (Vol Down + Power for a couple of seconds)
Step 4: Plug phone into PC and open CMD to folder where you have the files that you downloaded
Step 5: Type
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
Step 6: When it's done flashing boot into recovery (scroll with Vol Down and select with Vol Up)
Step 7: Once in TWRP click on Reboot -> System it'll notify you that you aren't rooted and ask if you want to root
Step 8: Profit... :laugh:
PLEASE KEEP IN MIND THAT THIS IS WHAT I DID, AND IT WORKED PERFECTLY FOR ME. I CAN'T FULLY GUARANTEE THAT IT'LL WORK FOR YOU THOUGH!!!
Best of luck!!!
shaya4207 said:
Yep, it was very easy...
PLEASE KEEP IN MIND THAT THIS IS WHAT I DID, AND IT WORKED PERFECTLY FOR ME. I CAN'T FULLY GUARANTEE THAT IT'LL WORK FOR YOU THOUGH!!!
Step 1: Download TWRP Recovery for KitKat here and mfastboot from here and put them in the same folder
Step 3: Power off phone, and power on to bootloader (Vol Down + Power for a couple of seconds)
Step 4: Plug phone into PC and open CMD to folder where you have the files that you downloaded
Step 5: Type
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
Step 6: When it's done flashing boot into recovery (scroll with Vol Down and select with Vol Up)
Step 7: Once in TWRP click on Reboot -> System it'll notify you that you aren't rooted and ask if you want to root
Step 8: Profit... :laugh:
PLEASE KEEP IN MIND THAT THIS IS WHAT I DID, AND IT WORKED PERFECTLY FOR ME. I CAN'T FULLY GUARANTEE THAT IT'LL WORK FOR YOU THOUGH!!!
Best of luck!!!
Click to expand...
Click to collapse
Thank you sir your process worked fantastically, not excited about reloading apps back up but i'm 4.4 so it's worth it Thanks again!
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?
i am on stock firmware but rooted ..my device was lagging so i decided to install stock firmware...i dont take any backup.
i download two firmwares one is single file firmware and anthor one is 4 files firmware
when i am trying to flash single file firmware via odin its said that complete(write)operation failed
when i am trying 2nd 4 files firmware
re-partition failed
but twrp recovery installed successfully via odin ..
i have installed samsung drivers .
i also tried old version of odin
i also used other cable and usb port
Sent from my Redmi Note 4 using XDA-Developers Legacy app
sukha961 said:
i am on stock firmware but rooted ..my device was lagging so i decided to install stock firmware...i dont take any backup.
i download two firmwares one is single file firmware and anthor one is 4 files firmware
when i am trying to flash single file firmware via odin its said that complete(write)operation failed
when i am trying 2nd 4 files firmware
re-partition failed
but twrp recovery installed successfully via odin ..
i have installed samsung drivers .
i also tried old version of odin
i also used other cable and usb port
Click to expand...
Click to collapse
Do you enable oem unlock in developer options if not go to the developer options and enable oem unlock and USB debugging
to enter developer options go to settings about phone and click on 10 times build number
I flashed my mobile number of times through single firmware file
my phone is bricked stuck samsung logo i cant enable oem unlock in developer option
Sent from my Redmi Note 4 using XDA-Developers Legacy app
sukha961 said:
my phone is bricked stuck samsung logo i cant enable oem unlock in developer option
Click to expand...
Click to collapse
Go to download mode and flash stock firmware via Odin (for your model ofc ^^ )
try to flash userdata and cache only. if u can access tools that let u filter files thats great, extract from tar and re-pack if not.
When I put TWRP on my phone I stuck in Bootloop and when I put firmware my mobile turn on with all data but my twrp and supersu are deleted. How can I leave bootloop without deleting my twrp?
Is there any developer working on TWRP root for Samsung SM-A305F?
If not then please start working on it.
I need it....
Obliged...!
You don't need twrp recovery.
You can use Odin to flash patched boot.img from magisk to gain root access once your bootloader is unlocked
Sent from my Nokia 7 plus using Tapatalk
Always Wipe Data after Magisk-patched Bootloader?
K9998 said:
You don't need twrp recovery.
You can use Odin to flash patched boot.img from magisk to gain root access once your bootloader is unlocked
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Doesn't this method of rooting the A30 require that you must wipe data after the modified boot image is flashed? Is there a way to re-root after installing a ROM update without destroying the user data?
PPS
cmexec said:
Doesn't this method of rooting the A30 require that you must wipe data after the modified boot image is flashed? Is there a way to re-root after installing a ROM update without destroying the user data?
PPS
Click to expand...
Click to collapse
When you get ota notification of system update.
DO NOT install it directly.
Before click the install button, open magisk and uninstall it.
Now, power off the phone and flash original boot.img.
Once boot up, do the ota.
Then redo the boot.img patching thing.
I haven't fully test it because my phone only have 2 images right now. xsa.
I use the similar approach in other phones, and they all doing well.
(Nokia 7 plus and xiaomi a2)
Sent from my Mi A2 using Tapatalk
K9998 said:
When you get ota notification of system update.
DO NOT install it directly.
Before click the install button, open magisk and uninstall it.
Now, power off the phone and flash original boot.img.
Once boot up, do the ota.
Then redo the boot.img patching thing.
I haven't fully test it because my phone only have 2 images right now. xsa.
I use the similar approach in other phones, and they all doing well.
(Nokia 7 plus and xiaomi a2)
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Oh, thanks!
The guide for flashing the modified bootloader implied that the wipe data was a mandatory step.
PPS
Can anyone tell me the whole procedure for rooting samsung a30 (andorid 10) and the useful links?
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
this is what the screen says when i try to flash
no content in your post
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time
i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com