Database Info

Help!

I need real help guys.
Last night i change my desire s to s-off and rooted it. I then decided to stop the processing and went to unroot it, by loading a stock rom back onto the phone.
Everything seemed to go fine, i switched the phone back on and everything looked fine although the superuser was still on the phone.
The phone then sporadically started turning on and off and when i tried to enter a few menus i was greeted by android.process.media has had to stop etc and there was another one.
At 6am this morning the phone started vibrating and froze so i turned it off, ive now tried to turn it back on to change it back to normal, but the phone now wont turn on.
I cant get a charge LED and when plugged into the laptop it makes a funny jingle from the laptop and not the duh duh that you would normally get when plugging a usb device in the laptop.

ajtaylor09 said:
I need real help guys.
Last night i change my desire s to s-off and rooted it. I then decided to stop the processing and went to unroot it, by loading a stock rom back onto the phone.
Everything seemed to go fine, i switched the phone back on and everything looked fine although the superuser was still on the phone.
The phone then sporadically started turning on and off and when i tried to enter a few menus i was greeted by android.process.media has had to stop etc and there was another one.
At 6am this morning the phone started vibrating and froze so i turned it off, ive now tried to turn it back on to change it back to normal, but the phone now wont turn on.
I cant get a charge LED and when plugged into the laptop it makes a funny jingle from the laptop and not the duh duh that you would normally get when plugging a usb device in the laptop.
Click to expand...
Click to collapse
Hey did you tried adb .. does it shows your device..
Check it, search forum for adb setup..
then
open cmd
adb devices - to see if adb recognizes your device
adb bootloader - to get into boot loader menu
if you successfully get into boot menu try flashing once again RUU(check in DS Delvelopment section)
else you are S-ON , i guess after flashing Stock ROM..So better to give in customer service center

I can't understand and get the adb to work

ajtaylor09 said:
I cant get a charge LED and when plugged into the laptop it makes a funny jingle from the laptop and not the duh duh that you would normally get when plugging a usb device in the laptop.
Click to expand...
Click to collapse
Remove the battery. Wait about 30 seconds and put it back in. Then press and hold the "Volume down" button. Press the "Power" button wait a little and let go. Do not let go the "Volume down"! If it works the phone will boot to the Bootloader. Then check the version (it has to something like 6.98.1002) and post it here. After that try to select Recovery from the menu. Then we will see what will come next

Nothing! Dead as a door knob

ajtaylor09 said:
Nothing! Dead as a door knob
Click to expand...
Click to collapse
If it makes a sound on connection to the PC you can try to start a RUU but most probably it will not work...
So you next step is the repair center then

Is it going to cost alot or is it worth just buying a new desire s?

ajtaylor09 said:
Is it going to cost alot or is it worth just buying a new desire s?
Click to expand...
Click to collapse
As far as I know the reapair is about 1/3 of the phone price. But you can skip the "custom software flashing" part and say only this:
At 6am this morning the phone started vibrating and froze so i turned it off, ive now tried to turn it back on to change it back to normal, but the phone now wont turn on.
Click to expand...
Click to collapse
If you are a good liar they will repair it under warranty
Since it is completely dead and probably the technicians will not bother to analyze the problem, most probably they will replace the motherboard (eMMC). Good luck...

I have now sorted the adb problem out and install the drivers onto the laptop (no more jingle)
How do i try your first suggestion?

ajtaylor09 said:
I have now sorted the adb problem out and install the drivers onto the laptop (no more jingle)
How do i try your first suggestion?
Click to expand...
Click to collapse
ok. open cmd (command prompt) and type:
Code:
adb devices
if it connects the output sholud look someting like this:
HAJ45345L35H device
you can try the same with
Code:
fastboot devices
and look for the same output
btw is your device branded?

Yes was 3 branded

im getting adb is not recognised.

ajtaylor09 said:
im getting adb is not recognised.
Click to expand...
Click to collapse
There is a guide in my signature. It is quite easy. Try it.
If you have flashed a non branded RUU to your branded phone there is nothing you can do even if you manage to connect it to the PC. It will be completely messed up. No offense but since you have difficulties with an adb setup all the advanced methods will be very hard for you. So my suggestion is to go for a repair (if you have warranty) and try with the story that is just stopped working...
But of course it is up to you to decide

completed the adb and says device not found

