Hi there,
Not sure if this is the right place to post - if it isn't, I'm sorry. Mods can move it to where it should be.
Anyway, as I was attempting to upgrade my radio and SPL, I was able to flash my SPL and Amon Ra's hero recovery. Unfortunately, I wasn't able to flash the radio. Using "fastboot usb", it says sending is fine but writing makes the screen fade out and fade in with gray. I wasn't satisfied so I tried updating through the recovery screen through update.zip.
Now, everytime I load up, an image with a box and an arrow pointing out and towards the phone shows - after that it fades out and sometimes fades to gray or fades to black etc. I haven't had any luck when I try taking the SIM out nor plugging in the USB. adb can't detect it at all. Any ideas?
You said almost everything except what phone it was. 32A could be magic 32A,or a mt3g le/1.2
Also on the box screen try holding home + power again.
kbeezie said:
You said almost everything except what phone it was. 32A could be magic 32A,or a mt3g le/1.2
Also on the box screen try holding home + power again.
Click to expand...
Click to collapse
I'm sorry! It's a 32A Magic from Rogers.
Tried what you mentioned - it still fades.
Tereno said:
I'm sorry! It's a 32A Magic from Rogers.
Tried what you mentioned - it still fades.
Click to expand...
Click to collapse
try going into HBOOT by pressing vol down + power.... if you can go there...than you still have a chance and just reflash the recovery using fastboot...
That didn't work either. I've tried so far:
Back + Power
Menu + Power
Home + Power
Camera + Power
Call + Power
Vol Down + Power
Vol Up + Power
Trackball + Power
They all give me the same result with the exception of Trackball + Power which gives me a blue LED and a blank screen.
that's a brick unless you find the right file that it is looking for.
Suggest putting the upgrade radio file on the sd card and try booting again: http://forum.xda-developers.com/showthread.php?t=605239 . follow the upgrade radio version section.
You might not have flashed the radio and that is what it is looking for.
edit-> when you drop the new radio on the sd and boot don't get upset when you see that graphic again, that is what you'll see while the phone tries to load it. give it a minute before panicking.
Re: Upgrading the radio - do I edit the file to update.zip, put it in the root dir of the SD card and just let it go?
I'll try that. Thanks! I'll post my radio settings before.. and my radio settings that I was trying to flash to when I get home.
Tereno said:
Re: Upgrading the radio - do I edit the file to update.zip, put it in the root dir of the SD card and just let it go?
I'll try that. Thanks! I'll post my radio settings before.. and my radio settings that I was trying to flash to when I get home.
Click to expand...
Click to collapse
Normally when you have to upgrade the radio, the typical method is to get into Fastboot then fastboot flash radio radioimage.img
If you can't do that, then usually you have to change it via a new SPL, such as a sappimg.zip or .img in the root of the SD card (as I don't think hboot automatically catches an update.zip which I would associate with a file being used in the recovery console, not hboot/fastboot)
It seemed like the SPL and the recovery img that I flashed earlier on worked.
And then I booted into recovery mode, renamed my radio update to update.zip and used the recovery mode to update the radio. I'm guessing that's where I went wrong?
I tried using flashboot radio radio.img and it was sent fine but the writing failed. The same error image as I am having now pops up but I could still have gotten into fastboot mode. It then prompted me to use the method above which is probably not what I wanted and ended up not being able to get into fastboot mode.
Have you tried a "fastboot erase radio" command before trying to reflash the radio? I think that's maybe one of the things I had to do when I hosed my 1.2. Shoot... There was someone else asking about a bricked 1.2, and I forgot I had used "fastboot erase"...
MassiveAttack said:
Have you tried a "fastboot erase radio" command before trying to reflash the radio? I think that's maybe one of the things I had to do when I hosed my 1.2. Shoot... There was someone else asking about a bricked 1.2, and I forgot I had used "fastboot erase"...
Click to expand...
Click to collapse
I didn't do that. Maybe that's why. But now I can't get it recognized on my PC.
"fastboot devices" doesn't find anything? Is it booting to fastboot/hboot?
MassiveAttack said:
"fastboot devices" doesn't find anything? Is it booting to fastboot/hboot?
Click to expand...
Click to collapse
Nope. It can't be detected. Everything I do to turn it on, it goes straight to the image with box and arrow pointing outwards and fades out.
I doubt that I can help but that image is telling you that the phone is looking for a specific file like it does at the factory. No telling exactly what file though. Normally that's a brick sorry to say.
But on the off chance that it is looking for the radio image I'm using try this, drop this file on the SD card and see if it helps. Let it run for a few minutes:
http://www.theandroidkitchen.com/fi...wnload=update-radio-32A-6.35.10.18-signed.zip
Related
I wanted to go to the official ION with my Magic 32A, so first I flashed the update.Engineering-SPL-HBOOT-1.33.2010-signed.zip and that seemed to go fine, then restart into fastboot and applied the signed-google_ion-ota-14721.zip from the htc developer site and thats when the s**t started.
When restarting I get the "htc magic" slash screen and thats it. I cannot get into the fastboot console (home/power or back/power) in fact nothing seems to do anything.
Before I burst into tears, is there a solution to my problem?
This was a HTC badged unlocked phone that I have flashed roms before, but this attempt has gone horribly wrong....
Can you get it into bootloader?
VOLUME DOWN+ POWER ?
no, it buzzes once, shows the "htc magic" splash then nothing :-(
does the same thing with any of the key combinations I try...
no, it buzzes once, shows the "htc magic" splash then nothing :-(
does the same thing with any of the key combinations I try...
ghaywood said:
no, it buzzes once, shows the "htc magic" splash then nothing :-(
does the same thing with any of the key combinations I try...
Click to expand...
Click to collapse
edit : that is only system image and only for ion
does adb detect it?
you can try one thing
make a gold card
paste some ones backup (make sure its for 32A)
boot.img
system.img
recovery.img , etc
and then
try loading boot loader
i.e vdown + power
and check if ruu picks ur phone or not
mostly it wont
Thanks for the reply, I have a nandroid backup with the *.img files would they do for a gold card?
Also, I know this is n00b, but I an a bit confused with the gold card thing. Is there a howto for using via ubuntu?
Thanks
I have read the gold card creation, and it talks about getting the CID when the phone is on. Obvoiusly I cant do that
Is there a way to get this CID even though I cannot start my phone?
Did you check this thread:
http://forum.xda-developers.com/showthread.php?t=571457&highlight=unbrick ?
Been there, done that. Send it into HTC. They fixed mine for $20.00. Had to use my iPhone and actual ion for 10 days.
Hi everybody
Sorry for my bad English I'm Belgian and I have a big problem with my phone
I bought my phone on ebay, it's a HTC Magic 32a TimMobile.
I installed GyD rom and it worked perfect. But yesterday, I look that the new version of this rom is available for RADIO 3.22 and RADIO 6.35.
Firstly, I install version for 3.22 (like mine) but the phone begin very slow. Then I wanted install new radio and spl from this forum.
I installed SPL 1.33.2010 on first and reboot my phone : no problem.
After I downloaded and installed the 1.76.2007 SPL HBOOT image, 6.35.10.18 Radio Image and Amon_RA Hero Recovery.
But with that, when I went in fastboot, my phone restarted after 5 seconds.
I see that 6.35.10.18 Radio is for CA then I downloaded 6.35.08.29 radio on my sd card. But when I installed this and that my phone reboot, I have a pics of installation with a phone and a arrow and after a few seconds screen begin dark and nothing else...
I can't access in fastboot, adb, nothing
Is there a issue or my phone is definitely brick ?
Thank you very much.
Did you flash Hero Recovery to your phone prior to using fastboot ?
Power off your phone
Press HOME + POWER simultaniously .......are you back in Recovery now ?
应该是变砖头了~需要刷字库的。在中国大概500rmb左右。
tnp0511 said:
Hi everybody
Sorry for my bad English I'm Belgian and I have a big problem with my phone
I bought my phone on ebay, it's a HTC Magic 32a TimMobile.
I installed GyD rom and it worked perfect. But yesterday, I look that the new version of this rom is available for RADIO 3.22 and RADIO 6.35.
Firstly, I install version for 3.22 (like mine) but the phone begin very slow. Then I wanted install new radio and spl from this forum.
I installed SPL 1.33.2010 on first and reboot my phone : no problem.
After I downloaded and installed the 1.76.2007 SPL HBOOT image, 6.35.10.18 Radio Image and Amon_RA Hero Recovery.
But with that, when I went in fastboot, my phone restarted after 5 seconds.
I see that 6.35.10.18 Radio is for CA then I downloaded 6.35.08.29 radio on my sd card. But when I installed this and that my phone reboot, I have a pics of installation with a phone and a arrow and after a few seconds screen begin dark and nothing else...
I can't access in fastboot, adb, nothing
Is there a issue or my phone is definitely brick ?
Thank you very much.
Click to expand...
Click to collapse
Same thing happened to me. I have the Canadian phone but ended up with that same graphic that fades to nothing in a couple of seconds. I never did get mine back but here's what I know:
The phone is in some kind of factory load mode and it is possible that it is looking for a specific file from the SD. I found that out by changing the SD format and seeing a linux style lost.dir directory appear on the card after a boot (home + back + tap power). It is trying to do something but gives you no control over what it wants. You should see it fade to a bluish screen that then fades to a whitish screen. I've tried all sorts of files named to update.zip but never found the right one.
Unless you can find the file it is looking for you are bricked. That experience scares me from flashing any more radio versions.
silvertag said:
Did you flash Hero Recovery to your phone prior to using fastboot ?
Power off your phone
Press HOME + POWER simultaniously .......are you back in Recovery now ?
Click to expand...
Click to collapse
When I press home + power or down + power, phone always start install of radio and screen begin dark
tnp0511 said:
When I press home + power or down + power, phone always start install of radio and screen begin dark
Click to expand...
Click to collapse
Can you delete userdata? home + back + power
sindrefyrn said:
Can you delete userdata? home + back + power
Click to expand...
Click to collapse
Always the same
tnp0511 said:
Always the same
Click to expand...
Click to collapse
Hmm. And fastboot or adb dever finds your phone?
no usb isn't detect
I had the same problem when I tried to update my SPL.
At least, the symptoms are the same.
Luckily, I could enter the recovery, and as I had left the previous rom on the sdcard, I could restore it.
tschork said:
I had the same problem when I tried to update my SPL.
At least, the symptoms are the same.
Luckily, I could enter the recovery, and as I had left the previous rom on the sdcard, I could restore it.
Click to expand...
Click to collapse
you're a lucky man !
wow....same to me. and i have no idea to fix this problem.
yes, it sames the phone is looking for something....
tnp0511 said:
you're a lucky man !
Click to expand...
Click to collapse
Hmm... If placing some ROM file on a SD card is all that needed to flash it in your case, why don't you buy SD card reader for PC (they cost like $5) of find a friend/relative with a notebook computer?
I already try to put ROM file into my SD but it didn't work
damn every other thread I see people have bricked their phones...
did you flash update-hboot-1.33.2010-signed.zip? I flashed it when I saw one of cursordroid's post, and then now it is dead and stuck on splash screen. I can't access fastboot via back+power or vol down+power, I can't access recovery mode either. It's definitely a brick.
yes like me
2girls1cup said:
damn every other thread I see people have bricked their phones...
Click to expand...
Click to collapse
probably because they didn't follow exact instructions (for their exact model).
youthzone said:
应该是变砖头了~需要刷字库的。在中国大概500rmb左右。
Click to expand...
Click to collapse
Do u think anybody here can read this?
kerry_xu_cs said:
Do u think anybody here can read this?
Click to expand...
Click to collapse
Should be changed bricks of the ~ need to brush font. In China, probably around 500rmb.
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
I'm a little stuck as to what to do now. Flashed clear droid 1.2.3 (gb) over clear droid 1.1.51 (froyo) after doing a factory reset and clearing the dalvik cache from clockwork recovery and flashing the recommended radio for gb. The stock mms app was force closing, for which ClearD recommended flashing the radio again... but the phone refuses to go into HBOOT when I hold the power button + the volume down button on startup. It just buzzes a few times and the screen stays black until I release the buttons and then it just boots normally except it gets stuck in airplane mode or refuses to recognize the SIM card until it's rebooted without holding down the volume button.
I did a backup with clockwork and a nandroid I think? If those are the same thing then I did two nandroids I'm thinking I should do another factory + dalvik wipe and flash the backup, but I'd like to get this thing on gingerbread. Any advice as to what I did wrong the first time would be greatly appreciated before I start over.
stompsfrogs said:
I'm a little stuck as to what to do now. Flashed clear droid 1.2.3 (gb) over clear droid 1.1.51 (froyo) after doing a factory reset and clearing the dalvik cache from clockwork recovery and flashing the recommended radio for gb. The stock mms app was force closing, for which ClearD recommended flashing the radio again... but the phone refuses to go into HBOOT when I hold the power button + the volume down button on startup. It just buzzes a few times and the screen stays black until I release the buttons and then it just boots normally except it gets stuck in airplane mode or refuses to recognize the SIM card until it's rebooted without holding down the volume button.
I did a backup with clockwork and a nandroid I think? If those are the same thing then I did two nandroids I'm thinking I should do another factory + dalvik wipe and flash the backup, but I'd like to get this thing on gingerbread. Any advice as to what I did wrong the first time would be greatly appreciated before I start over.
Click to expand...
Click to collapse
The good thing about Android (And ClearDroid) is that there are several ways to go about doing things.
Instead of trying the volume down + power trick, try installing the modpack (can be done by installing the zip through Rom Manager like it is a ROM) and then after install, just hold the power button, press "Reboot", then "Reboot into Bootloader" I believe.
If you still wish to try the power down option, make sure that USB Debugging is turned on and that fastboot is turned off in your settings. If still no success, post here and we will keep on troubleshooting. It might be good for others to see the steps we take to get this figured out.
:O thank you for trying to help me, master ClearD! I flashed the modpack like you said, and the sms errors went away However, I still can't get into HBOOT, and there isn't an option to do so in the modded shutdown menu Also, I don't have the option to turn off quick boot?? It's supposed to be in settings>applications>developement, right? And the phone lost the new radio! It went back to 12.56... instead of 12.62... and you said to flash that in HBOOT, so I didn't try doing it from recovery (which I can get into). I tried holding the volume button while the phone rebooted (instead of shutting it down then turning it back on) but that trick didn't work either.
It's a really sweet ROM, just so nobody gets the wrong impression from all my whining thank you for it, ClearD!
To get to the bootloader from the shutdown menu, hit "Restart" then select "Bootloader" from the next menu lol.
Try the latest release, 1.3.0, which has the advanced shutdown menu cooked back in, and the radio is not included in the Rom, it must be flashed separately or else it will stay as it was. Try that and let me know what happens.
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
Lol I'm such a tard... found bootloader... can I just put in the disclaimer that this isn't my phone? I'm trying to help a friend, I swear...
I redownloaded the radio and the checksum is 9ad454c7ac2a9bd69d9f0a5200f089b6, which is the checksum for 26.10.04.03_M (froyo radio). I'm confused, I totally downloaded 12.62.60.27P... do u um... have the right file hosted on techsupporteverything.com... when I went into HBOOT it got mad and said I needed an update so I guess that's why I got the OTA radio. Which is fine, really the sms thing was what I wanted to fix and that's all good now but I think you may have the wrong file up.
stompsfrogs said:
Lol I'm such a tard... found bootloader... can I just put in the disclaimer that this isn't my phone? I'm trying to help a friend, I swear...
I redownloaded the radio and the checksum is 9ad454c7ac2a9bd69d9f0a5200f089b6, which is the checksum for 26.10.04.03_M (froyo radio). I'm confused, I totally downloaded 12.62.60.27P... do u um... have the right file hosted on techsupporteverything.com... when I went into HBOOT it got mad and said I needed an update so I guess that's why I got the OTA radio. Which is fine, really the sms thing was what I wanted to fix and that's all good now but I think you may have the wrong file up.
Click to expand...
Click to collapse
Lol flash it and see, it should be correct though, I think...
The way the radio flashes is through hboot update, it will always ask you to update if there is any file on your microsd card named PD98IMG.zip that is valid to flash lol. I will double check though.
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
I was on Digitalhigh GPE with the Elite Kernel and the Verizon firmware offered on their thread (http://forum.xda-developers.com/showthread.php?t=2716306) and my power button wasn't working. Pressing it wouldn't turn the screen on/off and holding it wouldn't access the power menu. Holding it to restart/hboot would work so the power button was obviously not broken and I decided to just reset everything. After a failed ruu, my phone keeps switching between the ruu screen (pic attached) and the htc 4 ! screen. I tried the exe ruu (http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103) but it didnt work because the phone just keeps rebooting itself into the htc 4 ! screen. I don't have extensive experience with adb/fastboot commands, but tried flashing both the L hboot and RUU offered in that thread and got the "error: cannot load" response. Everything was backed up before I ruu'ed but my google/xda searches havent gotten me anywhere.
KeltischDeutscher said:
I was on Digitalhigh GPE with the Elite Kernel and the Verizon firmware offered on their thread (http://forum.xda-developers.com/showthread.php?t=2716306) and my power button wasn't working. Pressing it wouldn't turn the screen on/off and holding it wouldn't access the power menu. Holding it to restart/hboot would work so the power button was obviously not broken and I decided to just reset everything. After a failed ruu, my phone keeps switching between the ruu screen (pic attached) and the htc 4 ! screen. I tried the exe ruu (http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103) but it didnt work because the phone just keeps rebooting itself into the htc 4 ! screen. I don't have extensive experience with adb/fastboot commands, but tried flashing both the L hboot and RUU offered in that thread and got the "error: cannot load" response. Everything was backed up before I ruu'ed but my google/xda searches havent gotten me anywhere.
Click to expand...
Click to collapse
Pay attention to the thread... He makes a statement about this issue there.
To flash, put it into the fastboot folder (which should be the platform-tools folder within the Android SDK) and open a command window there. Use the command 'fastboot flash zip nameoffile.zip. It should work. Until it can successfully flash, you are boned.
If this doesn't work, I have one more method you can try.
ironbesterer said:
Pay attention to the thread... He makes a statement about this issue there.
To flash, put it into the fastboot folder (which should be the platform-tools folder within the Android SDK) and open a command window there. Use the command 'fastboot flash zip nameoffile.zip. It should work. Until it can successfully flash, you are boned.
If this doesn't work, I have one more method you can try.
Click to expand...
Click to collapse
Retried that and it failed again. After doing another oem reboot command (which I did idk how many times during the process), the phone randomly got passed the ruu screens, into the white htc boot screen with red text, started up and seems to be working fine. After work I'm going to retry the ruu via the exe this time
Edit: Now it seems that my motion launch, auto-rotate, and proximity sensors aren't working so the only way I can use it at work is to plug/unplug the usb to turn the screen on.
KeltischDeutscher said:
Retried that and it failed again. After doing another oem reboot command (which I did idk how many times during the process), the phone randomly got passed the ruu screens, into the white htc boot screen with red text, started up and seems to be working fine. After work I'm going to retry the ruu via the exe this time
Edit: Now it seems that my motion launch, auto-rotate, and proximity sensors aren't working so the only way I can use it at work is to plug/unplug the usb to turn the screen on.
Click to expand...
Click to collapse
Now flash a custom recovery via flashify and try flashing a custom rom.
KeltischDeutscher said:
Retried that and it failed again. After doing another oem reboot command (which I did idk how many times during the process), the phone randomly got passed the ruu screens, into the white htc boot screen with red text, started up and seems to be working fine. After work I'm going to retry the ruu via the exe this time
Edit: Now it seems that my motion launch, auto-rotate, and proximity sensors aren't working so the only way I can use it at work is to plug/unplug the usb to turn the screen on.
Click to expand...
Click to collapse
From the looks of your screen shot you ended up there because certain partitions failed to flash. That' the protect mode your phone will go into in the case of even a partial failure on flash. You need to reflash the entire RUU again and not "force" it past that screen. INVALID DSP info is NOT A good thing to see.
Personally I would flash the RUU in fastboot RUU mode using the htc_fastboot I have posted.....
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
From the looks of your screen shot you ended up there because certain partitions failed to flash. That' the protect mode your phone will go into in the case of even a partial failure on flash. You need to reflash the entire RUU again and not "force" it past that screen. INVALID DSP info is NOT A good thing to see.
Personally I would flash the RUU in fastboot RUU mode using the htc_fastboot I have posted.....
Click to expand...
Click to collapse
Finally had some time to sit down and try this. Basically not sure what to do because the phone always reboots before the flashing process is done for the 0P6BIMG.zip sd and ruu mode methods. Same with just entering hboot, sits for 7 seconds max then reboots
KeltischDeutscher said:
Finally had some time to sit down and try this. Basically not sure what to do because the phone always reboots before the flashing process is done for the 0P6BIMG.zip sd and ruu mode methods. Same with just entering hboot, sits for 7 seconds max then reboots
Click to expand...
Click to collapse
See if you are able to get the hboot.zip to flash (you will probably have to be quick on commands).
dottat said:
See if you are able to get the hboot.zip to flash (you will probably have to be quick on commands).
Click to expand...
Click to collapse
Yeah, whenever I try to enter fastboot now (Fastboot oem rebootRUU ), the command window just hangs on < waiting for device > and the phone restarts. Fastboot devices does list my phone
KeltischDeutscher said:
Yeah, whenever I try to enter fastboot now (Fastboot oem rebootRUU ), the command window just hangs on < waiting for device > and the phone restarts. Fastboot devices does list my phone
Click to expand...
Click to collapse
try renaming the zip to 0P6BIMG.zip and putting on your ext SD. See if bootloader is able to flash that.
dottat said:
try renaming the zip to 0P6BIMG.zip and putting on your ext SD. See if bootloader is able to flash that.
Click to expand...
Click to collapse
Says it succeeded, gives me the power button to reboot option, and reboots itself before i hit power. Still at the same situation
KeltischDeutscher said:
Says it succeeded, gives me the power button to reboot option, and reboots itself before i hit power. Still at the same situation
Click to expand...
Click to collapse
Hmm... try now this one in bootloader (renamed and placed on your ext-sd)
https://www.androidfilehost.com/?fid=95916177934540511
dottat said:
Hmm... try now this one in bootloader (renamed and placed on your ext-sd)
https://www.androidfilehost.com/?fid=95916177934540511
Click to expand...
Click to collapse
Yeah, right after it begins the process after I hit the volume up button, it restarts while updating splash 1
KeltischDeutscher said:
Yeah, right after it begins the process after I hit the volume up button, it restarts while updating splash 1
Click to expand...
Click to collapse
Did it immediately restart to bootloader or attempt to boot to os?
dottat said:
Did it immediately restart to bootloader or attempt to boot to os?
Click to expand...
Click to collapse
os
Edit: Also - just for an extra description of the situation - when I got to work after trying to reflash this afternoon, I noticed my power button started working again. Data/wifi still work fine, but music (cant play anything), motion launch, auto screen rotation, audio or video (youtube, websites, gallery, etc) are still not functional and occasionally the entire ui will disappear and freeze for a few seconds.
Haven't been able to flash any fixes. After using my m8 more, I've also seen that the calls and anything voice related are also down and the phone freezes up quite a bit, plenty of FC's.
KeltischDeutscher said:
Haven't been able to flash any fixes. After using my m8 more, I've also seen that the calls and anything voice related are also down and the phone freezes up quite a bit, plenty of FC's.
Click to expand...
Click to collapse
Install teamviewer and pm me the id and passcode. Make sure you have stuff backed up off your internal sd card first. We will get this straightened out.
dottat said:
Install teamviewer and pm me the id and passcode. Make sure you have stuff backed up off your internal sd card first. We will get this straightened out.
Click to expand...
Click to collapse
So I finally had time and installed team viewer today and when I booted to start backing up everything, the phone didnt automatically restart itself in hboot this time (over the past couple days I've been having barely any FC's or hang ups) so I tried the ruu you posted again and it finished. First time, it hung on the Verizon logo after boot, I ruu'd again and it fully booted, when the android app optimizing was finished, it gave me the acore force close, did a factory reset and everything (autorotation, music, power button, etc) is back to Verizon stock and working with no force closes/problems so far. Thanks for your files/help, dottat :good: