I've been locked out! - Galaxy Note 4 Q&A, Help & Troubleshooting

I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
I bought a refurbished AT&T Galaxy Note 4 (SM-N910A) from eBay that was unlocked so I could use Straight Talk service. I believe it is using 4.4 KitKat but I could be completely wrong. I've had the phone for a year now. I never had to use the lock screen before until today. Reason is is because last time I didn't and I left it around co-workers, I ended up with a few unsightly photos from my 400lbs manager. Hahah. So today, I decided to use the pattern lock and put it on charge as I was outside for about an hour. I came in, was able to take the pattern off. But noticed my swipe option had been greyed. So I put the pin on (using only four numbers). For some reason, I thought it would enable the swipe option. I was obviously wrong. So I went to change it from the pin to the pattern and my pin became unrecognized/incorrect. Thought it was only because of the option settings. So I locked my screen. Obviously an extremely bad idea.
I now cannot get past my screen lock. I have tried getting into it with my computer through USB, it won't connect. Not even trying a Mini SD mounted (won't read on my computer). I have tried ADM, but apparently it has been **** for the "Lock" option for over a year now. I didn't register the phone with Samsung so "FindMyMobile" isn't working. The option to enter my Google account info doesn't show up; even after 35 attempts. No idea how to use ADB. Have read that Windows OS is pretty much impossible to use debugging. Especially with Win10. I have nothing backed up as I never expected/thought this would/could happen.
Of course, like nearly every other person, I just want to save the thousands of photos I have accumulated over the year of having my phone. At least before I have to do a factory reset.
I am a hardcore n00b at going so in depth with phones. So Layman's terms would be extremely appreciated. Or direct links would be great as well.
I believe I have covered as much information as I can think of. If any more info is needed to help figure out this issue, please ask. And thank you to all in advance!

itsjoshwho said:
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
...
Click to expand...
Click to collapse
I am no expert in this matter, but I believe factory reset is one option but you will loose all your data.
(non-root method- safest)
1. Power off
2..Keep holding the power button +volume up+home button together to go into recovery
3. Use volume keys to navigate and select factory reset
4. reboot and you are done
Second option is to root your phone. This will trip knox and your warranty will be void if you still have it
(Root Method)
The method I use to root is :
1. Download TWRP recovery for your mobile(search for your device) from https://twrp.me/devices/samsunggalaxynote4qualcomm.html site and keep it ready on your system
2. dowload super su 2.71 beta and put that into your external sd card using card reader.
3 Put your phone on download mode(power off and restart by holding power button + vol down + home)
4. Open latest version of Odin and connect phone to system via usb cable. Now "COM" in odin should turn blue
5. select tar file in AP section. Make sure repartition and reboot is unchecked just before flashing
6. click start
7.It will run for a few min and say pass when complete.
8.now remove your battery and insert after a few seconds. reboot into recovery by using step 2 in non-root method and you should login to twrp recovery
9.click install button and select super user zip u placed in sd card. flash it (u may have to uncheck signature verification). Now you are rooted!
10. wipe cash and reboot again into recovery
11. download the zip from :http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 (Developed by Dr. Ketan)
12. Install this zip as you installed Super SU and you should be good to go.
There are so many links and step by step guides on how to root your device. You can choose your favorite. This is what I can think of and please don't hold me responsible if you damage or brick your device. Good luck!
Note : It would be better to keep super su and the zip from Dr. Ketan downloaded and moved to external SD card before you flash the recovery

