Related
please delete
Tips & Suggestions, Common Fixes & Questions
please delete
Cant get PC to read watch in step 10 of flashing
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Tom19146 said:
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Click to expand...
Click to collapse
Are you trying to flash the ROM or trying to run the patch? They are two different things. This thread is for the Patch.
No root
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
urmcgwy said:
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
Click to expand...
Click to collapse
What OS?
EDIT;
What model?
Lokifish Marz said:
What OS?
Click to expand...
Click to collapse
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
urmcgwy said:
Sorry Win7 x64
Click to expand...
Click to collapse
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
---------- Post added at 09:25 PM ---------- Previous post was at 09:18 PM ----------
urmcgwy said:
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
Click to expand...
Click to collapse
Omate "Developer Edition" 1/8
urmcgwy said:
Sorry Win7 x64
And I have no idea why I wrote Win7.... its Win8.1 x64
Omate "Developer Edition" 1/8
Click to expand...
Click to collapse
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Lokifish Marz said:
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Click to expand...
Click to collapse
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
urmcgwy said:
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
Click to expand...
Click to collapse
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Lokifish Marz said:
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Click to expand...
Click to collapse
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
urmcgwy said:
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
Click to expand...
Click to collapse
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Lokifish Marz said:
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Click to expand...
Click to collapse
Thanks for all the help! I'll just wait until tomorrow to see if the watch dies on me and see what Omate has to say. Really appreciate the quick responses!
I just flashed back to stock, what next is needed?
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Tom19146 said:
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Click to expand...
Click to collapse
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Lokifish Marz said:
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Click to expand...
Click to collapse
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Tom19146 said:
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Click to expand...
Click to collapse
Fixes have not made it to official firmware yet.
Rom = Patch + extras
Use an adblocker and only the actual download button will be seen.
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Tom19146 said:
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Click to expand...
Click to collapse
Iv'e had that happen to me a couple of times even when on stock w no patch. Short of pulling the battery you have to wait for the battery to die.
Omate TS slow and built-in memory full
Hi all, hopefully this time I am posting in the right place. After flashing the patch my TS seems to be slower and seems to ignore storing things on the sd card. The TS memory now has only 228mb free and the SD card is all free (this is set up as the default storage). Has anybody come across a similar situation (TS slow and memory full) and how could I overcome that? Many thanks in advance (please be patient, I am not an expert)!
Mods delete.
Unfortunately this won't happen. Had alot of trouble compiling the rom and deciding to sell it. Not much going on for my particular model anyway (G530T) and no guarantee the rom would work for other devices anyway.
On to the next one. Sorry guys and good luck
whats the catch? we need one to start custom roms and stuff.. and would it work for an SM-S920l Grand Prime?
I just want a custom recovery for the SM-S920L. I did manage to get adb shell working on the stock recovery but haven't figured out how to get an insecure adb binary to be picked up and used so no root.
xSpartacusx said:
whats the catch? we need one to start custom roms and stuff.. and would it work for an SM-S920l Grand Prime?
Click to expand...
Click to collapse
Not sure what you mean by "catch". In theory, the software should be the same for all Galaxy Grand Prime models? This is the only thing I would be modifying. I understand the kernel/baseband is different between devices (whether through reason of network, region or chipset variences) but the base software should be almost exactly the same across devices and therefore no kernels or basebands would be altered. I would obviously need willing participants to test on their personal devices throughout the development process and be able to provide logs and feedback on bug reports, but as this is supposed to only modify the software and applications I can't really forsee many issues.
That being said, I only own the 530T variant of the Grand Prime and cannot guarantee that EVERY model will accept the rom upon initial release. My team and I will valiantly make every effort to support as many Primes as possible so long as appropriate feedback from the community is gathered.
As I mentioned in the OP, I can just as well provide a tutorial of sorts to guide users along the path to modifying their device on their own. If a full blown rom isn't of much interest since all of the modifications can be done at will, we won't bother. We only look to simplify the process and hope to gain a reputation for doing so
bfoos said:
I just want a custom recovery for the SM-S920L. I did manage to get adb shell working on the stock recovery but haven't figured out how to get an insecure adb binary to be picked up and used so no root.
Click to expand...
Click to collapse
Unfortunate as flashing a custom rom (be it modified stock or otherwise) would require both root and a custom recovery. One of our members has experience building and porting recoveries, but only to devices they have had on hand
My device is rooted, I'm speaking of getting adb root working on the stock recovery which only supports adb sideload. I did manage to get adb shell working, but like I said, if I try and replace the stock adbd binary with an insecure version, the recovery won't pick it up.
by catch, i mean will it cost us anything to get it? etc. etc. and can i contribute to the developement of my grand prime? of like a stock rom or whatever..?
yes please!!!!
xSpartacusx said:
by catch, i mean will it cost us anything to get it? etc. etc. and can i contribute to the developement of my grand prime? of like a stock rom or whatever..?
Click to expand...
Click to collapse
This development is entirely on our own time with our own resources. We will never openly ask for money to make something happen. This is a passion, not a business prospect. We do this because we want to. If you'd like to support to the cause by means of monetary or physical device donations so that we may continue to expand our list of supported devices, we won't say no. It's of your own will to do so
i dont have money to send nor a device to give.. would giving you my kernel help in any way to make a stock rom for SM-S920l? or a stock recovery?
xSpartacusx said:
i dont have money to send nor a device to give.. would giving you my kernel help in any way to make a stock rom for SM-S920l? or a stock recovery?
Click to expand...
Click to collapse
It wouldn't hurt. It would also be useful to have something like a TWRP/CWM backup of ONLY the stock system, kernel, data partitions and stock recovery of as many variants as possible so we can ensure support for specific models where needed, provided you have the means to do so (root and custom recovery obviously). This would require a factory reset of your device or an Odin restore. We don't want or need any personal information you have on your phone. It's absolutely imperative that we get a fresh untouched image of the device. Its kind of a backdoor way of getting the information we need pertaining to each device, but obviously it does require some sort of recovery to get even that far. I can attempt to build from my current personal setup and that would allow feedback from others on the stability of flashing and report any and all issues.
Sound complicated? You have no idea lol
bfoos said:
My device is rooted, I'm speaking of getting adb root working on the stock recovery which only supports adb sideload. I did manage to get adb shell working, but like I said, if I try and replace the stock adbd binary with an insecure version, the recovery won't pick it up.
Click to expand...
Click to collapse
I personally don't have much experience in recovery modifications or obtaining such permissions from them but we do have a team member who may. How far his knowledge extends into the subject is beyond me. I just build the roms and do most of the PR stuff on the forums
dragonhart6505 said:
It wouldn't hurt. It would also be useful to have something like a TWRP/CWM backup of ONLY the stock system, kernel, data partitions and stock recovery of as many variants as possible so we can ensure support for specific models where needed, provided you have the means to do so (root and custom recovery obviously). This would require a factory reset of your device or an Odin restore. We don't want or need any personal information you have on your phone. It's absolutely imperative that we get a fresh untouched image of the device. Its kind of a backdoor way of getting the information we need pertaining to each device, but obviously it does require some sort of recovery to get even that far. I can attempt to build from my current personal setup and that would allow feedback from others on the stability of flashing and report any and all issues.
Sound complicated? You have no idea lol
Click to expand...
Click to collapse
ok um TWRP doesnt support the grand prime,, only the grand prime VE, which is completely different, and the CWM doesnt support the grand prime at all, either variants. i tried downloading odin.. and it wouldnt work (likeit wouldnt install)
but heres my kernel: https://www.dropbox.com/s/pv96mgsp9uqgo27/kernel-from-24-11-2015-4-18.img?dl=0
and STock recovery..: https://www.dropbox.com/s/hmdgsot6x6aybcl/stock recovery.img?dl=0
and if im wrong about the suppot for this device on either of those, please tell me and show me how to get a custom recovery from them...
xSpartacusx said:
ok um TWRP doesnt support the grand prime,, only the grand prime VE, which is completely different, and the CWM doesnt support the grand prime at all, either variants. i tried downloading odin.. and it wouldnt work (likeit wouldnt install)
but heres my kernel: https://www.dropbox.com/s/pv96mgsp9uqgo27/kernel-from-24-11-2015-4-18.img?dl=0
and STock recovery..: https://www.dropbox.com/s/hmdgsot6x6aybcl/stock recovery.img?dl=0
and if im wrong about the suppot for this device on either of those, please tell me and show me how to get a custom recovery from them...
Click to expand...
Click to collapse
Doesn't support the Grand Prime at all? I've flashed both CWM and TWRP with no issues. I have currently TWRP installed on my device (530T) but I'm not entirely sure it will support your device. It's not my development so no guarantees
Here's the thread I used:
http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
It says only for 530H, I know. But have you tried? I used RASHR from the Play Store to get it on mine. RASHR will also allow you to backup your current recovery in case the flash doesn't take. I recommend doing that first
dragonhart6505 said:
Doesn't support the Grand Prime at all? I've flashed both CWM and TWRP with no issues. I have currently TWRP installed on my device (530T) but I'm not entirely sure it will support your device. It's not my development so no guarantees
Here's the thread I used:
http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
It says only for 530H, I know. But have you tried? I used RASHR from the Play Store to get it on mine. RASHR will also allow you to backup your current recovery in case the flash doesn't take. I recommend doing that first
Click to expand...
Click to collapse
i used rashr to get those two files but i got rom manager by CWM and TWRP manager and both didnt have the normal grand prime in them
xSpartacusx said:
i used rashr to get those two files but i got rom manager by CWM and TWRP manager and both didnt have the normal grand prime in them
Click to expand...
Click to collapse
It won't because its not "officially" supported. But neither is my 530T and I got off just fine. Try to flash the file in RASHR from the thread I linked. If it doesn't take, you've got your backup so no harm no foul
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
wait wait wait no, it doesnt.. i did it again and hitreboot, and it says Custom Binary Blocked by reactivation lock.?
---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------
help?
xSpartacusx said:
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
Click to expand...
Click to collapse
Have you booted into the custom recovery or did you simply reboot the phone back to the system? I ask because Flashify also told me it was successful but in reality did nothing. That's why I suggested RASHR. Flashify is hit or miss in my experience
idfk what i did.. i hit chhoose file, selected the img it says successful and i hit the reboot option it gave me, and then that came up... i never rooted a phone before i never de any flashing **** before..
---------- Post added at 06:07 AM ---------- Previous post was at 06:06 AM ----------
it says custom binary blocked by reactivation lock with a big yellow triangle on the screen
xSpartacusx said:
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
wait wait wait no, it doesnt.. i did it again and hitreboot, and it says Custom Binary Blocked by reactivation lock.?
---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------
help?
Click to expand...
Click to collapse
Try booting into download mode (vol - home and power) then select no (vol -) and should boot you into the OS?
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
part fixed
graminou said:
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
Click to expand...
Click to collapse
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
graminou said:
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
Click to expand...
Click to collapse
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
corkiejp said:
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA[/URL] again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
Click to expand...
Click to collapse
Hi corkyejp and thanks, i was aiming to go back to current supported not the beta N release, I officially unenrolled received the OTA image, installed, got stuck in bootloop, tried sideloading MOB30G which i beleive was the correct wifi not LTE version (I saw that version mentioned in my crashlogs too). the device was in developer mode, I think but am not sure, however the HBOOT screens always showed LOCKED. i tried the fastboot flashing unlock (and OEM unlock options) but neither unlocked me. anyway at least I have a device that boots now, will put up with crashes if they occur. thanks again
If you are not an H918, H830, or US996 (Unlocked, NOT US Cellular) user, kindly leave this thread, this will not do anything for your device, exchange it if you're so desperate. Thank you.
Note for US996: It's probably easier for you guys just to flash TWRP the normal way and pull your battery then do the factory reset dance to get in!
Team Win Recovery Project 3.0.2-1
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
This will allow you to install TWRP and flash SuperSU!
Step 1: Unlocking your bootloader
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
H918/H830 users only:
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You will probably need to complete the Android setup wizard at this point to get access to ADB again.
US996 users only:
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once you're finished with unlocking your bootloader, continue on to step 2.
Step 2: Running recowvery
You can find the recowvery binaries (you need to download all of these) at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow#running (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3: Flashing TWRP & Rooting
Notice: There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, you can also just use adb push. (mentioned here)
Download TWRP: (official builds, V20 is waiting for TWRP 3.1.0 for twrp.me download)
H918: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
US996: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
H830: https://twrp.me/devices/lgg5h830.html
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4: Have fun!
I know a few people have mentioned donating, there is a button right on this post under my username.
Sorry, I don't keep a list as I prefer to keep people's information confidential, but if you do send any money my way, you can request that I mention you at the bottom of this post with any details.
I ask that people please not attach files in this thread, everything required is mentioned in this post, and should be stable in its present state. Thank you.
Thanks for testing on my phone! =]
Does This wipe data on the phone?
justthefacts said:
Does This wipe data on the phone?
Click to expand...
Click to collapse
Unlocking the bootloader does.
jcadduono said:
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that I'm still working on getting TWRP to boot, there seems to be something about the stock kernel sources that doesn't want TWRP to be a part of it.
This will not get you SuperSU or app root access, this is only a root shell allowing you to flash TWRP when it's ready and do other things.
This does however open up some methods of installing SuperSU without TWRP. @Chainfire might have some ideas if he wishes to show up here and stir up some noise.
We do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for TWRP.
For the instructions on using recowvery, you should read the README.md on the GitHub page:
https://github.com/jcadduono/android_external_dirtycow
You can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, I'm really tired.
Click to expand...
Click to collapse
Thank you for taking the time to begin with the first step to develop on this device! (although i will have to do a replacement tomorrow for 2 defects that emerged on my phone) I always had in mind that this device had only a 50% of chances to get rooted, and that it might actually never get rooted . But now chances have increased even more thanks to your hard work. and also thanks to the others you previously mentioned. Let us see if Chainfire takes an interest on adding the final details :good:
I've got ADB working fine, but get nothing with fastboot. Just a blank line when I type 'fastboot devices'. Tried 3 different USB ports also. Windows 10 x64.
I did grab the ADB/fastboot files linked in the first post, but the older files I had don't work either, and they have no issues with my Nexus 7 2013 and HTC 10.
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
So Idk what to do or how to get the file to flash it.. Any help?
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
My advice? Never, ever take an update until the developers say that they are sure they can exploit it. From what I can see, this process uses the "dirty cow" exploit which will assuredly be fixed on the next security update.
---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------
bambam126 said:
So Idk what to do or how to get the file to flash it.. Any help?
Click to expand...
Click to collapse
Why not wait until they can get full root and TWRP? As I see it, this process is to help other developers and people that know what they're doing refine and advance the move to full root. I don't think it's quite ready for prime time yet. It does nothing but get the foot in the door for rooting.
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
And, we're off to the races. Let the "I bricked my phone" threads begin!
douger1957 said:
[/COLOR]And, we're off to the races. Let the "I bricked my phone" threads begin!
Click to expand...
Click to collapse
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Oh. Great to know. I hope they manage to do something with the verizon variants, in fact, with all the variants . Maybe after that they will have more interest on the device
jcadduono said:
alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over teamviewer thanks to @slayerh4x and @darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that i'm still working on getting twrp to boot, there seems to be something about the stock kernel sources that doesn't want twrp to be a part of it.
this will not get you supersu or app root access, this is only a root shell allowing you to flash twrp when it's ready and do other things.
this does however open up some methods of installing supersu without twrp. @chainfire might have some ideas if he wishes to show up here and stir up some noise.
we do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for twrp.
For the instructions on using recowvery, you should read the readme.md on the github page:
https://github.com/jcadduono/android_external_dirtycow
you can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
you will need to unlock your bootloader first. For this you'll probably need lg's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00120120425
mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00320110909
you will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
start by turning on developer options in settings -> about device -> software info -> build number. (tap 7 times until it's enabled)
now navigate to settings -> developer options -> oem unlock. (turn it on)
don't ever turn oem unlock or developer options off when using a custom rom or recovery. This could lose to loss of all your data.
For your computer to see adb, you will need to put the phone in ptp mode (for transferring images). I don't know why this is, a misconfiguration in lg's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your pc.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other usb ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
warning: This step will wipe all your data and factory reset your phone!
you can check the status of your bootloader lock with the fastboot getvar all command.
Ex. (bootloader) unlocked:yes
you should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
there's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, i'm really tired.
Click to expand...
Click to collapse
you are the man !!!!!!!!!!!!!!!!!!!!!!!
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
douger1957 said:
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
Click to expand...
Click to collapse
yup! i couldn't have written it better hahaha. But it is bound to happen for some people that will not pay careful attention. I mena, im not an expert, im maybe a little more than a noob now since i have been dealing with this for quite some time, and that is why i just started my C++ class in order to reach at least a good-to-go level of understanding.
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a H918 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Locked or unlock
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Oh, ye of little faith. Where there's a will, there's a way.
Chainfire just tweeted:
Just installed SuperSU on a V20, based on @jcadduono 's initial work. Good times.
Can this method be used on other devices?
Sent from my R1HD(ZenUI) via Tapatalk
This is for the Sprint SM-T587P "gtaxlqltespr" Galaxy Tab A 10.1 variant only.
As far as I can tell, the Nougat update came out for the Sprint Variant sometime around the 20th of September 2017. Update to the T587PVPU1BQI1 Nougat update if you have not already.
1. Read all instructions, there are no known issues. Be on 7.0.0 official. (QI1)
2 Enable Developer Options. Settings, About Device, Software info, tap on build number until it is enabled.
3. Enable OEM unlock and USB Debugging in the Developer Options menu.
There are a couple options here. You can do any combination of the following:
install TWRP
root via superuser (requires installing TWRP)
disable dm-verity (requires installing TWRP)
root by flashing magisk patched bootimage (does not require TWRP)
disable force-encryption (requires installing twrp)(required if you want TWRP to see /data/ files)(not required for flashing zips such as superuser through TWRP)
To install TWRP:
1. Boot into download mode
2. Launch ODIN, Uncheck "Auto Reboot" in the options tab. Flash included TWRP file in the AP section of ODIN.
To Disable Force-Encryption (if want to see /data/ in twrp)
1. Install TWRP recovery
2 Boot into TWRP recovery
3. Format Data
4. Reboot into TWRP from TWRP reboot menu, without rebooting into system.
5. Flash the included superuser.zip to disable force-encryption and dm-verity
To Root via superuser or disable dm-verity
1. Install TWRP recovery.
2. Boot into TWRP recovery
3. flash superuser.zip (this needs to be done with ADB if you have not disabled force-encryption and are unable to see /data/)
Superuser root provided as-is. Magisk is the recommended root. If you prefer the outdated, beta, un-updatable phh superuser binary which breaks safetynet that's all you. However it is the only way i have found to disable dm-verity.
Magisk v16 root:
Device is stock
If you have not installed twrp, disabled dm-verity, or disabled force encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-dm-patched_boot.img.tar"
Disabled dm-verity, but NOT force-encryption
If you did not format DATA in TWRP and have installed superuser.zip using ADB:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-patched_boot.img.tar"
Disabled Both
If you disabled dm-verity AND disabled force-encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "Magiskv16_patched_boot.img.tar"
WIFI IS NOW WORKING AFTER ROOT/BOOT PATCH
Recovery: twrp-3.1.1-0-gtaxlqltespr.tar
phh's Superuser.zip
fe-dm-patched_boot.img.tar
fe-patched_boot.img.tar
Magiskv16_patched_boot.img.tar
Magisk Manager 5.6.1(105)
XposedInstaller_3.1.4_Magisk.apk
Stock 7.0.0 boot image
Stock 7.0.0 Recovery
phh's Superuser
Nougat Firmware
AP
BP
CP
CSC
Gonna try it now!!! Been waiting for along time.... thanks
Sent from my Sprint Samsung Galaxy Note5 using XDA Labs
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
T587P need stock firmware and recovery
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Ok what i did being i just didnt have recovery and wifi , i restored the tablet in samsung smart switch now everything works again as it should..i will hold out until we have a safe root for our T587P devices. Thank you
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Any updates on WiFi fix?
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Rpartin04 said:
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
Click to expand...
Click to collapse
A stock kernel has to be built from source.
Rpartin04 said:
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
Click to expand...
Click to collapse
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
DavidBeckett.db said:
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Click to expand...
Click to collapse
I didnt realize the firmware was behind a paywall, the correct link has been posted.
This is a proper root via the magisk patched boot. There is no reason to flash the recovery at all.
Rpartin04 said:
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Click to expand...
Click to collapse
Anyone who doesnt read the first post closely enough to locate locate the stock firmware being made to pay for it seems like a form of natural selection. Edit: or that would be the case were this the case, however, i posted the wrong link in the OP ( i had visited a lot to find the firmware, i misremembered which one was correct.)
ashyx said:
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Click to expand...
Click to collapse
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
arlyn said:
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
Click to expand...
Click to collapse
This as well is not a free deal. It would help out a ton if you just link these files to your account via Google drive, mediafire, ect....
EDIT!!!!
I didn't scroll all the way down... ignore me
arlyn said:
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
Click to expand...
Click to collapse
Did you edit it? If not must be going blind.
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Rpartin04 said:
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Click to expand...
Click to collapse
Haha, I didn't realize you had to subscribe to your own threads, I didn't know people were even replying in here for weeks. Thank you for attempting to compile, i know there are some tutorials on xda, i'm pretty sure an flashing an SELinux permissive kernel will fix the wifi issue with the magisk root. I do not know that I'll ever have the time or motivation to compile it myself, but I can help to test.
Thanks arlyn! Will definitely be trying this out.
Says root is not properly installled.... any ideas? I followed directions to a T... even flashed back to stock nougat and tried a 2nd time...