Related
I am using a Macbook Pro to connect to my AT&T GS4. It is originally NC1. I have flashed GPE 4.4.4 with Safestrap.
Everything works brilliantly except for the one thing that hardly ever worked before I even changed anything on my GS4 - connecting it to my Mac.
AFT is the biggest crock of ****, it literally never works. I was forced to use Kies on my Mac, since AFT doesn't work, ever.
Ever since I flashed GPE the phone connects to my Mac as a Media Device, but in Kies it just stays on "Connecting..." forever.
I am using the USB cable from Samsung. AFT says "Could not connect to device", but AFT didn't even work when it was stock, and Kies did.
Does anyone know how to fix this issue?
Is anyone able to explain why my phone isn't connecting properly?
Is it because I flashed GPE 4.4.4?
tarend said:
I am using a Macbook Pro to connect to my AT&T GS4. It is originally NC1. I have flashed GPE 4.4.4 with Safestrap.
Everything works brilliantly except for the one thing that hardly ever worked before I even changed anything on my GS4 - connecting it to my Mac.
AFT is the biggest crock of ****, it literally never works. I was forced to use Kies on my Mac, since AFT doesn't work, ever.
Ever since I flashed GPE the phone connects to my Mac as a Media Device, but in Kies it just stays on "Connecting..." forever.
I am using the USB cable from Samsung. AFT says "Could not connect to device", but AFT didn't even work when it was stock, and Kies did.
Does anyone know how to fix this issue?
Is anyone able to explain why my phone isn't connecting properly?
Is it because I flashed GPE 4.4.4?
Click to expand...
Click to collapse
All the GPE Roms have it in their OP that USB mount doesnt work.
So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.
here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"
My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk
EDIT: Solution was to sit with OP5 technician which flashed my ROM to Oxygen 4.5.1. After this didn't do it, I RMA-ed it and got a new OP5.
EDIT: TL;DR: After updating OP5 to 4.5.5, It doesn't recognizes sim nor wifi, and can't rollback to 4.5.3 that did and stuck on phone setup (needs wifi). ADB devices is empty, I have Google USB Driver from SDK, Windows 10
Hello,
I just got a new OP5 today.
Opened it in the store, came with Oxygen 4.5.3 outta the box.
I putted the sim in, and I connected to the store's wifi, all was good and even had a phone call to my mother to check if the mic and speaker are working well.
Then when I got home, I upgraded the OS to 4.5.5 through the settings, where Android suggested. I'm new to OP and android (moved from iphone 5) and so if there is a right way to do it, and that's not it, I wouldn't have known.
Then, OP5 didn't recognize the sim anymore and couldn't start the wifi (switching it on wouldn't work, it would do nothing), so I tried Factory reset. Unfortunately it didn't reset the OS as well and now I'm stuck outside can't use my sim card or connect to my home wifi to setup the device.
Tried installing OP5 usb drivers (show when connecting the OP5 to PC) and press the power button and lower speaker volume together, then flush the 4.5.3 OS through USB, but it doesn't recognize ZIP folder and when I tried to unzip and send boot image (cmd->"adb sideload boot.img) it started and then failed at 0%.
Please help, the phone right now is unusable.
Tried the Factory reset through settings, but it took so long I thought it was stuck, so I did it through recovery screen.
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
ultramag69 said:
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
Click to expand...
Click to collapse
Why should it be replaced in less than a week? Also, isn't there a fix for adb problem so I could flash 4.3.5? Maybe a remote takeover?
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
ultramag69 said:
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
Click to expand...
Click to collapse
I can't pass the "Connect to Wifi" in the initial setup of the android, as it finds no wifi networks (but of course there are, when I use the sim in my iphone it works properly and there are wifi networks). So I don't know how can I get the IMEI number.
Right now my PC recognizes the OP5 connected via USB, but "adb devices" bring back empty list.
I think that once I get that working, I could unlock the bootloader. But I can't seem to be able to enable dev mode in settings - I can't get there.
I can only get to the recovery screen beyond the initial steps of setting up android.
Right now there is no important data on the phone and I have my laptop which is virgin to ADBs and Drivers (didn't use it to try to resolve it).
What driver and where do I get the right ADB so I could load 4.5.3 from usb to the phone?
When you upgraded, did you wipe cache and dalvik?
Binary Assault said:
When you upgraded, did you wipe cache and dalvik?
Click to expand...
Click to collapse
Wiped after the upgrade whem problems started
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
ultramag69 said:
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
Click to expand...
Click to collapse
It doesn't seem like I can skip it. Can't pull down a menu or anything
I guess only Oneplus can help me now?
Do you have any suggestion on fixing adb so it would recognize the OP5?
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
ultramag69 said:
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
Click to expand...
Click to collapse
Welp it is a pickle.
Going to go live chat with OP "level 2" representative.
See if they wipe the phone out and restore an older ROM.
If that't not going to work, RMA it is :/
Shame. A new phone. Took only one picture with my dad when we opened it back at the store. nothing else.
Unfortunately bad things can happen... You just got to be the one who got the dud this time round.....
Here's hoping it's the last time....
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
OcazPrime said:
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
Click to expand...
Click to collapse
When I connect the OP5 to the PC there are no folders under it (Computer -> OP A500 -> no folders), but I'll try and give it a shot. see what happens. Will update this reply.
Update:
After Oneplus flashed Oxygen 4.5.1 on the phone and some other magic I was able to skip wifi step on setup, yet still when I try to activate it it won't budge. the slider won't move and it looks as the page is being refreshed. Also, when I try to get into sim section in settings it would just freeze and alert the program stopped and suggest to close or wait.
Oneplus says it is hardware issue, and the fact it happened when I upgraded to 4.5.5 from settings menus is coincidence. They say I need RMA it.
If anyone knows how to fix it then I'm more than welcome to hear it.
EDIT: it also won't shut off unless I long press the power button.
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Modify_inc said:
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Click to expand...
Click to collapse
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
kevintm78 said:
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
Click to expand...
Click to collapse
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Modify_inc said:
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Click to expand...
Click to collapse
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
1. Power down, pull the battery for 3 seconds, then boot into Download Mode
2. Using Odin, flash the BPA1\CPD1 hybrid firmware
3. Once that's done flashing reboot to recovery and factory reset. Then reboot and let that firmware install
4. Once you've gotten past all the setup part you'll want to power off again and boot to download mode again
5. Using Odin, flash the CQI2 aboot and then reboot. From this point on the process is the same as before.
6. Enable developer options, turn on USB debugging and turn on "allow unknown sources" in the security settings.
7. At this point, you'll want to have your spare SD card in and go ahead and open a command window from the same location that you have the samsung_unlock_n4-fix file in. In my case it was in my download folder and the easiest way to do that is to open that window, hold down the shift button, then right click. You should see an option that says "open command window here" then click that to open.
8. Once you open the terminal enter this command: adb devices
9. Then this command: adb push samsung_unlock_n4-fix /data/local/tmp/
10. Then install kingroot and let it start rooting. Be sure to keep the terminal open and your phone connected.
11. Once kingroot starts the rooting process do not let the phone go to sleep. Just keep a finger on the screen.
12. When kingroot gets past 50 -60 percent, enter this command in the terminal: adb shell
13. If you enter adb shell and it gives an error or says your offline, just unplug the Usb from your phone and plug it right back in. Then enter the adb shell command
14. As soon as kingroot says you're rooted, enter this command in the terminal: su (You have to grant root permission on the phone and continue)
15. Then this command: cd /data/local/tmp/
16. Then this command: chmod 777 samsung_unlock_n4-fix
17. Then this command: ./samsung_unlock_n4-fix
18. Once the scripts starts it will ask you if you want to continue, just type out: yes
Then it will do it's thing, back up your bootloader, and then power your phone down when it's done.
19. Once powered down, PULL OUT YOUR SD CARD, and boot back into Download Mode
20. Using Odin, flash Twrp and immediately boot into recovery when Odin reboots your phone.
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
Click to expand...
Click to collapse
Thanks for all your help, I finally got around to upgrading it. Everything went smooth and I am finally running MM 6.0.1 but unfortunately, I still can't find the feature for Wi-Fi Calling. I do now have a Advanced Calling option under Settings, which I believe you must have to use WiFi Calling, but I can't find the WiFi Calling anywhere to enable it. I must say, I'm really disappointed, yet still proud of myself that I didn't brick my phone in the upgrade process.
So, any suggestions as to why I can't find WiFi Calling on MM 6.0.1?
So no one has any ideas why I would still not have the wifi calling after installing the 6.0.1 MM? Is there a security or other update that I now need to install to get this feature? I installed the Jasmine v6 rom, if that makes any difference. Is there a way I can install 7.0 Nougat on this device, and would it likely provide the wifi calling feature or likely be a waste of time and effort?
I'm using Safelink with my Verizon phone, but they are no help, though they do say they support wifi calling as long as I can enable it on the phone. Is it possible Verizon could tell me what I need even though I don't have service with them but do use their towers?
Sorry for so many questions, I just really need wifi calling and can't understand why I don't have the option for it using 6.0.1.
I found an app named WiFi Calling while browsing through my phone directory. It looks like a system file, so shouldn't that mean the phone should have it? Is my Jasmine ROM keeping it from working or is it likely something else?
I'm now using Jasmine v7, if that makes any difference.
Help! Now my wife has no phone
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
Click to expand...
Click to collapse
I tried to do the same for my wife since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
I made a complete backup using TWRP before attempting this upgrade. So, can I just restore it or are there other steps I need to perform before I attempt to revert back?
Did you ever get this resolved? I have been having an issue since mid-July where my phone does not send or receive texts or calls within half a mile radius of my office but otherwise works great everywhere else. I don't have to be in the building...I can be standing in the parking lot, parked at a nearby building/area, or driving down the street in vicinity of the area and nothing. When I try to send a text, I get a message stating there's no service. When I try to call, the phone goes from 4G with four bars to 4G with zero bars and is stuck on "dialing". When I end the call, it goes back up to four bars.
I have tried contacting Verizon many times and they tell me I need to enable WiFi calling but I don't have the Advanced Calling option in my settings. I am also running 5.1.1 on a rooted SM-N910V. Today when I spoke to them, they told me that even though my phone shows 4G, I really only had 1G service. I find this explanation ridiculous because if this was the case, I would have problems in other areas too and not just in the middle of the 8th largest urbanized area in Louisiana (while elsewhere in the same urbanized area, the phone works great). They told me I needed to do a system update which will cause me to lose root.
So I go to schools and help them with IT issues, I noticed they had some tablets sitting there and I asked what was wrong with them and said they were locked and no one knows the code.
SM-P550 - there is account that was signed in with, I have gone to Google admin and noticed there are other 10 of the same type against that account, but has not checked in over a 1000 days as they cant use them.
I can't turn them off, only restat, I can't get to recovery menu, only thing I can go and do is press the power, volume down and home button to get to the screen and it says downloading, and seems to be suck there as nothing ever happens.
I have downloaded all the tools, Odin, Officaial firmware, Samsung USB drivers but nothing comes up on my computer.
Does anyone have any thoughs on fixing this, seems like a waste having these devices just sitting there,
I have tried all the passwords I can get of, nothing.
Thanks
Load a Linux distro and try
Bash:
heimdall detect
If heimdall can detect it, you can use heimdall to flash TWRP and then you can download stock or my ROM (my ROM has no S-pen support).
xdesdx said:
So I go to schools and help them with IT issues, I noticed they had some tablets sitting there and I asked what was wrong with them and said they were locked and no one knows the code.
SM-P550 - there is account that was signed in with, I have gone to Google admin and noticed there are other 10 of the same type against that account, but has not checked in over a 1000 days as they cant use them.
I can't turn them off, only restat, I can't get to recovery menu, only thing I can go and do is press the power, volume down and home button to get to the screen and it says downloading, and seems to be suck there as nothing ever happens.
I have downloaded all the tools, Odin, Officaial firmware, Samsung USB drivers but nothing comes up on my computer.
Does anyone have any thoughs on fixing this, seems like a waste having these devices just sitting there,
I have tried all the passwords I can get of, nothing.
Thanks
Click to expand...
Click to collapse
If they are locked by a Google Account, there is a possibility that, depending on what version of Android is installed, that the FRP lock can be bypassed. Typically, anything later than Android 6, you'd have to send them to Samsung tech support to have the lock removed.
retiredtab said:
Load a Linux distro and try
Bash:
heimdall detect
If heimdall can detect it, you can use heimdall to flash TWRP and then you can download stock or my ROM (my ROM has no S-pen support).
Click to expand...
Click to collapse
Hi can you provide me the link that you used. I have tried using it and doesnt work for me. Went to Heimdall website and followed some videos
Update, the USB cable I was trying was crap so I change to a better quailty Odin can see my device, I have installed the fireware for that device but the old account stays there, so it has not been removed.
xdesdx said:
Update, the USB cable I was trying was crap so I change to a better quailty Odin can see my device, I have installed the fireware for that device but the old account stays there, so it has not been removed.
Click to expand...
Click to collapse
What version of Android did you install? I see that the last version for that device was 7.1, which won't work. But if you can find and flash a early 6 version, I may be able to help. Try Sammobile.
edit: Read this link.
Sorted, so I put the original firmware back on and the account was still there, then I put the combination firmware on, which worked and I removed and reset the tablet. Than I put the original firrware back on. Boom done plus odin needed a high quality cable.
Thanks all