First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
Related
Hi everyone,
Yesterday I made a Radio update to version 63.18.55.06_6.35.07.08. I made it putting the update.zip (radio rom) file in the SD Card.
All worked fine until the htc hero restarted (after appears the box with the orange arrow). Thereafter the Hero only shows the Hero logo when I turn on.
I tried to init the fastboot pressing home+power and home+back+power buttons (without SD Card and without SIM card) but always the result is the same, the logo appears and nothing happens.
The computer doesn't detects the Hero's USB connection and I can't run adb commands because it raises the "device not found" error.
Someone can help me?
Thanks in advance!
Did you let the screen with the box run its course?
Did the recovery console come back up saying formatting cache?
Have you tryed holding just back+power? ive never heard of using back+home+power
And also, i think your supposed to enter recovery with the sd in.
If that works then in that state is should be found by adb.
But yes, as the poster before me said, it should show the "unpacking" image, and then it should reboot. It should then go straight back into the recovery and the recovery will format the cache. If you tryed to turn it off at any point then, then something is badly mucked up. But it isnt bricked, and probably can be saved. Its only bricked when no logos at all come up on boot. If you managed to get it reconised by adb, you could probs format the cache manualy, though i dont know the command
All the previous steps after the breack are as you say, but after the "unpacking" image, the htc hero restarted and showed the hero logo instead the correct menu.
The problem with the adb is that the computer doesn't recognize the htc hero across usb. When I write the adb command ("adb devices") doesn't displays any device, and I can't run any adb shell for the same reason. How can I run any adb command if the device isn't recognized by the computer?
Have you tryed just taking the battery out, waiting 30 seconds, putting it back in, then booting the phone holding back+power?
And adb is very strange i find... Sometimes it reconises a phone, sometimes it doesnt, for no apparent reason. Have you tryed leaving it on the hero logo for a while then running adb commands?
If he has flashed, wouldnt the USB Debugging setting be reset also, wouldnt this be why he cannot access via adb.
Hi.
I habe exactly the same problem. I have updated radion.
Now ther come only the T-Mobile Logo and that's all.
I can not enter neither Recovery Mode nor fasbtoot does do something.
Any suggestions?
Lado
this problem shud be fixed asap because i think its a threat for all hero modders and owners as our phones get killed at anytime with this process. so guys lets try to find a solution for this problem. cheers
Updated Radio to 63.18.55.06JU_6.35.09.26 and it killed my hero.
first the box with the orange arrow came up and then the whole phone died... now it wont even turn on the screen.
please fix?????????????????
I had the box with the orange arrow yesterday after flashing radio.
The phone isn't dead, I think it's just working.
I kinda paniced also when it happend but I got into recovery eventually.
When you flash a radio it does not actually install that image until your first boot (when you see that phone out the box image).
At this point DO NOT DO ANYTHING WITH THE PHONE just wait and it will install the image and reboot for you. IT CAN TAKE UP TO 10 MINUTES.
If you turn it off or otherwise interrupt this process it can really mess up your phone. however the general rule is so long as you can see the HTC logo when you turn on i.e. it still turns on you can in theory always recover, its just a matter of finding the way that works.
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
There's a TL;DR at the end !
Hi - I hope you will be able to help me !
I have a XT910 Motorola Razr from Rogers in Canada.
I've had a Nexus S for a long time and I guess I wasn't prepared for a phone that wasn't as friendly to modding and flashing.
Before trying to flash a version of CM10 found here in the forums, I installed CWM Touch and made a nandroid backup - standard stuff.
What I didn't realize until it was too late is that booting into recovery DOES NOT boot CWM Touch - but rather the regular android one - the one that does not allow you to do much other than to factory reset.
I found out about RSD Lite but not until my battery wasn't charged enough and couldn't do anything about the phone.
I searched for the longest time on a LOT on different forums about how I could fix this and resorted to getting a factory cable - which works.
So, now, I can flash stuff using fastboot. Great, right ? Well, I still can't get things working.
RSD Lite doesn't detect my phone, and I believe that's because ADB doesn't detect it as well - so I tried that alternative way to flash fastboot files provided by the eternity project.
I've tried various fastboot packages but to no avail.
The best I can do is to get past the motorola logo - then black screen. Otherwise, I get boot or flash failures and get sent back to fastboot.
When the phone is on the black screen and that I plug a USB cable to my phone, Windows sees the device but it doesn't recognize it - I assure you I've tried all the different drivers to try and get it to work. Nothing.
Worth mentioning - I often get errors "Preflash validation failure" when trying to flash stuff.
I really feel I could fix this issue by flashing an IMG version of CWM touch or some other sort of recovery so that I can recover using a nandroid but they are no where to be found ! I can't believe that all recovery options are installed by APKs.
Any ideas ?
TL;DR, XT910 went boot looping after trying to flash CM10 - resorted to getting a factory cable and even then, can't get the phone back into working condition. Phone is detected by fastboot but not ADB.
Thanks !
first... the battery is the problem
this article can help...
How to Boot your Phone on Low Battery with Fastboot Flash Failure
To boot your phone on low battery where you get stuck on fastboot flash failure, hold down Volume Up and Volume Down then plug in “AC” USB charger to your Droid Razr. This will give you the bootloader menu upon where you can choose “Normal Recovery” to boot. If your phone doesn’t boot here, it will at least re-charge the battery normally instead of being stuck on fastboot flash failure which will re-charge your phone “very very slowly”.
Hi, first of all I love this forum, this is my first time posting here but I found it indispensable when I was doing Android development-related stuff. However I've now managed to do some damage to my phone and need some expert advice!
So I was following the instructions on the CM wiki (I can't post external links yet but the address of the page is /w/Install_CM_for_i9100) for installing CM (I'm using a Mac). I got my phone into download mode and used Heimdall to flash ClockworkMod Recovery. This is where I think I went wrong: Heimdall found the phone fine and transferred everything, however the progress bar held at 'full' for about 5 minutes. After a while I thought it must be done and just doesn't have a confirmation once it's done, so I unplugged the phone and rebooted into ClockworkMod Recovery. Recovery boots up fine but when I try to connect using ADB the phone can't be found. When trying to boot up normally I now get the warning triangle below the Samsung Galaxy logo and the phone just turns off. Booting into download mode, Heimdall can no longer find the phone when it's connected. So, since I can't boot into my stock OS, and I can't transfer a new OS or re-flash CMR, does this mean my phone's bricked? Or is this a known issue with a fix? I've tried the search function on this board but can't find this exact issue.
Since FuHu has removed the updates for the nabi2 ant otheres probably,i decided to give it a whir myself. I installed twrp 2.2.,went through some setting and in doping so somehow i have deleted the OD on the tablet. I searched and found the stock rom for the nabi2-nv7, put it on a sd card, put the sd card in, and wouldnt ya know it the version of twrp i had wouldnt read the card. I downloaded vers 2.8 and installed it, everything seeemed to be ok untill i went to slid the button to install, it wouldnt move. I rebooted, then went back into twrp once more with hopes, no deal, slider stil wouldnt work. After doing more reading I downloaded twrp 2.6 and that one was supposed to work, installed it, nowi have next to nothing. Without being plugged in to power, i can get to this screen,but anything i select will no work. Now if i plug the tablet into power, it automaticall goes into screen #2 still with no being ablee to get into anything.
Screen#1
boot normally
fastboot protocol
recovery kernal
forced recovery
Screen #2
bootloader
continue
reboot-bootloader
reboot
power off
It just keep fliping back and forth betwen thos 2 screens,it shows connected on my laptop,but try to do anything ( adb devices ) and it says no device connected..
Im thinking that the twrp's are working against one another and has meloced out in some way or another, is there any way i can wipe it all clean and start from scratch?
Any and all help is appreciated. also read wher xda has a toolkit for the nabi2, searched but not really sure what im looking for.
Thank you
Rascle