Database Info

Unlocked S-ON No ROM

Hi
I have a problem i forget to s-off before a wipe my phone and right now it's:
Bootloader UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT 2.15.0000
I can install any Recover but i can't load any ROM
There is problem with CID i thing but how i can change it without rom?
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT26RW400500
(bootloader) imei: 352103050681713
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4083mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Please help

Cach said:
Hi
I have a problem i forget to s-off before a wipe my phone and right now it's:
Bootloader UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT 2.15.0000
I can install any Recover but i can't load any ROM
There is problem with CID i thing but how i can change it without rom?
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT26RW400500
(bootloader) imei: 352103050681713
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4083mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Please help
Click to expand...
Click to collapse
This is Dev Section, not Q&A Section. You have opened the thread in the wrong section. I've asked a moderator to move it. Please try to read forum rules, this is how we can keep it well structured and helpful for others.
Now, related to your issue, flashing a ROM shouldn't have anything to do with your CID. You should be able to flash any ROM that's made for 2.15 hboot.
Where do you get problems? When flashing the ROM or after that because it's not booting? You didn't detail the steps you do when flashing also you didn't specified any errors so I presume ROM is flashing OK and you have phone stuck on boot logo or animation after that (correct me if I'm wrong). Well this it's mainly because of your S-On flag. You MUST flash separately in fastboot the ROMs kernel after each ROM you flash in recovery, or else it won't boot

Rapier said:
This is Dev Section, not Q&A Section. You have opened the thread in the wrong section. I've asked a moderator to move it. Please try to read forum rules, this is how we can keep it well structured and helpful for others.
Now, related to your issue, flashing a ROM shouldn't have anything to do with your CID. You should be able to flash any ROM that's made for 2.15 hboot.
Where do you get problems? When flashing the ROM or after that because it's not booting? You didn't detail the steps you do when flashing also you didn't specified any errors so I presume ROM is flashing OK and you have phone stuck on boot logo or animation after that (correct me if I'm wrong). Well this it's mainly because of your S-On flag. You MUST flash separately in fastboot the ROMs kernel after each ROM you flash in recovery, or else it won't boot
Click to expand...
Click to collapse
It's my mistake
i have 2 kind of problems:
When i try to flash
HTC_One_S_-_MAximusHD_10
i have black screen after HTC logo
Viper_One_S_3.1.3
i have logo screenc Viper One S and reboot
CM-11-20140425..
Black screen and reboot

Cach said:
It's my mistake
i have 2 kind of problems:
When i try to flash
HTC_One_S_-_MAximusHD_10
i have black screen after HTC logo
Viper_One_S_3.1.3
i have logo screenc Viper One S and reboot
CM-11-20140425..
Black screen and reboot
Click to expand...
Click to collapse
MaximusHD is a 2.16 hboot ROM. You shouldn't flash it and run on 2.15. So that's why you have issues with it.
Viper or CM11 are OK to flash on your hboot but as I said you MUST flash the kernel in fastboot AFTER you flash the ROM in recovery. Did you do that?
To flash kernel in fastboot, you must extract boot.img from the ROM zip, place it on your PC. Then after flashing ROM, reboot to bootloader, connect your USB and go to FASTBOOT. You should see FASTBOOT USB on screen. Then issue from a command prompt opened in the location of you ADB comand the following: fastboot flash boot boot.img
Have you done that? If not, ROM won't boot

Rapier said:
MaximusHD is a 2.16 hboot ROM. You shouldn't flash it and run on 2.15. So that's why you have issues with it.
Viper or CM11 are OK to flash on your hboot but as I said you MUST flash the kernel in fastboot AFTER you flash the ROM in recovery. Did you do that?
To flash kernel in fastboot, you must extract boot.img from the ROM zip, place it on your PC. Then after flashing ROM, reboot to bootloader, connect your USB and go to FASTBOOT. You should see FASTBOOT USB on screen. Then issue from a command prompt opened in the location of you ADB comand the following: fastboot flash boot boot.img
Have you done that? If not, ROM won't boot
Click to expand...
Click to collapse
OK it's working. Before i use to flash kernel from recovery. When i did this using fastboot everything was ok.
Thx I am grateful for the help

