Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!
The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.
Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?
What ROM are you using? Also, which gapps did you install? Please be as specific as possible.
The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far
more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?
Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.
like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync
What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...
I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.
I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.
Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627
Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.
We have same device, but still i can't upgrade my tab in any roms. And unable to install TWRP higher than 3.1 version.
davidzvi said:
Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.
Click to expand...
Click to collapse
Have you just tried flashing stock firmware, using odin?
I was trying the CF_autoroot (and other kernels(?)) and TWRP in odin.
Oddly over the weekend I left it plugged in for a day and and when I opened the cover it was in TWRP.
I was able to wipe, format, and load a ROM. But I think I might have broken the battery connection now, it doesn't seem to want to plug into the main board. So it doesn't want to do anything now. I'll probably play around with the connector a bit and see if I can sort that out.
But I'm not sure what @rufio85 issue might be and I would be the last person to advise anyone on this stuff.