ajtaylor09 said:
completed the adb and says device not found
Click to expand...
Click to collapse
@amidabuddha (@ajtaylor09)
Look again like another valiant effort, although does sound like your dealing with a brick this time, as you've already pointed out there are benefits here in that the service centre should take device under warranty and either replace or put in new motherboard. No questions asked...but as long as no daft answers are given

Phone won't turn on, can't get into Hboot

Hi,
I was just wondering if anyone can give me any pointers on what I could do.
I don't own the device since its my girlfriend's, but her phone is refusing to turn on, tried getting into the bootloader by pressing volume down and power - nothing. This happened after she left it in her locker at work with no problems and upon returning she found it like this.
Charging it up with battery plugged in does nothing, red led shows for about 5 secs then it turns green indicating the battery is charged? Tried taking the battery out and tried to power it from mains, nothing.
When I plug the phone into my computer it does show in devices and printers as a android phone so something must still be working.
Is there any way I can flash a new RUU this way or access adb? I've tried installing the drivers but when searching for devices it says not found.
She didn't let me root the phone when she first got it so it is covered under warranty, however when we phoned HTC to process a repair we told them about a screen crack which she incurred MONTHS ago, but they are now saying she has to pay for the screen to be fixed for the phone to be fixed under warranty even if we don't want it fixed? They can't even tell us how much it would cost either because they have to see it to get a quote :/
Needless to say I'm not very happy with HTC right now and not even sure if they are allowed to do this.
Is there anything I can do to see if I can sort the phone, or do we have to chalk up at least £27 for courier costs?
Cheers

cmonthegas said:
Hi,
I was just wondering if anyone can give me any pointers on what I could do.
I don't own the device since its my girlfriend's, but her phone is refusing to turn on, tried getting into the bootloader by pressing volume down and power - nothing. This happened after she left it in her locker at work with no problems and upon returning she found it like this.
Charging it up with battery plugged in does nothing, red led shows for about 5 secs then it turns green indicating the battery is charged? Tried taking the battery out and tried to power it from mains, nothing.
When I plug the phone into my computer it does show in devices and printers as a android phone so something must still be working.
Is there any way I can flash a new RUU this way or access adb? I've tried installing the drivers but when searching for devices it says not found.
She didn't let me root the phone when she first got it so it is covered under warranty, however when we phoned HTC to process a repair we told them about a screen crack which she incurred MONTHS ago, but they are now saying she has to pay for the screen to be fixed for the phone to be fixed under warranty even if we don't want it fixed? They can't even tell us how much it would cost either because they have to see it to get a quote :/
Needless to say I'm not very happy with HTC right now and not even sure if they are allowed to do this.
Is there anything I can do to see if I can sort the phone, or do we have to chalk up at least £27 for courier costs?
Cheers
Click to expand...
Click to collapse
Could you just send it and say the screen got cracked in the post
Sent from my HTC Desire S using xda app-developers app

My phone isn't recognizing a USB cable is plugged into the computer in fastboot

Hey guys, I have a softbricked Atrix2, I tried making a factory cable the other night, wired it correctly as far as I know, it turned on straight away without a battery into fastboot, but wouldn't recognize that a usb cable was plugged in (So power, but no data). And when I plugged in a normal usb cable with the battery in the phone still wouldn't recognize that a usb cable was plugged in. I am currently charging my battery right now, I wasn't having this problem before and am starting to think this phone is cursed by the devil himself . I'll be really disappointed if I charge this battery up and another problem arises, been waiting weeks for this charger. The phone was recognizing usb data cables without issue, tho of course I couldn't do anything because of the low battery, and suddenly it just stopped. Any ideas? Just don't want to spend all day trying to work this out because I've had a softbricked phone for weeks and only got to use it for all of about an hour .
More info: When I plug a normal USB in without a battery the white LED lights up and stays lit. Everything is pointing to power but no data... What would cause that and is there a fix
More more info: Battery OK
OK to program
Connect USB
Data Cable
Shows in device manager as "Unknown device", trying to force install of the "Mot single ADB interface" drivers just gives the error "The device cannot start (Code10), wont show up in ADB or RSD, and phone WILL NOT change status to USB plugged in. Time to think up a legit reason why my phone would say "Flash failure" and get a replacement?