Cach said:
OK it's working. Before i use to flash kernel from recovery. When i did this using fastboot everything was ok.
Thx I am grateful for the help
Click to expand...
Click to collapse
Don't forget to do this after each ROM flash. Since you're S-On, kernel partition is not writeable in recovery, only in fastboot

[Q] Bricked K2_UL

Hello.
First of all, I am new to Android development. I like to play around with stuff and a friend of mine who is a total noob asked if I could take a look at his HTC One SV. He said that the phone switched off during software update and now the phone is stuck in bootloop.
I spent 2 whole days reading up on what can be done and trying to fix it but right now I am fed up and would appreciate if anyone could help me in any way, especially a walktrough via PMs.
I tried to flash TWRP recovery via fastboot. It flashes, it goes on to the red warning message and goes back to bootloop after a minute. I think I tried every possible TWRP version. I cleared the cache before and after flashing. I flashed multiple times, I ereased cache multiple times with each image.
I am unable to go into recovery. What can I do about it? What am I doing wrong? What can I try? The guy that gave me the phone already made peace with the idea that it will never work again so I am willing to try anything. I would like to start from scratch as I do not know if anyone played with it before me.
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOTT-2.00.0000
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Apr 12 2013, 01:55:41:-1
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.15.118.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: T-MOB009
(bootloader) battery-status: low
(bootloader) battery-voltage: 3453mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.077s

You can't restore your boot.img through TWRP because you are S-On. Would require Dumlock to do this.
You need to rename boot.emmc.win to boot.img and flash it via fastboot after restoring your device using a twrp backup.
Same concept as flashing a Rom.
Sent from my C525c using Tapatalk

[Q] Unable to unlock again after "fastboot oem lock"

I'm trying to get my HTC Sensation to boot one of the 4.4 CyanogenMod unsupported ROM's, and after going through several walkthroughs I found here, I realized I had to upgrade my firmware before I could do that. So I used the "fastboot oem lock" command and reloaded a stock ROM using an RUU process. Now I'm ready to load one of the new CM ROM's, but I can't flash any boot image until I unlock the bootloader again. I tried using the HTCDev process again using my original Unlock_code.bin as well as a newly generated Unlock_code.bin, but no luck. I feel like this is the last speed bump to get over. Here are the results of my "getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.106
(bootloader) serialno: HT162T527781
(bootloader) imei: 355066041626260
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I go into the bootloader it currently says:
Code:
*** RELOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
Any ideas of how I can unlock the bootloader long enough to flash a boot image? Any advice is much appreciated!

roswell1329 said:
I'm trying to get my HTC Sensation to boot one of the 4.4 CyanogenMod unsupported ROM's, and after going through several walkthroughs I found here, I realized I had to upgrade my firmware before I could do that. So I used the "fastboot oem lock" command and reloaded a stock ROM using an RUU process. Now I'm ready to load one of the new CM ROM's, but I can't flash any boot image until I unlock the bootloader again. I tried using the HTCDev process again using my original Unlock_code.bin as well as a newly generated Unlock_code.bin, but no luck. I feel like this is the last speed bump to get over. Here are the results of my "getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.106
(bootloader) serialno: *************
(bootloader) imei: **********
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I go into the bootloader it currently says:
Code:
*** RELOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
Any ideas of how I can unlock the bootloader long enough to flash a boot image? Any advice is much appreciated!
Click to expand...
Click to collapse
since you are on S-OFF flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
after that install a custom recovery and flash a custom rom from it
you don't need to flash the custom rom's boot.img because you are on S-OFF
by the way you could just flash 3.33 universal in first place and avoiding the ruu process
note:remove you imei and s/n
don't show them in public

rzr86 said:
since you are on S-OFF flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
after that install a custom recovery and flash a custom rom from it
you don't need to flash the custom rom's boot.img because you are on S-OFF
by the way you could just flash 3.33 universal in first place and avoiding the ruu process
note:remove you imei and s/n
don't show them in public
Click to expand...
Click to collapse
That was it! Thank you very much. It's running like a champ now.

[Q] Not booting After RUU 3.18

Dear all,
I tried to restore my phone to stock rom (for stability reasons)
however I tried RUU rom 3.18.502.6
Phone is Telstra Australia HTC one XL
now it goes into bootloop displaying HTC quietly brilliant logo then reboots and displays the same thing.
i can get into fastboot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3679mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Any help would be much appreciated!!
Thank you

