Develop Bugs

help please my evo won't power on

ok here's the story i was flashing a new rom to my evo and after i rebooted it it gave me an icon of a little android man with an arrow coming out of a box and when it went away the phone would not come back on, it still gets power and when connected to a computer it tries to install a "Qualcomm CDMA Technologies MSM" but nothing on the screen of the evo, i can't boot into recovery or anything the screen just stays blank, is it dead or can i fix it somehow?

take the battery out, put it back in, then reboot
*not liable for this advice, but has worked for me.

Tried that no luck tried with just the power cord no luck tried both no cigar it just doesn't do anything
Sent from my SPH-M900 using XDA App

i think there might be possible for you to put your SD card in your computer, copy over the PC136img zip, then reboot into recovery and flash it so you can get back to working.

cabbieBot said:
i think there might be possible for you to put your SD card in your computer, copy over the PC136img zip, then reboot into recovery and flash it so you can get back to working.
Click to expand...
Click to collapse
But he/she said he/she can't reboot into recovery...
marvelouswonder8 said:
ok here's the story i was flashing a new rom to my evo and after i rebooted it it gave me an icon of a little android man with an arrow coming out of a box and when it went away the phone would not come back on, it still gets power and when connected to a computer it tries to install a "Qualcomm CDMA Technologies MSM" but nothing on the screen of the evo, i can't boot into recovery or anything the screen just stays blank, is it dead or can i fix it somehow?
Click to expand...
Click to collapse
What ROM were you flashing? What root method did you use? Are you fully unlocked (+NAND)? These are all questions we need answers to before we can help.

Yes I was fully rooted nand and all, I used the latest clockwork recovery to flash the new cm6 and followed all the install instructions on the forum exactly (wipe data wipe cache flash latest radio etc) after I flashed the rom I hit the reboot to system button and it showed me the box with the android guy coming out of it when that went away I couldn't get the unit to start up at all
Sent from my SPH-M900 using XDA App

Can you connect it to your compter? Will adb recognize the device? If so, it may be possible to issue the 'adb reboot recovery' command and restore your NAND backup. If not, I don't know what you can do.

when i hook it to the computer the only device that it recognizes is the "qualcomm CDMA technologies MSM" which i haven't been able to find a driver for i had the adb driver installed on my computer and it doesn't recognize when plugged in

