Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
adix631 said:
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
Click to expand...
Click to collapse
Don't panic brother. I've been in a similar situation many times. Whatever you do... DO NOT PULL THE BATTERY till the phone is switched off!!
Just disconnect the phone from the laptop or wall socket (remove the usb cable from the phone) and leave the phone. Don't sit and stare at it, and don't try to reason it into rebooting. Also, stop pestering God...he doesn't do phones. (I think) Just relax, and go watch T.V. or something.
One out of two things may happen :
1. It may reboot on it's own. Has happened to me... Sometimes it happes in 5 mins, sometimes in 20, and sometimes, never.
2. The battery will eventually run out of charge and your phone will switch off by itself. Now remove the battery, reinsert after 2 mins and boot up into recovery. From here, you can restore your previous nandroid backup.
P.S. If you do not have a nandroid backup, just reflash the ROM after a full format ("format all partitions, except sdcard" option in recovery). Note that if you have unlocked using HTC site, this will not work until you manually flash boot.img (you can find it in the ROM (Reaper_v1.2.zip) file) from fastboot.
Let me know what happens.
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
adix631 said:
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
Click to expand...
Click to collapse
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
enigmaamit said:
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
Click to expand...
Click to collapse
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
adix631 said:
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
Click to expand...
Click to collapse
Well in that case, don't worry your phone is safe. Just wait for it to switch off. Then after booting into recovery, just restore the last working ROM backup that you have. Don't flash the Reaper 1.2 that you downloaded till you have confirmed that the md5 checksum matches the one posted by Lowveld.
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Can you still boot to recovery?
adix631 said:
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Click to expand...
Click to collapse
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
enigmaamit said:
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
Click to expand...
Click to collapse
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
adix631 said:
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
Click to expand...
Click to collapse
Well, it that's not workin, Wait till the phone switches off again. Then configure adb, make sure it detects your device (use the command: adb devices) and then type the following at the cmd prompt :
adb reboot recovery
This should take you to recovery.
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
adix631 said:
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
Click to expand...
Click to collapse
You're welcome brother! And Congratulations!!
I know what you must have gone through till you reclaimed your phone. I remember the first time i was in a situation like yours... had to figure out this discharge the phone, LED blinking etc... thing on my own..., everyone else said battery pull was my only option. But i sitll didn't do it. I had around 60% battery remaining before this happened, so you can only imagine how many sleepless hours i spent waiting for the damn battery to run dry. http://forum.xda-developers.com/showthread.php?t=1271360
The important thing is to resist the temptation of pulling battery. Everything can be salvaged if you don't do that, but once you fry your eMMC, there is nothing anyone can do without physically repairing the phone.
May I suggest you edit the topic your OP and add the word [SOLVED] to the title. This will ensure anyone in trouble can easily locate this thread out of the cacophony on xda!
Wife was running CleanRom 2.1 for a week or so. Yesterday she goes to wake the screen and the phone wouldn't wake by pushing any buttons. She pulled the battery and tried to boot the phone with no success. At this point we are stuck with the attached (IMG_01.jpg) image when plugging the phone into a USB port. Plug it into the wall charger and you get the same image however leaving it on this charge for a while brings IMG_02.jpg. Unplugging the phone from the cable results in no power at all to the device. This means no Download/Recovery Mode from battery only.
On to plugging into the computer. By quickly inserting the cable and pressing the keys to enter Download mode i can successfully enter Odin mode and flash files. From here i have flashed full stock images and still no full boot success.
So, next I can boot into recovery (sometimes, again only plugged in) I was able to wipe following stock odin flash. After rebooting from recovery i can see the samsung and galaxy sIII boot logos then the stock VZW 4GLTE boot animation(with sound). once i get to the language select screen and move to activation the phone shuts off and goes back to the empty battery with a circle in the center (IMG_01.jpg).
So far I have tried:
1. Different USB ports/cables - Incl. OEM (connection appears to be fine to the system either way though)
2. Flashing full stock images in odin with PASS results.
3. Ive tried to unbrick using the methods found here: http://forum.xda-developers.com/showthread.php?t=1840030
Im looking for any help or suggestions on moving forward here. Overall there is no power to the device without plugging in the cable. I have tried another battery still with no power. I have thought about flashing the insecure bootloader however i have not found a way to do this in Odin if it is possible at all.
ODIN MODE (Reads as follows)
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLED
Thanks in advance for any help at all. If you share a similar problem please post as well, may help narrow down the cause and eventual fix.
With my ability to access ODIN MODE and boot to the setup screen, does this mean i have a good chance at recovery?
Looks like you might have a bad battery.
I tried another battery and that's not working.
This morning I had a green LED (charged) light. I woke the screen to the lock screen and it seemed to stay on. I couldnt get past the activation since the sim is no good. ( I had to deactivate it with vzw to activate a temp phone.) I eventually pulled the plug to see if it would hold charge but it just shut off and I wasn't able to boot up again.
The same thing happened to my first s3. You will need to get a replacement.
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Pra7ul said:
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Click to expand...
Click to collapse
adb reboot bootloader
waterdaan said:
adb reboot bootloader
Click to expand...
Click to collapse
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Pra7ul said:
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Click to expand...
Click to collapse
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
noahvt said:
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
Click to expand...
Click to collapse
Even If my volume button dosent work then why wont it enter bootloader via advance reboot it just restarts to system after selecting reboot to bootloader,so i should hard brick my device once again, P.S. i have done that twice before though.
I recently updated Magisk from 16.0 to 17.1. The installer asked to reboot after finishing up. After rebooting, however, the phone gets stuck on boot animation. I've tried to let it run all night and I've tried charging/discharging a few times. The bootloader is still unlocked (the opened lock icon shows up under the Google logo on boot). I can't get into recovery/fastboot mode: Holding power+volume down turns on the phone but gives a black screen with backlight on. My computers also don't recognize the phone. I haven't found any similar issues here while searching so I am at a loss on how to fix it.
Possibly related: Charging the phone has been weird for a few months: the charging LED indicator only turns on when the phone screen was on. It seemed to charge slower compared to previously and the OS doesn't recognize that the phone is charging.
With the phone off, hold the volume down button and connect the phone to your computer. This may force the phone into fastboot mode.
Thanks for the advice! Although that didn't immediately work (it still booted to a black screen w/ backlight on), I tried one or two more times to boot holding down volume down + power with the phone unplugged. I got lucky somehow and it finally booted to Fastboot. From there, still neither my MacBook nor my Windows computer recognized my phone (nothing in device manager). I booted to TWRP, and saw that Magisk had .zip's of previous versions stored in /sdcard/MagiskManager. I flashed the last working version, 16.0, wiped Cache and Dalvik, rebooted and finally got through boot animation.
Time to backup!