First thing you need to do is edit the IMEI out of your post, never post that publicly. Is there a reason you're using an at&t RUU? If you really want to return the device to stock you should use a Telstra RUU. The at&t RUU will work because you have s-off, but it isn't technically stock (plus tethering won't work on an at&t ROM). Have you tried running the RUU a second time?
Transmitted via Bacon

Good idea. Thanks! I have tried ruu with that file multiple times. I used it before people have said it is compatible with super cid and S-off
Is if worth trying another ruu?
Would it be compatible?
I just want a stock HTC rom as this is now my backup phone. Will just use it to stream music.
Cheers!

Because you're s-off you can use any Evita RUU.
http://androidruu.com/?developer=Evita
Transmitted via Bacon

hmm. Tried updating to HTC_One_X_RUU_5.18.502.1.exe
still no dice.
STill boot looping
then tried flashing the latest TWRP via fastboot.
can't even get into recovery. just reboots.
Any other ideas?
Many thanks!!

tzuyang said:
hmm. Tried updating to HTC_One_X_RUU_5.18.502.1.exe
still no dice.
STill boot looping
then tried flashing the latest TWRP via fastboot.
can't even get into recovery. just reboots.
Any other ideas?
Many thanks!!
Click to expand...
Click to collapse
also tried clear storage and factory reset. these just result in system rebooting.......

'(Remote: image update error)'

please help me anybody!
the run 'fastboot flash recovery recovery.img' after
"....writing 'recovery'...
FAILED (remote: image update error)"
is there any solution for this problem?
htc one sv, unlocked, k2_ul, HBOOT- 2.21.000 S-ON

Whats wrong, what are you going to do?
What recovery version, what software, phone working or dead?
Wrong download, the whole error message could help too?
Sure that file ending is not hidden in windows (recovery.img.img)
Not much information...

phone is dead, because the battery full empty , after turn-on the phone dont run the twrp, or android, just a white screen, and dont work it.
the screen is:
UNLOCKED
K2_UL XA SHIP S-ON RL
HBOOT-2.21.000
OS-
eMMC-boot 1024MB
Nov 7 2013, 15:32:31.0
FASTBOOT USB (red)
VOL UP
VOL DOWN
POWER
BOOTLOADER
REBBOT
REBOOT BOOTLOADER
POWER DOWN
i try to bootloader-recovery menu, but dont work it, and try to fastboot recovery.img from (http://forum.xda-developers.com/htc-one-sv/orig-development/recovery-twrp-touch-recovery-t3152555)
and fastboot this error message:
d:\1>fastboot flash recovery TWRP_2871_Recovery.img
< waiting for device >
sending 'recovery' (11516 KB)...
(bootloader) start check_usb: usb_ep0: type=128, request=6
OKAY [ 6.977s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 7.211s
d:\1>
any tips? any hope, data in storage is save?
what i can do?

K2_UL XA...? What region are you from? Whats your Cid?
Output from " fastboot getvar all "?
I don't think you will get your data back! You did unlock the bootloader, don't you? In this case data gets wiped.

old.splatterhand said:
K2_UL XA...? What region are you from? Whats your Cid?
Output from " fastboot getvar all "?
I don't think you will get your data back! You did unlock the bootloader, don't you? In this case data gets wiped.
Click to expand...
Click to collapse
thank you for you answer!
K2_UL XA SHIP S-ON RL
europe region
after 'fastboot oem readcid'
"d:\priv\---HTC---\adb>fastboot oem readcid
...
(bootloader) cid: ORANG001
OKAY [ 0.013s]
finished. total time: 0.013s"
after 'fastboot getvar all'
d:\priv\---HTC---\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012
(bootloader) imei: 352803050972026
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
yes, bootloader is work (i hope we thing same thing) ('fastboot-recovery-factory reset-clear storage-simlock-show barcode' menu)
next step? :crying

I assume you need a RUU or firmware package matching to your device/CID/MID which i don't have (ORANG001/PL8010000).
Would be all not so difficult, if you made your device S-off after the last "brick".
You also can try to use a toolkit like this, with support for your device. Maybe this is able to flash the recovery.

old.splatterhand said:
I assume you need a RUU or firmware package matching to your device/CID/MID which i don't have (ORANG001/PL8010000).
Would be all not so difficult, if you made your device S-off after the last "brick".
You also can try to use a toolkit like this, with support for your device. Maybe this is able to flash the recovery.
Click to expand...
Click to collapse
thanks a lot... i try...

unfortunately the windroid universal not working...
unlock bootloader (step 1)---> ok (no error message)
flash recovery (step2) ---> ok (no error message)
flash supersu (step 3) --- > NO DEVICE FOUND (Please ensure tha that USB Debugging is enable (but the android dont run this device ) your device is plugged correctly, and you correctly installed the ADB Drivers. If this is a persistent issue, please reply in the XDA thread
the past succeeded the new RUU and flash recovery. (http://forum.xda-developers.com/htc-one-sv/help/htc-one-sv-help-t3034790 ), but now dont see the device in 'my computer'
and just s-on 'mode' at the present. is there a method, which is there is S-OFF?
any idea?

Hi,
i figured I should join this thread since I have the same phone, same region (even the same carrier) & same problem here. For a little context my One SV was rooted (unlocked bootloader, installed CWM recovery and superuser), nothing more, no custom rom or anything like that. I was running stock 4.1.2, worked fine for 6 months after getting root access, then out of the blue, I get stuck on Fastboot/Bootloader just like OP. Recovery and factory reset don't do anything, just loop back to fastboot. I have fastboot usb working, but no adb connection apparently (adb devices is empty).
***unlocked***
K2_UL XA SHIP S-ON RL
HBOOT - 2.00
eMMC-boot
jun 13 2013
Output from " fastboot getvar all "?
Click to expand...
Click to collapse
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012 <== see i'm gonna leave this here because i have the same as you sanka01, isnt that weird ?
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG202
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
c:\>fastboot getvar commitno-bootloader
commitno-bootloader: dirty-15afa7fc67c51747c2eaca17ce1ac7846d555b6a
c:\>fastboot getvar hbootpreupdate
hbootpreupdate: 11
c:\>fastboot getvar gencheckpt
gencheckpt: 0
i've tried windroid universal, it says "success" at flashing recovery but after that, recovery still can't be entered. as u can see i'm S-ON, can't change CID or anything.... can u get s-off on a bricked phone ? I have found a super old stock ICS ruu but I can't figure how to install it.... and even after that I would need someone to walk me through the steps of getting back to 4.1.2 cause I'm a huge noob
so, I'm very interested in the resolution of your problem. any help appreciated.

ononyn0us said:
Hi,
i figured I should join this thread since I have the same phone, same region (even the same carrier) & same problem here. For a little context my One SV was rooted (unlocked bootloader, installed CWM recovery and superuser), nothing more, no custom rom or anything like that. I was running stock 4.1.2, worked fine for 6 months after getting root access, then out of the blue, I get stuck on Fastboot/Bootloader just like OP. Recovery and factory reset don't do anything, just loop back to fastboot. I have fastboot usb working, but no adb connection apparently (adb devices is empty).
***unlocked***
K2_UL XA SHIP S-ON RL
HBOOT - 2.00
eMMC-boot
jun 13 2013
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012 <== see i'm gonna leave this here because i have the same as you sanka01, isnt that weird ?
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG202
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
c:\>fastboot getvar commitno-bootloader
commitno-bootloader: dirty-15afa7fc67c51747c2eaca17ce1ac7846d555b6a
c:\>fastboot getvar hbootpreupdate
hbootpreupdate: 11
c:\>fastboot getvar gencheckpt
gencheckpt: 0
i've tried windroid universal, it says "success" at flashing recovery but after that, recovery still can't be entered. as u can see i'm S-ON, can't change CID or anything.... can u get s-off on a bricked phone ? I have found a super old stock ICS ruu but I can't figure how to install it.... and even after that I would need someone to walk me through the steps of getting back to 4.1.2 cause I'm a huge noob
so, I'm very interested in the resolution of your problem. any help appreciated.
Click to expand...
Click to collapse
i have a same program buddy my phone is running few month, after the root, and after dead. the seral number, is so weird... but my phone cidnum was t-mobile first root...
and any recovery or boot. img not working, because the reply is: "image update error"
do you have an idea? or any solution? anybody? somewhere? or phone throw to the trash?