HTC Desire :: Stuck Without Fastboot - Recovery Or ROM After Failed RUU Flash
Nov 7, 2010
My Problem: Was using the HTC Desire bought in India. I rooted with Unrevoked 3.21, S-OFF with Alpharev.
I was thinking of taking my phone to HTC to show an LED burnin problem, and tried to unroot by flashing the RUU for Asia_India: RUU_Bravo_hTC_Asia_India_1.21.720.4_Radio_32.36.00 .28U_4.06.00.02_2_release_127705_signed. I thought that was the correct RUU.
I booted my phone in Fastboot, applied the RUU, and it rebooted my phone into RUU. Then it flashed an error message saying the RUU version was incorrect. Being the idiot that I am, I rebooted the phone..And got stuck!
The phone does not boot. On pressing Vol- and Power button, it vibrates, and then nothing. Screen is blank. It wont boot into Fastboot, Recovery or the ROM. If I connect it to USB and do the Vol- and Poweron, it detects my device as an Android 1.0 device.
I have tried the following:
1. Went to Android SDK, tried flashing Clockworkmod recovery image with the command:
I have an AT&T Atrix 4G and I wanted to imstall CM7.2.
I had the latest Atrix Android version on it. Then I followed the instruction at the cyanogemod wiki for the atrix. So I flashed the sbf (cyanodenmod wiki -> Motorola_Atrix_4G:_Full_Update_Guide).
The rsd lite flashing didn't succeed because the atrix rebooted and the programm couldn't switch into BP passtrougth, or so. At this point the device said something about 0x1000 no bootloader, but I could choose between rsd, fastboot and the other possibilities.
I booted into the fastboot mode and did an oem unlock. Now it says unlocked.
I booted again into the fastboot mode, and now it should be a simple
Code: fastboot flash recovery recover.img
But: Windows) it always says:
Code: sending 'recovery' (4824 KB)... OKAY [ 0.453s] writing 'recovery'... FAILED (status read failed (Too many links)) after that the device reboots and is in a boot loop
so i tried linux) The first time i tried the command everythings worked fine, but after reboot i chose.
Code: android recovery mode, but after a while (secs) the device rebooted.
so went to fastboot again, but now the device reboots after the sending command and then it says writing failed because of no device
I don't know if when I am using rsd lite to flash a complete image the phone reboots again and i have a hard brick.
I deleted /system folder on my nexian cosmic journey. And now my nexian is stuck...
I try to using fastboot mode to flash recovery image, but my device seems not detected. I already installed the android composite driver, but when i use "fastboot devices" command, it shows (?) So how the heck to get my nexian back to normal?..
Or perhaps, if i just be able to put back the /system folder to its place again, it would be more easy to recover it... But how access the root when phone is like that?
OK update failed, i have tried posting in other threads but the pace is to quick with other stuff.
i had a flashed stock phone, as took my branding off, i have since been told that you need to keep the gold card in when doing updates.
i have also tried resetting but no joy. im told i need to re flash the orginal 2.1 stock and then re do the update with the gcard in. only trouble is my phone keeps resetting on its own and i can't seem to enable hd mode on the sd card which i need
i have a HTC Desire 601 with Virgin Mobile (in canada) and i tried to flash a custom rom, and it didnt work, i got an error 7, i tried several rom and all i got is a error 7.now i want to go back to a stock rom , but every time i think i have a good stock rom, i get an error 7.
i flashed PhilZ Recovery (philz_touch_6.19.3-zara.zip is the exact filename), but i think i've done something wrong because everytime i try to flash anything, i get an error 7, even doing a nandroid backup gave me an error..
so, what should i do to get the phone to a working state?
I rooted it last week with the unrevoked 3 method which seemed to go ok then i tried some different roms and some worked some didnt. I tried to install the r8-bravo-desire-modacocustomrom-withadditions-a2sd+-signed...! This rom got stuck on the white start up screen. I thought that if i cleared the sd card it would install but still the same thing then i just got the white htc screen which i cant get off and i cant load the recovery to change anything...! The sd card is working and i can get into the hboot and when it reads the sd card says wrong img! Is there something missing on the sd card? Have i bricked my phone? Any ideas on a fix?
can you flash this before you actually root your phone so you dont get bricked?and what are the ways to get a REAL brick? because i've tried looking and everyone has gotten either a usb brick or something else where they can just reflash or something.
i recently installed open etna which was awesome (great job guys) But then stupidly i plugged it into my computer and LG update popped up saying their was an update stupidly i clicked yes. God knows what i was thinking. now my phone wont get past the default android loading screen. I have left it on for days and the animation just keeps replaying over and over again. I can't access fasboot either to re-flash it back to open etna or whatever.The only thing i can get access to is emergency mode is there anyway i can get my phone working again?
I have read other tutorials about the fastboot update command, but I do not understand how to make system.img from a zip Rom. How to install a Rom with fastboot? Cwm recovery can't read zip files for some reason.
HTC sensation blackscreen, trying to flash a nand backup. ADB, fastboot and Shell working.
I got into shell, can #ls that directory ok ..#cd sdcard... try to #ls sdcard or any other folder and will not show content. Im not up with linux commands. I believe I am missing a mount command somewhere.
What Im after is the location of backup folder so I can see the filename of the nand backup to restore in fastboot. And the commands necessary to restore a nand backup via adb, shell or fastboot.
When I was trying to get Clockwork Mod sorted for my Huawei u8160 phone I accidentally chose to flash it with the official Clockwork mod for the Huawei u8150 stupidly misreading it as my own phone and now it has left me with an unusable recovery so I can't install any new recovery or ROM's or anything, I am getting almost constant errors whenever I try to run my phone saying whatever process has stopped working and that I need to force quit it. I have tried to start it in fastboot or whatever it is called but all I am getting is a screen that says "firmware update step 1/2 unpacking update failed", I have tried to start with many different key combinations but nothing is working.
My Galaxy Nexus won't boot with the power button and I don't think my volume down button works either. There is also a pattern lock I don't know so I can't get into the OS. Is there anyway to wipe/fastboot/enter ADB without the power button or without needing USB debugging? Or is there a way to turn on USB debugging without getting into the OS?
I used insecure boot and root trying to root my phone, which was a huge mistake as i noticed a few minutes later since i cant startup anymore and only get into bootloader.
Now I'm trying to flash my stock rom back.
My CID is VODAP102 and my Version is 220.127.116.11 so i downloaded the rom and tried "fastboot flash boot boot.img" the result is: sending 'boot' <8192 KB>... FAILED <data transfer failure <Unknown error>> finished. total time: 0.158s
I hit the top button. Flash Clockworkmod recovery or what ever it said. I then backed up my Current ROM. I then downloaded Cyanogen v6.0.0 cr2. It downloaded and rebooted my phone. But It went to a screen with a Triangle w/ exclamation and a phone under it. I then hit the up vol button and camera, and now I'm at the Android system recovery page and I don't know what to do next. These are my options reboot system now apply sdcard:update.zip wipe data/factory rest wipe cache partition wipe base band data. I did click to backup current ROM and wipe data and cache.
I should have just left it as it was out of the box..So after attempting to install a custom rom (4.4.2 Play edition)my s4 is stuck at the Samsung I9505 boot screen. I wiped the 'Dalvik cache' 'System' and 'cache' partitions in TWRP as I was following along with a Youtube video (that didn't work). When I tried to flash the custom ROM it automatically said failed. After giving up and turning on the phone I found that I'm stuck at this screen.
Have I bricked the phone? $550 could have gone down the drain just like that. I don't want to touch it without any advice and make everything worse. My only hope now is that I've managed to wipe the original software and it has nothing to boot from.
Why did the ROM install fail in the first place? I had it copied on the SD card. It was zip file.I can still access TWRP just fine and my SD shows up with the custom ROM still there, it's just whenever I hit install it fails in under a second.
Android Version: 2.1 (Doughnut?) Network: T-Mobile Issue: I'm having a little trouble connecting to my phone using adb when it is booted into fastboot (from an XP machine). Basically my phone has stopped booting correctly (it just loops infinitely between the HTC and TMobile splash screens), and I'd like to use adb to have a look around and see if I can fix the problem. If possible I'd like to avoid a factory reset.At first when I plugged my phone into the pc via usb it popped up a 'Found New Hardware' saying it had discovered an 'Android 1.0 device', and asked me for drivers. The drivers I got from HTC Synch weren't recognised, and after a little playing around I realised the USB Bus ID listed for a HTC Desire phone in the .inf file for the drivers did not match the actual ID for my phone reported by windows. After I fixed that the drivers installed correctly and the 'Found New Hardware' box stopped popping up when I plugged my phone in.Unfortunately adb still didn't detect my phone, and neither did HTC synch. Also, when I tried to access the SD card on the from from the generic Mass Storage device added into explorer it popped up an 'insert disk' box and wouldn't let me access it.Has anyone else had this problem, or have any suggestions on how to fix it? Should I be able to connect to the phone using adb when it is in fastboot? I've seen several examples on the net where people claimed to have done it so I'm assuming you should be able to. Very last resort before I give up and factory reset the phone.If anyone's interested I posted earlier describing the infinite-loop problem here: No Space Left On Device
Friends of Jupiter Huawei g525-u00and have been asked Ram Kastvm able but Alanmshkl. Already green screen after power ... not that fast boot mode will not go into recovery mode and not the original ROM using loam bottom half Vbala White gets going
I was playing around with my phone today, just trying to create a cool symmetrical pattern on my droid. Mind you this was just on the screen where after about 5 tries it locks you out for 30secs. So i keep playing around with it and than the email and password screen shows up, saying i have to log in. Alrite sure, so I just put in my credentials and it fails.
Things I have tried: 1. @gmail.com, @googleemail.com 2. password null 3. case sensitive 4. playing around with people calling me and emergency dialer, etc. 5. changed password 6. battery pulls..............
i have a samsung galaxy S3 with t-mobile. i recently updated to jelly bean 4.1.2 and disliked the new gallery and a couple of other new functions so i decided to downgrade. i dl odin v. 1.85 and jelly bean 4.1.1 and started the process. it failed and when i reboot my phone the triangle warning about putting it in kies emergency recovery mode pops up whenever i turn it on regularly. i can go into the downloading menu so i know its not bricked or completely ruined but i don't know what to do from here. i did follow the phone instructions and dl kies and try getting into emergency recovery mode but it wont recognize my phone. i tried another Samsung phone and it picked it up right away.
I've been trying to go back to barebone 2.1. Im running 2.1 but have themes installed. I ran the fab theme killer and still have aspects of the last theme stil hanging out like the themed facebook and themed power control widgets. I tried to sbf flash it and failed.