Related
hi, i just got my tablet back from repairs and i asked them to install ICS if they had to reset the firmware, and they did. now my problem is that i want to update to the 4.2 JB that came out (while my ASUS was in repairs for 3 WEEKS) but i can't. when i try to update, it just says "no update found". i have already talked to their "experts" and he just kept saying "oh, it come to your tablet when it ready" I have also tried to download the update from their site, but then when it tells you what version you need by looking at the build number, i noticed mine was IML74K.WW_epad-9.4..... and shouldn't it be something more like US_epad-9.4.....? i tried to install it anyways but it never detected it on the sd card. so then i tried to just use fastboot and flash it to the device, but when i entered the boot menu, THERE WAS NO OPTION!! In fact, there was only 2 options, wipe data, and boot android. there was no usb or RCK (or whatever it was) option. i also have several other problems, but i'll leave them for another day and another post, sense they may be related
Any help would be awesome sense it's obvious I'm not going to get much help from ASUS. Let me know if you need any other info too!
Thanks in advanced!!
Jake
Snakester15 said:
hi, i just got my tablet back from repairs and i asked them to install ICS if they had to reset the firmware, and they did. now my problem is that i want to update to the 4.2 JB that came out (while my ASUS was in repairs for 3 WEEKS) but i can't. when i try to update, it just says "no update found". i have already talked to their "experts" and he just kept saying "oh, it come to your tablet when it ready" I have also tried to download the update from their site, but then when it tells you what version you need by looking at the build number, i noticed mine was IML74K.WW_epad-9.4..... and shouldn't it be something more like US_epad-9.4.....? i tried to install it anyways but it never detected it on the sd card. so then i tried to just use fastboot and flash it to the device, but when i entered the boot menu, THERE WAS NO OPTION!! In fact, there was only 2 options, wipe data, and boot android. there was no usb or RCK (or whatever it was) option. i also have several other problems, but i'll leave them for another day and another post, sense they may be related
Any help would be awesome sense it's obvious I'm not going to get much help from ASUS. Let me know if you need any other info too!
Thanks in advanced!!
Jake
Click to expand...
Click to collapse
The stock 4.2 (10.6.1.8) has an assert that will only allow it to be installed from 10.4.2.20. If memory serves me correctly ICS does not have the usb icon until unlocked. Also the new 4.2 bootloader only has three icons - no usb.
Are you unlocked? Most units that come from repair are not and can't be unlocked.
With all the unresolved issues on 4.2 I would not put it on my tablet at this time. There are many bricks waiting for a resolution.
thanks, that helped fix it!
tobdaryl said:
The stock 4.2 (10.6.1.8) has an assert that will only allow it to be installed from 10.4.2.20. If memory serves me correctly ICS does not have the usb icon until unlocked. Also the new 4.2 bootloader only has three icons - no usb.
Are you unlocked? Most units that come from repair are not and can't be unlocked.
With all the unresolved issues on 4.2 I would not put it on my tablet at this time. There are many bricks waiting for a resolution.
Click to expand...
Click to collapse
I downloaded the 4.1 firmware and it detected it and installed it right away. I don't know why they couldn't tell me that when I called, but it fixed the problem. And I know you said not to, but I installed 4.2 anyways because I was too curious, and I have personally found no problems and like the new features.
I bought an Acer A700 tablet off ebay, was supposed to be new unused condition. Booted it up and it had no system bar at bottom of page. That means you can't get out of any app you have to reboot, useless. Thru reading on site and exploring this tab i found out it has super user installed on it and on bootup in the left hand corner it reads "boot loader ICS-MRI 7173de1 (unlock mode)" every thing on the tablet seems to work except no navigation bar, no circle in center, and no status info no bar at all full screen. I have played with this thing been on Acer chat and they say hard ware failure. That is before i new it was rooted, i guess that is the reason the update he wanted me to try did not work. I don't know if i try a new OS system if that will even work. I am 68 years old and this is my first android tablet, new ground for me. Most every thing i read is above my knowledge, would appreciate any advice i might just try it. thanks ahead of time
demo mode
Is there a demo mode on this acer A700 and if so where to look thanks
easyreble said:
I bought an Acer A700 tablet off ebay, was supposed to be new unused condition. Booted it up and it had no system bar at bottom of page. That means you can't get out of any app you have to reboot, useless. Thru reading on site and exploring this tab i found out it has super user installed on it and on bootup in the left hand corner it reads "boot loader ICS-MRI 7173de1 (unlock mode)" every thing on the tablet seems to work except no navigation bar, no circle in center, and no status info no bar at all full screen. I have played with this thing been on Acer chat and they say hard ware failure. That is before i new it was rooted, i guess that is the reason the update he wanted me to try did not work. I don't know if i try a new OS system if that will even work. I am 68 years old and this is my first android tablet, new ground for me. Most every thing i read is above my knowledge, would appreciate any advice i might just try it. thanks ahead of time
Click to expand...
Click to collapse
Ok, so whoever you bought it from, told you an outright lie. The bootloader is unlocked, and, it most likely has a custom OS installed on it. You can check this by going into "Settings" "About Tablet" and seeing what is installed on it.
Or,
The previous owner had root access (obviously) and went mucking around with the SystemUI.apk and goobered something up (most likely). In fact, I would guess he had CM installed and didn't like the way the nav icons were (in the center) and tried doing something about it by modifying files he had no idea of what to do.
The most simple fix, would just be to install a fresh version of either a custom ROM, or, revert it back to a stock factory ROM. Both of which are relatively easy to do.
MD
EDIT: Other things to look for now that I think about it. Check your applications and see if any of the following are installed.
Launcher (Nova, Go, etc) These sometimes have an option to disable the system bar (Nav Bar).
ExPosed Installer - This allows loading of custom exposed frameworks mods that several have the option to disable the System Bar (nav bar)
Any Nav Bar/System Bar "Hide" application. These at one time were useful to open more display real estate for games. (not many use them anymore)
Those applications you can safely uninstall through Settings/Applications, then reboot.
Other than that, I can't think of anything else. Will wait till you tell us which OS is installed (CM; Cyanogen Mod, PA; Paranoid Android, etc)
Oh, and one more thing. Stop talking to those folks on Acer Chat. This is a software issue, and not a Hardware issue. This I can promise.
easyreble said:
Is there a demo mode on this acer A700 and if so where to look thanks
Click to expand...
Click to collapse
"Demo" mode, is not a configurable option on most devices. In reality, it is a custom software from Acer that is installed for Store Display purposes. Several items have been left out of the build, specifically to prevent casual customers from mucking things up.
This is generally fixed by installing a full ROM.
MD
Moscow Desire said:
Ok, so whoever you bought it from, told you an outright lie. The bootloader is unlocked, and, it most likely has a custom OS installed on it. You can check this by going into "Settings" "About Tablet" and seeing what is installed on it.
Or,
The previous owner had root access (obviously) and went mucking around with the SystemUI.apk and goobered something up (most likely). In fact, I would guess he had CM installed and didn't like the way the nav icons were (in the center) and tried doing something about it by modifying files he had no idea of what to do.
The most simple fix, would just be to install a fresh version of either a custom ROM, or, revert it back to a stock factory ROM. Both of which are relatively easy to do.
MD
EDIT: Other things to look for now that I think about it. Check your applications and see if any of the following are installed.
Launcher (Nova, Go, etc) These sometimes have an option to disable the system bar (Nav Bar).
ExPosed Installer - This allows loading of custom exposed frameworks mods that several have the option to disable the System Bar (nav bar)
Any Nav Bar/System Bar "Hide" application. These at one time were useful to open more display real estate for games. (not many use them anymore)
Those applications you can safely uninstall through Settings/Applications, then reboot.
Other than that, I can't think of anything else. Will wait till you tell us which OS is installed (CM; Cyanogen Mod, PA; Paranoid Android, etc)
Oh, and one more thing. Stop talking to those folks on Acer Chat. This is a software issue, and not a Hardware issue. This I can promise.
Click to expand...
Click to collapse
You are correct, i will never talk to acer support again. I am getting ready to install a rom if i can figure out which one to start with. It has Adroid Veersion 4.0.4 Kernal version 2.6.39.4+ Boot loader ICS-MRI 7173de1 (unlock mode) It has superuser app installed, I did download an app which gave me a navigation bar that i am using till i can get a rom installed. My problem is that looks like i need to upgrade this 4.0.4 ICS before i can install the up to date roms is that correct. Thanks for helping be get this straight this is a lot for an old man to take in lol.
easyreble said:
You are correct, i will never talk to acer support again. I am getting ready to install a rom if i can figure out which one to start with. It has Adroid Veersion 4.0.4 Kernal version 2.6.39.4+ Boot loader ICS-MRI 7173de1 (unlock mode) It has superuser app installed, I did download an app which gave me a navigation bar that i am using till i can get a rom installed. My problem is that looks like i need to upgrade this 4.0.4 ICS before i can install the up to date roms is that correct. Thanks for helping be get this straight this is a lot for an old man to take in lol.
Click to expand...
Click to collapse
4.0.4 should be the original ICS ROM. If you get it installed, it should get you a locked bootloader, and hopefully offer the upgrade to JellyBean (4.1.x I believe)
Don't worry about age, I'm not far behind you
Have an issue, just PM me and I'll see if I can help.
MD
Moscow Desire said:
4.0.4 should be the original ICS ROM. If you get it installed, it should get you a locked bootloader, and hopefully offer the upgrade to JellyBean (4.1.x I believe)
Don't worry about age, I'm not far behind you
Have an issue, just PM me and I'll see if I can help.
MD
Click to expand...
Click to collapse
No that is what is on my tablet now unlocked and rooted. thanks. i am not clear as to get it upgraded form 4.0.4 and not sure if i need to upgrade to put new rom on it, and which one to work with. I have all my info downloaded on my computer, got to get a cable to work with. Just not sure if i can put the newest version on it without flashing it back to stock locking the boot loader upgrading and then rooting it again just to much i may need to take a break after 3 days of reading, but i have learned a lot. thanks what do u think
easyreble said:
No that is what is on my tablet now unlocked and rooted. thanks. i am not clear as to get it upgraded form 4.0.4 and not sure if i need to upgrade to put new rom on it, and which one to work with. I have all my info downloaded on my computer, got to get a cable to work with. Just not sure if i can put the newest version on it without flashing it back to stock locking the boot loader upgrading and then rooting it again just to much i may need to take a break after 3 days of reading, but i have learned a lot. thanks what do u think
Click to expand...
Click to collapse
Well, 4.0.4 ICS (ice cream sandwich) is the OS these tablets were shipped with. Then, it generally, after some days, would upgrade to 4.1x (jelly bean) Gotta love Google and the names.
Now, considering your tablet has SU (Superuser), and and unlocked bootloader, means somebody mucked with it, hence the missing NAV(Sys) bar. Dude undoubtedly mucked around with things.
As I stated before, this can happen due to several different reasons. How it got to that point, who knows.... In testing ROMs, Ive had this issue by installing a different SystemUI.apk that didn't match all the other files, Or, by "dirty" flashing a ROM without wiping /System partition.
Basically, to get it back to a completely stock A700, you will need to install a stock Factory A700 ROM. the 4.0.4 version. Should be able to find one quite easily, but if not, let me know and I'll help.
Basically, you rename that Stock ROM to "update.zip", copy it to ext SD, then boot the tablet holding "VOL+ then PWR and it "should see the zip and start to install it. "Should".
If not, then I can walk you through the steps to install a custom recovery, and we can do it that way. Acer, with JellyBean, actually has a somewhat recovery menu. Not sure if the 4.0.4 has it or not. Been too long. It may just look for "update.zip" and try and install it.
So will just have to see how it plays out.
For my own, I use "fastboot" so install image files to revert back, but that's just me. Also I have an A701, so it wouldn't do you much good
Same hardware so to speak, except for the 3g part and some different files.
MD
Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope
S8+ /S8 Global Unlocked Variants, (ie: G955FD, etc) Desperately need help w/issue After 8.0 Update...
Hi, I have a G955FD & have family members with this same model, as well as the Global unlocked regular S8-dual sim. We all have the same issue after the Samsung 8.0.0 update. The phone is no longer reliable. Randomly, these devices will not have any ring on incoming calls. If they don't leave a VM, then you have no indication of a missed phone call. In addition, random periods where text messages will also just not come thru. Difference on the texts is, when you reboot, they all populate in the message app and notifications. But the incoming calls are not known and lost forever w/o a VM left for you by caller.
I have been in contact with Samsung, although they indicate right off that I have no warranty because I didn't buy a carrier device from an authorized vendor for my local use, they were open & helpful to reveal that they are aware of '8.0 ringer issues' on the unlocked global devices. BTW, this must be a huge number of people across the world with this problem, but like my friends/family, originally think they have signal/carrier issues etc. Samsung says that it should be addressed in a patch or update..... but, WHEN? I have had a messed up phone for over 3months and counting.
The only thing that can be done to attempt having the phone work 'more often' is to do a restart every hour all day long and hope that your phone will ring when someone is calling.
I, personally, being the family tech guy, am the one working on the issue so I'm here to ask for help/input.
Been dealing with this issue for over 3 months now, here's some of what I have done and what I'd like help with please...
I have attempted 5x to install a custom ROM from XDA to alleviate this issue completely, but as of now, still unsuccessful. I've been rooting/hacking my android devices since my 1st but somehow can't get the process to work thru. At this point, using Odin, I have no issue to get my phone running TWRP and rooted. Somehow, after that point something isn't going right and my phone has to be re-odin flashed with OEM ROM and then wait 1 week for OEM unlock to re-appear to try again. So, If I could complete this process next time the OEM-unlock is back up, my problem would be over.
Now, since I am having issue with completing a custom ROM install... I thought, why not flash a previous OEM ROM (7.0 NOUGAT) and again, my problem should be over and I could wait until a 9.0 update to see how that goes. So far, any 7.0 stock ROMS I have been able to find/download, have 'failed' install in Odin. (I have standard Odin, patched and Prince Comsey) so I always try them all before I say it's a true fail.
Can anyone help me to understand why, with all the root/roms Ive done, cannot get custom ROM to complete install. I was trying for the CarHD or Batman. after rom flash, something goes wrong and the phone either goes bootloop or failed verify. (BTW, couple X I did flash the no-verify to alleviate that issue but still get bootloop or no new rom boot up)
The other thing I'd love to be able to do right now that 'should' be a piece of cake, (but hasn't been) until I figure out the custom rom install issue, is to ask for anyone that can post a link to a valid ODIN-flashable Stock 7.0 NOUGAT ROM for my S8+ G955F/FD. That would solve everything for now and I'd just disable updates for the interim. As previously mentioned, the couple I have found would only FAIL on Odin flash attempts. Seeing that this is a global, unlocked device, is it possible to flash a stock rom or flash a diff CSC that can get me North America Tmobile setup (my USA provider) I noticed that the global phone has no options to disable LTE or turn wifi calling on/off etc.
I apologize if I have jumped around in my post, not provided enough details or not written very eloquently, but I am happy to provide any other needed info to move forward if any of you have ideas here. I'm just at the end of my rope with this right now.
Any help, input here is much appreciated! TIA! mark~
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
JeffDC said:
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
Click to expand...
Click to collapse
hey jeff, thanks for checking in when the OEM unlock button returns again tomorrow, I'll keep this in mind on my next attempt. i did encounter that fail several times with some OEM firmware flashes (trying to go back to 7.0) and this should resolve that problem. overall though, my real issue seems to be when attempting a root/custom rom instead of a stock replacement... and 'after' i get TWRP completed. I'm doing something wrong with a button hold sequence or something else. maybe need flash 'do not verify' right off too. I'm gonna go extra slow/careful following each step from a great, detailed post for TWRP/ROOT/ROM procedure that i found here over weekend written by 'jesec' what i hate the most is, i only have 1 shot doing this with the oem unlock button, if messed up, have to re-flash a stock rom and wait another 7 days to try this all again.
i still cannot believe its been about 13wks and samsung says they are aware, yet still has not patched this problem. i love my samsungs but im so fed up, i almost ordered a oneplus 6 this weekend just because of this random no ring issue.
thanks much!
Good morning, I've been on the phone for two days now that's crazy ... and everything is clear to touch where I should not surely hehe
I comment a little to see if you can throw me a handle, either to put the phone right or neck.
I had a rom on my cell phone for maybe 4 or 5 months and the only thing that a couple of weeks or so ago every time I went in the car or with the bike when using bluetooth calls failed, so I started looking in internet and I saw that many rom failed in that, because I decided to put another rom. All good, but the same mistake followed and the one that did not vibrate added up. Well now I have been trying to try different but yesterday there is no way, you can see that I made a small brick. After talking for some comments on YouTube, he told me that it could be that he has damaged binary, (I do not know what it is), they told me to download to Android 6.0
The question is yes, I tried a firmware (the only one that I could install with odin, the rest always fails) and I have now the phone that works half, because it still does not vibrate, every time I turn on I have to enter key wifi and some more things , not counting the andorid that I have haha that is outdated.
Testing with Odin to install other firmware now I get on the mobile, secure check fail bootloader. (I understand that it may be that the bootloader is blocked) but I do not know how to unblock it either, I have the developer options enabled with debugging usb and OEM.
I have also tried to install with Odin the TWRP and it comes out that if it has been installed correctly but then I try to get in and out fail and restart.
I have seen that there is a guide here for TWRP but it is for android 7.0 ... so I do not think it's good either.
After this billet ... does anyone give me a hand?
Thank you very much in advance!
PD: I add, right now I have the J710FXXU5BRC3 version but J710FXXS3AQG1 runs too. both with android 6.0
PD2: another mistake, is that when I go to flash it puts: sw rec. check fail. device 5, binary 3