I'm flushing a tmibile ruu into rooted with custom ROM. I did all step. Installed drivers, relocked bootloader, launched the exe all went well except that the whole operation should take about 10min. It's been an hour now and it's not finished, it's still updating. That's not normal. Am I doing something wrong? Any suggestion on what to do to finish this update up.?
dihcar said:
I'm flushing a tmibile ruu into rooted with custom ROM. I did all step. Installed drivers, relocked bootloader, launched the exe all went well except that the whole operation should take about 10min. It's been an hour now and it's not finished, it's still updating. That's not normal. Am I doing something wrong? Any suggestion on what to do to finish this update up.?
Click to expand...
Click to collapse
If your sure your using the correct ruu it could be HTCSync. Do you have it installed. If you do uninstall it but leave drivers installed. Reboot your pc and try again. HTCSync is known to interfere with RUU mode
Other than that just make sure you have the correct ruu. It should match your MID and CID and if your s-on it must match or have a newer firmware than you currently have :good:
Danny201281 said:
If your sure your using the correct ruu it could be HTCSync. Do you have it installed. If you do uninstall it but leave drivers installed. Reboot your pc and try again. HTCSync is known to interfere with RUU mode
Other than that just make sure you have the correct ruu. It should match your MID and CID and if your s-on it must match or have a newer firmware than you currently have :good:
Click to expand...
Click to collapse
I have htcsync unstalled, I'll try to uninstall it. The ruu is T-Mobile'd that's what it say.
I'll give it another try. Later on. Thanks
finally I was able to flash my m7 to tmobile stock, I did nothing special except I repeated the operation and the third time was a charm. buuuut now I'm confronted with another problem, the phone randomly reboots with no reason, I tried to fix that by booting in safe mode didn't help, got into recovery and wiped cache partition didn't help either and now am stuck again. the phone is unusable as it is. any HELPFUL suggestion will be very welcome.
dihcar said:
finally I was able to flash my m7 to tmobile stock, I did nothing special except I repeated the operation and the third time was a charm. buuuut now I'm confronted with another problem, the phone randomly reboots with no reason, I tried to fix that by booting in safe mode didn't help, got into recovery and wiped cache partition didn't help either and now am stuck again. the phone is unusable as it is. any HELPFUL suggestion will be very welcome.
Click to expand...
Click to collapse
is your phone T-mobile US ?
try this RUU >> http://www.htc.com/us/support/htc-one-t-mobile/news/
clsA said:
is your phone T-mobile US ?
try this RUU >> http://www.htc.com/us/support/htc-one-t-mobile/news/
Click to expand...
Click to collapse
Yes T-Mobile and I flushed the same RUU as in your link it's the latest.
dihcar said:
Yes T-Mobile and I flushed the same RUU as in your link it's the latest.
Click to expand...
Click to collapse
Check in the phone settings
Settings>About>Phone Identity - Is your Imei displayed as Unknown? Also check baseband in
Settings>About>Software Information>More - is it displayed as Unknown also?
Danny201281 said:
Check in the phone settings
Settings>About>Phone Identity - Is your Imei displayed as Unknown? Also check baseband in
Settings>About>Software Information>More - is it displayed as Unknown also?
Click to expand...
Click to collapse
I did that already all informations are displayed imei...etc. The software too that's how I knew it's the same ruu. The #s match.
dihcar said:
I did that already all informations are displayed imei...etc. The software too that's how I knew it's the same ruu. The #s match.
Click to expand...
Click to collapse
Can you post the output of
Code:
fastboot getvar all
What type of bootloop are you having, looping before its finished booting or is it booting up ok then randomly restarting.
Did it bootloop immediately after flashing the ruu or did you flash something after like a custom recovery or rom?
Danny201281 said:
Can you post the output of
Code:
fastboot getvar all
What type of bootloop are you having, looping before its finished booting or is it booting up ok then randomly restarting.
Did it bootloop immediately after flashing the ruu or did you flash something after like a custom recovery or rom?
Click to expand...
Click to collapse
It reboots randomly sometimes just after boot loop when swept lock screen to get to home, sometimes it for about 10min then reboots. I'm not rooted anymore I have stock recovery that's why I flashed the ruu. Because when I was running custom ROMs, there was no random reboot but the baseband was unknown, no radios I couldn't connect to network. I tried to flash tmo radio through twrp it succeeded but baseband remained unknown. That's why I wanted to unroot and go back to stock. Sorry I don't know the history of this phone. That's the way i got it rooted, unlocked bootloader, twrp recovery running cm11 with no baseband.
dihcar said:
It reboots randomly sometimes just after boot loop when swept lock screen to get to home, sometimes it for about 10min then reboots. I'm not rooted anymore I have stock recovery that's why I flashed the ruu. Because when I was running custom ROMs, there was no random reboot but the baseband was unknown, no radios I couldn't connect to network. I tried to flash tmo radio through twrp it succeeded but baseband remained unknown. That's why I wanted to unroot and go back to stock. Sorry I don't know the history of this phone. That's the way i got it rooted, unlocked bootloader, twrp recovery running cm11 with no baseband.
Click to expand...
Click to collapse
Unknown IMEI and Baseband Most likely a hardware problem. If you have warranty i would return to stock and send it for reapair :good:
That's a why I asked you to check these settings.
Danny201281 said:
Check in the phone settings
Settings>About>Phone Identity - Is your Imei displayed as Unknown? Also check baseband in
Settings>About>Software Information>More - is it displayed as Unknown also?
Click to expand...
Click to collapse
If flashing an RUU didn't fix it then its probably hardware related :good:
Danny201281 said:
Unknown IMEI and Baseband Most likely a hardware problem. If you have warranty i would return to stock and send it for reapair :good:
Click to expand...
Click to collapse
Wow no hope!? how sure are you about that!
Like I said I have no warranty. Maybe a good motherboard will fix it, otherwise like you said I'll send it to the reaper! lol.
dihcar said:
Wow no hope!? how sure are you about that!
Like I said I have no warranty. Maybe a good motherboard will fix it, otherwise like you said I'll send it to the reaper! lol.
Click to expand...
Click to collapse
I have come across many cases of this on the forum. Only one of them I was able to help get working again and the symptoms were slightly different. There was no RUN in that case so we returned it to stock with a ROM and firmware package and it was working normally again. Obviously the RUU will have done this for you.
Only 1 other i know of that was repaired and it was opened up and to the best of my knowledge the Antenna Connector wire was replaced. And it solved the problem. I'll try track down a link for that one and post it here.
Danny201281 said:
I have come across many cases of this on the forum. Only one of them I was able to help get working again and the symptoms were slightly different. There was no RUN in that case so we returned it to stock with a ROM and firmware package and it was working normally again. Obviously the RUU will have done this for you.
Only 1 other i know of that was repaired and it was opened up and to the best of my knowledge the Antenna Connector wire was replaced. And it solved the problem. I'll try track down a link for that one and post it here.
Click to expand...
Click to collapse
Just FYI after the flash the baseband and imei are there.
This is the baseband 4T.28.3218.04_10.33E1718.01L it's a tmobile and it looks normal.
dihcar said:
Just FYI after the flash the baseband and imei are there.
This is the baseband 4T.28.3218.04_10.33E1718.01L it's a tmobile and it looks normal.
Click to expand...
Click to collapse
Well and i'm clutching at straws here, but have you tried flashing it multiple times before booting the device. Maybe that will help it stick??
Danny201281 said:
Well and i'm clutching at straws here, but have you tried flashing it multiple times before booting the device. Maybe that will help it stick??
Click to expand...
Click to collapse
Yeah I'll try that when I get little more time. Meanwhile thanks and happy new year or holidays. :angel:
update
I did flash the ruu once again it was worse, I did not go past the lock screen. as soon as I swipe to get to home it reboots. now I decided rooting it again and using a custom rom like cm11 or smoothliquid, the rebooting problem did not exist when I used them, but I hope the base band holds there this time.
I succeeded to submit a token to htddev to unlock bootloader again, and I'm waiting for the unlock code bin email. it's been like 10hrs and still nothing. should I do something or just wait?
dihcar said:
I did flash the ruu once again it was worse, I did not go past the lock screen. as soon as I swipe to get to home it reboots. now I decided rooting it again and using a custom rom like cm11 or smoothliquid, the rebooting problem did not exist when I used them, but I hope the base band holds there this time.
I succeeded to submit a token to htddev to unlock bootloader again, and I'm waiting for the unlock code bin email. it's been like 10hrs and still nothing. should I do something or just wait?
Click to expand...
Click to collapse
CM11 will stop the rebooting, I don't know why but it does. It won't fix it though. But at least the device will be stable.
This issue is also known to get worse overtime. So I think it will only get worse.
If you have your original unlock_code.bin you can just flash it again you don't need to wait for htcdev.
If you don't have it on your pc see if you still have the original e-mail it was attached to. :good:
Danny201281 said:
CM11 will stop the rebooting, I don't know why but it does. It won't fix it though. But at least the device will be stable.
This issue is also known to get worse overtime. So I think it will only get worse.
If you have your original unlock_code.bin you can just flash it again you don't need to wait for htcdev.
If you don't have it on your pc see if you still have the original e-mail it was attached to. :good:
Click to expand...
Click to collapse
I don't have the first one, I was given the phone already rooted, I checked my spam nothing should I wait or submit again?
dihcar said:
I don't have the first one, I was given the phone already rooted, I checked my spam nothing should I wait or submit again?
Click to expand...
Click to collapse
Well given its new years day it may take a little longer than usual. So I would just wait it out :good:
Related
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
help me
lastrastuff said:
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
Click to expand...
Click to collapse
Did this work? my first has been in a boot loop for months. I can't get ADB, Fastboot or RUU to recognize the device.
sara_groves said:
Did this work? my first has been in a boot loop for months. I can't get ADB, Fastboot or RUU to recognize the device.
Click to expand...
Click to collapse
Well I have a working phone if that's what you mean. If you are able to get your phone into fastboot you can go through with an RUU usually.
lastrastuff said:
Well I have a working phone if that's what you mean. If you are able to get your phone into fastboot you can go through with an RUU usually.
Click to expand...
Click to collapse
I with it some more last night. I did finally get ADB to work, but still no fastboot. Shop i was able to push in filters... i just have no way of flashing.
bootlaoder block you should have before making the ruu to lock the bootloader needs to enter fastboot, in fastboot type this command fastboot oem lock, try it on mac as it would not need to install drivers.
Ok this guide works for me!
the problem is this traslate for spanish, a don't speak english, i hope you fix your phone...
http:/ /www. htcmania. com/ showthread. php?t=548748
lastrastuff said:
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
Click to expand...
Click to collapse
It seems your phone stuck in a bootloop after flash a rom and kernel,are you sure the rom and kernel is ok?
Well my htc one was working fine but then one morning it go stuck on the loading screen so i hard reset it. Then thats when the problem started my htc one would go black screen (Still backlit) after a couple of sec of idle, this also happens when i try to change a setting or use a app. For example when try to log on to the wifi the screen goes black but i can still works cause i vibrates when i type something. I can receive and make calls and texts although another problem is the keyboard disappears after the first character i type. I can use google chrome but not the stock internet app it goes black screen the keyboard problem makes it really hard to use the internet. i can change the know if the usb debugging is on so i cant try to custom rom it. Is there anything i can do other then getting a new phone?
0kenny0 said:
Well my htc one was working fine but then one morning it go stuck on the loading screen so i hard reset it. Then thats when the problem started my htc one would go black screen (Still backlit) after a couple of sec of idle, this also happens when i try to change a setting or use a app. For example when try to log on to the wifi the screen goes black but i can still works cause i vibrates when i type something. I can receive and make calls and texts although another problem is the keyboard disappears after the first character i type. I can use google chrome but not the stock internet app it goes black screen the keyboard problem makes it really hard to use the internet. i can change the know if the usb debugging is on so i cant try to custom rom it. Is there anything i can do other then getting a new phone?
Click to expand...
Click to collapse
Im not sure to understand everything you said here but first you should try to clear cache ''fastboot clear cache'' and clear dalvik cache if you have a custom recovery on your phone.
Then if your phone still crashes, use the factory reset option.
0kenny0 said:
i can change the know if the usb debugging is on so i cant try to custom rom it
Click to expand...
Click to collapse
usb debugging is not required to flash a custom rom. Only to use adb when the phone is booted in the OS
alray said:
Im not sure to understand everything you said here but first you should try to clear cache ''fastboot clear cache'' and clear dalvik cache if you have a custom recovery on your phone.
Then if your phone still crashes, use the factory reset option.
usb debugging is not required to flash a custom rom. Only to use adb when the phone is booted in the OS
Click to expand...
Click to collapse
So how would you clear said things? And this happened after the factory reset.
0kenny0 said:
So how would you clear said things?
Click to expand...
Click to collapse
clear cache using fastboot:
Code:
fastboot erase cache
0kenny0 said:
And this happened after the factory reset.
Click to expand...
Click to collapse
You said this happened after a hard reset not factory reset. So try to factory reset from the OS or from recovery
it go stuck on the loading screen so i hard reset it. Then thats when the problem started my htc one would go black screen
Click to expand...
Click to collapse
alray said:
clear cache using fastboot:
Code:
fastboot erase cache
You said this happened after a hard reset not factory reset. So try to factory reset from the OS or from recovery
Click to expand...
Click to collapse
ya i thought factory reset and hard reset was the same so what i meant to say is after the factory reset it happened.
0kenny0 said:
ya i thought factory reset and hard reset was the same so what i meant to say is after the factory reset it happened.
Click to expand...
Click to collapse
what rom are you on? stock? Do you have a custom recovery installed?
Bhavpreet said:
what rom are you on? stock? Do you have a custom recovery installed?
Click to expand...
Click to collapse
i have no idea i bought it from some one i would assume it was the stock.
0kenny0 said:
i have no idea i bought it from some one i would assume it was the stock.
Click to expand...
Click to collapse
go to settings>about>software information and tell me what it says beside software number.
Bhavpreet said:
go to settings>about>software information and tell me what it says beside software number.
Click to expand...
Click to collapse
the software number is : 4.19.666.8
0kenny0 said:
the software number is : 4.19.666.8
Click to expand...
Click to collapse
So i guess its stock, from bell. Go to setup>backup and reset>backup now and let your phone get backed up to either google drive or dropbox. Then on the same page hit "reset phone", it should be the last option, if you cant find it its setup>backup and reset>reset phone and see if that helps.
After the resets done just restore everything from that backup and it should be fine after that.
Bhavpreet said:
So i guess its stock, from bell. Go to setup>backup and reset>backup now and let your phone get backed up to either google drive or dropbox. Then on the same page hit "reset phone", it should be the last option, if you cant find it its setup>backup and reset>reset phone and see if that helps.
After the resets done just restore everything from that backup and it should be fine after that.
Click to expand...
Click to collapse
Well i reset it still the same. any other suggestions?
0kenny0 said:
Well i reset it still the same. any other suggestions?
Click to expand...
Click to collapse
Well there's plenty of things you could do, but these would require modifying the phone and possibly getting rid of your warranty. So is there any warranty left on the phone?
Also, boot into the bootloader: shutdown the phone, make sure fastboot is turned off, and hold the down volume button and the power button. It should boot into a screen thats white, let me know some of the information on that screen. On the top of the screen does it say anything like
***unlocked*** or ***tampered***? And does the line following these words say "M7UL PVT SHIP S-ON RH" or "M7UL PVT SHIP S-OFF"
Look at the pic for reference.
Bhavpreet said:
Well there's plenty of things you could do, but these would require modifying the phone and possibly getting rid of your warranty. So is there any warranty left on the phone?
Also, boot into the bootloader: shutdown the phone, make sure fastboot is turned off, and hold the down volume button and the power button. It should boot into a screen thats white, let me know some of the information on that screen. On the top of the screen does it say anything like
***unlocked*** or ***tampered***? And does the line following these words say "M7UL PVT SHIP S-ON RH" or "M7UL PVT SHIP S-OFF"
Look at the pic for reference.
Click to expand...
Click to collapse
No warranty. It says lock M7_UL PUT SHIP S-ON RH.
0kenny0 said:
No warranty. It says lock M7_UL PUT SHIP S-ON RH.
Click to expand...
Click to collapse
so i would suggest unlocking the device, installing a custom recovery, and getting a custom rom on the device, this will most probably solve the issue and give you some other benefits as well.
Note that these things can be potentially dangerous if not done properly, so be careful, because no one (including me) will be responsible if you mess up your phone.
Theres plenty of tutorials around xda teaching you how to unlock and install these things etc.
Bhavpreet said:
so i would suggest unlocking the device, installing a custom recovery, and getting a custom rom on the device, this will most probably solve the issue and give you some other benefits as well.
Note that these things can be potentially dangerous if not done properly, so be careful, because no one (including me) will be responsible if you mess up your phone.
Theres plenty of tutorials around xda teaching you how to unlock and install these things etc.
Click to expand...
Click to collapse
Quick question does the phone lock again when you use a different sim cause i bought this unlocked.
0kenny0 said:
Quick question does the phone lock again when you use a different sim cause i bought this unlocked.
Click to expand...
Click to collapse
if the phone was sim-unlocked then it will remains unlocked even if you flash a custom rom.
alray said:
if the phone was sim-unlocked then it will remains unlocked even if you flash a custom rom.
Click to expand...
Click to collapse
would you suggest any rom or should i just go for one that looks good.
0kenny0 said:
would you suggest any rom or should i just go for one that looks good.
Click to expand...
Click to collapse
every roms are good, but I would recommend you to use ARHD 53.
or you can try arhd 62 if you want to try sense 6. not sure if 62 is rock stable yet so if you want a stable rom go with arhd 53.
alray said:
every roms are good, but I would recommend you to use ARHD 53.
or you can try arhd 62 if you want to try sense 6. not sure if 62 is rock stable yet so if you want a stable rom go with arhd 53.
Click to expand...
Click to collapse
ok i installed clockwork recovery and then i installed ARHD 53 and now its stuck on the htc screen the recovery will not boot up it just boots up for a sec then it goes to the htc logo and i cant factor reset it cause it just goes to recovery so now what.
0kenny0 said:
ok i installed clockwork recovery and then i installed ARHD 53 and now its stuck on the htc screen the recovery will not boot up it just boots up for a sec then it goes to the htc logo and i cant factor reset it cause it just goes to recovery so now what.
Click to expand...
Click to collapse
clockworkmod recovery?
From ARHD thread:
Hey guys,
I'm desperately trying to flash a ROM on my HTC One, after it began boot looping. I've tried sideloading several ROMs but everyone stucks on Writing Data & System. I really don't know what to do next. This comes after almost a sleepless night trying to make it work. Glad that now it enters Recovery. Can you please help me? I'd kindly appreciate..
Even when I try to restore a backup it stucks and reboots, returning an error something like (error /tmp/... status 1). If anyone knows how to fix it..
whoisrikk said:
Even when I try to restore a backup it stucks and reboots, returning an error something like (error /tmp/... status 1). If anyone knows how to fix it..
Click to expand...
Click to collapse
You'll have to post much more info about your handset if you want help. What rom/version number are you trying to flash? What is your recovery/version number? Did you MD5 check sum your rom and recovery before flashing? What is the output of fastboot getvar all (except imei/sn)
alray said:
You'll have to post much more info about your handset if you want help. What rom/version number are you trying to flash? What is your recovery/version number? Did you MD5 check sum your rom and recovery before flashing? What is the output of fastboot getvar all (except imei/sn)
Click to expand...
Click to collapse
Thank you for your help. I was running the Insertcoin M8 Port and the latest TWRP recovery. The problem seems to be bigger. I took the phone to a local GSM service and the guy there (the only one repairing HTCs in the whole city) said that there was a big mismatch between the hboot and baseband (not sure if these two) and also the ROM I was using started altering the system and the internal storage (he mentioned something about clusters and how the ROM degraded the system).
There were also some artifacts on the boot screen, he assumed that there are problems from the video card. I previously owned a Nexus 4 and had no problems rooting/flashing/using any ROM. He also pointed that the ultimate solution would be to disassemble the phone and repair the memory chip but with 50/50 chances of working..
whoisrikk said:
Thank you for your help. I was running the Insertcoin M8 Port and the latest TWRP recovery. The problem seems to be bigger. I took the phone to a local GSM service and the guy there (the only one repairing HTCs in the whole city) said that there was a big mismatch between the hboot and baseband (not sure if these two) and also the ROM I was using started altering the system and the internal storage (he mentioned something about clusters and how the ROM degraded the system).
There were also some artifacts on the boot screen, he assumed that there are problems from the video card. I previously owned a Nexus 4 and had no problems rooting/flashing/using any ROM. He also pointed that the ultimate solution would be to disassemble the phone and repair the memory chip but with 50/50 chances of working..
Click to expand...
Click to collapse
post your fastboot getvar all
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.
Hello,
One week ago, I was using my phone as usual when suddenly froze and I pulled the battery, then I was stuck in boot loop so I decided to go into download mode and reflash it, but I accidentally flashed H811N instead of H811H , now my phone is hard bricked !! " No charging / No download mode / Nothing at all " , is there any way to fix it ?
Thanks
There's a fix a couple posts down. Have you tried that yet?
mjoecarroll said:
There's a fix a couple posts down. Have you tried that yet?
Click to expand...
Click to collapse
Yes I tried but I got some errors ! I don't know why, I think it might be because of I did not find a stock dump (img) of H81110H ?
What errors did you get? Which build did you use?
Also, try this. It doesn't look like he has the system.img available, but you could always try to pull it out of the kdz. There's some directions online.
mjoecarroll said:
What errors did you get? Which build did you use?
Also, try this. It doesn't look like he has the system.img available, but you could always try to pull it out of the kdz. There's some directions online.
Click to expand...
Click to collapse
Thanks a lot for your answer, what it really happened that I manged to make it boot to bootloader for the first time, then I tried to flash the KDZ file, but it stuck on 9% giving me an error, then I tried to go to download mode again but now it gives me blank screen !! ..
mo5br said:
Thanks a lot for your answer, what it really happened that I manged to make it boot to bootloader for the first time, then I tried to flash the KDZ file, but it stuck on 9% giving me an error, then I tried to go to download mode again but now it gives me blank screen !! ..
Click to expand...
Click to collapse
Were you able to try the files I gave you there?
And do you know which error it gave you? You might want to try to fastboot a recovery (put a recovery in the same folder as your adb and fastboot, name it recovery.img, run command "fastboot boot recovery.img", then installing a rom from the recovery), although I haven't tried his method yet so I am not sure if that is even possible.
mjoecarroll said:
Were you able to try the files I gave you there?
And do you know which error it gave you? You might want to try to fastboot a recovery (put a recovery in the same folder as your adb and fastboot, name it recovery.img, run command "fastboot boot recovery.img", then installing a rom from the recovery), although I haven't tried his method yet so I am not sure if that is even possible.
Click to expand...
Click to collapse
I actually the error was about flashing a different version then I tried for another time gave an error of different size of firmware.
When I try to connect the phone to my computer, it appeares as "qhsusb_bulk" and doesn't recognize the phone.
Now I can't turn it on or charge it, or even getting to download mode ! ??
Try using the Google Android adb drivers. Keep trying different USB ports until it works.
mjoecarroll said:
Try using the Google Android adb drivers. Keep trying different USB ports until it works.
Click to expand...
Click to collapse
I tried but still not recognizable, I tried all ports in my computer but still not working .. any other ideas ?
mo5br said:
I tried but still not recognizable, I tried all ports in my computer but still not working .. any other ideas ?
Click to expand...
Click to collapse
Something similar happened on my G2 at one point, so everything I'm saying is going off that.
Firstly, what was the situation of your phone prior to this? Was it rooted? Did it tend to overheat? What are the first three numbers on your serial number?
mjoecarroll said:
Something similar happened on my G2 at one point, so everything I'm saying is going off that.
Firstly, what was the situation of your phone prior to this? Was it rooted? Did it tend to overheat? What are the first three numbers on your serial number?
Click to expand...
Click to collapse
Well I did a really strange thing, in which I put my phone in the freezer, and I got into the download mode again. When I start to flash the KDZ file, I got an error " Erro Code = 0x2000, TOT antirollback version is smaller than device version. " , any ideas how can I solve it ?
mo5br said:
Well I did a really strange thing, in which I put my phone in the freezer, and I got into the download mode again. When I start to flash the KDZ file, I got an error " Erro Code = 0x2000, TOT antirollback version is smaller than device version. " , any ideas how can I solve it ?
Click to expand...
Click to collapse
That usually means you were on marshmallow and tried to downgrade to lollipop. You sure you had lollipop?
mjoecarroll said:
That usually means you were on marshmallow and tried to downgrade to lollipop. You sure you had lollipop?
Click to expand...
Click to collapse
I am actually not sure which version I had !! any ideas ?
Did your notifications show up on your lockscreen?
mjoecarroll said:
Did your notifications show up on your lockscreen?
Click to expand...
Click to collapse
I think I was on Lollipop (5.0) , since i did a quick research and I found out that ..
mo5br said:
I think I was on Lollipop (5.0) , since i did a quick research and I found out that ..
Click to expand...
Click to collapse
What build versions did you use to try to fix your phone?
mjoecarroll said:
What build versions did you use to try to fix your phone?
Click to expand...
Click to collapse
Unfortunately, I don't know I am so sorry...
mo5br said:
Unfortunately, I don't know I am so sorry...
Click to expand...
Click to collapse
At this point, I'd recommend trying the method with every version on opensource.lge.com newer than the version you tried that gave you the previous error.
mjoecarroll said:
At this point, I'd recommend trying the method with every version on opensource.lge.com newer than the version you tried that gave you the previous error.
Click to expand...
Click to collapse
I'll try and let you know what would happen, thanks a lot
mjoecarroll said:
At this point, I'd recommend trying the method with every version on opensource.lge.com newer than the version you tried that gave you the previous error.
Click to expand...
Click to collapse
Unfortunately, nothing worked with me ? what's the next step now ? :crying: