I was running resurrection remix, when i saw the 4.4.3 based slimkat. So naturally, i had the urge of flashing it. i was on TWRP 2.7.0.0, i flashed the 2.7.1.0 version of twrp, flashed the rom, gapps, and rebooted, but my phone wont boot up. later, after a series of flashes and wipes, when i failed to boot the rom, i tried to install some other rom. but my phone wont connect to pc in recovery. i flashed the TWRP 2.7.0.0, then CWM 6 but no luck. finally, i flashed phillz along with the kernel from viperx and the phone mounted. copied viperx, flashed, rebooted. now the phone wont pick up my sim card. i thought this might be the issue with the kernel. went back to fastboot to flash the kernel, everything was working fine but as soon as i connected the usb cable, and phone was in fastboot usb mode, my volume buttons and power key stopped working,windows said that a device has malfunctioned, tried to flash but it would just say <waiting for device> and as soon as i removed the usb cable, my phones hardware keys started working again. if booted in hboot with usb connected, it would get stuck on checking sd card for update. Now i am stuck and need urgent help, coz i might miss some important calls if this continues and i am unable to flash.
Some other information that might be useful.
Rom: ViperX
Windows: 7 ultimate.
only HTC usb drivers installed, nothing else.
To flash i usually use Hasoon`s tool as it is very handy
Related
hey there!
Ok so I got this problem. My phone felt to the floor like 2 weeks ago and the screen got crashed, everything else works normally, touch is ok, screen is ok, just glass is broken, after 2 days I downloaded some dota apps and it suddenly started rebooting and crashing:
By this I mean, apps stopped working and lots of pop-up messages appeared, after some reboots It stopped turning on, so I decided to root it and installed a custom ROM the one from mike, Android Revolution, this was last week, this weekend it worked fine until sunday when it got bricked because of an outdated recovery from clockwork. I managed to solve this with some help from you guys, but now again.
I flashed the android monday again with same version, it was working well until yesterday at night, it started showing some whatsapp stopped working stuff again, i rebooted it and now a bunch of window errors... reboot it again and well... no luck it stayed in the Android loading window.
After this I was trying to install the stock version ROM from mike also, and that's when it got worse.
Flashed boot and recovery OK, then rebooted and when I tried to install the ROM it just won't let me, failed unknown error, failed remote : 00030000, and other messages, now when I try to flash the recovery again it says low battery, and when I try the script to charge it it won't work, FAILED remote: unknown reason.
What can I do guys? =S (Sorry for the long post, I just don't know what could it be, and I wish by giving that much information someone can find out the reason, contacted HTC and they said it has no guarantee since I rooted and the glass is broken)
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
faiz02 said:
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
Click to expand...
Click to collapse
I can but there is some weird reason that won't let me do any flash, either low battery and when it gets charged a bit (because it may charge enough sometimes) it says FAILED remote:00030000 or unknown reason.
Don't know what it could be.
I ran into the exact same problem, the charger script does not help me too (low power on usb port of pc).
Thats how I fix this:
1) disconnect original charger, let's phone die. or use shutdown in fastboot.
2) connect original charger, and wait while phone powered up (He himself off as he does not have enough battery power.). disconnect charger.
3) vol.down and hold power,choose fastboot
4) connect charger
5) choose reboot bootloader (phone will reboot in fastboot)
6) choose reboot bootloader (phone will reboot in fastboot)
7) choose reboot bootloader (phone will reboot in fastboot)
....(do it fast)
249) choose reboot bootloader (phone will reboot in fastboot)
250) choose reboot bootloader (phone will reboot in fastboot)
251) disconnect charger, choose shutdown.
252) go to PC
253) vol down, power up
254) choose fastboot
255) flash the custom recovery with power supply support
256) flash custom kernel
257) don't disconnect USB!
258) fastboot / reboot bootloader / hboot
259) recovery
260) mount USB storage
261) drop zip of custom flash to the phone
262) unmount
263) advanced / restart recovery
264) flash the zip of rom
265) restart phone and dont disturb it, at 30 minute, let hi charge.
266) disconnect USB and connect original charger (1A)
267) Have fun!
It worked but bad news... now as always I am getting the message windows, with some weird apps.
First it was htc.com.bgp or something which I found it was the weather, then whatsapp, then Personalize, pretty much everything I open stops working after a while, what can I do? This was the exact reason that brought me here in the first place. It started showing these messages and I decided to install a custom ROM, it was first stock and locked and happened, now with this Android HD ROM it is still the same.
Thanks man... i was scared like hell when i realised that by script my battery voltage didnt raise up... even worse... it became less... i was reboting bootloader for 1h, but finally it worked... now im charging it to max... then ill flash stock rom
Thanks again.
I've been running Cyanogenmod 9 for a couple of months, but decided to restore to stock so I can try out ICS and the new version of sense. I tried this a while ago but got stuck when when phone wasn't recognised via USB when connected to my laptop. Fastboot would change to Fastboot USB when plugged in, but the phone wasn't picked up. However, on this occasion I was able to restore Cyanogenmod without problems.
I tried this again yesterday with the same result regarding the USB connection, but when I restored Cyanogenmod it now just hangs on the boot screen and won't go further. Prior to this, when I ran the restore function in Clockworkmod, the phone would hang on the HTC splash screen with the beats audio logo on it. I did manage to get the phone to boot into recovery, but rather than the usual menu option I had a message something like "checking SD card..." and then nothing.
I am not sure where to go from here. The only thing I am wondering is if I tried to do this with the battery being too low, and the installation has failed because of this. I do want to go back to the stock OS, but not sure how to go about resolving the USB issue.
UPDATE
Partially solved the problem, in that I've managed to reinstall the cyanogenmod. Still stuck with lack of USB connectivity though.
Wrong section.....
Do you have the Fastboot files all in the same folder and do you have the HTC Sync drivers installed? You need that set up correctly to get a fastboot USB connection.
My suggestion is to simply "fastboot oem lock"
Then flash corresponding RUU to your current HBOOT. You can find out which RUU you need by typing "fastboot getvar version-main"
Hi guys !
I believe I just bricked my phone, and I'm looking for some help. Here's the story :
I wanted to upgrade my GNex to AOKP kitkat (latest nightly : aokp_maguro_kitkat_nightly_2013-12-25.zip ).
I wanted to wipe it clean, so I first flashed the latest Google factory images : yakju-jwr66y-factory-09207065.tgz, everything went smoothly.
I then flashed the latest TWRP (openrecovery-twrp-2.6.3.2-maguro.img) via fastboot, still no issue.
I used the MTP mount on windows to transfer the new ROM, kernel and Banks Stadard Gapps.
I flashed them through recovery, in that order:
aokp_maguro_kitkat_nightly_2013-12-25.zip
franco.Kernel-nightly-r394.zip
12-14_GApps_Standard_4.4.2_signed.zip
I did a Factory reset prior to that, but no wipe between flashes I believe.
Now I'm stuck into the boot animation, which goes on forever (basically until the battery dies)
NOW : The thing is, I can't simply boot into bootloader; MY HARDWARE VOLUME KEYS ARE BOTH BROKEN !
During the boot process, The device is recognized by the computer (plug in/out sound), I can see the device with adb, but it's marked as "off line" when I try to reboot into recovery or bootloader.
When the phone was switched off but plugged onto the computer, it was detected as "OMAP 4440", and the drivers could not be installed. I then downloaded the latest Samsung drivers from this post : http://forum.xda-developers.com/showthread.php?t=961956 , and the phone doesn't do anything when it's plugged in (but switched off) now...
Does anyone know how to deal with the situation ? The phone seems to not be not quite dead yet, but I can't find a way to reset it.
I can provide any additional information if needed !
Thanks in advance for the help !!
You can try with a USB JTAG (very cheap from ebay) to boot your phone into Download Mode and then flash it with Odin.
Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.
Hello,
I have this strange issue that occurred after I flashed one of the many custom roms floating around.
The USB connection menu in the phone is greyed out and technically I cannot transfer anything over the cable from a computer and with this obviously I cannot use any adb command so I can flash the stock.
The phone is only charging when being plugged in nothing else
Prior to be flashing the rom I have booted TWRP tethered so I could flash it but now since my usb settings are greyed out I cannot boot TWRP anymore nor I can boot from the phone as I didn't make TWRP permanent.
Is there any way at this point that I can flash TWRP, any rom or even stock image considering that I cannot see the phone over the USB ?
Appreciate any input
...why don't you just reboot into bootloader and boot twrp again and this time flash it in recovery? Are you saying you no longer have a usb connection to your phone, as in it's broken?