Related
i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
you know that the "max download size" thing is just a WARNING message, in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
anyway, see if it really wont come on, my phone was like that, but in fact it was in qualcomm´s QD-LOADER 9008 (i had to install some drivers for it to show up on pc). if your phone does get detected(even if as an unknown device)then you have some hope, if not - too bad you are mostly screwed.
Check your device manager
opssemnik said:
in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
Click to expand...
Click to collapse
It showed for every fastboot flash I did just a few days ago. I don't recall that warning showing up back when I flashed 4.4.4 and prior. I think it's a change with the new bootloader.
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
shiva-x said:
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
Click to expand...
Click to collapse
Wrong...
Google- said:
i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
Click to expand...
Click to collapse
Tried a forced reboot? (Power + volume down button for bout 15 seconds).
Seems like the go-to solution but I see no one asked you yet.
Do this while connected to a charger.
Also try booting into the secondary bootloader by pressing volume up , down and power simultaneous.
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
gee2012 said:
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
Click to expand...
Click to collapse
Agree , but it should still be salvageable - assuming the incomplete firmware didn't cause hardware damage.
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
nirmal212 said:
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
Click to expand...
Click to collapse
any new device showing up in the device manager when you connect your phone to your pc?
bitdomo said:
any new device showing up in the device manager when you connect your phone to your pc?
Click to expand...
Click to collapse
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
nirmal212 said:
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
Click to expand...
Click to collapse
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
bitdomo said:
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
Click to expand...
Click to collapse
Can I perform this action even if my device is not started? I tried all the button options and still the device won't power on.
Maybe this has been solved before but so far I haven't found a solution to my OPO Hardbrick and I really need of your help. I tried flashing resurrection remix to my OPO and I guess it went wrong, I tried restoring my backup and it didn't work so I decided to factory reset it which deleted the rom. Now, I have used several tool kits and they all seem to have not worked, it only removed my custom recovery (TWRP) and replaced it with the Cyanogen Recovery, now my phone doesn't even turn on, its all black and vibrates, I am able to use the tool kits using the volume up and power button, but no fastboot, any solutions? Thank you so much
Ok, first step is not to panic and don't do crazy stuff and go over logically. There is no help in starting to flash stuff when your pc doesn't properly connect to your phone.
Does your pc recognize the phone when you insert the USB port after you placed it in the vol+ and power on mode (fastboot)? If yes the device should be seen in the device manager as a android or usb thing.
Check with skipsoft toolkit if you see the device with adb. Do you see any number?
Don't panic here is the solution
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Juan_Cuen said:
Maybe this has been solved before but so far I haven't found a solution to my OPO Hardbrick and I really need of your help. I tried flashing resurrection remix to my OPO and I guess it went wrong, I tried restoring my backup and it didn't work so I decided to factory reset it which deleted the rom. Now, I have used several tool kits and they all seem to have not worked, it only removed my custom recovery (TWRP) and replaced it with the Cyanogen Recovery, now my phone doesn't even turn on, its all black and vibrates, I am able to use the tool kits using the volume up and power button, but no fastboot, any solutions? Thank you so much
Click to expand...
Click to collapse
Like the other people are saying, don't worry, it's probaly not that big of a deal. I had this before. Try booting into fastboot mode and reflash TWRP recovery using the method showcased in this video: https://www.youtube.com/watch?v=KZaajUEybNM (you need to skip through it a little). Make sure you have all the proper drivers installed on your computer.
The phone doesn't go into fastboot, but it is recognized by my computer as QU something with a q, with the qualcomm drivers, I have managed to only let it be recognized via tool kits, It doesn't go into fastboot or anything. I have tried the ColorOS toolkit but apparently its more succesful if I try it on an XP computer. Whenever I hold the power and Volume Up the Phone vibrates and is recognized by the tool kit
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.
UPDATE: I've unbricked my phone! I used MSM Tool for OnePlus 7 Pro.
Here is a link to the video that saved my phone:
=====================================
Today i installed Android 10 Public Beta on my OnePlus 7 pro. It was great, i liked it. But i noticed i didn't have root. So i tried rooting it by flashing twrp.
Now this is where i fqed up. I flashed a TWRP image to boot. So i tried to boot into TWRP, but it just loaded back into fastboot. So i got myself stuck. But there is more.
I then wanted to give up and go back, but i couldn't find a OnePlus 7 pro stock boot image for Android 10. So i tried installing the latest version, and i thought it worked.
Now when i boot up my phone, it does the boot animation, but crashes in the process and turns off (Or i think so, the screen goes black). I for some reason can't access fastboot anymore. And i can't access the phone through adb. Windows makes a device connected sound, but doesn't show up anywhere.
Someone please help, what to do?
-HLVM
Use the MSM tool. That should sort you out.
HLVM said:
Today i installed Android 10 Public Beta on my OnePlus 7 pro. It was great, i liked it. But i noticed i didn't have root. So i tried rooting it by flashing twrp.
Now this is where i fqed up. I flashed a TWRP image to boot. So i tried to boot into TWRP, but it just loaded back into fastboot. So i got myself stuck. But there is more.
I then wanted to give up and go back, but i couldn't find a OnePlus 7 pro stock boot image for Android 10. So i tried installing the latest version, and i thought it worked.
Now when i boot up my phone, it does the boot animation, but crashes in the process and turns off (Or i think so, the screen goes black). I for some reason can't access fastboot anymore. And i can't access the phone through adb. Windows makes a device connected sound, but doesn't show up anywhere.
Someone please help, what to do? ((
-HLVM
Click to expand...
Click to collapse
You probably still have fastboot just not hitting the right buttons. Hold volume up and down and power untill you see fastboot mode. When you get there run fastboot -w (it will wipe your device) and see if it will boot then.
joemossjr said:
You probably still have fastboot just not hitting the right buttons. Hold volume up and down and power untill you see fastboot mode. When you get there run fastboot -w (it will wipe your device) and see if it will boot then.
Click to expand...
Click to collapse
Thanks for replying!
I did what you told me to, but fastboot never shows up. The screen is just black. But i can hear the phone disconnecting and connecting to my Windows pc
hallo dare said:
Use the MSM tool. That should sort you out.
Click to expand...
Click to collapse
Thanks for the suggestion, i will check it out
HLVM said:
Thanks for replying!
I did what you told me to, but fastboot never shows up. The screen is just black. But i can hear the phone disconnecting and connecting to my Windows pc
Click to expand...
Click to collapse
if its booting and windows is connecting something does it show up under adb devices?
dat_Noko said:
if its booting and windows is connecting something does it show up under adb devices?
Click to expand...
Click to collapse
Nope, the device doesn't show up when i run the command "adb devices". But i can see the device as "QUSB_BULK_CID:0404_SN:B8F829A6" in Device Manager
have you tried edl mode heres thread hope this helps you man if not dont give up on edl the screen dont come on but the exe will show connection heres fix ive done that to lg g5 hope this does it edl mode works forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
i installed the DSU package and now the phone is stuck on your device is corrupted and cannot be trusted. I can only get into fast boot mode
can someone guide me through resetting it, I dont care about anything on the phone i just want it to go back
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
If you can reach fastboot this method should work
_MartyMan_ said:
If you can reach fastboot this method should work
Click to expand...
Click to collapse
dont i need unlocked bootloader?
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
dont i need unlocked bootloader?
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
casualBricker said:
dont i need unlocked bootloader?
Click to expand...
Click to collapse
To flash critical partitions, yes
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
mattie_49 said:
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
Click to expand...
Click to collapse
My bad, didn't see that he changed op. I mean if he could not connect through msm, there are a few options to try, including installing a driver manually for the qcom device. I had to fiddle with drivers and whatnot for about an hour or so before flashing was able to successfully commence. msm should help but scheduling a remote repair might take a day or so from oneplus so might as well try you know?
casualBricker said:
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
Click to expand...
Click to collapse
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
D3G0N said:
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
Click to expand...
Click to collapse
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
casualBricker said:
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
Click to expand...
Click to collapse
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
D3G0N said:
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
Click to expand...
Click to collapse
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
casualBricker said:
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
Click to expand...
Click to collapse
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
D3G0N said:
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
Click to expand...
Click to collapse
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
casualBricker said:
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
Click to expand...
Click to collapse
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
D3G0N said:
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
Click to expand...
Click to collapse
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
casualBricker said:
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
Click to expand...
Click to collapse
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
D3G0N said:
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
Click to expand...
Click to collapse
im not touching the powerbutton, it confuses me as well. do I wait for it to vibrate before I plug in the phone?