Hi
I was rooting my phone today (not for the 1st time). I had root, and needed to use a few commands in terminal. I updated to Jesus Freak's 1.5 software, and I am now stuck in the boot screen (Android).
I'd appreciate help. I can't access my SD...
Anyone? It's late, i've got a busy day tomorrow and I need my phone to work... i'd really appreciate it...
Ok, it got me through somehow, but it says i'm on a dev phone???
paddlesmack said:
Ok, it got me through somehow, but it says i'm on a dev phone???
Click to expand...
Click to collapse
yes because you flashed Jf's ADP image......
Problem solved
I'm assuming you used icoke to unlock first?
mssmison said:
I'm assuming you used icoke to unlock first?
Click to expand...
Click to collapse
Yeah i did, i relocked it then unlocked it with an older version of coke I had and it seems to be working now. Freaked me out though >.<
Same problem....
Hey i seem to be having the same problem with my phone, was wondering if u could give me the steps u used and what relocker u used and unlocker. I would greatly appreciated!!=)
Why do you people necro post? Make a new thread with your problem. I can garuntee you whatever he did in march is not going to work for you now.
Finally froyo is being rolled out to wildfire this week in europe first.
So if is it possible to get the official update in our phones without losing superuser
privilege? Any developer pls consider this issue and post the official update....
Official update is in HTC facebook.
Just when I've rooted my phone...
shann_mishra said:
Finally froyo is being rolled out to wildfire this week in europe first.
So if is it possible to get the official update in our phones without losing superuser
privilege? Any developer pls consider this issue and post the official update....
Official update is in HTC facebook.
Click to expand...
Click to collapse
****s sake.
Been done. Learn to read
Marc. said:
Just when I've rooted my phone...
Click to expand...
Click to collapse
You say that like it's a bad thing. It's not. Its good.
Hmmm I have downloaded the new update and tried it twice. It was running for an hour so I pressed the power button and then says unable to initiate... I am doing something wrong or is there something else I need to do. I have had a different rom on this phone but reset phone to vodafone standard... Hopefully someone will be able to reply with me being blasted of the site for being a newbie who can not read. However, I have searched long and hard for an answer to this and have yet to find one!
Cheers
Steve
stephenr said:
Hmmm I have downloaded the new update and tried it twice. It was running for an hour so I pressed the power button and then says unable to initiate... I am doing something wrong or is there something else I need to do. I have had a different rom on this phone but reset phone to vodafone standard... Hopefully someone will be able to reply with me being blasted of the site for being a newbie who can not read. However, I have searched long and hard for an answer to this and have yet to find one!
Cheers
Steve
Click to expand...
Click to collapse
I don't understand...your phone doesn't boot?
After unlocking my phone using HTCDEV,
I've tried to root it using "HTC_QuickRoot_1.1.13_Release",
and it claimed something like the flash img not compatible
with it and then my phone shut down (!)
now I can't turn it on for a couple of hours (theres no LED btw).
Please Help! (Iv'e searched in the threads for some problems declaimed like mine and found nothing like)
Thanks in advanced guys!
nyg85 said:
After unlocking my phone using HTCDEV,
I've tried to root it using "HTC_QuickRoot_1.1.13_Release",
and it claimed something like the flash img not compatible
with it and then my phone shut down (!)
now I can't turn it on for a couple of hours (theres no LED btw).
Please Help! (Iv'e searched in the threads for some problems declaimed like mine and found nothing like)
Thanks in advanced guys!
Click to expand...
Click to collapse
Well, one word : Service :laugh:
this is the only way huh?
nyg85 said:
this is the only way huh?
Click to expand...
Click to collapse
I guess.......and next time when you wanna root etc. just have the patience and read everything that is written here.
Never the less some phones are more durable in that matter ( i don't know why ). Some phones are like butter, 1st attempt and you are rooted. And with another you sweat like a pig and even then you can't do it right :laugh:
well
Well,
I hope it'll get better
thanx
Before bringing your phone to service you could try:
- a factory reset. Maybe the unsuccessfull rooting attempt has messed up something you can fix this way.
- flashing a RUU and see if the issue remains. This usually sorts out...
Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)
Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse
Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.
alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?
Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia
akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.