Issue since cm11,4.4.4, es manager and usb not recognized - Samsung Galaxy S (4G Model)

My 959V is rooted, had plenty of roms,ect over the last 3 years decided to do Gremlin remover and update it...,
Couple days ago upgraded to the "909" download of CM11,4.4.4, but every site I get it from gives me 908 (even though they all say 909) (last 3 digits of download version). The 908 will not recognize on my Win 7 laptop, but was fine up to now with previous cm11 same phone..
I have used the same cable for the last year for both my Galaxy and 2 Sidekicks phones, data and charging, now the Galaxy only charges, Windows detects but wont recognize, does on the sk4g's
Also (908) will not allow me to paste into sys/media with a " read only issue", although up to now swapped 15 different bootani without problems. Tried 3 different root file managers,same outcome.
Is the driver for the phone firmware windows looks for(on the phone itself) replaceable from sdcard? Im guessing its a bootloader issue and the 908 is the one not to of put on my phone.
Whats the probability I am getting the 909 but the 908 will not allow it to surpass it. Goes through the whole flash and on reboot I have to reenter emails,playstore apps,ect, but on 908 still in settings.
I can/ have been able to swap 1 rom via twrp and sdcard on 908 ( to slimkat4.4.4 and back to 909, but comes up 908) any other roms error before flash(and slimkat does not recognize on usb either).
is it a Kernel fix, and can it be flashed via sdcard? Bootloader via sdcard? Bad usb port? Does charge, and the drivers/ cable verified.
Thank you for any help, been 3 days now, redone my laptops (2) from scratch, everything ,c++,java,netframework,samsung,zadig 2.0, and more.

DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.

FBis251 said:
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
Click to expand...
Click to collapse
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.

Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
I didnt do a backup, if thats an issue , can I backup 2nd motherboard and apply to the first?

Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?

FBis251 said:
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
Click to expand...
Click to collapse
O.K., so Ive been playing with the second mobo just to test different angles.
1) E.S. File manager is the culprit, swapped out for a paid app Ive used with Sidekick 4g, Root Explorer, and boot ani. goes fine, on both mobos.
2) The latest gapps (cm 11 w/ gaps 4.4.x) was giving me a "Google servers cannot be reached" error on both mobos, used the gapps for cm 10.1 (jb 4.3) and all is working, both mobos.
3) Was reading that possibly the adb driver is in the kernel, and thats what windows is looking for? Ive tried but can only sd card flash at this point so, giving up. I can bluetooth,wifi share or email files to myself if need be. Im guessing its a hardware issue beings that the 2nd mobo was reflashed identical to to the first. (with exception of one click 2.3.6,and w/a twist oc/uv on the 2nd),1st one will not downgrade at all below 4.4.4 by sd, I was trying to ics a rom guessing the foundation might overwrite any missing stuff then upgrade back to 4.4.4.
One post mentioned that the mtd/bml cross flash is a no-no, could that mess up usb driver identity on the phones side?
Not a big deal, both phones/ roms are working great and have no issues (except 1 doesnt connect to a computer for file transfer). Thank you for your help.
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Also, the phone was working fine up to about a month ago, it was recognized by the computer, only difference I made was trying apps, off playstore, five fingers for ebay,different weather apps for widgets,silver/gold prices apps. Thats when it started not recognizing.

I was getting the same error about the google servers, then I tried a earlier version of gapps. Connects now.

Floridasun said:
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Click to expand...
Click to collapse
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
As far as the phone itself goes, the phone should be recognized even if there is no driver for it installed on your computer. You can use this software to verify that
http://www.nirsoft.net/utils/usb_devices_view.html
I don't believe you can even edit anything on the phone to make the USB device not be recognized when plugged in short of bricking your phone, so if there isn't even a USB connection being made, as I mentioned before, it looks like a hardware issue is causing your problems.
In that case, it'll be hard to flash anything without going through a lot of hassle since all the reliable recovery methods we have need that you are able to use your USB port on the phone.
EDIT
If you do still have TWRP available on the phone, flashing any ROM will reflash a kernel, but be careful because the recovery is tied to the kernel and some ROMs have a non-working recovery, so if you happen to flash some of these you'll be stuck with a nice paperweight . The latest CM11 I have posted does have a working kernel/recovery but I still don't think it'll fix your issue.

FBis251 said:
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
Click to expand...
Click to collapse
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.

bhundven said:
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
Click to expand...
Click to collapse
I still use two of them. Great little phones really. I see no need or use for 5.0 I think running this CM11 from you guys is about the end of the road for these phones. A great ride indeed. Ill be sticking around regardless just to see what happens. Thanks guys☺

Related

Recovery problems.