Ok so I did some digging and found a driver that loaded up no problem for the qualcomm device, it was an adb device and in device manager it said it was running fine but when I went to issue the adb reboot recovery command adb returns that there's no device connected I tried several other drivers as well with the same results best I can figure somehow the only portion of the phone that's receiving power is this one device as my battery was completely dead when we tested it in my friends evo (charging it then transplanting to my evo didn't work either) so it looks to be dead
Sent from my SPH-M900 using XDA App

I had a similar issue when I installed CM6. Hung at the boot screen. I was able to boot into recovery using ADB. I don't think the computer showed that the phone was connected...I don't remember though. Try to run reboot recovery from ADB again. My second install attempt worked perfectly...loving CM6!

Try to instal the original ruu from your computer.
Sent from my PC36100 using Tapatalk

This is an older thread but just happened to me (updated radios) so I googled it. I tried rebooting many times with the volume down but would not go into recovery. Same qualcomm thing while I was reading this thread it magically booted. All I had to do was wait a couple of minutes (no more than 5). I panicked because of the screen but its all good.

fully rooted - now mt3gs wont show in adb

i have done the complete root process just fine
and now i can not for the life of me get my phone to show up in adb
i have tried literally like 100+ times for hours on end over the last weeks
and it hasnt worked a single time, did just fine before, now it hasnt one time the last hundred times i have tried
i try everyday for about a half hour and it hasnt worked in weeks
has anyone else had this issue??

While booted or while trying to get in to recovery?
If while booted, turn USB debugging on.
If recovery, just flash the engineering image and save yourself the hassle.

all it does is show up for a spilt second when running the loop
and it never sticks even just at offline so you can plug and unplug usb to show recovery
and usb debugging is on

ParkerOviedo said:
all it does is show up for a spilt second when running the loop
and it never sticks even just at offline so you can plug and unplug usb to show recovery
and usb debugging is on
Click to expand...
Click to collapse
As I said, since you are already rooted flash the enineering rom. Then you don't have to try and the loop to work ever again.

Yeah but how do you flash the engineering build without adb?

ohhdavid said:
Yeah but how do you flash the engineering build without adb?
Click to expand...
Click to collapse
adb should be working while booted normally. You don't need to get in to recovery.

Yeah but (I think) his problem and mine is that the phone won't show up in adb during normal operation
One note for mine is that tmos update notification is up there in my notification bar.. perhaps that affects it?

[Q] Bricked?

I wouldn't consider myself a newb and I did read up on how to successfully root my galaxy nexus, but mine did something weird. I was using the GNex Toolkit V6 to root it. I went to unlock my bootloader and my computer tried to install the driver for the bootloader and it failed. The toolkit still said <waiting for device>. The phone wouldn't allow me to do anything in the bootloader. I pulled the battery and now it won't turn on, bootloader, etc. My computer does recognize the phone and tries to install OMAP4440 driver, and fails, but it constantly connects and disconnects.
Any ideas?
I saw somewhere where someone said something about a faulty sd partition.
Edit: I let the phone sit without the battery in it for about 5 minutes and it turned on. Any thoughts on that?

Same happened to mine. I didn't even use Toolkit. I was on CM9 and just used the reboot to bootloader option, it shut down and never turned back on. I've sent it back for a refund and have yet to hear from them. I hope they give most of my money back, if at all. If not, I still have the right for a repair.

This is the reason why I don't use tool kits.
If you can get to the Google screen it's not bricked. Just use the traditional way with the android sdk and fastboot to flash a stock Google image.
Sent from my Galaxy Nexus using XDA

[Q] Kindle Won't Turn On

So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?

philip1192 said:
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Click to expand...
Click to collapse
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again

Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

persano said:
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Click to expand...
Click to collapse
I'll try that and see if it'll help.
mindmajick said:
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is that a problem?

Other than voiding the warranty since you opened the device... And removed a battery not meant to be removed? Naaaah
You should NEVER have to pull the battery on ANY android device.
Edit: couple more things
1. As long as you are USING the device it won't charge on USB to PC. Always better to charge off a wall outlet. MUCH faster charging too.
2. NEVER flash a ROM if your battery is low.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.

philip1192 said:
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
Click to expand...
Click to collapse
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
How was it not actually unlocked?
Hopefully someone can...

philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163

philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

soupmagnet said:
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
Click to expand...
Click to collapse
Well, they're lame. I like HTC better.
mindmajick said:
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I guess I'll see if I can make that work. If not, I guess I have an expensive paperweight on my hands...

Need help. accidentally wiped os after flashing recovery and now have trouble

So I have had this device since February and finally decided I wanted to Unlock the bootloader, install a custom recovery and get some cool new roms on it. I have the GPE by the way.
Anyways so I unlocked the bootloader and flashed TWRP and then rooted the device by flashing a zip file for root. I assumed the tablet got rooted so I then decided to try the multi window hack and flashed that. Well it caused some apps to corrupt (the phone app in particular) and they would keep crashing preventing me from doing anything. I decided to go back into recovery and try to do a data and cache wipe but that did not help. Eventually I wiped the entire OS which was a mistake. I was still able to get into recovery mode but I have no SD card to load up with a rom to flash and it was late to go buy one. I also tried ADB through the recovery mode that did not seem to work.
I did some searching and found out that I could download the LGMlauncher and it could get me back to stock but to use that I needed my serial number which is on the box (which I had at the office). So I plugged it in (and got the little battery icon) and a few hours ago went to the office to get the box. I tried the LGMlauncher and it keeps on crashing while trying to update and now I am not able to get into recovery mode. What are some other steps I can take to try and recover it?
Thanks.
Edit: I tried the LGMlauncher again and it said my battery was low so I plugged it back in. is there a trick to charging it while it is off? I assume that could be why recovery mode wont work.

Hi, if you have twrp recovery and it is working you can install your missing system by following this post
http://forum.xda-developers.com/showthread.php?p=53744333
Good luck
Sent from my LG-V510 using Tapatalk

schalmers said:
Hi, if you have twrp recovery and it is working you can install your missing system by following this post
http://forum.xda-developers.com/showthread.php?p=53744333
Good luck
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
Yeah It appears as though the battery was not charging even though I had plugged it in and now it is dead. I cannot seem to get it to go into recovery or anything. Is it safe to say it is bricked?

When my HP Touchpads battery was to low to take a charge from the wall charger, the only way it could get enough charge to be able to use the wall charger was to trickle charge it from my computer usb port for a couple of days.

Jubeldum said:
When my HP Touchpads battery was to low to take a charge from the wall charger, the only way it could get enough charge to be able to use the wall charger was to trickle charge it from my computer usb port for a couple of days.
Click to expand...
Click to collapse
Yeah it has been plugged into my PC for a few days and nothing.