Does anyone have this problem? I`ve searched and cant find a solution.
I had sense rom on my phone then decided to go back to jboogie rom. I booted into stock recovery(power+vol down) and when i tried to tap bottom right of screen the screen wouldn`t respond so I couldn`t do a factory reset. I then tried volume up=power button to flash sbf through RSDlite. Nothing came on my phone screen telling me to attach usb, it juat stayed blank, although rsdlite said phone was connected so i started to flash sbf anyway. Then on the phone screen it said software update in progress, once it finished flashing, instead of saying rebooting phone on RSDlite it came up with "pass" and the phone wont boot or do anything at all now.
Sorry for long message, but hope someone can help.
Thanks
Mark
try to flash a stock rom sbf with rsdlite and after that, do a wipe in recovery mod. to enter recovery press power+ vol down, after the droid apears, push vol up+vol down. You have to see then the stock recovery menu. I did in the same way and is working. I think is now so easy to really brick this phone.
Thanks for your reply, unfortunately when I try to get into stock recovery by pressing power+volume down I dont get anything on the screen at all anymore, nothing happens. Its the same when I press power+volume up to try to flash it too.
not even white led?
maybe your battery is 2low?
if u see the white led u can still go into bootloader and flash .sbf with rsd lite
Hi there,
I can't believe its dead!!
I have tried every rom available and tried out all the .sbf's too. A couple of times i thought i have bricked it but it was always done to user error (or a lack of understanding at times on my part). These Defy's seem to be almost bullet proof!
I had the "pass message" from RSDLite and all i had to do was flash the "2.2 bootonly" sbf to get past it. I have had corrupted boot loader messages and more but it just keeps coming back for more once things the right things are done in the right sequence.
Assuming your battery is ok, I would try installing one of the latest froyo .sbf's with RSDLite 3.9 only completion do a wipe from the stock recovery (hold pwr + vol down). Press vol up and vol down to activate the menu, select wipe with volume up or down, press power to go. The after rooting apply one of the excellent roms from Jboogie & Pays.
Good luck... sure it will be fine.
Andy
qpzmaluk said:
Thanks for your reply, unfortunately when I try to get into stock recovery by pressing power+volume down I dont get anything on the screen at all anymore, nothing happens. Its the same when I press power+volume up to try to flash it too.
Click to expand...
Click to collapse
If you have only black screen, you have to flash the latest undowngradable rom you flashed, then you you finally get to moto logo, you will be able to go to recovery and wipe. After it it will boot just fine.
I had the exact same problems, i tried to reflash. It ended up not showing anything on the screen in any of the button combinations. It did however show in RSD Lite and after i tried to flash the chinese rom it said "pass" after that i only got a white led and it no longer was detectable through usb. I tried to recharge the battery so i left it on white light with charger plugged over the night... No success. It's now in service and hope they fix it.
I would like to point out to anyone trying to help me that bootloader no longer shows up, neither recovery menu.
astearon said:
I had the exact same problems, i tried to reflash. It ended up not showing anything on the screen in any of the button combinations. It did however show in RSD Lite and after i tried to flash the chinese rom it said "pass" after that i only got a white led and it no longer was detectable through usb. I tried to recharge the battery so i left it on white light with charger plugged over the night... No success. It's now in service and hope they fix it.
I would like to point out to anyone trying to help me that bootloader no longer shows up, neither recovery menu.
Click to expand...
Click to collapse
I had a similar thing when i flattened my battery half way through flashing an .sbf. I borrowed a friends battery, flashed the boot only and all was fine. There is a couple of pointers on the forum on how to charge your battery if you dont have a working rom (it wont charge without one! You have to get the motorola logo followed by the battery animation to charge your battery).
In your case im pretty certain you could have saved yourself the hassle of sending it off for service.
Andy
Thanks for all the replys, I have already had the dead battery a couple of weeks ago and "revived" it by putting the + and _ wires of usb cable into the battery of the defy, but this seems different, I cant get anything to work on it, no roms will flash and all I get is black screen. I do get the white led but only sometimes. It is very change indeed, I will try some of the solutions you guys said tomorrow and let yous know how I got on.
Thanks again
Mark
I did not want to risk charging out of wires, i have unlimited warranty on it after all so i gave it to service hoping a fix will be made by guys who know what they where doing (i hope).
In any case i see -qpzmaluk- tried off of wires and nothing happened.
I tried to flash again this morning using all the techniques above but I cant get rsdlite to recognise my phone either now. All i get is when connected to usb is the white led, nothing else happens when i try to go into recovery etc.
Mark
Huge thanks to EDITION I got my phone working again.
I did what he said about flashing last undowngradeable rom and surprisingly it came back to life. Brilliant mate, i cant thank you enough.
Mark
how did u do that? if u said your rsd lite cant recognize your phone?
I kept trying to connect to pc with usb and rsdlite eventually found it so I took the chance of flashing froyo 3.4.3-the one I last had on the phone, and surprisingly this time it went throughht to the end of booting the phone and now I have everything working again including stock recovery etc.
One thing to mention was that I couldn`t get into pwer+vol up or down before I flashed this time I flashed my phone. I just connected it to pc and luckily rsdlite recognised it this time and I just pressed flash button, then eventually phone booted up. So something was wrong and it didn`t flash it the normal way by going into stock recovery on phone but it worked
Related
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!
So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.
tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!
it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2. The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
strabo231 said:
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2.
Click to expand...
Click to collapse
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
Click to expand...
Click to collapse
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
Click to expand...
Click to collapse
sd_shadow said:
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
Click to expand...
Click to collapse
Ah Shadow! I was hoping you'd see this. Let me clarify a little bit.
1. I am able to get phone to boot into OS. I did try to install the update.zip already but I'm still having the same problem with the boot loader.
2. I know about the easy sbf, and tried that with this particular phone, but because of the problem with the boot loader when easy sbf or RSD Lite switch the phone, or attempt to switch into flash mode, the computer no longer recognizes the phone.
3. I did think about rooting the phone to try to open up a few other options to at least get around the problem. Since it's on .629 already though I'm limited to rooting using easy sbf as far as I've understood, but again since I'm having the issue with the boot loader that hasn't been an option I have been able to successfully use.
4. The power button on the phone isn't working, so I'm unable to use the key combo to access the boot loader; however, I have a factory cable...now I say factory cable not meaning the stock charging cable...but the 5-wire factory cable. Typically with Motorola phones using this cable you simply remove the battery, and then with no battery in the phone hold down both volume buttons and plug the factory cable in and it automatically reverts to the boot loader.
I know that there is a consumer replacement boot loader for the droid 1 to fix issues like this, but I haven't seen one for the two. The other issue is that the replacement is an sbf file which ill be unable to use, and didn't know if that was something that would exist as an update.zip that could be flashed through the stock recovery
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
sd_shadow said:
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
Click to expand...
Click to collapse
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
sd_shadow said:
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yeah I tried that last night. I saw where you were having problems with it too. I had seen where a few months back there was someone else that was having this issue that you were trying to help walk them through, but the thread kinda died off, so I wasn't sure if there was ever a resolution to it. Ok well thanks for your time. I'll be sure to post an update for people coming behind me if I manage to get anywhere with it.
strabo231 said:
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
Click to expand...
Click to collapse
if you are still working on this a Bootloader Only
HS_S_signed_AP_BL_D11_cdma_droid2we_Consumer_replacer.zip
has been posted here http://sbf.droid-developers.org/cdma_droid2/list.php
If you're still looking to root, try Framaroot from here. It worked for me on .629. No idea about the bootloader however . Good luck though!
I wanted to make a clean start on my phone after flashing way too many ROM's, so I RUU'd via HBOOT using a .zip on my Ext SD card. I used Dottat's 5.0.1 file. Everything seemed to work fine. Once I got up and running and rebooted, I went back into my bootloader (vol - + power) and did a factory reset. Everything worked smoothly and I got through first boot to the setup screen. At this point I wanted to install enewman's 5.1.1 GPE ROm then upgrade to the 6.0 Marshmallow build I had just been running. I powered down the phone and went back into bootloader. I selected Recovery and pressed power button to select. Phone turned off and never rebooted. And now I can't get it to turn on at all. I've tried holding power button for a long time, power + vol up, power + vol down. I get no bump, no lights, no nothing. When I plug it in to a charger I get no charging symbol.
Is it possible that when I RUU'd I removed my TWRP recovery, then when I tried to boot into recovery it got lost? A few things that might help - I am S-OFF, and I did notice right before I tried to reboot that the phone did say it was still unlocked.
Can anybody please suggest a fix? Or do I have a fancy paperweight to gift someone with this holiday season?
Thanks in advance for your help.
bdyer said:
I wanted to make a clean start on my phone after flashing way too many ROM's, so I RUU'd via HBOOT using a .zip on my Ext SD card. I used Dottat's 5.0.1 file. Everything seemed to work fine. Once I got up and running and rebooted, I went back into my bootloader (vol - + power) and did a factory reset. Everything worked smoothly and I got through first boot to the setup screen. At this point I wanted to install enewman's 5.1.1 GPE ROm then upgrade to the 6.0 Marshmallow build I had just been running. I powered down the phone and went back into bootloader. I selected Recovery and pressed power button to select. Phone turned off and never rebooted. And now I can't get it to turn on at all. I've tried holding power button for a long time, power + vol up, power + vol down. I get no bump, no lights, no nothing. When I plug it in to a charger I get no charging symbol.
Is it possible that when I RUU'd I removed my TWRP recovery, then when I tried to boot into recovery it got lost? A few things that might help - I am S-OFF, and I did notice right before I tried to reboot that the phone did say it was still unlocked.
Can anybody please suggest a fix? Or do I have a fancy paperweight to gift someone with this holiday season?
Thanks in advance for your help.
Click to expand...
Click to collapse
An RUU unless edited will have stock recovery in it..
As to why it won't turn on - what was the battery at, could it have died? Their are some sites online to try and get your battery to charge if it dies. Try plugging into USB computer for 24h with phone off was one I read at some point. Best of luck.
andybones said:
An RUU unless edited will have stock recovery in it..
As to why it won't turn on - what was the battery at, could it have died? Their are some sites online to try and get your battery to charge if it dies. Try plugging into USB computer for 24h with phone off was one I read at some point. Best of luck.
Click to expand...
Click to collapse
Thanks @andybones, I was hoping someone like you would reply (I've been following your work since running BoneStock on my SIII - we have similar taste in stripped down OS's). There should have been plenty of juice on it, I think I was in the 60% range last time I booted. In fact, the phone was plugged into the charger when it died. Yeah, really concerning that I get nothing at all...
Anyone else have any suggestions? Thanks in advance...
bdyer said:
Thanks @andybones, I was hoping someone like you would reply (I've been following your work since running BoneStock on my SIII - we have similar taste in stripped down OS's). There should have been plenty of juice on it, I think I was in the 60% range last time I booted. In fact, the phone was plugged into the charger when it died. Yeah, really concerning that I get nothing at all...
Anyone else have any suggestions? Thanks in advance...
Click to expand...
Click to collapse
What steps have you taken thus far as to rule them out?
first check out this link and try this
also check out this link about fixing the charging logic
https://www.ifixit.com/Answers/View/219029/Device+will+not+power+on+after+battery+ran+dry
Also could call HTC, they may send you a new device, which sucks but better than nothing.
andybones said:
What steps have you taken thus far as to rule them out?
first check out this link and try this
also check out this link about fixing the charging logic
https://www.ifixit.com/Answers/View/219029/Device+will+not+power+on+after+battery+ran+dry
Also could call HTC, they may send you a new device, which sucks but better than nothing.
Click to expand...
Click to collapse
Thanks for the suggestions. I held pow and vol+ for 10 seconds, pow and vol - for ten seconds.. I held pow and vol + and vol - for two minutes. No joy. I called HTC, they were super nice and very helpful, but unfortunately none of their suggestions helped. They had me plug it into my pc to see if it registered, had me do the pow and vol +/- for two minutes. After that, they recommended I send it in for repair. Unfortunately, since my phone is out of warranty, they said I would need to pay for repair.
I filed an insurance claim, got a new one coming Friday. Gotta refresh myself on getting s-off... Thanks again for your help. If anyone else has any suggestions (or questions), wouldn't be a bad thing to repair the phone and have a spare waiting in the wings... Is there a way to change the IMEI in case I can repair the old one? :silly:
Happy Thanksgiving, all!
Good Morning,
yesterday when i flashed a rom, something goes wrong.
My opo don't go in boot animation and work only the recovery and fastboot.
I don't know why but afther another reboot the phone is dead, i think that is a normal hard brick so i try to restore with the tool "msm8974 download tool" but it don't work, when i start the restore come out a red word.
I never seen a hard brick like this, the phone is 100% dead , when i press the power button don't vibrates and nothing come out, diplay is black.
What can i do to restore my opo? :crying:
Try Wiping everything from TWRP and try a different ROM.
Another thing to try is connecting ADB to get the logcat.
Can you give more details on what you've tried so far?
Additionally, I remember reading that the OPO can stop booting correctly when the battery starts failing.
umer936 said:
Try Wiping everything from TWRP and try a different ROM.
Another thing to try is connecting ADB to get the logcat.
Can you give more details on what you've tried so far?
Additionally, I remember reading that the OPO can stop booting correctly when the battery starts failing.
Click to expand...
Click to collapse
Now the phone is dead, if I press the power button nothing come out (no vibration, no screen) the phone look like without battery! (But it is over 50%)
I followed the tutorial to restore HARD BRICK with the tool but it don't success!
ghibli2 said:
Now the phone is dead, if I press the power button nothing come out (no vibration, no screen) the phone look like without battery! (But it is over 50%)
I followed the tutorial to restore HARD BRICK with the tool but it don't success!
Click to expand...
Click to collapse
Me to.. this morning my phone dead.. i dont know what can i do again..
Trying pressing all combination button not showing anything even in pc device manager usb not recognize or qhsusb_bulk not appear
Anyone can help me please.. @netbuzz
I have bricked this phone in and out, believe me lol all you gotta do is open the phone, unscrew all (TOP HALF) screws and UN plugg battery......wait about 30 sec RE plugg/connect battery and re run the unbricking tool