Related
Yes you read it right I want to know how I can brick my phone or make it stop working completely. Now let me explain the reason why. I had installed an app called "Launcher Pro". Later I uninstalled it and that is when all hell broke lose. Basically when ever I would swipe my screen to unlock the phone, I would get constant error messages that would reappear the moment I would close them, and to make matters worse it would lock out the rest of the screen so I can not click any thing else (just like in windows vista and windows 7 when a UAC message pops up). This is further complicated by the fact that I have a Bell Canada Samsung Galaxy Phone, which does not have the 3 button recovery ability but that is not the end of my problems. I got this phone at a store called Best Buy and got their warranty. Now one of the things that voids the warranty is unlocking the phone, guess what?? My phone is unlocked. So since my phone is not dead, it boots up, the lock screen loads up, the top bar shows u the battery life and the fact it is getting service and can receive calls (but which I can not answer since when it comes to that screen, the screen freezes up with the error messages). So if I take the phone to Best Buy, they are going to pop in a different sim other then bell and when they see that it works, will hand me back my phone and void my warranty. So I need to have the phone in such a condition that they can not check that and yes there can be no physical or water damage either. How do I accomplish this?
Is it rooted ? Did u happen to enable usb debugging ?
If so a mere "adb reboot recovery" followed by a wipe data would solve ur issues
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Zink6 said:
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Click to expand...
Click to collapse
Have you tried booting into safe mode. Usually booting into safe mode will disable any 3rd party apps from loading. This might give you the chance to uninstall LauncherPro or even enable USB debugging. The method to get into safe mode for the Bell Vibrant seems tricky though:
Menu + Home + Power On right when you see the Samsung logo (specifically: http://forum.xda-developers.com/showpost.php?p=8583886&postcount=17) probably hold the keys. I know in the other Android phones (HTC Ion) you have to hold Menu from beginning til it boots.
http://forum.xda-developers.com/showthread.php?t=758678
Seems to work sometimes...
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Why unlocking it with code would void the warranty? if you flash, yes, maybe. but you enter the unlock code... isn't the official way? Don't bother how i got the code, I bought it, it's mine, i can unlock it. period. i dont understand how they would consider to void the warranty because you unlock with code. btw, Bell does give unlock code for 75$. so, my phone is not eligible for warranty?
MadWhips said:
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Guys c'mon.. At least read his post. He can't gain access to the phone at all right now. How do you expect him to relock?
Honestly with no adb you can't do much if u dont have 3button working
Try all those 3button tricks posted for those who can't get to recovery/download mode.
One if i recall is :
Turn off phone
Press n hold Home + Vol Down (or Vol up, up 2 u) + power
Keep holding, your phone will restart once, then twice, then let go off power button.
Its worth a shot
I work at best buy. They will not stick another sim card into the phone. Is it within the 30 day return policy? If its within 30 days go return it and show them the phone dont work and they will exchange it for you.. If its not within the 30 days they will most likely have to send the phone out to Samsung.
What i would do :
1. Take the phone back to the store.
2. Tell them the thing dont work...they wont know if its unlocked or rooted.
3. Ask them to exchange it under the manufactures warranty (if its not within the 30 days) and hopefully they will exchange it and not have to send it out to samsung.
WIN.
PM me if anything.
Asked the rep at best buy (by the way this is best buy Canada), and he said warranty is void if unlocked.
like eduard said, just take it do them. don't even ask or mention unlocking coz that will make them think that you have unlocked it.
take it there, say it doesn't work. done. don't ask, don't tell.
lol thats why you dont tell him you unlocked it! wow man.
its not about you telling them that u unlocked it, their procedure is to insert a different sim into the phone before sending it out for repair and/or exchange. And that is when I will be caught. So aside from giving best buy the phone, does any one else have any other ideas?
Did you try this?
http://forum.xda-developers.com/showthread.php?t=813580
I also have a Bell SGS. I got it from Wireless Wave and fortunately I have 3b recovery. You've tried both (up+home+power) as well as (down+home+power) right? You let go as soon as you see the boot screen that says i9000.
Drop it in the water?
zorxd said:
Drop it in the water?
Click to expand...
Click to collapse
Water damage is not covered by warranty.
From what i read, i can't imagine this is a hardware problem (though i could be wrong), so probably the worst that can be is that your phone needs a reflash. How much would that cost in CA if you can't talk it into a warrantee case?
Ya its not a hardware issue, its a software one. Let me give u more information. The phone boots and goes to the lock screen. Shows the correct time and date and shows on the top that it was connected to my phone service but the moment I swipe the screen to unlock, I get repeating messages, one of them reads "The process android.process.acore has stopped unexpectedly. please try again." and the other reads "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again". Both messages have a "force close" button on the bottom that takes the message away just for it to reappear a second later.
Also from what I have been reading in the forums, if I can only get my phone into usb debugging mode in any other way then the typical MENU > Settings > Applications > Development > USB debugging, it would solve all my problems. If any one knows how to do that, please share your knowledge.
There is a post on here for making a USB dongle that powers the phone straight into download mode.
You need a USB plug and a resistor.
You can then re flash.
Sent from my GT-I9000 using Tapatalk
Here's what you can do:
When you've started the phone (and the error messages come up) you connect your device to your PC with the USB cable.
At that point you'll see a new menu on the background (behind the error messages) for the selection of your connection (Samsung Kies, Mass Storage, etc...)
Click away the error messages very quickly and press the button Samsung Kies (you may have to try several times before you can do this but it's possible)
Then you open Samsung Kies and you use the procedure that is mentioned in the post below to reflash your device with a test firmware:
http://forum.xda-developers.com/showthread.php?t=766589
Make sure to read through that tread to know what codes you have to use in the registry. You should be able to flash your device in Kies with a (test/official) firmware this way.
In the end you my not even have to return it at all...
Hi,
out of nowhere, my phone deleted my email accounts (and the emails inside). It took me a while to identify it was actually the phone which deleted it.
The phone's display did not work. When I turned it on, it shows the Galaxy logo which then disappaers in a way that you believe it run out of power.
I connected the phone to the computer and noticed it got a lot of free space, so everything on it obviously got deleted.
Here is the interesting part: The only feature which does not work is the display, everything else functions normal. I can receive calls, it vibrates, the LED light flashes etc.
So you might think this is a hardware issue. I thought the same thing. I cannot put the phone into recovery mode (don't ask me why), but I can put it into download mode.
While being in download mode, the display remains on without any error.
I flashed already two Roms. The phone is a Korean version: E210S
The issue remains. How can I make sure the device got totally wiped during the flashing process? I still suspect there is a virus on my cellphone. At least I do not have any better explanation for this behaviour.
Your help is appreciated
THanks
have you tried to install an antivirus?
since you can't get into recovery(with and advanced recovery it would be easy to do a full full wipe)...you need to flash your firmware and have checked the repartition box...that requires a .PIT file...there is one on the forum...just a quick search and you will find it...but not many peoples replied to that...some said boot loop(maybe don't know how to use it)....
but even if the PIT is ok i don't know how to use it...on my s mini(s5570) used successfully the right PIT file(several times) but firmware came in 3 separated files....now it comes in 1 file...
can someone with more experience let us know? i also want to know how to fully erase the phone...
I'd buy a micro usb to hdmi plug, and plug it into my tv. then download an antivirus on my phone and that way scan it.
ozgame said:
I'd buy a micro usb to hdmi plug, and plug it into my tv. then download an antivirus on my phone and that way scan it.
Click to expand...
Click to collapse
Thanks guys. Did the virus scan with Kaspersky, didn't help / there wasn't any result
I cannot find a PIT file for the E210S 16GB, was only able to find one for 32GB. Any help here?
Thanks
I got my Gear Live off eBay last week. Didn't come with anything but the watch, and just got the cradle from China. And it's definitely Chinese.
It's a third-party cradle, and it lacks USB data. I know this because across three computers, it doesn't detect a device. All I can do is charge this thing, and use 4.4W. I can't force it to grab an update, and because the cradle can't do data, I can't ADB into the recovery when I can force it (I have to route commands through the phone's bridge).
I'm desperate here. Is there ANY WAY to work the Bluetooth ADB and force an update, or at least move an update and flash it manually? I'm seriously low on funds, and this is killing me to not have the software updates.
As a note, I purchased my cradle from this guy here on eBay. If I hadn't instantly given positive feedback, I'd yell about it not supporting data. This is real bull.
EDIT: Seeing as it's a cheap charger anyway, I figured I'd pry it apart to see what actually makes this thing tick, and the results are supremely underwhelming. I've attached photos, but I can't see them being anything more than voltage regulation, to ensure nothing bursts into flames.
Go to https://www.youtube.com/watch?v=x7oRjESQh_o
Follow the video fro unlocking the Gear Bootloader. Make sure to use v2 of his software. v3 is riddled with bugs. Once you unlock the software, use option 8, then reboot. Load back into the flashbooter/recovery menu, then use option 6. Update from there using OTAs.
Read my post. Actually read it.
I CAN'T GET A DATA CONNECTION VIA USB.
UltimaXtreme said:
Read my post. Actually read it.
I CAN'T GET A DATA CONNECTION VIA USB.
Click to expand...
Click to collapse
Have you tried debugging over Bluetooth?
BRANDENDEUCE said:
Have you tried debugging over Bluetooth?
Click to expand...
Click to collapse
It disconnects after rebooting into Recovery. Unless it's possible to throw a flash down while in the OS, I think I'm gonna concede and grab an OEM cradle.
delete
Hello guys!
I have a situation also with a device. I just received today, it has 5.0.1 on it, and i cannot use the tool that is specified in that video + after activating the dev. menu, i dont have the usb option ...
Any advice ?
R3d_Wolf said:
Hello guys!
I have a situation also with a device. I just received today, it has 5.0.1 on it, and i cannot use the tool that is specified in that video + after activating the dev. menu, i dont have the usb option ...
Any advice ?
Click to expand...
Click to collapse
You can force the watch to boot into bootloader mode. Turn off your watch. Press power button and at the same time start swiping from top left corner of the screen to bottom right. (Diagonally) Do it multiple times.
aligatro2010 said:
You can force the watch to boot into bootloader mode. Turn off your watch. Press power button and at the same time start swiping from top left corner of the screen to bottom right. (Diagonally) Do it multiple times.
Click to expand...
Click to collapse
Thanks for your reply aligatro2010, but i decided to return the device and got something else .
Scenario:
User had a Galaxy S6 T-Mobile and the USB would charge but not allow a data connection (no detection in windows).
Phone is rooted.
User was playing around in "developer options" and accidentally enabled OEM lock somehow.
Now the phone says "custom binary blocked by FRP lock" when the phone boots and then shuts off.
He gave it to me and I've read about several fixes involving Odin but I am unable to get any computer to detect the phone while in download mode.
I thought that maybe the USB module was bad so I meticulously removed and replaced the USB module (I have all the right tools after doing screen repairs for years).
It didn't make a difference. The phone will charge with USB but it won't boot except to download mode and it won't detect on any PC that I try it on. It's not a driver issue, it doesn't even detect at all so you never get to the install driver step.
Is this a brick now or is there any hope besides motherboard replacement?
Kafluke said:
Scenario:
User had a Galaxy S6 T-Mobile and the USB would charge but not allow a data connection (no detection in windows).
Phone is rooted.
User was playing around in "developer options" and accidentally enabled OEM lock somehow.
Now the phone says "custom binary blocked by FRP lock" when the phone boots and then shuts off.
He gave it to me and I've read about several fixes involving Odin but I am unable to get any computer to detect the phone while in download mode.
I thought that maybe the USB module was bad so I meticulously removed and replaced the USB module (I have all the right tools after doing screen repairs for years).
It didn't make a difference. The phone will charge with USB but it won't boot except to download mode and it won't detect on any PC that I try it on. It's not a driver issue, it doesn't even detect at all so you never get to the install driver step.
Is this a brick now or is there any hope besides motherboard replacement?
Click to expand...
Click to collapse
I always recommend smartswitch... have you tried that one?
Smartswitch won't work because the computer won't detect the phone USB for some reason
Any other thoughts?
I know bumping isn't cool but I'm a couple of days away from taking this thing to the shooting range.
Idk man... try another pc?
That's usually what other user day to ppl...
britchel said:
Idk man... try another pc?
That's usually what other user day to ppl...
Click to expand...
Click to collapse
Not the PC. I've tried multiples.
https://forum.xda-developers.com/galaxy-s6/general/samsung-reactivation-lock-bypass-t3417151
Taje a look on this
britchel said:
https://forum.xda-developers.com/galaxy-s6/general/samsung-reactivation-lock-bypass-t3417151
Taje a look on this
Click to expand...
Click to collapse
Thank you but that is only for Verizon. There is no maintenance boot mode for Sprint Galaxy S6
Kafluke said:
Thank you but that is only for Verizon. There is no maintenance boot mode for Sprint Galaxy S6
Click to expand...
Click to collapse
The only method I've been successful with has been with using Realterm to make my way into replacing the Google.loginservice.apk
Mrm27 said:
The only method I've been successful with has been with using Realterm to make my way into replacing the Google.loginservice.apk
Click to expand...
Click to collapse
Thanks, the problem is I cannot get the phone to detect on any PC with any USB cable. I even replaced the USB module inside the phone thinking maybe it was faulty. Something is preventing it from being detected.
Just checking back one more time before I take this perfectly good phone to the shooting range. Any more thoughts from anyone?
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
When the bootloader is unlocked, "allow oem unlocking" is greyed out.
You use fastboot commands when flashing firmware and locking the bootloader
Code:
fastboot devices
The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
Trade you for a locked 4a 5g...
sipotek said:
Hey Bro can you share a method that how can I root Google Pixel 5, I tried a lot but i can't update the recovery mode? can you share some simple method like with the help of any Apk, or recovery file.
Click to expand...
Click to collapse
Lots of threads and guides online that show how to root