itsjoshwho said:
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
I bought a refurbished AT&T Galaxy Note 4 (SM-N910A) from eBay that was unlocked so I could use Straight Talk service. I believe it is using 4.4 KitKat but I could be completely wrong. I've had the phone for a year now. I never had to use the lock screen before until today. Reason is is because last time I didn't and I left it around co-workers, I ended up with a few unsightly photos from my 400lbs manager. Hahah. So today, I decided to use the pattern lock and put it on charge as I was outside for about an hour. I came in, was able to take the pattern off. But noticed my swipe option had been greyed. So I put the pin on (using only four numbers). For some reason, I thought it would enable the swipe option. I was obviously wrong. So I went to change it from the pin to the pattern and my pin became unrecognized/incorrect. Thought it was only because of the option settings. So I locked my screen. Obviously an extremely bad idea.
I now cannot get past my screen lock. I have tried getting into it with my computer through USB, it won't connect. Not even trying a Mini SD mounted (won't read on my computer). I have tried ADM, but apparently it has been **** for the "Lock" option for over a year now. I didn't register the phone with Samsung so "FindMyMobile" isn't working. The option to enter my Google account info doesn't show up; even after 35 attempts. No idea how to use ADB. Have read that Windows OS is pretty much impossible to use debugging. Especially with Win10. I have nothing backed up as I never expected/thought this would/could happen.
Of course, like nearly every other person, I just want to save the thousands of photos I have accumulated over the year of having my phone. At least before I have to do a factory reset.
I am a hardcore n00b at going so in depth with phones. So Layman's terms would be extremely appreciated. Or direct links would be great as well.
I believe I have covered as much information as I can think of. If any more info is needed to help figure out this issue, please ask. And thank you to all in advance!
Click to expand...
Click to collapse
If it's the reactivation lock then Factory reset will NOT help, it will just make you lose the data and still keeps you locked out.
Only "fix" i know for this is through a service center.
You could try to use ADB to pull the data so you won't lose anything, but i'm not sure if that would work (maybe through the recovery)
Good luck though :good:

Related

S7 SM-G930F Rent-A-Center Lock Workaround

