Related
Hi,
I bought a diamond a few days ago, and the touch screen recently stopped working. Before it's death, I flashed it with HardSPL 1.40 Olinex, but kept the rom and the radio stock. The problem now is that I would like to send it in for warranty to repair the screen, and I can't revert it back to the original SPL. I've read several threads about how to change it back to OEM specs, but all of them have resulted in the bootloader still displaying HardSPL 1.40Olinex.
Since my touch screen is broken and I recently performed a hard reset to try to fix the screen, I can't get past the align screen, so i've attempted all my upgrades from the bootloader screen(the screen with 4 colors is bootloader screen i think?). I've tried several SPL's from a thread which i beleive where 1.24 original, 1.37 original, 1.93Olinex, all of them still resulting in 1.40Olinex displaying on the bootloader. I also tried installing an official ROM, but that did nothing. I'm desperate for any help or advice so I can get this phone fixed and start enjoying it.
Thank you
Try make connection via AS ( not bootloader ) and shipped rom with not patched custom_ruu
Did you read this single post by cmonex?
HERE
kvm55 said:
Try make connection via AS ( not bootloader ) and shipped rom with not patched custom_ruu
Click to expand...
Click to collapse
I'll try that. I think i've tried it before, where I could make a connection but was not able to update due to me being stuck on the align screen? I'll give it another go.
R3PUBL1K said:
Did you read this single post by cmonex?
HERE
Click to expand...
Click to collapse
Yes I have thanks. That was where I tried using the RUU-SSPL-withoutNBH.zip along with the 1.37 from the first attachment, which still ended up as 1.40OliNex. I'll give it another go from the active sync rather than bootloader.
Thanks guys
Ok so I tried from AS, here's what i got:
Using CMONEX's post, with all the roms and the custom ruu I was able to detect the phone version and press update, but before it starts updating it gets an error [202], connection.
Using a shipped ruu with the 1.37 from CMONEX's post as well as the shipped nbh, the device loaded into bootloader and updated, but still displayed 1.40OliNex. It was able to install from AS though.
I really have no clue what's going on. Any suggestions?
EDIT:
I was able to magically get the touch screen to work to get past the align screen after updating to a different rom, and I was able to update it normally following CMONEX's post.
Thanks for your help guys.
Great News
Glad you got it sorted
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
tommo123 said:
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
Click to expand...
Click to collapse
Weird..did u try flashing a different radio?
not yet. in work for a while longer. the only other thing i can see it being, is the kernels in the rom i'm using now, using too little voltage.
might try flashing a different kernel
I have had this problem before & as has been suggested a different radio did solve the problem. Hope it turns out something as simple for you.
As a last resort try wiping and flashing an RUU, that will replace the kernel, radio and rom
yea, had a thought on doing that too. grabbed 2 of em (not sure which i need) but today it's not rebooting
ok, somethings gone real wrong now. cant do anything more than go into fastboot. recovery causes a reboot with 7 vibrations on the boot screen and it wont go past it. i can go into fastboot/fastboot usb and that's it.
how do you flash a ruu now? i found a guide but it refers to downloading .zip images and putting em on an sdcard? i could only see .exe ruus
Just run the ruu exe while your phone is connected in fastboot. Do you have the ruu that was originally on the phone?
Sent from my HTC Desire using Tapatalk
trying it now. got the ruu downloaded. tried it before but got some funky errors
phones doing some funky stuff at the mo. if this works (i hope) then i can use unrevoked and then alpharev to get root/s-off later again yea?
ta mate
Yeah, you can do that.
Sent from my HTC Desire using Tapatalk
coolio.
worked. now booted up. wonder what the hell happened though!
Dunno but I guess you're relieved
Sent from my HTC Desire using Tapatalk
i am, but tried 2 pcs and my netbook, installed usb drivers off their site but just cant get unrevoked working for my desire.
off to try the old goldcard method
odd, even the goldcard tool didnt work. did a year or so ago when i 1st rooted. had to go old school on this thing.
edit
and after several tries, alpharev doesnt work
cant make the phone reboot when it needs to. worked last time with opendesire with no probs at all. no joy with oxygen though, or the default sense rom
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
tommo123 said:
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
Click to expand...
Click to collapse
I had this problem after I flashed a radio. I ended up sending it back to O2 due to a corrupt radio/cpu stack on the actual device.
So i was running a miui rom and did a clean wipe to try and a new rom. I couldn't get past the boot screen of the rom so i figured it was just a bad download. so i went and unrooted the phone. i have Hboot .92 thew radio is 2.15.10.07.07. i have the phone to s-on. i downloaded and installed the stock verizon gingerbread rom by renaming it to th P whatever lol. the reboots gets to the incredible screen then goes the htc quetly brilliant screen then it does the droid sound and i get the red snapdragon logos. but when it get's to the droid eye after it circle goes back and forth once then freezes on the second one. it sits there for like 3 or 4 minutes and then it just reboots to the droid sound and snapdrogon screen then the droid eye and stops and just keeps repeating this. i am hoping someone on might have a cure for this. the only thing i can get into iss hboot. hoping it's not fried. thanks for your time. and sorry for the long post, just trying to be very detailed to get the right help.
scoobntaz1996 said:
So i was running a miui rom and did a clean wipe to try and a new rom. I couldn't get past the boot screen of the rom so i figured it was just a bad download. so i went and unrooted the phone. i have Hboot .92 thew radio is 2.15.10.07.07. i have the phone to s-on. i downloaded and installed the stock verizon gingerbread rom by renaming it to th P whatever lol. the reboots gets to the incredible screen then goes the htc quetly brilliant screen then it does the droid sound and i get the red snapdragon logos. but when it get's to the droid eye after it circle goes back and forth once then freezes on the second one. it sits there for like 3 or 4 minutes and then it just reboots to the droid sound and snapdrogon screen then the droid eye and stops and just keeps repeating this. i am hoping someone on might have a cure for this. the only thing i can get into iss hboot. hoping it's not fried. thanks for your time. and sorry for the long post, just trying to be very detailed to get the right help.
Click to expand...
Click to collapse
Have you tried doing a factory reset from hboot, and then reflashing the ruu (PB31IMG.zip file) thru hboot again. Also why did you go s-on, just makes it way harder to reroot or fix issues like these? The only reason anyone should ever go s-on is if you need to return it to verizon under warranty.
the reason for s-on is because i was selling it and the new owner just wanted it stock. they know nothing about rooting or any of this kinda stuff. i do believe i tried the factory reset but i will give it a go again.
so i believe i have found the problem. and doing some research it's my own fault. i am still on the .07.07 radio baseband and i found out that i should have downgraded before getting s-on. now i don't know if i can fix this problem or did i just ruin my phone. hoping for some good news. thanks
scoobntaz1996 said:
so i believe i have found the problem. and doing some research it's my own fault. i am still on the .07.07 radio baseband and i found out that i should have downgraded before getting s-on. now i don't know if i can fix this problem or did i just ruin my phone. hoping for some good news. thanks
Click to expand...
Click to collapse
Im pretty sure you have to downgrade the radio to get s-on. As in it wont work to get you s-on if your not on the right radio. Are you sure you didnt downgrade and doing the ruu just upgraded it again?
I would try doing the latest ruu.exe with a pc, instead of PB31IMG.zip.
i would love to but the pc will not read the phone because it just boot loops.
scoobntaz1996 said:
i would love to but the pc will not read the phone because it just boot loops.
Click to expand...
Click to collapse
Try flashing the PB31IMG.zip ruu with fastboot. androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
do you happen to have a workable link for the adb and fastboot. the link on android forums is through megauploiad and is not a workable link.
scoobntaz1996 said:
do you happen to have a workable link for the adb and fastboot. the link on android forums is through megauploiad and is not a workable link.
Click to expand...
Click to collapse
Here ya go: http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip
phone is not recognized in hboot or fast boot. it says hboot usb and fastboot usb on my phone but when i go in the coomand prompt on my pc it doesn't show any devices.
scoobntaz1996 said:
phone is not recognized in hboot or fast boot. it says hboot usb and fastboot usb on my phone but when i go in the coomand prompt on my pc it doesn't show any devices.
Click to expand...
Click to collapse
Have you installed the phone drivers on your pc?
i have installed everything that i can to try and get this phone working. hboot comes comes up on the phone just fine and i can get to fastboot on the phone. when i go to recovery from fastboot it goes to the green triangle then it turns red. i do the volume and power to get to recovery but when it comes up i get a bunch of error messages. and am at a lost with this. all i know is i don't think it is bricked because i can get to hboot. when i try to install another pB file from hboot it either does not do anything or it tells me it failed because it was an older version. i am pretty sure it is a software problem i just can't figure it out.
Hi All,
The story, I'm on vacation in Austria with my new HOX+ and suddenly I get an update for it. So I downloaded it and installed it. Suddenly I have no cell connection and cannot use wi-fi anymore. The phone is stuck in Airplane Mode and can not get out.
So I go looking on the web and spent hours reading on flashing, downgrading, rooting etc. So I decide to downgrade it to stock. Something went horribly wrong, as it didn't work. I unlocked it, every step correctly. Then I tried it again, and again, and again. Multiple different guides, video's everything. So then I thought I found a solution, install JB 4.1.2. So, following every step correctly I try this, no succes. But now suddenly I cannot see the sdcard, htc sync doesn't find my phone etc. Also, my phone doesn't go past the HTC bootlogo. I can now only run the bootloader by power vol-
So I try to flash the JB again, connection error, cannot find folder etc. So I start looking again, tried recovery, factory reset, nothing works. Flashed CWM 5.8.4.0 into the recovery, does not boot, only up to the HTC logo then powers down and reboots bootloader.
So here I go to the last resort: Stock RUU. I download the correct RUU for my HOX+ -in this case RUU_ENRC2B_U_JB_45_HTC_Europe_1.16.401.6_Radio_3.1204.168.32_release_297177_signed .... I start the programme and it works good and then it starts rebooting the bootloader and then I get the black background with silver HTC letters and then the RUU says Error 171 USB Connection Error.
I've tried about 10 times now in different USB slots, same thing every time.
Also, when I start the bootloader from scratch, it says Checking SD update... Failed to open usb master mode
Is there anybody who can help me? I have tried for 30 hours now, every single option (I think?)... I don't care what kind of ROM goes on there, stock, jb, evolution as long as it works!
Ran the RUU with admin rights?
Sent from my HTC One X
TToivanen said:
Ran the RUU with admin rights?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, I did, first without and then multiple times with as I read that advice somewhere as well.
Also, I did relock the phone first as I read that somewhere, forgot to state above.
Ok the twentieth time seems to be a charm, after 5 hours trying the RUU is succesfully installed and everything works perfectly fine now!
Many thanks! Not sure if I would have tried again and again after it kept failing!
Also, probably wrong forum? HoX+ should have it's own forum does it not?
Gerolamos said:
Ok the twentieth time seems to be a charm, after 5 hours trying the RUU is succesfully installed and everything works perfectly fine now!
Many thanks! Not sure if I would have tried again and again after it kept failing!
Click to expand...
Click to collapse
i have same problem should i try diffrent RUU or try 20th time ??
what should i do
Okay, this is really weird. I tried flashing the no red text HBOOT file via RUU and it seemed to get rid of the red text, but now for some reason it goes through the entire boot sequence and boots into the OS while still showing the boot screen. I can get texts and notifications in the background, and it vibrates when I hold down the power button, meaning the power menu is showing up but nothing else will respond. The boot screen on my phone is actually the google bootscreen from the GPE version for some reason, because when I switched to and from the GPE edition it just stayed that way.
This is pretty weird, does anybody know what it could be?
Alright, I tried flashing the stock hboot and the red text is back, but I'm still having the same problem.
Aaand I managed to fix it by flashing the entire stock firmware via RUU. Still though, what was going on here...? Also, the red text is gone too for some reason, even though I never flashed the red text-less version again. Huh.
octagonPerfectionist said:
Aaand I managed to fix it by flashing the entire stock firmware via RUU. Still though, what was going on here...? Also, the red text is gone too for some reason, even though I never flashed the red text-less version again. Huh.
Click to expand...
Click to collapse
Red text shows only when your try to use a custom recovery etc etc. Stock boot doesnt even show that screen.
bloodhawk said:
Red text shows only when your try to use a custom recovery etc etc. Stock boot doesnt even show that screen.
Click to expand...
Click to collapse
Yeah, I realized that.
Do you know why my phone got stuck with the google bootscreen...? This really seems to be causing quite a bit of trouble, I've had to reflash the firmware several times after having it get stuck in that weird state again. It happened again after I tried to flash the kernel to a custom one, but everything was working fine before I tried flashing that custom HBOOT.
octagonPerfectionist said:
Yeah, I realized that.
Do you know why my phone got stuck with the google bootscreen...? This really seems to be causing quite a bit of trouble, I've had to reflash the firmware several times after having it get stuck in that weird state again. It happened again after I tried to flash the kernel to a custom one, but everything was working fine before I tried flashing that custom HBOOT.
Click to expand...
Click to collapse
Did you by chance flash the wrong hboot the first time around?
bloodhawk said:
Did you by chance flash the wrong hboot the first time around?
Click to expand...
Click to collapse
Nope, I downloaded the Telus one, the one for my device - my CID though was set to SuperCID, though I'm not sure how that would make much of a difference. I did switch it back to the Telus one while it was doing that thing, but I didn't reflash the HBOOT while it had the Telus CID.
octagonPerfectionist said:
Nope, I downloaded the Telus one, the one for my device - my CID though was set to SuperCID, though I'm not sure how that would make much of a difference. I did switch it back to the Telus one while it was doing that thing, but I didn't reflash the HBOOT while it had the Telus CID.
Click to expand...
Click to collapse
That is pretty weird, im guessing either the Hboot was corrupted maybe or the version on the file was wrong. One way i would suggest would be to flash a full RUU or a full firmware.zip (1.4Gb + size).
bloodhawk said:
That is pretty weird, im guessing either the Hboot was corrupted maybe or the version on the file was wrong. One way i would suggest would be to flash a full RUU or a full firmware.zip (1.4Gb + size).
Click to expand...
Click to collapse
Where would I find the full RUU or full firmware.zip? It was honestly pretty hard to even find the small ~40MB one that I pulled the stock HBOOT from, since Telus isn't an american carrier. I couldn't find any of that stuff on HTC's website either.
Anyway, I never bothered trying to flash the modified HBOOT again since I didn't want to deal with that problem again.
Do you have any idea what's up with the initial boot screen still being stuck as the Google one though?
octagonPerfectionist said:
Where would I find the full RUU or full firmware.zip? It was honestly pretty hard to even find the small ~40MB one that I pulled the stock HBOOT from, since Telus isn't an american carrier. I couldn't find any of that stuff on HTC's website either.
Anyway, I never bothered trying to flash the modified HBOOT again since I didn't want to deal with that problem again.
Do you have any idea what's up with the initial boot screen still being stuck as the Google one though?
Click to expand...
Click to collapse
Nope this is the first time im hearing about this issue.
Ill probably look for it once im back home later today. Can you post your original MID and CID? Also what was the original firmware version ?
bloodhawk said:
Nope this is the first time im hearing about this issue.
Ill probably look for it once im back home later today. Can you post your original MID and CID? Also what was the original firmware version ?
Click to expand...
Click to collapse
The MID is: 0P6B16000
Original CID: CID-TELUS001
How would I go about finding the original firmware version?
Thanks for the help!
The base firmware the phone came with. Im not entirely sure if you can just change the CID/MID and flash a RUU from a different region.
But if you are running a custom ROM, it might be different.
Alright sorry for the super late reply, just been busy. I tried looking for the RUU but couldnt really find the executable. The best option would be to look for the proper zips.
Is the problem still there or did you manage to fix it ?
bloodhawk said:
Alright sorry for the super late reply, just been busy. I tried looking for the RUU but couldnt really find the executable. The best option would be to look for the proper zips.
Is the problem still there or did you manage to fix it ?
Click to expand...
Click to collapse
Well, I'm still running into the problem with the red text removal HBOOT not working properly, but honestly I think I can probably just deal with it for now. I still honestly have no idea how to fix the boot splash being the stock google one though. It seems kind of weird that it just got stuck like that. I don't have any urgent need to switch that back to stock for now though.
Thanks a lot anyway!!
Stucked on boot screen
I accidently installed wrong boot.img via adb and i'm stucked at boot screen, I wiped rom , factory reseted, cleared everything, tryed installing valid .zip . nothing worked for me. Plz tell me some solution. I'm owning a uk h3g htc one m8.
Ahsan- said:
I accidently installed wrong boot.img via adb and i'm stucked at boot screen, I wiped rom , factory reseted, cleared everything, tryed installing valid .zip . nothing worked for me. Plz tell me some solution. I'm owning a uk h3g htc one m8.
Click to expand...
Click to collapse
Not nearly enough info. Saying things like "cleared everything" and "nothing worked" doesn't help. You need to state specifically and in detail what you have tried, otherwise its difficult to help. More detail is always better.
What ROM did you try to install? Did you try others? What recovery and version?
Normally, if you want to replace the boot.img, just re-flash the current ROM.