Hi there, I'm not feeling very cluey right now.
I finally got around to trying a custom ROM, I went with the latest one @daniel_hk had uploaded which was Slim-p6810-4.4.4.build.7.2.1-UNOFFICIAL-20140816-1116.
I used the cwm-6.0.2.3-p6810.tar recovery.
I had been using the official ICS ROM from a long time ago, it mostly worked fine for me but an app I've started using recently says it really wants a newer version of android.
Before flashing it I took a backup.
Having used the SlimKat for a bit I found a few things I wanted to work didn't and the colour inversion thing was getting to me so I tried CARBON-KK-UNOFFICIAL-20140912-1616-p6810 to see if it would work well enough for me. It has the same Bluetooth problem but I haven't had the screen inversion problem.
Before trying the second custom ROM I also took a backup. I also took a backup after setting up the Carbon ROM so I wouldn't have to do it twice!
Somewhere around here I noticed that my Winblows 7 PC wasn't recognising the tablet anymore, it also was charging slower than it used to.
Wanting to go back to the ICS ROM I was using originally I booted into recovery and went to restore it and here's the problem.
It isn't there to restore.
The other two backups I made are there though.
I was going back to ICS to see if Winblows would detect it again, although I'm starting to suspect that the USB board in the tablet might be faulty now. Windows says that the device has malfunctioned so it doesn't recognise it, I've tried numerous different versions of the USB driver. I remember Winblows update saying it had a newer version of the Samsung Android drivers and let it update them, this may have been a mistake.
So how do I restore my ICS backup, I think I recall there being a file system change when they added the multiple accounts on a device patch, 4.3 I think, so is that part of my problem?
I've also tried using twrp-2.8.0.0 and discovered that it can't use the CWM backups and I then flashed cwm-6.0.4.5 to see if the newest version would help me. Still no dice. As my tablet won't talk to my PC I flashed that with Mobile Odin Pro, I'd avoided buying that as I will probably be getting a Sony Z3 Compact Tablet and Odin seems to be a Samsung only thing.

[Q] Urgent help needed please!