I thought I would post this in case someone else is stuck like I was. I purchased an S7 SM-G930F off ebay and it worked fine for a 45 days until 2 days ago when a Rent-A-Center lock screen popped up and rendered the device unusable. I tried to get it returned through ebay but the seller and ebay both said that the return window closed. Based on web searches this has been in place for a few years on Rent-A-Center acquired devices but I couldn't find anything fixing it for the S7. Long story short I tried everything under the sun to get a firmware on it and every way failed. It seems like anything based on Samsung firmware would trigger it including multiple different builds such as Superman. Others probably know more, but it seems like there is something in Samsung produced firmwares (maybe knox) that checks and trips on the IMEI number causing the lock to trigger.
There are guides and information out there about using Cyanogenmod on an S5 to work around it so I looked through all the firmware available and decided to try the N7 Google Pixel Edition 2.0 here by Angelo27093 since it wasn't based on Samsung Firmware.
That worked! Many Thanks to Angelo27093 and anyone else who worked on that firmware because it turned my 500.00 brick into a usable device.
Steps (I'm a newb so maybe I didn't need all this)
1. Download the Stock firmware of your choice from Sammobile
2. Unzip/unrar it and pull out the BL and CP for bootloader and modem (I used 7Zip)
3. Grab TWRP from here
4. Grab Odin 3.12 here
5. Download the N7 Google Pixel Edition 2.0 ROM here
6. Put the N7 ROM on an SD Card
7. Put the Device in Download Mode (Hold Vol Down, Power, Home)
8. Use Odin to flash TWRP to the device (AP)
9. Reboot into Recovery Mode (Hold Vol Up, Power, Home)
10. In TWRP use Advanced Wipe to Wipe everything except the SD Card. If it fails use Reset Data first, then Wipe
11. Reboot into Download mode from TWRP Reboot menu
12. Use Odin to Flash the BL, CP, and TWRP
13. Reboot into Recovery mode
14. Use Install from the TWRP menu to browse to N7 Google Pixel ROM on the SD Card
15. That's it. Wait for it to boot and setup (might take 5-10 min)
The only other thing I did was grab exchange services and the samsung email client from an APK mirror.
Again, MANY Thanks to all the people that put all this software together. Saved my device!
Just tried this, still doesn't work for me. Followed all the steps. Did the lock come back for you?
1- install twrp
2- boot into recovery
3- Go to Advanced -> Terminal Command -> hit "Select"
4- type these comands
dd if=/dev/zero of=/dev/block/sda11
dd if=/dev/zero of=/dev/block/sda13
5- do a factory reset with the recovery
deshaney said:
1- install twrp
2- boot into recovery
3- Go to Advanced -> Terminal Command -> hit "Select"
4- type these comands
dd if=/dev/zero of=/dev/block/sda11
dd if=/dev/zero of=/dev/block/sda13
5- do a factory reset with the recovery
Click to expand...
Click to collapse
When doing dd if=/dev/zero of=/dev/block/sda11 I get the following error:
Code:
dd: writing 'dev/block/sda11' : No space left on device
Thank you for this!! At our cell-repair place we had a customer have this stuck on their S7 and we could not get it off. We had actually tried this exact thing once before without a few of the steps. Well, we did everything in this order again, including flashing twrp again and typing the code before installing the rom and it worked! Not sure what was different between our two separate tries, but in the end it worked! So thank you!!
deshaney said:
1- install twrp
2- boot into recovery
3- Go to Advanced -> Terminal Command -> hit "Select"
4- type these comands
dd if=/dev/zero of=/dev/block/sda11
dd if=/dev/zero of=/dev/block/sda13
5- do a factory reset with the recovery
Click to expand...
Click to collapse
after do odin flash with G930FXXU1APB6 and all ok
Note 8
I just bought a "unlocked" note 8 and everything was clean when I checked it and everything works and is activated but when I was scrolling though the settings I saw under "knox" there's a Rent-a-center profile with the contact number and everything. So I'm assuming this is going to do the same exact thing. And if it does, will this method work for my phone as well? I've been doing research about what it means and a solution when i stumbled on this post and figured I'd ask some people who are familiar with the issue and might know what to do and not to do. So If anyone has any advice or can help please let me know
mjohnson27401 said:
I thought I would post this in case someone else is stuck like I was. I purchased an S7 SM-G930F off ebay and it worked fine for a 45 days until 2 days ago when a Rent-A-Center lock screen popped up and rendered the device unusable. I tried to get it returned through ebay but the seller and ebay both said that the return window closed. Based on web searches this has been in place for a few years on Rent-A-Center acquired devices but I couldn't find anything fixing it for the S7. Long story short I tried everything under the sun to get a firmware on it and every way failed. It seems like anything based on Samsung firmware would trigger it including multiple different builds such as Superman. Others probably know more, but it seems like there is something in Samsung produced firmwares (maybe knox) that checks and trips on the IMEI number causing the lock to trigger.
There are guides and information out there about using Cyanogenmod on an S5 to work around it so I looked through all the firmware available and decided to try the N7 Google Pixel Edition 2.0 here by Angelo27093 since it wasn't based on Samsung Firmware.
That worked! Many Thanks to Angelo27093 and anyone else who worked on that firmware because it turned my 500.00 brick into a usable device.
Steps (I'm a newb so maybe I didn't need all this)
1. Download the Stock firmware of your choice from Sammobile
2. Unzip/unrar it and pull out the BL and CP for bootloader and modem (I used 7Zip)
3. Grab TWRP from here
4. Grab Odin 3.12 here
5. Download the N7 Google Pixel Edition 2.0 ROM here
6. Put the N7 ROM on an SD Card
7. Put the Device in Download Mode (Hold Vol Down, Power, Home)
8. Use Odin to flash TWRP to the device (AP)
9. Reboot into Recovery Mode (Hold Vol Up, Power, Home)
10. In TWRP use Advanced Wipe to Wipe everything except the SD Card. If it fails use Reset Data first, then Wipe
11. Reboot into Download mode from TWRP Reboot menu
12. Use Odin to Flash the BL, CP, and TWRP
13. Reboot into Recovery mode
14. Use Install from the TWRP menu to browse to N7 Google Pixel ROM on the SD Card
15. That's it. Wait for it to boot and setup (might take 5-10 min)
The only other thing I did was grab exchange services and the samsung email client from an APK mirror.
Again, MANY Thanks to all the people that put all this software together. Saved my device!
Click to expand...
Click to collapse
didn't work for me, model g930f. please helpppp!!! ((
TLDR, follow back to stock procedures for your phone. In this case they have used an exploit to gain system persistence. Without clearing the system and data partitions, the exploit will likely return ("factory restore" only wipes data partition).
Sounds to me like the Rent a Center lock is a legitimate lock by Rent a Center... It seems that whomever you bought your phone from had acquired it from Rent a Center on a "rent to own" or something similar - And they sold you a phone that wasn't theirs to actually sell....In other words it looks - walks & smells like fraud on the part of the person who sold you the phone.
https://www.rentacenter.com/smartphones/shop-smartphones/c/5001
Sent from my SM-G955W ??
magmafire said:
actually i bought a note 8 on ebay after 2 months use my phone was locked too with its was saying rent a center and asking for password
a friend of mine has commented on facebook post for someone who was saying he have sucessfully removed this lock
i did contacted him on his facebook he told me to send picture of the lock i did send it and he said he can unlock it he asked me for 90$ to remove the lock i accept and and paid him via skrill he asked for team viewer the logged to my pc then made the screen black and i do not know what he did then he tell me to do some steps and volla my phone was in download mode for 2 minutes then rebooted and i cant believe the lock was gone
this is the link where i found his post
www . facebook . com/ baselalzoupi/posts/2089441677959653
and this his facebook id page where i contacted him
www . facebook . com/ baselalzoupi
i cant post links because i just registered to make you guys know about it because i spent 1 month searching for solution
remove spaces in the link to make it work
Click to expand...
Click to collapse
Had great experience with this service referred by @magmafire. Basel was very professional, friendly and patient. He is passionate about his work. The price was more than fair for the service he offered. I highly recommend him for anyone's got a rent-a-center locked phone. :good:
shaggyskunk said:
Sounds to me like the Rent a Center lock is a legitimate lock by Rent a Center... It seems that whomever you bought your phone from had acquired it from Rent a Center on a "rent to own" or something similar - And they sold you a phone that wasn't theirs to actually sell....In other words it looks - walks & smells like fraud on the part of the person who sold you the phone.
https://www.rentacenter.com/smartphones/shop-smartphones/c/5001
Sent from my SM-G955W
Click to expand...
Click to collapse
if it really comes down to it rent a center are a bunch of crooks who over charge people 2,500.00 for a 800.00 phone ??? screw rent a center.
Any one here can verify this method works? Seems ever one saying its not working. I bought a s7 other day mint condition for 25 bucks guy said it wouldn't turn on so i got home and charged it and it came on but it has a RAC lock on it. I figure if its ez enough for me to get it off i will try that but if not i will wait till i get another s7 with bad lcd and swap boards. I tried flashed U1 FW and that didnt work.
Flash the engineer bootloader that matches your firmware version. This will give you root she'll access. Then you can use the "dd if" commands to remove rac lock. I've done it on multiple phones.
I have the opportunity to buy a Note 9 from a seller that seems to deal with second-hand stuff (maybe a pawn shop, or they bought a pallet of electronics for resell/repair/etc). I don't think it's some degenerate that just didn't pay their bill and are trying to rip off RAC. It's the unlocked international version (N9600) that can be bootloader unlocked, rooted, etc. I'm familiar with the process of entering download mode, wiping, rebuilding partitions, etc. Would this process work on this phone to permanently remove the RAC lock? I plan to use the phone on Verizon, FWIW.
Now, a note on the legality/honesty of this situation:
I know that there is the possibility of dishonesty here... so it's a little taboo to talk about. RAC locked down the device due to non-payment. However, I hate the idea of the hardware going to waste. The fact is that when someone defrauds a lender (carrier, rent a center, etc)... it sucks, and there's a phone that's locked until it's paid for. However, in most cases, they don't pay for it, and it gets sold on the gray market. I just want this device to be able to be used again. If RAC is the only entity that can *legally* unlock it, then it's just not going to happen. They might want thousands of dollars to pay it off.
Stolen cars are eventually sold at auction, assuming they are in suitable condition. It's the most legitimate end to preventing a running car from going unused.
So... on the honor system... we technically capable people that just want to battle entropy of electronics might be able to remove the lock permanently and save the device from the e-waste heap. That's my goal. And a good deal, of course.
So... Will this work for the N9600? Thanks
KerwinSiwa said:
I totally agree. State courts throughout the US have consistently held that a failure to pay for leased merchandise is civil in nature, and does not rise to the level of theft or other criminal charges. Hence, a person in possession of a Rent-a-Center locked smartphone is not in possession of stolen property. No harm, no foul. Ethically, I can see where Rent-a-Center posits in terms of a loss. Nevertheless, the civil dispute is strictly between Rent-a-Center and the lease signer. That's none of my business. My name's Paul and that's between ya'll; my name's Bennett and I ain't in it. Anyway you get my point. A Rent-a-Center in Tennessee recently sought civil damages against an individual who was charging a fee to remove RAC remote security from RAC smartphones. Rent-a-Center ultimately lost the case (See Rent-a-Center, Inc vs. Jerry Garvey, Jr (Tenn. R. App. P. 81 (Aug 2018)).
By the way these locks are super simple to remove and, on most devices, the remote security protocol can be removed from the device in 15 minutes or less. Rent-a-Center should perhaps look into some better security. Yes, you can do this on the N9600 as well. I can confirm on that model.
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, the item in question already sold to someone else... But now that I'm interested in the topic, I'm also curious. Can RAC blacklist the phone like a carrier could? Could they put the IMEI or MEID on a list of stolen devices and carriers like Verizon or Tmobile could refuse to activate them? Or, do they have no authority to do that? If they could blacklist the device for all carriers, it doesn't matter how simple their security is.
Thanks again
So... Let's say I came across a phone with a RAC lock and did an ESN check. If I got the attached results... What would be the outcome? It's not on the blacklist, but it is on the NCIC list (national crime information center). Would Verizon or any other carrier allow it, or not? I kind of want to ask Verizon directly, but that would be like asking a TSA agent what weapons *are* allowed on a plane.
Any advice?
DrPhant0m said:
So... Let's say I came across a phone with a RAC lock and did an ESN check. If I got the attached results... What would be the outcome? It's not on the blacklist, but it is on the NCIC list (national crime information center). Would Verizon or any other carrier allow it, or not? I kind of want to ask Verizon directly, but that would be like asking a TSA agent what weapons *are* allowed on a plane.
Any advice?
Click to expand...
Click to collapse
ncic is the national database that police use for lost/stolen stuff. carriers generally dont have access to it. but cops do. if a cop runs the imei in ncic it would come back as stolen and you might get in trubble with the law for possing stolen property. however unlike cars or guns the cops only check phones through ncic if something suspicious is happening like phone theft investigation where they have a description of person or vehicle possibly involved

Oneplus 5 stuck on setup?

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.

Boot help Galaxy S7 Edge

Folks I initially tried to root my phone *SM-G935F* using Odin and a CF hero2lte file. The flashing was all good to go with a green pass. Then upon rebooting the phone got stuck on the Samsung logo boot screen with red words at the top that said **Recovery Is Not Seandroid Enforcing**. This being the case all I was able to get into was (Download Mode). I tried to do the samething a few times and gave up after no successful attempts and the phone not being able to successfully reboot.
Fast forward to present I downloaded the phone's firmware which was a zip that contained 4 files (5 total actually because there was another CS file in the event that you wanted to preserve your data etc.). I loaded all of the files in Odin and made an attempt to flash the phone again however it got stuck on *System* and never go to Green *Pass*. So I figured I would try it a couple of more times in case Odin or something just got hung up on the first try. Any how that wasn't the case.
Now with the above being said what did change is when I would try to reboot into *Download Mode* again it said something along the lines of Emergency Smart Switch Recover. I downloaded Smart Switch onto my computer and went through the specific steps to try to Recover the phone using Smart Switch. Now after it was all done I got to the blue screen with the Android and it said *Erasing...* then the phone booted up and its now stuck at the Samsung animation screen. This being said as of current I can now access *Download Mode* and also boot into the black screen or *Recovery Mode* I think its called where I can reboot the phone through a bootloader, power off, factory data wipe / reset, etc etc.
The above being said I have tried the factory reset / wipe. The reboot in bootloader, reboot phone, all with no success.
Also would like to add that before doing all of the above I forgot to tick *USB Debugging* in Developers Mode when the phone was in its normal state. I must also mention that all of this was a first for me and I looked at doing so to try and recover lost data on my phone. Also wanna add that I am not too familiar with ADB or twrp or how to mess with any of that stuff given the limited access I have to my device because it can no longer bootup like it normally would.
I'm currently at a lost of words as to what I can do next as I am out of ideas and could really use some help. I would also be more than happy to donate a little to anyone who is able to help me boot my phone back up and get things back to normal.
Any and all help would be greatly appreciated.
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
Bro would you tell pls , what you did to restore. Thanks
shah22 said:
Bro would you tell pls , what you did to restore. Thanks
Click to expand...
Click to collapse
After me not being successful with the root or with flashing the stock OEM firmware using Odin the phone would get hung up in download mode and the only difference when it would go into download mode it would say to use SmartSwitch Emergency Recover which is what was used and that fixed the issue and the phone rebooted completely fine.
However the above being said I honestly still feel the phone has some small minor issues that I did try to resolve all with no luck. First off when loading to my home screen the icons, and clock, etc etc take about 2 or 3 seconds longer for them to appear on screen than it used like when the phone was new out of the box.
Other thing to note is for some odd reason this issue was thought to be worked out by just booting into recovery mode and doing a factory reset from there, wiping the cache, etc etc. Well this also didn't solve the issue and for some odd reason when performing this the phone didn't reboot on its own.
Basically how it should be normally is after you select that you want to do a factory reset, wipe cache, etc etc, the phone should normally reboot and go through the entire process by itself, however this was not the case. The phone instead went back to the recovery screen and I had to select reboot rather than it normally rebooting on its own.
I've honestly given up on things and given that it is in working order with just a few small minor hiccups I've decided to give the phone to a family member which they plan to use as trade-in credit towards a new Galaxy Note 8.
That being said I will always have a soft spot for the S7 Edge being it was my first smartphone after I had bought a Sony Xperia Z during the same year but returned it the day after because what was to me being poor quality of the Sony phone.
Hmm, looks strange bro , your phone didnt worked after flashing stock rom with odin , and this is the last resort , but you said it was normal before you tried to root , so i guess it was still a software issue other than some hardware problem due to software , but anyways wish you good luck in future , another thing is that my s7 edge has also a very poor build quality , has front camera issues , paint peeling around usb port , wifi issue and high battery degradation , but that happens i guess with today's phones
The version of Odin I used was v3.10.6. I had tried the most current version and a few others, and from the get go for whatever reason this was the only version that would actually pickup the phone being added. Well wait hold on a second the other version would say added when the phone was in but when hitting start nothing would happen, even after waiting an extensive amount of time, also note that the com was highlighted that blue ish color indicating the phone was being recognized by Odin but once again for some odd reason it was only version v3.10.6 that carried out the process of my root attempt and also the attempt I made flashing the original firmware on it.
As for quality the phone had no paint chip or peeling, neither the silver aluminum frame around it either. The build quality was beautiful and up to par with mine. I had a soft spot for my S7 Edge also because it was in the white color which at the time of purchasing was a bit more scarce than the other colors. I purchased the phone from an Amazon.com seller, and during that time I also purchased 2 others from other Amazon sellers but returned those because they had carrier animations for them that were Band LTE or Brand LTE, whatever its called.
This one had no carrier animation upon boot and turned out to be a UK Nougat model. Haven't really seen or came across another one since that would be from a trusted seller or source. Nowadays you never know what you're getting both on eBay and Amazon from these third party sellers.
Yeah thats really strange with odin , its good that you dont have quality issues which struck heavily on me , but yes everyone should be quite careful when ordering online and only should do with trusted resellers
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
vini3237 said:
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
Click to expand...
Click to collapse
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Hydranize said:
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Click to expand...
Click to collapse
Phone is SM-G935FD
I do not know what caused it, I already got the celuar so, in status it says Custom.
I already tried to blink for odin 3 different Stocks and the same thing continues.
When I got it it could not access the recovery mode, only the download mode was accessible, after flashing the Brazilian Stock 6.0.1 I was able to access recovery mode.
The phone turns on, and hangs at boot, Samsung logo, restarts and stays in infinite looping.
Can it be Hardware?
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Hydranize said:
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Click to expand...
Click to collapse
Ok now i think what was the problem , you didnt enabled usb debugging , and for flashing with odin its a must ! , for guys who want to flash firmware using odin .. please enable usb debugging in developer options or you will have much issues and may also brick your phone , so if you dont want to enable usb debugging or developer options , just use samsung smart switch on pc to flash your firmware.
Yeah that was my issue was I had OEM Unlock checked off and one other thing in Developer Options and forgot to enable USB Debugging leaving me stuck in the process when the phone couldn't reboot normally after the flash attempts. But yeah SmartSwitch Emergency Recovery should definitely be able to fix and resolve the issue if the phone can't reboot normally.

S8 Patten lock help PLEASE

Good day
i come to you with a story that many of you might have heard,
Good friend of mine passed away last weekend in a motorbike accident his funeral was today 11/17/2018
His wife asked me today if i can help remove the Patten lock of his phone as she wants to get the photos of the daughters play of the phone
she knows his Patten lock for all of his other phone but this one is different for some reason, because she knows everything the steps i have tried is as followed
1. Samsung account to remotely unlock the device ( S8 was not registered with the account ) only the S4 that was stolen many years ago
2.Google find my device i don't see an option there
3.looked thru all 5 email account including the outlook account nothing there ( We played online together as well)
things i know because i have been at this all day
( I have Googled this ) all my phones are rooted and have a custom recovery
His phone was never Rooted, no custom recovery, i highly doubt he had OEM unlock usb debugging etc
please can someone point me i the right place or help me if its even possible
thanks all for taking the time to read this
PS. The lock Screen does not have a option to use the gmail via recovery, again thank you all
Go into download mode (vol down, bixby and power on at the same time) to check if he really never had OEM unlocked.
It's a worth try it.
If he had, you could easily flash TWRP and recover the files.
If not it's a tough nut to crack.
I will brainstorm a little bit.
T3L3P4TH said:
Go into download mode (vol down, bixby and power on at the same time) to check if he really never had OEM unlocked.
It's a worth try it.
If he had, you could easily flash TWRP and recover the files.
If not it's a tough nut to crack.
I will brainstorm a little bit.
Click to expand...
Click to collapse
Thanks for the quick reply i have done that, OEM is locked
Okay then, we need a different angel of view.
Did you try common numbers out of his life?
Such as birthdates, special events from children/wife, banking pin, something like this?
The other method would be to reflash the firmware via odin, unlock OEM, flash TWRP and then recover the pictures with DiskDigger Root Access.
The problem in this method is, that it isn't guaranteed that it works.
I consider this as the last chance, if everything else fails.
You wrote that you don't have any restore options in pin menu.
Is there anything else that could help or that you can tap?
Any Options or so?
A diagnose from far away is not that accurate of course and really would like to help.

Trying to enable WiFi Calling on my Note 4 N910V

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.

Categories

Resources