Related
I don't know what I did wrong. After downloading a moddet statusbar vor Oxygen 0.2 I wanted to reboot into recovery and it took me very long. It freezed. After pulling the battery and setting it back in and pushing the power button my desire vibrated in 3 short intervals.
Since that I can't boot into the os or into recovery. Only thing that is working is the bootloader and the fastboot.
First thing I tryed is to flash (with fastboot) a new recovery but nothing changed. still it freezes at the splash screen.
I also downloaded official o2 rom from their homepage. But I think they want me to run the .exe while in android. A error comes up and tells me that it can't find a phone.
official htc roms don't work too. one told me that I'm not allowed to install this particular rom and an other official rom keeps exiting with error code: 170 telling me that the usb connection couldn't be established or something like this.
is there something else I can try?
I googled and searched the board. Tryed to boot into recovery without microSD card too but still no success.
help
Unpack the Rom and get the image out of the file...
Rename it to pb99img.zip dump only that on the root of your sdcard and boot into hboot .
T i d y .
Or just look on shiped roms for an 02 pb99img.zip and download then rename
T i d y .
Thank you so much. I already tryed this with 3 different pb99img images and had always the same error (CID). One of them was a o2 uk rom. So I gave up on trying it this way. But I didn't know that it could be extracted from every rom.
Now I think every thing is working again. Thank you.
Oh well ... I destroyed it again. Like I said I was able to install official o2 rom and everything was working again. After that I wanted to root it with unrevoked 3.21 but it freezed at "waiting for reboot". So I had to pull the battery once again.
But now I can't even enter bootloader. Only a screen pops up with htc in the middle and with four ! in every corner of the display.
Tryed to install official o2 rom again. It can find it and starts installing but at the end of the installation it stops with an error:
error [110]: error while opening data. Tryed it 3 times but always the same.
This might work for you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
EDIT: YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck
You have to have a working Goldcard and be able to access HBOOT to do the above
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Peikko said:
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Click to expand...
Click to collapse
Well lad you had USB brick, easy to fix.There is a thread on this thing.
I am having similar problem described.
Currently I can get into Fastboot, and have tried reflashing recovery but still boot loop.
What should I do now?
please help my desire break
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Hi,
I have the same problem and getting pretty desperate now.
Only FASTBOOT and BOOTLOADER works.
I have clockwork recovery installed but it wont boot into recovery. It just gets stuck on the white boot screen.
I can't copy PB99IMG.zip or any other zip file because I can't access the phone through usb. I tried:
adb push PBIMG99.zip /
error: device not found
Is my phone useless now? As good as a brick?
try pack it in some tolietpaper put it in to the freezer fore 5 min an try again
jalal.arkat said:
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Click to expand...
Click to collapse
janielsen's idea seems crazy but give it a try..
put it in the freezer for few minutes then take it out
and then try to get into recovery mode..
you'll be able to do that
if you see a triangle with ! mark at the center that means it's a serious hardware issue and we can't do anything about that you have to send it to htc service center
Ha, funnily enough I did try the freezer thing but that didn't work either. What did work was booting into fast boot, connecting the usb and flashing with an official RUU in windows.
The phone is still stuffed!!!
It now has an official htc rom, no root, no mods, nothing... just stock!
But whenever it has to do a bit more processing like viewing a complex web page with flash, playing a game, downloading from the market it resets itself. Why?
I am starting to think it's a hardware problem but I need confirmation. I tried different roms but I get the same result. Has anyone has the same experience???
well i have sent my phone in fore repare the trick whit the freezer is only so u can unroot it so they cant see that it has bien rooted
the problem is that the cpu is getting to hot
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
yes u have warrenty because htc can see by the imei when the garanty is running out
they will replace the mainboard
FreshNClean said:
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
Click to expand...
Click to collapse
i thit also buy my second hand an didtn have the warrantypapper
but they said that i still have the 2 year warrenty so my is in fore repair
i shut get it back this week
Hi,
My first phone was rooted and I rooted my second too so I am confident rooting them however my second phone which had been rooted for a while had a space issue on SD card so I cleared out a few things which unfourtunatley included all the backup files ....
It worked fine afterwards but didnt let me change rom (using rom manager) so I just left it in working order for a few months until I wanted to reflash a new rom (as I am sure most people do every few months)
When it didnt let me, I tried to unroot and root options using superoneclick and unrevoked3 however, unrevoked 3 just stayed on "running root" and superoneclick got so far and crashed. When I go into the bootloader, it says something about some filed missing (think might be some nbh files).
At the moment, when normally turning the phone on, it stays on the screen with the pink circle, the first boot screen.
I have tried updating it using the RUU but it takes a long time and then says "use the correct rom for your device" which I am, this method just boots my phone and goes to a htc logo.
I can also get into the bootloader but when I apply update.zip, it says it has failed and something about files not existing/step 7 failure.
The thing is, I can get to fast boot and I am sure there is a way via ADB to force a new image (such as a cyanogen recovery image) on to the device.
Can anyone tell me how to push an image to the phone without using the RUU (as this didnt work for me)??
Maybe my phone is just bricked
Thank you very much!!
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Thanks but I do not have another Desire...
Any card reader
yeah, I got a card reader laying around somewhere, if not ill go get one in Tesco, what where you thinking?
bortak said:
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Click to expand...
Click to collapse
Hi Bortak, I am having similair problems with my phone sticking on the pink circle screen. I cant seem to load a recovery file from Bootloader. Will I need to make a Gold Card, my phone is s-off.
thanks mate
if phone is S-OFF go to my guide, look at advanced boot problems S-OFF.
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Mugube said:
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Click to expand...
Click to collapse
#facepalm#
Translation: I flashed another ROM because my other one didn't boot.
Hi, I have foolishly (possibly?) wiped Android off of my OneX
I was attempting to apply the Tegra tweak and well things went downhill.
I successfully unlocked the bootloader from HTCdev.
I proceeded to apply Interim ClockworkMod to gain root access
This is where things started to go wrong. Any new reboot would only take me to Clockworkmod screen.
I tried http://forum.xda-developers.com/showthread.php?t=1599748
clear cache, davik cache... relocking the bootloader - This results in the device constantly rebooting.
I attempted to apply the RUU ROM's ( from: http://forum.xda-developers.com/showthread.php?t=1543604)
From within ClockworkMod I was then able to:
adb push One_X_1.26.401.2_odexed.zip /sdcard/
Once there I used ClockworkMod to apply an update zip (which I was hoping was the Stock ROM).
A reboot just brought me back to Clockwork.
I then locked the bootloader ( fastboot oem lock. ) hoping it would then proceed to boot as expected.
It didn't just going to HBOOT or an attempted recovery (isometric view of a phone with a green arrowed circle -> RED triangle).
Please someone help, starting to panic a bit. The fact I can upload, the fact that there is some basic interactions should imply this is fixable, but how?
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
mwhincup said:
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
Click to expand...
Click to collapse
This may help.
with the locked bootloader you will only be able to run a proper ruu so before even attempting the instruction above unlock your bootloader again and proceed from there.
I might start working on some core .IMG files that can be flashed through fastboot to get you going again tomorrow
Sent from my HTC One X using XDA
THANKS!!!
booted back to the lovely ICS desktop
It looks like I did end up flashing RUU since none of the Vodafone branding is present (and it is actually better!)
No idea what went wrong but probably flashed over the boot as hinted at in the other thread.
The provided img files assisted. just need to get this Tegra thing working (not showing up as a running/registered process but thats another story)
Thanks all
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
clown6198 said:
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Click to expand...
Click to collapse
stathis95194 said:
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
Click to expand...
Click to collapse
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
clown6198 said:
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
Click to expand...
Click to collapse
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Yet another user stuck because they followed a tutorial or video guide, instead of taking the time to learn, read, and really understand the steps and concepts. This is exactly why I discourage such tutorials or YouTube guides (and Toolkits as well), as they leave you completely unequipped to recover if you have a problem, leaving your buddies at XDA to clean up the mess.
YouTube video or not, you shouldn't be doing anything you don't understand, and you shouldn't be wiping anything if you don't understand what the result will be.
You will need to troubleshoot the USB connectivity issue first. From there, unlock the bootloader again, install custom recovery and flash a ROM (as stathis95194 has already stated).
stathis95194 said:
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Click to expand...
Click to collapse
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
clown6198 said:
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
Click to expand...
Click to collapse
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
redpoint73 said:
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
Click to expand...
Click to collapse
will this work even with the S-ON?
clown6198 said:
will this work even with the S-ON?
Click to expand...
Click to collapse
Of course. I wouldn't be telling you to do it, otherwise.
redpoint73 said:
Of course. I wouldn't be telling you to do it, otherwise.
Click to expand...
Click to collapse
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Honestly, I would just install Philz recovery instead of TWRP and try to either install the ROM zip directly (after a full wipe), or sideload the ROM zip from your PC.
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time. Find a ROM for your device that is based off of the 1.x firmware and download that. To get your device out of the bootloop and back into boot loader/recovery, hold power and volume up for quite some time until the screen shuts off. Then, hold power down while the screen is black and you'll be in the boot loader. From there you can use the arrow keys to select recovery. Of it isn't there, first select fastboot or hboot and look for it there. You should be in recovery, now you can go ahead and push the file to your phone. Ensuring it is a sense ROM based off of the 1.x firmware, go to wipe and do the standard swipe to wipe (will erase app data not pictures or downloads), then go into install and select your ROM and swipe. Be patient while your device turns on for the initial boot, it might take a while but your phone should be functional after that.
wtoj34 said:
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time.
Click to expand...
Click to collapse
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
Hi so Im in TWRP. I pushed a ROM called Android_Revolution_HD-One_M8_11.1 which is supposedly the closest rom to a stock one. I tried flashing the ROM many times, Im in the process of flashing it again after whiping like you said. The result is the same. After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Thanks,
clown6198
clown6198 said:
After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Click to expand...
Click to collapse
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
redpoint73 said:
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
Click to expand...
Click to collapse
ahahaha THANK you so much!!!! I got the phone to work but now the problem is, I cant get the sound to work when Im playing music. I installed the harman kardon software and I cant get the music to work at all
clown6198 said:
I installed the harman kardon software and I cant get the music to work at all
Click to expand...
Click to collapse
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
redpoint73 said:
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
Click to expand...
Click to collapse
Damn. Apparently I need to get s-off in order for the harman kardon to work. Just need to uninstall harman kardon now... But yea sorry all I needed was to flash the rom. I didn't know the booting was going to take 5 mins and over. I thought that I was just stuck on the HTC logo. all I needed was to be patient ahaha Thanks a lot guys
Alright guys, I'm new to posting here but I used tutorials from here to root my LG G-Flex 2 and now my HTC One M9. I rooted it about 4 months ago, used it normally for a portion of that, for a time the charger port was broken so I had to get that fixed and got it back still normal, rooted and with TWRP as a custom recovery and such but otherwise working perfectly fine.
I had the android update notification up in my face all the time and I couldn't get rid of it myself and couldn't be bothered wasting too much time fixing it so I just decided I'd unroot the phone and go back to normal android since I hardly took advantage of the fact that it was rooted anyway.. I downloaded the system update and told it to install, I figured this would just get rid of the root for me and all would be good, but it didn't work. It would start the update then just boot itself into TWRP as normal. TWRP was getting in the way of it going into normal recovery mode to do the update.
This is where I ****ed up big time, and I know this was entirely my fault and I feel retarded for thinking it would do anything other than what it did. I went into the Wipe option in TWRP (V2.8.5.0 btw) and wiped the entire system folder. I don't know what I was thinking, something in my head made me think it would just factory reset the system and get rid of the root, which was just dumb as hell because it wouldn't have changed the custom recovery or anything anyway, and it didn't..
I've tried everything I can think of, the phone boots into all the different modes normally, Bootloader works fine, Download mode works fine, recovery works fine.
I used Squabbi's HTC One M9 Toolkit V 1.6.1.0 to update my TWRP to 3.0.0 but it won't go any higher than that without just looping until I flash it back to 3.0.0. I have tried ADB sideloading, it won't work, adb won't even read the Viper zip file I have in the same folder and stuff correctly. I've tried using an SD card to put the Viper zip onto the phones internal storage and install using TWRP, it all installs correctly and encounters zero problems but when I reboot the phone it just boots to the bootloader, the same thing happens when I tried Android Revolution ROM.
adb push command doesn't do anything, adb sideload doesn't do anything, nothing does anything.
I should also mention my HTC One M9 should be the international model, I live in Australia, its second hand and works with 2 different carriers that I have tried it with, I'm with Optus and didn't have to get it unlocked to use my SIM with it right away.
For transparancy I'll list out what is shown on each screen in case it helps in some way..
In download mode:
hTC download mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.710.5
Sep 30 2015, 14:12:12(573756)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
^ Those all function properly except for reboot, that reboots to bootloader.
In bootloader:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***
and all the menu items as normal, again all function properly except for the general reboot.
The phone has been completely system wiped with TWRP now, flashing new ROMs still doesn't work.
I'd like it if people could give me suggestions and I can let you know if I've tried them already since I have tried a fairly large array of things to fix this problem, some of them I can't remember right now tbh..
Thanks all
UPDATE: Using lamahgra's suggestion I have successfully fixed the problem, phone is functioning perfectly normally now
CryloRends said:
Alright guys, I'm new to posting here but I used tutorials from here to root my LG G-Flex 2 and now my HTC One M9. I rooted it about 4 months ago, used it normally for a portion of that, for a time the charger port was broken so I had to get that fixed and got it back still normal, rooted and with TWRP as a custom recovery and such but otherwise working perfectly fine.
I had the android update notification up in my face all the time and I couldn't get rid of it myself and couldn't be bothered wasting too much time fixing it so I just decided I'd unroot the phone and go back to normal android since I hardly took advantage of the fact that it was rooted anyway.. I downloaded the system update and told it to install, I figured this would just get rid of the root for me and all would be good, but it didn't work. It would start the update then just boot itself into TWRP as normal. TWRP was getting in the way of it going into normal recovery mode to do the update.
This is where I ****ed up big time, and I know this was entirely my fault and I feel retarded for thinking it would do anything other than what it did. I went into the Wipe option in TWRP (V2.8.5.0 btw) and wiped the entire system folder. I don't know what I was thinking, something in my head made me think it would just factory reset the system and get rid of the root, which was just dumb as hell because it wouldn't have changed the custom recovery or anything anyway, and it didn't..
I've tried everything I can think of, the phone boots into all the different modes normally, Bootloader works fine, Download mode works fine, recovery works fine.
I used Squabbi's HTC One M9 Toolkit V 1.6.1.0 to update my TWRP to 3.0.0 but it won't go any higher than that without just looping until I flash it back to 3.0.0. I have tried ADB sideloading, it won't work, adb won't even read the Viper zip file I have in the same folder and stuff correctly. I've tried using an SD card to put the Viper zip onto the phones internal storage and install using TWRP, it all installs correctly and encounters zero problems but when I reboot the phone it just boots to the bootloader, the same thing happens when I tried Android Revolution ROM.
adb push command doesn't do anything, adb sideload doesn't do anything, nothing does anything.
I should also mention my HTC One M9 should be the international model, I live in Australia, its second hand and works with 2 different carriers that I have tried it with, I'm with Optus and didn't have to get it unlocked to use my SIM with it right away.
For transparancy I'll list out what is shown on each screen in case it helps in some way..
In download mode:
hTC download mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.710.5
Sep 30 2015, 14:12:12(573756)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
^ Those all function properly except for reboot, that reboots to bootloader.
In bootloader:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***
and all the menu items as normal, again all function properly except for the general reboot.
The phone has been completely system wiped with TWRP now, flashing new ROMs still doesn't work.
I'd like it if people could give me suggestions and I can let you know if I've tried them already since I have tried a fairly large array of things to fix this problem, some of them I can't remember right now tbh..
Thanks all
Click to expand...
Click to collapse
hi,
try to download a full twrp backup of a stockrom from
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
put it on your sd card an recover it via TWRP... so all partions should work....
lamahgra said:
hi,
try to download a full twrp backup of a stockrom from
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
put it on your sd card an recover it via TWRP... so all partions should work....
Click to expand...
Click to collapse
This might be the way to go, I've already lost all my data on the phone so I don't care if its a stock restart. I just need to know how to identify which backup I would need for my particular phone?
CryloRends said:
This might be the way to go, I've already lost all my data on the phone so I don't care if its a stock restart. I just need to know how to identify which backup I would need for my particular phone?
Click to expand...
Click to collapse
Nevermind, figured it out. This seems promising, I'll reply with results once I've tried it. File is downloading at the moment.
CryloRends said:
Nevermind, figured it out. This seems promising, I'll reply with results once I've tried it. File is downloading at the moment.
Click to expand...
Click to collapse
success?
lamahgra said:
success?
Click to expand...
Click to collapse
Sorry, its taking some time to sort it out because the only SD card I had access too was my dads and it wouldn't let me format it when I plugged it into my laptop with an adapter, now it doesn't work in my dads phone or my laptop so I'm buying a new one as soon as I can, will let you know once I've tried that..
lamahgra said:
success?
Click to expand...
Click to collapse
Success. Can't tell you how much I appreciate your suggestion, after the first hitch of the bloody SD Card failing on me I got a new one and it all worked smoothly, 0 problems at all Thanks so much!