A little more info maybe
What were you on before soft brick stock 2.3.6,2.3.5 or ICS???
How exactly did you soft brick it??
Have you tried getting the phone to start in the normal mode?(by pressing power+vol up+vol down and choosing boot normally???)
Sent from my MB865 using xda premium

deveshmanish said:
A little more info maybe
What were you on before soft brick stock 2.3.6,2.3.5 or ICS???
How exactly did you soft brick it??
Have you tried getting the phone to start in the normal mode?(by pressing power+vol up+vol down and choosing boot normally???)
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Went from 2.3.6 to stock 2.3.5 to OTA 2.3.6 to OTA leak to SCV7, phone kept crashing, tried to fxz back to 2.3.5 stock, said completely successfully but just bootlooped so I went to try again but the battery was low, so that's how I softbricked. And me being the impatient person I am I tried to make a moto factory cable with 2 non standard cables (Micro usb end from a mini to micro converter and the other end from something else), I'm sure I wired it correctly but I guess not, it booted into fastboot without a battery, but said connect usb cable, so I tried to plug in a normal usb cable (tried different ones) and it said the same thing. I shorted something out, the damage might just be on the micro usb PCB connector or it might be something worse. Yes I tried normal mode, no go, recovery works. So basically, my phone is now hardbricked because I'm impatient and screwed something up along the way. Now I have a 12 month warranty on the phone, can someone help me come up with a believable story that'll get me a new phone? Keeping in mind the phone boots into fastboot with (flash failure)

Trust me. The folks on the line at AT&T DON'T CARE.
Just BS your way through it. IE: I went to bed, plugged my phone in, woke up and the battery was really hot. Then the phone shut off and won't boot. Just play dumb.
All else fails. Hook that motherboard up to a car battery.
Sent from my SAMSUNG-SGH-I727 using xda premium

Fall of Enosis said:
Trust me. The folks on the line at AT&T DON'T CARE.
Just BS your way through it. IE: I went to bed, plugged my phone in, woke up and the battery was really hot. Then the phone shut off and won't boot. Just play dumb.
All else fails. Hook that motherboard up to a car battery.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I bought it from a 3rd party seller (Mobicity.com.au). I think I might just go with "The phone kept crashing every 4-5 minutes, I tried to do the system update to 2.3.6 and the phone crashed halfway through, tried to turn it on again and it showed the Moto logo and something about a fastboot". Wish me luck guys .

Okay shipped it off, wish me luck guys, I'll keep you updated.

"Technicians needed to know which ROM used to update your handset?"
Not liking my chances with this at all. I got my dad to give them a call and act dumb, should be convincing because he honestly doesn't know what he's talking about. The phone says flash failed and he's denying ever flashing anything, I don't think a failed OTA update would give that error message so I don't think they're going to replace it..... .
EDIT: Dad called the technician and the tech said he's gonna fix it and that the motherboard was fried, looking good, phew!.

Update:
Your phone has been deemed unrepairable and as a result will be replaced by your place of purchase. Please contact your place of purchase and quote xxxxxxxx to arrange a replacement handset to be dispatched to you.
Click to expand...
Click to collapse
Wooo .

[Q] Super bricked my One S? No lights or nothing