I was trying to update to the newest version of MIUI, decided to do a clean install as I have been having some problems lately.
So wiped the phone in BMM recovery and installed the zip for MIUI and GAPPs, but then my BMM removed itself (it did tell me it was doing this, but following the instructions to get it to stay didn't work, and it didn't say why it was doing this).
So now I am stuck with stock recovery, I still have the zips for MIUI and GAPPs on the sd card, but no ROM installed. Without the ROM installed I can't boot to install custom recovery, and without custom recovery I can't install the ROM, so I am kind of stuck here.
Is there a way to install either a custom ROM or recovery from the stock recovery? It doesn't have to be BMM, I originally had that as I was trying different ROMs, but I have decided to stick with MIUI now.
Thanks in advance for any help.
I guess maybe I should look for the stock rom, install that, then install custom recovery and ROM. I will look for that in the meantime while I await any better answers
I have tried flashing a current stock rom from a different country, and also an older version from my country (can't find the current one anywhere), on both was the same result, cannot verify signature.
I am all out of ideas now, is there anything I can do, or is it time to bin the phone?
Final update, have tried various things throughout the day, finally found a way of getting stock rom on that looked like it was going to work, but now my battery is dead, so I guess thats that.
obsidianwings said:
Final update, have tried various things throughout the day, finally found a way of getting stock rom on that looked like it was going to work, but now my battery is dead, so I guess thats that.
Click to expand...
Click to collapse
Don't worry, it's not the end. Cannot verify signature also happens when your battery life is below the safety margin of flashing.
On this phone a working OS is required to charge it, going below the 30% battery flashing requirement is something a lot of people have run into. Including me, with my mothers's phone. You can get it working again, if you have a spare a usb cable.
I had to charge it manually, the only disadvantage is it doesn't stop charging if it reaches max with this method. Therefore you should only charge it for an hr max at a time.
Method 1: Charge the battery manually without an os (warning, you'll have to destroy a usb cable and need celotape)
-Take the battery out of the phone, we're going to charge this manually.
-Cut a usb coord at the other end of where you'd plug it into a pc. (the usb female or microusb side) I used a small usb extension coord.
-Strip back the wire so you have about a centimeter of exposed wire on the red and black wires. If you have any other additional wires/exposed wire, ignore them, you can lookup what these wires are for if you're interested.
-Celotape the exposed red wire to the + shown on the battery and the black exposed wire to the - shown on the battery. Just make sure these two don't touch, it's easy enough by twisting the exposed wire to make it stick together.
-Wait 1 hr.
-Detach the charging wires and put in phone, push the stock firmware through "RSD Lite" with the firmware file named "6.7.2_EDEM-18-SEARET_cfc.xml", or any other, this is a jellybean release.
-Have another go to flash, just by making sure you start with 100% battery life.
Method 2: Make a Motorola factory cable, (warning, you'll have to destroy a micro usb to usb cable)
-For some reason many Motorola phone's power routing is controlled by the OS, without a working one installed, it cannot charge. However, the device was required to be flashed without a battery at the factory, this exploits that method and lets you power your phone through the coord to fix it.
-Cut the usb coord in half, separate the wires, and make the #1 wire attach to the #4 wire in a micro usb arrangement image. As I don't have 10 posts, I can't post links.
-I advise you to use the first method, and this as a last means for various reasons. Plus you can reuse the first method for other things in the future.
obsidianwings said:
I was trying to update to the newest version of MIUI, decided to do a clean install as I have been having some problems lately.
So wiped the phone in BMM recovery and installed the zip for MIUI and GAPPs, but then my BMM removed itself (it did tell me it was doing this, but following the instructions to get it to stay didn't work, and it didn't say why it was doing this).
So now I am stuck with stock recovery, I still have the zips for MIUI and GAPPs on the sd card, but no ROM installed. Without the ROM installed I can't boot to install custom recovery, and without custom recovery I can't install the ROM, so I am kind of stuck here.
Is there a way to install either a custom ROM or recovery from the stock recovery? It doesn't have to be BMM, I originally had that as I was trying different ROMs, but I have decided to stick with MIUI now.
Thanks in advance for any help.
Click to expand...
Click to collapse
First of all, you're not supposed to flash GApps with MIUI. Bad combination.
Second, if you notice the "Removal of BMM" after the ROM installation is over, you have to reboot, go to recovery, system keeper, and press Install BMM.
Anyways, your only solution may be to flash an SBF in fastboot using a fastboot cable, or to see if you could boot up the phone somehow or get it in ADB.
Good luck!
I know I am very late responding, but just wanted to say thanks to everyone for trying to help. By the time these posts were posted I had thrown my phone away, so didn't come on here for quite a while, hence not seeing the replies till now.
I did actually try manually charging the battery as I found the instructions on google, but unfortunately it didn't work. I didn't come across the factory cable idea though, that's interesting.
I had no idea you weren't supposed to install gapps with MIUI, I had had it working for a long time like that. I had thought it said that in the original thread where I got the MIUI rom from, but maybe I was just installing gapps out of habit. Thanks for that though, as I might get MIUI in the future.
As far as pressing "install BMM" in the recovery goes, I did that several times (that's what I meant by following the instructions to get it to stay in OP) but it just wouldn't stick. I figured there was only so long I could sit in recovery wasting battery trying to get BMM to stick so thought I would go ahead and reboot and work on trying to fix things from there
Anyway I appreciate you both trying to help, but I ended up throwing the phone away the day or two after my last post so I didn't see these till now when I logged on to talk about the new phone I just got.
I just went and took a look at the MIUI for atrix 2 thread, and it does say that you can optionally install gapps, so I guess that's why I did.

(J700F) any ROM installed does not boot

Every time I install a rom, the device does not want to boot up. It loads the Samsung J7 logo, then goes black. Waiting for a long time does not work. I've waited for an hour to no avail. I have tried Alpha Centauri, Nameless 3.5, SyneXOS and all do not boot up. The aroma installer loads up correctly in TWRP. I have tried downgrading TWRP, wiping phone clean before installs, different downloads, and even reflashing stock FW and reinstalling TWRP. my phone's baseband version is J700FXXU4AQD1, just in case someone asks for it. I have yet to find out a way to get a log of the system while booting, as it may help uncover why so. To my knowledge, this phone may be SIM locked, but I have yet to confirm. Feel free to ask for any more necessary info. Thanks! <3
I have the same model fon and all those roms boot for me.
Maybe use a fresh flash disk - only ROM zip no other files / folders, and do a FULL wipe before flashing.
As usual keep a backup of EFS and Radio folders.
Latest TWRP is best. Battery > 90%
Sent from my SM-J700F using Tapatalk
Battery dead? Or too weak to get beyond splash?
I did something awhile back (phone was unrooted and 100% stock) and it refused to charge or to boot beyond Samsung splash screen, and of course the battery was drained, so ZERO way to get phone to turn on as it'd instantly shut down. Happened after doing a win7 windows optional update adding Samsung usb drivers or something. Phone was charging via usb I sometimes have connected to the PC, hence windows update detected the phone and suggest the driver. I don't know exactly what wrong, but it'd loop constantly when trying to charge. Pulling the battery and reinserting fixed it.
Also, fwiw, I just had to do a factory firmware reinstall on a rooted J7 after mistakenly turning off the developer options. It was fully locked, including recovery. I used the giant 1.4gb zip from Samsung (had to join the SamMobile BS to get the file) that ballooned to 2.5gb unpacked, that was exactly for my phone. After flashing that with most recent Odin, phone is back to it's pre-rooted state, replete with bloatware. But all files (pics, etc.) are still there. Maybe try that if battery isn't at fault?
Yes, I too have experienced that stupid "non charging" charging on the usb port.
@aMega329 make sure your fon is not connected to a pc / laptop as you flash ?
Sent from my SM-J700F using Tapatalk
Ok. thank you for the tips. I am now going to try flashing the rom now. I will update soon.
UPDATE: nope. no avail. Fully wiped, battery at 95% at start of flash. Not plugged in to a charger nor a PC. Formatted data partition after flash. Reflashed 2 times. Guess i'm SOL for custom roms. :'( Stock works tho.
Hmmm ..... , I thought just wiping the data partition is enough. Why are you formatting?
I don't format ever!
---------- Post added at 03:53 PM ---------- Previous post was at 03:44 PM ----------
Are you sure J700FXXU4AQD1 is marshmallow 6.01? https://shell.boxwares.com/Download.aspx?L=1250
You need to be on MM first before installing these roms.
I'm on 5.1.1... hmm. I'll try updating f/w to 6.0.1 first then doing everything again. Thank you for the idea though. I'll get back soon after i flashed 6.0.1. Man, it'll take forever to download that.
www.updato.com is your friend for speedy firmware downloads.
Sent from my SM-C900F using Tapatalk
Okay. So guys, I finally got Alpha Centauri to boot. What I did was i downloaded a MM firmware for a J700F in another country, then flashed twrp and the ROM. Thank you guys. I guess our telcos just suck for delivering OTA's to our devices.
For people who have this problem, make sure you are on MM firmware first. If you can't find MM firmware for your device, such as my case, just use firmware from another version. It works for me, but if you doubt it, it's worth giving it a shot. I used J700FXXU4BQI2. Luckily, my Wifi, BT, and mobile data still work nicely.
Congs!

USB issues - charging/audio/pc link

Hey guys,
Not sure when this started, but it wasn't like this out of the box...
At some point via an OTA update, I lost fast charge, I lost stereo sound from the USB c port (only plays left channel) and I can't connect my phone to a computer (yes, drivers etc are all in tact.. it's a software issue with USB on the phones ROM)
I managed to update via OTA to miui10 8.8.4 device ROM after a few tried (had to wipe).. issue still persists.
I've seen a few people mention this issue, but most responses are suggesting hardware replacement. I know for a fact the hardware is unaltered and was fine prior to update.
Anyone know a fix for this? It literally takes 8 hours to charge my phone ATM. Given I can't connect via USB, I can't unlock my phone and go custom ROM (I'm kinda liking miui 10 also)...
Any options asides from waiting for an OTA uodate?
Thanks
Bump!
Still have this issue. Anyone else?
I'm now on MIUI 10 (8.9.20) and problem still exists. Driving me crazy. My mi6 charges in no time at all. This mix 2s takes forever
leighaus said:
Hey guys,
Not sure when this started, but it wasn't like this out of the box...
At some point via an OTA update, I lost fast charge, I lost stereo sound from the USB c port (only plays left channel) and I can't connect my phone to a computer (yes, drivers etc are all in tact.. it's a software issue with USB on the phones ROM)
I managed to update via OTA to miui10 8.8.4 device ROM after a few tried (had to wipe).. issue still persists.
I've seen a few people mention this issue, but most responses are suggesting hardware replacement. I know for a fact the hardware is unaltered and was fine prior to update.
Anyone know a fix for this? It literally takes 8 hours to charge my phone ATM. Given I can't connect via USB, I can't unlock my phone and go custom ROM (I'm kinda liking miui 10 also)...
Any options asides from waiting for an OTA uodate?
Thanks
Click to expand...
Click to collapse
Sounds bad. Some people also have problems with the front camera wich stopped working after an OTA Update.
Have you tried Clean flash a custom rom?
I cant flash custom rom, as i cant unlock bootloader - usb is not detecting. I am literally stuck on stock beta until it is fixed.
Yea sry i kinda failed to notice this point
Would it then be posible to flash a Recovery ZIP of an older Version of MIUI via the official MIUI updater app?.
Ps.. I dont have the Phone myself just trying to bring some ideas in.
leighaus said:
I cant flash custom rom, as i cant unlock bootloader - usb is not detecting. I am literally stuck on stock beta until it is fixed.
Click to expand...
Click to collapse
Maybe you need to change a cable.
I have about 4 official cables abd 4 non official. Makes no difference. My mi6 still works as expected with the same cables.
It is a rom based problem.
Still not fixed . Absolutely ridiculous.i actually hate this phone because of this stupid software issue

differents problems with my j7...

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

Categories

Resources