Hi,
I've been trying to install different images to a HTC Wildfire. As some apps were unavailable at the marked, I tried to got back to 0001_WildPuzzleROM_v8.0.8.zip.
Thing is, the phone has a bootloop. I cannot enter the recovery. Pressing POWER+VOLDOWN does not start the recovery. Other button combindations don't help. As soon as the green robot comes up, POWER+VOLDOWN+TRACKBALL result in immediate reboot. I tried a replacement of the SD-Card, no SD-card, and no SIM. All of this does not help.
In the BIOS-Bootscreen, there is "press the TRACKBALL" written. But the TRACKBALL does not work there, too.
Checking with ADB yields an unknown device with no permissions.
Is there any chance to unbrick the phone or is it finally dead?
TYIA
dsplayer
Related
Can't find info on this anywher but bought a phone off ebay and just boots into recovery mode. Can't get into bootloader mode to dreaming.nbh the thing. Is this considered bricked? i can get to recovery mode. i hit alt + L and i have the factory recovery system. at the bottom it does say E:Can't open /cache/recovery/command ... HELP PLEASE
I'm having the same EXACT issue. Haven't found a solution yet.
I'm going to bump this.
I've researched the last 4 hours about how to restore the G1 and all of them require the phone to enter into the bootloader (gray screen). I can not for the life of me get my G1 into the boot loader. It has no water damage that i know of. If I hold Home + Back + power I can get to the HTC erase phone thing but nothing responds.
Camera + Power does nothing other than turn the phone on and it goes into recovery mode.
Maybe an official bootloader in an update.zip format?
Tried all 3 here:
http://forum.xda-developers.com/showthread.php?t=455860
They all get verified and installation starts but then it aborts installation immediately.
Bumpage for some answers. I have an ADP1 phone. I've tried all the images from http://developer.htc.com/adp.html#s3.
1.1 and 1.5 all verify and start the installation but they immediately stop and I get a message saying "Installation aborted". I've tried flashing the radio image first but I get the same result.
My phone is stuck on the start-up HTC screen, the one with the green "HTC" logo non a white background.
I was just changing my font to "Cees Hand Regular" using Font Changer and it was not my first time using this application. Every font change requires a reboot, and when I did so my phone got stuck on the start-up screen.
I'm currently running the latest stable version of Cyangonmod if I'm not wrong, and my phone is still able to enter bootloader mode.
I've already tried Googling around for answers and there were some saying to reflash a new rom. But how can I do so if my phone is in such a state? I also tried pulling out the battery to cool and even cleared my memory.
Can someone help me with my problem? Any help or replies is very much appreciated!
If you can enter bootloader mode, you can enter recovery (Clockworkmod) and can flash a ROM again from there.
Enter bootloader, wait for the file scan to get over, then use the volume keys to navigate to RECOVERY, and press the Power Key. Phone will restart in Clockworkmod. Here, perform a wipe data / factory reset, format /system under Advanced, and re-flash the ROM again.
Solved!
Please buy hyelton a beer or a damn new phone. He's a hero.
This worked: http://forum.xda-developers.com/showthread.php?t=2432476&highlight=decrypt
Hey guys, but of an emergency here...
I'm stuck at the LG logo after flashing the Pacman ROM with the latest unofficial CWM, and it seems to have failed at Formatting system. All four touch buttons on the bottom were blue, as if they had been pressed and highlighted. No response from anything.
Reboot. Then it got stuck on the LG logo. I can't access CWM anymore, holding power + vol down does nothing, I just go back to the logo. I'm running a D802.
This was a pretty standard flash for me, I have done this many times, so I was confident in it, but now have no way back into a phone I desperately need within hours.
Process went as follows;
Full wipe, format, initialize install, it failed/crashed/whatever, rebooted, now stuck on logo, unable to access CWM, and obviously unable to access ROM.
USB Debugging was on, but as the ROM doesn't exist anymore, not sure how much help that'll be.
I'll gladly go back to either CWM or TWRP, as well as stock ROM or whatever. I can sort all that out later, right now just need things back in running order.
Edit1: I can't even turn it off. It simply boots up again, so now also worried of damaging display or battery.
Edit2: It's not showing after entering "adb devices". List is empty.
ANY help appreciated.
I'm running Windows 8, and no, I will not be able to reinstall to W7 or Ubuntu.
Thank you
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
Hello
I bricked my M3 and tried using Huawei Tool to unbrick it.
I followed all the instructions, and realized that the bootloader needed to be unlocked. I unlocked it and since then, I can't enter Fastboot mode.
I've tried pressing Vol - and power and it's stuck in a loop where it tells me
"Your device has been unlocked...
Your device is booting now"
And then it doesn't move.
Am I screwed?
Thanks a bunch
My device is a BTV-W09
I saw many of the same symptoms and I showed the same symptoms.
At this time, there seems to be no recovery method.
Same symptons as you. I guess the fastboot partition wiped itself after unlocking so there's no way else to get in anymore.
Same here: unlocked bootloader than flashed TWRP (maybe not the right one) and now the TABLET power ups for only 3 seconds with the message "Your device has been unlocked...Your device is booting now" and then it shuts down!!
Anyone could suggest me how can I return to fastboot mode to try to relock the bootloader?
Thank you very much!!!
(I tried VOLDOWN+POWER / VOLUP+POWER with and without USB cable connected with the PC but after 3 seconds of warning message it shuts down!!)
Anyone could help?
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
ETOSoft said:
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
Click to expand...
Click to collapse
Volume up + Hold Power for 3-4 Seconds during the locked boot. When the screen goes blank let go of both and it should go into recovery like it was supposed to. You have to let go though at the right time. I unbricked some op phones doing the same thing but it's been awhile.