I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Lirezh said:
I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Click to expand...
Click to collapse
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Alfa Kenny One said:
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Click to expand...
Click to collapse
Hi,
I solved it.
It took about 30-50 reboots until the phone entered the fastboot menu.
The problem was that the phone kept skipping the whole fastboot menu and went into recovery instead.
A very strange firmware bug caused by the failed OTA
Related
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Paris6906 said:
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Click to expand...
Click to collapse
Likely no need to let it die -- a hard reset (hold the power and vol down for a very long time) should bring you back to the bootloader (hopefully). It'll seem like a good long while -- keep pressing.
From there, select 'fastboot' and press the power button, then plug in to your computer (USB). That'll show USB on the fastboot line.
Then, on your computer, open a command window (presuming you're using Windows) in the SDK platform-tools directory and type:
fastboot devices
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
Then, reboot into recovery.
Your kernel (boot.img) apparently is garbage, so hopefully you can either put a ROM on USB and flash from that (OTG) or adb sideload it. All the ROMs normally have a good kernel so would flash your boot.img properly during install. Were me me, I'd flash O.M.J's stock rooted ROM just so you at least get back to some place of sanity).
If that all fails, you might have to RUU and start over.
Let us know and we'll help out.
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
ok. can you use adb push in fastboot? also i noticed that my captive buttons blink when i tried to turn off my phone. don't know if that means anything.
OMG it worked! Thank you so much. I uber appreciate it. Today I learned a ton about how android works and how to use adb and fastboot. While the processed about gave me a heart attack i did learn a lot. I can not believe how great of a resource xda is. The knowledge of everyone on here is incredible. I cant thank you enough.
Thanks all,
Paris6906
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.
Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing
Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Revolution_09 said:
Last night I was running 5.0 Lollipop GPE on my unlocked Telus HTC One M7, when I got a notification for an OTA update to 5.1 . I let it download and install, it booted up and then ran through Optimizing Apps. When it finished, the phone rebooted - and then got stuck in this loop. I can either boot the phone and it starts Optimizing Apps (again) or I can get to the bootloader screen. Entering Recovery mode (then holding power and volume up) doesn't do anything- just leads me back into this loop.
Figured I need to flash the phone now, but cannot get it to show up when I run adb devices (just an empty list). I'm not sure if the phone isn't in USB debugging mode or there is something else going on here. I've tried both Mac and PC with several drivers, multiple usb cables, and any other potential solution google came up with. It obviously worked in the past in order to flash 5.0 GPE, but doesn't work now and not sure what has changed.
Any suggestions on getting out of this mess? Can I somehow flash it without being able to boot? Thanks!
Click to expand...
Click to collapse
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
alray said:
use fastboot commands, usb debug is only to enable adb when the os is booted.
Code:
fastboot devices
Click to expand...
Click to collapse
Thank you! Everything else went smoothly and I've flashed 5.1 now.
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)