So after I got my device activated I was able to make a call and text. After about a minute the phone reboots and goes back to not being able to call or text. So I know how to get my phone activated but not able to keep it activated without it rebooting. Any suggestions?
Used Method Below.
Enable the three packages disabled in step 1. Go into the phone dialer and type in ##72786# and your phone should reboot and begin the activation process. After the 5th retry, it will manually activate itself. It should say "writing to device". Don't click done yet. Press the home button and disable the three packages once again. Reboot.
Alternatively, after renabling the three packages and dialing ##72786#, you can go into Settings>Activate this device and manually try to activate it yourself. It still must say "writing to device". Don't click done. Disable the packages once again. Reboot. Voice and LTE should stick.
Hi there,
Sorry I didn't understand too well what exactly your device do, but maybe experts who own this device do. Please wait an answer after move to the correct forum.
Good luck
Related
So, dumb self made a pattern that I don't remember. So my Vibrant is at the Too Many Pattern Attempts screen. I've tried to wipe the phone using vol up and down plus power but that doesn't remove the too many attempts screen at all. The only gmail account that I hooked up to my phone keeps telling me that something is incorrect yet I can log in to my gmail fine from my computer... What can I do? I tried to do Odin, but vol down plus power does nothing on my phone. It just continuously power cycles... When I boot into the recovery screen I can use Odin but it just hangs at checking files... Any suggestions?
Do you have coverage? Maybe the Google verification can't connect. It always worked on my myTouch and once on the Vibrant.
Sent from my Samsung Vibrant using the XDA app
Tmobile Galaxy S pattern locked out, can't root
I just bought my first Android device, the Samsung Galaxy S from Tmobile from the US (I live in China) last week. I have only used it a few days and my girlfriend thought the pattern lock would be a fun game to play. Result - locked out. I have the same problems as in the below thread:
http://code.google.com/p/android/issues/detail?id=4784
I tried the receive a phone call then hammer the home key; emergency call and go to search and many of these type fixes; however none have gotten me through. It seems they fixed the security problem here but didn't fix the username password problem as I'm sure the credentials I entered are correct and I have data service.
After giving up on these methods I tried doing a hard reset. BTW, on this model you must hold down volume up AND down buttons at the same time, then press the power button to get the reset screen.
I have cleared user data etc, but when I try to reset the phone I get the error message "setup.zip not found".
I understand that I now need to root the phone, so I tried the method explained here but without having access to the phone I need to load this setup.zip file on the SD (not the one with Avatar).
http://samsungvibranthacks.com/samsung-vibrant-hacks/how-to-root-samsung-vibrant-galaxy-s/
I already installed Kies (has Outlook sync functionality!) on my desktop so that I can access the internal memory as an external drive. However the phone's USB mode must be set to (it will prompt whenever I connect) to Kies mode. However since I am locked out of the phone I can't tell the phone to get into Kies mode, therefore cannot access the internal memory, therefore cannot load setup.zip, therefore cannot root, therefore cannot get past the pattern lock screen = useless phone.
I need to root the phone anyway so I can load a few Asian IME's that didn't come with the phone so don't mind playing with this, but since I'm new to Android it may be a while before I can get through since most root instructions either require access to the internal memory via my computer or access to the phone (past the pattern lock).
If I offer to make a paypal donation could I summon the help of one of the more experienced Android gods that frequent this forum that can help me get through this?
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Genesis1791 said:
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Click to expand...
Click to collapse
On one or two tries, when the device was attached to my laptop I got a yellow on black downloading screen but had no idea what it meant. How does this help me root it? In general the volume down+plus power button didn't do anything but reboot it.
I just downloaded the SDK last night for the last time and haven't succeeded in installing it so have still got a bit of learning to go before I can make it useful.
I have the phone back in my hand now so adding some details:
Holding volume up and down and the same time, then pressing powere gets me to the "Android system recover <2e>" screen with four options:
Reboot system now
reinstall packagages
delete all user data
delete cache data
I've tried all and none will get me out of the username/password screen after reboot. If I select "reinstall packages" it says:
E:can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
Hey guys,
I flashed this ROM on my LG G2 (802) http://forum.xda-developers.com/lg-g2/development/rom-official-mokee-source-project-t3274849/page2. Everything has been okay so far.
In the Mokee thread I read installing gApps would work like this:
"you can go MokeeCenter after starting rom, there you can download the small gapps integrated into the system and have a lighter and clean rom."
Unfortunally for me there was no option to download gApps via "MokeeCenter". Of course I found Settings -> MokeeCenter.
So I decided to download open_gapps-arm-6.0 (has been the minimal version, I think) and flashed it.
After I rebooted into system, I now am stuck at a popup which immediately and continiously pops up, saying "setup assistent has been closed". So I cannot do anything else than pressing "ok ok ok ok ok ok"
Big problem for me now is, that for some unknown reason, I cannot boot into twrp recovery using one of the hardkey methods.
I usually was able to do it like this:
- Shut down.
- Press power + volume down until LG logo appears.
- Release only power button, then immediately press power button again (while still pressing volume down).
I think I now tried any of the other methods as well (power + volume up instead of down... or release power AND volume down, then press both again... and so on...)
None of them work for me.
I might have to mention, that after the first appear of the popup loop, I read something about flashing "bootstack-d802-CAF-signed" as part of a solution.
I did so, but it diddn't help. Instead of a solution this might be part of my problem, because since I was able to flash it I obvously must have been able to enter twrp before this step.
What should I do now?
By the way: Can some of you tell me, if the annoying crackle/hissing of my headphones is gone with Android M?
I want to know this, because this has been the ONLY reason for me to flash Android M, since I wasn't able to find a solution for Android Lollipop (CM12). I find it extremely (!) uncomfortable to talk to people using my bose qc25 headphones/headset since my Lollipop update, because everytime when a person speaks just a few words with longer pauses between the single words, I have sound errors and hissing/crackles and even some really wired kind of "distortion" at the beginning of each single word and often have to ask people to repeat what they said.
The headphones themselves sound absolutely okay, it's just with the LG G2 phone. (i.e. a friend's Samsung S5 works fine with the bose qc25)
If this bug isn't gone with Android M (or at least fixable) I think I will buy a new cellphone instead of trying to unbrick my LG G2 if unbricking will be a pain in the ass, so I am very interested in an answer regarding the sound bug as well.
Thank you for reading.
with best regards,
Milan
I now have been able to setup a guest account. Running the guest account, I can quit the popup by pressing "ok" once. It doesn't return and is followed by "Gallery stopped" which I am able to quit too. But as guest I cannot get root access to use a software based reboot to recovery, right?
follow these steps
1. go to settings and find applications menu
2. select find system applications from menu
3. find installiation wizard or something else (i am using my rom in Turkish "Kurulum Sihirbazı".
4. click on it and edit permissions
5. enable people and phone sections.
6. cheers
gttrk said:
1. go to settings and find applications menu
2. select find system applications from menu
3. find installiation wizard or something else (i am using my rom in Turkish "Kurulum Sihirbazı".
4. click on it and edit permissions
5. enable people and phone sections.
6. cheers
Click to expand...
Click to collapse
Thank you
Problem was, I could not navigate because there has been this fu*** popup always on top.
I have been able to enable root access and advanced shutdown options by clicking almost 1000 times "ok" at the annoying popup while I used another finger to tap something at the screen as soon as possible. Scrolling was like stuck motion this way... So I have been able to enter twrp and flash another rom.
Nonetheless I tested calling a person with the guest account (by allowing phone calls for guests via the same "tapping-technique"... took me aboout 10 minutes) and found out, there are exactly the same hissing /crackling problems with Android M than with Android L. So I will try Android Kitkat now. This bug is very common. Is there someone who can tell me a working solution? I am pretty sure my phone did not have this bug when I bought it with Kitkat OS installed. So a kitkat rom is my last hope right now.
regards,
Milan
I was messing around trying to root my phone. Now its stuck in the ODIN mode. Which is the necessary ODIN and stock firmware to flash it? Do all I need to do is load into ODIN using volume down home and power. And in ODIN, click AP and choose the tar file, and then start? Can someone link me the proper ODIN and AP file please? My phone is a brick. Im a retard noob. : ( lol. Im trying though. Any help is appreciated.
It says "An error has occured while updating the device software. Use the emergency recovery function in the Smart Switch PC software.
Using Samsung Switch
All hope is not lost. You may have done what I just did and tried to flash a root exploit inappropriate to you phone's firmware version. At this time, the latest factory firmware that you can revert to is rev02 (files with the string "G935TUVU4BQB1" in their name). If you're on the latest T-Mobile update, the you've got factory rev03 firmware, for which no online release is available. Basically, T-Mo users can't restore if we try to root and screw up. But don't panic yet. Hopefully you have a computer to install Samsung Switch on.
1) Download and install Switch, and start it up with your phone unplugged. When it shows the animation of connecting your phone, do so. It probably will list it as an unrecognised device, ignore that.
2)Next to the minimise button in the upper right, select "more", then "Emergency software recovery and initialization". Go to the second tab in the window that pops up, labeled "Device initialization". If you've got the T-Mobile version of the S7 Edge, your model number is SM-G935T (which I'm assuming since we're in the T-Mo subforum). If it rejects the model number, ensure that your internet connection is working; I experienced network issues at the same time and drove myself nuts for a few minutes.
3) It then asks for your device serial number. If you know that, great. Otherwise, unplug your device. Perform a safe reboot by holding Home+Volume Up+Power, and release when a blue screen comes up informing you that loading custom OSes is dangerous. At this point, push the Home key (which the phone should say leads to barcode). The barcode screen will have your serial number on it, write it down. Safe boot the phone again (Home+Volume Up+Power), but this time press Volume Up to get back to download mode. Go back to Switch, which reset itself when you power-cycled the device, go back to that "more" menu, to the second tab. Input your model again, followed by the serial you just wrote down.
4) At this point, Switch should start downloading a pretty big file. If it's anything like the size of the other factory firmwares I tried downloading (the rev02 ones that won't work, with the G935TUVU4BQB1 in the names), then it should be around 2GB. Wait for that to finish, and it'll start pushing it to the phone automatically. Afterward, your phone has been factory reset, and will ask you to sign in with a Google account that has been previously linked to it. This will most likely be the one you were using before you tried to root. From there, it's like doing the first time setup of a new phone.
Sorry my recommendation is a month late for you, I only just had the same problem tonight. We should have been on the same firmware version, though, so if you're still looking for a solution, then give this a go. Hopefully it also helps people who get stuck in a similar conundrum. Good luck!
-Kafte
Simply Odin stock and start over make sure partition is uncheckeded
same problem
kafte said:
All hope is not lost. You may have done what I just did and tried to flash a root exploit inappropriate to you phone's firmware version. At this time, the latest factory firmware that you can revert to is rev02 (files with the string "G935TUVU4BQB1" in their name). If you're on the latest T-Mobile update, the you've got factory rev03 firmware, for which no online release is available. Basically, T-Mo users can't restore if we try to root and screw up. But don't panic yet. Hopefully you have a computer to install Samsung Switch on.
1) Download and install Switch, and start it up with your phone unplugged. When it shows the animation of connecting your phone, do so. It probably will list it as an unrecognised device, ignore that.
2)Next to the minimise button in the upper right, select "more", then "Emergency software recovery and initialization". Go to the second tab in the window that pops up, labeled "Device initialization". If you've got the T-Mobile version of the S7 Edge, your model number is SM-G935T (which I'm assuming since we're in the T-Mo subforum). If it rejects the model number, ensure that your internet connection is working; I experienced network issues at the same time and drove myself nuts for a few minutes.
do you have a option if the smart switch is not recognizing at all?
3) It then asks for your device serial number. If you know that, great. Otherwise, unplug your device. Perform a safe reboot by holding Home+Volume Up+Power, and release when a blue screen comes up informing you that loading custom OSes is dangerous. At this point, push the Home key (which the phone should say leads to barcode). The barcode screen will have your serial number on it, write it down. Safe boot the phone again (Home+Volume Up+Power), but this time press Volume Up to get back to download mode. Go back to Switch, which reset itself when you power-cycled the device, go back to that "more" menu, to the second tab. Input your model again, followed by the serial you just wrote down.
4) At this point, Switch should start downloading a pretty big file. If it's anything like the size of the other factory firmwares I tried downloading (the rev02 ones that won't work, with the G935TUVU4BQB1 in the names), then it should be around 2GB. Wait for that to finish, and it'll start pushing it to the phone automatically. Afterward, your phone has been factory reset, and will ask you to sign in with a Google account that has been previously linked to it. This will most likely be the one you were using before you tried to root. From there, it's like doing the first time setup of a new phone.
Sorry my recommendation is a month late for you, I only just had the same problem tonight. We should have been on the same firmware version, though, so if you're still looking for a solution, then give this a go. Hopefully it also helps people who get stuck in a similar conundrum. Good luck!
-Kafte
Click to expand...
Click to collapse
do you have a solution or alternative if the smart switch in not recognizing or do you have access to stock firmware been looking everywhere
hey guys whenever i restart the phone it asks for pin or the password i setup and than only it will start the phone, why
is this normal, how to fix this
That's normal.... You'll always have to provide password or pin for the first time after phone reboots. Unless you select none for your lockscreen unlock method
My phone in the beginning asked every time I restarted but now it doesn't ask for anything. Is something wrong?
z1_nile said:
My phone in the beginning asked every time I restarted but now it doesn't ask for anything. Is something wrong?
Click to expand...
Click to collapse
There's two levels of lock. One is the lock before android starts and second one after boot is finished.
If your phone isn't asking for an unlock password/pin it's possible you may have disabled it. You can enable the lock before device starts by going through the same process as normal but checking Yes when it asks the question. See my attached image for how the screen looks. If you select No you can apply a regular after boot lock.
asn0304 said:
There's two levels of lock. One is the lock before android starts and second one after boot is finished.
If your phone isn't asking for an unlock password/pin it's possible you may have disabled it. You can enable the lock before device starts by going through the same process as normal but checking Yes when it asks the question. See my attached image for how the screen looks. If you select No you can apply a regular after boot lock.
Click to expand...
Click to collapse
Figured it out just after posting. But thanks a lot for helping.
Change secure start up settings
Is there a way to change secure start up settings aside from reset factory settings? Thanks in advance
Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.