So I'm pretty sure I killed my one S trying to run the RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB update...
I had rooted my phone years ago and had CWM running, Unlocked and SuperCID but no s-off... Phone started running horribly slow (couldn't even answer calls) so I decided it was time for an update. Seemed to be limited by my HBOOT ver of 1.09 and couldn't figure out an easy way to update so I decided to just run the TMO update and reroot from there. Well the above patch kept failing so I kept reading until I heard about the fastboot oem lock command which seemed to allow the update to run. I happily waited as it ran farther than it ever had before, through the slow progress bar and everything. Took at least 30 minutes instead of 5 this time and when I finally came back to the computer said it had completed successfully. Sweet! Go to turn on my phone and get nothing. Long press the power button and vol - for minutes... Nothing! No charging lights, no screen flash, nothing when I plug it back in to the computer or wall charger. Only thing I could find I didn't try was to pull the battery, so I pulled that mofo apart and disconnected the battery all night. Still no change this morning. Any ideas before I concede defeat? I'm dead in the water w/o my phone for work and will have to order something else by tonight. Thinking used nexus 5 so I can rock Lollipop if I have to but not real happy about it.
Any help would be greatly appreciated, please and thank you

XZP goes dead everyday

My XZP goes dead everyday once. No reaction and black screen, even if the power cable is connected. I had to press both volume up and down plus power to wake it up. I wiped everything and flashed the newest official firmware without root. It still died last night. I could go into fastboot but it doesn't recognise the device so I can't flash twrp. Adb is fine. Is it a hardware issue? Do I need a new phone now? The phone is almost 3 years.... please help.

Usually when flashtool (I'm guessing that's what you meant) doesn't recognize a device it's because of incorrect drivers.
The powering off thing is weird because it's not just powering off, because if it were you'd just hit the power button to turn back on. Is the phone reset when you power back up or is everything as it was? If you're on stock firmware that should eliminate it being software. My guess it's time for a new phone. Extremely doubtful Sony will make this a Treble phone which means no android 10 and they're already working on 11, plus the whole 5G thing. My advice, new phone, not Sony.

Thank you for your reply...I don't think it's the driver because I flashed TWRP before with the same laptop. And nothing has been changed. It just didn't recognise the phone in fastboot, when I typed 'fastboot devices' it just says 'waiting for device'. After the phone was dead, it didn't lose anything...I guess you are absolutely correct - it's time for a new phone, not Sony. Maybe a Pixel would be a good choice, my original Pixel is still working fine without any problems, only the battery is not lasting as long as the XZP...

xueyaotianxia said:
Thank you for your reply...I don't think it's the driver because I flashed TWRP before with the same laptop. And nothing has been changed. It just didn't recognise the phone in fastboot, when I typed 'fastboot devices' it just says 'waiting for device'. After the phone was dead, it didn't lose anything...I guess you are absolutely correct - it's time for a new phone, not Sony. Maybe a Pixel would be a good choice, my original Pixel is still working fine without any problems, only the battery is not lasting as long as the XZP...
Click to expand...
Click to collapse
Just for the heck of it go into device manager with phone plugged in, dev mode enabled, blah blah blah and see what it says. I've had to reinstall drivers in the past. Also try disabling usb debugging then re enable and see if the phone asks you to allow debugging from this device (your comp.). None of this is going to fix the powering off but just to see if you can get your computer to recognize the phone again.

Tried to reinstall the driver again...still cannot find device in fastboot mode...maybe I'll just monitor the phone for a few days to see if it behaves normally. It did freeze again yesterday when I was playing a video...

I deleted the old driver and installed again...it is ok now. I'll flash Carbon rom now and see if the phone will go dead in the next few days...

xueyaotianxia said:
I deleted the old driver and installed again...it is ok now. I'll flash Carbon rom now and see if the phone will go dead in the next few days...
Click to expand...
Click to collapse
I tried Carbon on my XZP and had issues with the phone not seeing a sim card. I use eXsistenZ on mine. I know it's not a rom but has nice customization options and works smoothly. I'm getting to where I really don't want to mess with all the glitches of custom roms just to be able to remove crapware and see some arbitrary improvement that means little to me, and then lose the stability of stock. You can always hide the crapware, and yes it's still there, hiding, but I can live with that.

I also had same sim issue with Carbon...back to stock now. Rooted and delete the bloat. It died once last night unfortunately...I think I'll get a new phone after this Covid 19 thing, don't really want to go out now under national lockdown...time to upgrade.

xueyaotianxia said:
I also had same sim issue with Carbon...back to stock now. Rooted and delete the bloat. It died once last night unfortunately...I think I'll get a new phone after this Covid 19 thing, don't really want to go out now under national lockdown...time to upgrade.
Click to expand...
Click to collapse
I hear ya. We need more people to take this seriously.

Just an update. The phone went dead again on stock. So I flashed carbon yesterday, until now there are no issues....I shall stay on carbon now. It feels way better than stock rom.

Hmmm. That's so weird. You would think that if it were a firmware issue, that glitch would be in all XZPs running it. How did you solve Carbon rom not seeing your sim card?

bobsright said:
Hmmm. That's so weird. You would think that if it were a firmware issue, that glitch would be in all XZPs running it. How did you solve Carbon rom not seeing your sim card?
Click to expand...
Click to collapse
Until now the phone is ok. So I'd say it is a firware issue. I found out I had to wait like 2 minutes after each reboot before Carbon recognises my sim card. But, it is still better than the phone dying everyday...it runs much smoother than stock. More features too..I am happy now haha...

Excellent!!