Hi, I recently installed lineage os rom (from sense-rom). So after the installation I was really pleased that the phone was back to normal but later i realize the audio has completely vanished. I can't play any songs, videos start but they are as on mute. same goes for playing videos on Instagram and YouTube. Actually on YouTube I get the error message '' There was a problem while playing Touch to retry''. Even there is no ringtone volume sound, i also tired to change it but its says unable to play. I also tried to recover my recovery of stock 4.4.4 and also did factory reset later but the problem still persists.
Any support would be appreciated. Thank you.
aweshlakhani said:
Hi, I recently installed lineage os rom (from sense-rom). So after the installation I was really pleased that the phone was back to normal but later i realize the audio has completely vanished. I can't play any songs, videos start but they are as on mute. same goes for playing videos on Instagram and YouTube. Actually on YouTube I get the error message '' There was a problem while playing Touch to retry''. Even there is no ringtone volume sound, i also tired to change it but its says unable to play. I also tried to recover my recovery of stock 4.4.4 and also did factory reset later but the problem still persists.
Any support would be appreciated. Thank you.
Click to expand...
Click to collapse
Flash RUU or firmware only .
Sent from my htc_m8 using Tapatalk
sonnu0100 said:
Flash RUU or firmware only .
Click to expand...
Click to collapse
Agreed. Sound issues like this are usually a result of outdated or damaged firmware.
@ sonnu0100 @redpoint73
Thanks! can you provide me link as i dont know which firmware is correct for my device.
Here is the details of my phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499166745
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
aweshlakhani said:
can you provide me link as i dont know which firmware is correct for my device.
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
Sure, here you go: https://forum.xda-developers.com/showthread.php?t=2729173
Firmware 6.20.651.3 is what you want. Modified vs. full or signed is up to you. But since you have s-off, the easiest is probably the one with recovery and boot removed. Otherwise, stock recovery and boot will be installed when you flash the firmware; and you will need to flash TWRP again, and also flash the custom ROM (or at least it's boot.img) again.
I'm glad you provided the getvar data in this case. From the results I can see you have the US Sprint variant, with s-off. This combination is a little dangerous. Whatever you do, do NOT try to flash firmware for another (non-Sprint) version. They are not compatible, and doing so won't work, and may even result in a permanent radio brick!
Hello Guys !!
So my brother had htc one m8 for like 4 years he was studying in uk he came back to india in 2016 and purchased one plus 3 and unfortunately he passed away after 15 days but thats not the point, so my dad kept the oneplus , this htc was somewhat dead and was kept in the cupboard for two years and i had my eyes on it a week back i tried to charge it and it actually did show a sign of life though it was stuck on htc screen, wasnt booting up i put some effort and managed to boot it up i wanted to listen to legendary boom sound but strangely their was no sound at all and tried to listen to ringtones but still no sound thought that it must be hardware issue but headphones werent working either, i came on xda read some threads found out that this can be case when rom is damaged it was running on MM sense 7 so i unlocked bootloader and flashed twrp and installed lineage os 17 but still there was no sound so i tried to get it back on stock but all i get is errors , I tried many RUU versions most of the time error was "error 12 signature verify fail i feel pretty helpless cause i wanted get my brother's memories back
i ve got so much expectations with you people
here is info about my device
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4AVWM00613
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
xostrator said:
i tried to get it back on stock but all i get is errors , I tried many RUU versions most of the time error was "error 12 signature verify fail i feel pretty helpless cause i wanted get my brother's memories back
Click to expand...
Click to collapse
Signature verify fail usually means you still have the bootloader unlocked. The bootloader needs to be relocked in order to run RUU. Relock with fastboot command: fastboot oem lock
You also aren't going to find the right RUU by guessing. It needs to match your CID and version number. In your case, there also isn't an exe version RUU for your M8 variant. But you can use the zip format RUU from the following post, using the instruction found there as well: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Also, I'm not sure what you mean by wanting your brother's memories back. Not sure if you are being literal (the actual data) or more figurative. But if you are talking data, that got wiped when you unlocked the bootloader.
Another thing, delete serial number for your post. This is personal data, that should not be posted on a public forum.
Related
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..
Did you recently do the GPE conversion?
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...
n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?
Hopefully I am not repeating a thread someone else has already started elsewhere but I have tried for many days and could not find anyone else having this same problem. Apologies if one already exists as I know people seem to repeat...
I recently acquired an HTC One M8 with Android Revolution 11.2 on it. Even though I had factory reset it a couple of times, I could not get it to accept my Google account but WiFi was working. So I flashed it with the latest 21.1 but this time the WiFi does not come on. I tried this a couple of times and the problem persists. I have TWRP recovery, S-ON, rooted/unlocked, UK. I reinstalled 11.2 and I am able to use the phone. The only problem here is that my music does not play through the phone speakers but it does through Bluetooth speakers (probably works through earpiece but have not tried that).
People seemed to have faced WiFi issues with earlier versions of Android Revolution but no one has mentioned this for the latest version. Does anyone have any idea what it could be or what I need to check to help with this problem? I would like to be able to flash to latest version and use all the functions of the phone to enjoy the phone, the latter taking priority. Failing that, I may have to resort to going back to stock ROM which does not seem like an easy thing as flashing the stock ROM. I am considering doing that anyway because of some of the great improvements HTC have introduced in the latest version.
DreadDroid said:
Hopefully I am not repeating a thread someone else has already started elsewhere but I have tried for many days and could not find anyone else having this same problem. Apologies if one already exists as I know people seem to repeat...
I recently acquired an HTC One M8 with Android Revolution 11.2 on it. Even though I had factory reset it a couple of times, I could not get it to accept my Google account but WiFi was working. So I flashed it with the latest 21.1 but this time the WiFi does not come on. I tried this a couple of times and the problem persists. I have TWRP recovery, S-ON, rooted/unlocked, UK. I reinstalled 11.2 and I am able to use the phone. The only problem here is that my music does not play through the phone speakers but it does through Bluetooth speakers (probably works through earpiece but have not tried that).
People seemed to have faced WiFi issues with earlier versions of Android Revolution but no one has mentioned this for the latest version. Does anyone have any idea what it could be or what I need to check to help with this problem? I would like to be able to flash to latest version and use all the functions of the phone to enjoy the phone, the latter taking priority. Failing that, I may have to resort to going back to stock ROM which does not seem like an easy thing as flashing the stock ROM. I am considering doing that anyway because of some of the great improvements HTC have introduced in the latest version.
Click to expand...
Click to collapse
Which is your firmware version?
lukes91 said:
Which is your firmware version?
Click to expand...
Click to collapse
I guess this is the Android version so I am going to quote everything here in case it is something else:
Androind: 4.4.3
HTC Sense: 6.0
Software: Android Revolution HD 11.1
HTC SDK API Level: 6.25
Kernel: 3.4.0-ge224610
Baseband: 1.19.21331147A1.09G_20.57.4196.01L_F
Build: 1.11.401.5 CL365360
DreadDroid said:
I guess this is the Android version so I am going to quote everything here in case it is something else:
Androind: 4.4.3
HTC Sense: 6.0
Software: Android Revolution HD 11.1
HTC SDK API Level: 6.25
Kernel: 3.4.0-ge224610
Baseband: 1.19.21331147A1.09G_20.57.4196.01L_F
Build: 1.11.401.5 CL365360
Click to expand...
Click to collapse
Please, post the output of
fastboot getvar all
Deleting imei and serial number...
You don't have to post your firmware version, because it's certainly wrong -- you need to update your firmware, or your WiFi won't work. If your phone works with 11.2 then you have the old firmware.
You're going to either have to try to get S-Off (which will likely require paying) or find an official OTA for your phone that you can use to upgrade firmware.
Her'es a good guide to all this : http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
This is discussed a lot in the ARHD thread and elsewhere, so you just have to sit back and do some reading and searching.
lukes91 said:
Which is your firmware version?
Click to expand...
Click to collapse
Sorry, took me a while to learn, install and run ADB and Fastboot. I managed to use Squabbi's Toolkit which installed ADB and Fastboot for me. Thanks Squabbi !
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.201s
DreadDroid said:
Sorry, took me a while to learn, install and run ADB and Fastboot. I managed to use Squabbi's Toolkit which installed ADB and Fastboot for me. Thanks Squabbi !
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.201s
Click to expand...
Click to collapse
As stated before, your firmware is wrong... I was pretty sure about this, but i wanted to be sure... Update to latest firmware and Wi-Fi will work again...
lukes91 said:
As stated before, your firmware is wrong... I was pretty sure about this, but i wanted to be sure... Update to latest firmware and Wi-Fi will work again...
Click to expand...
Click to collapse
Lukes91, thoroughly appreciate your responses so thanks. I missed your earlier post about Firmware. I will follow the details and some reading on how to do this. I will let you know how it goes.
Here are the steps I took to upgrade my firmware , it may be of some help to you ?
http://forum.xda-developers.com/showpost.php?p=56158006&postcount=13987
Sent from my HTC One_M8 using XDA Free mobile app
craigmoly said:
Here are the steps I took to upgrade my firmware , it may be of some help to you ?
http://forum.xda-developers.com/showpost.php?p=56158006&postcount=13987
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the details. I had not seen your post until I got into a lot of trouble and came back here for help. I had finished typing a whole lot of stuff but before I submitted it I managed to get over the ordeal. After hours of reading, trying to conjure up the courage to update the firmware without having to S-OFF as S-ON provides security for insecure people like me but also because FIREWIRE could not do it. I finally took the plunge with "http://forum.xda-developers.com/showthread.php?t=2696282" which seemed to work. But after rebooting, the phone got stuck on the HTC splash screen. After a few more hours of reading while crying, I came across a post which advised of power+vol-up option and then power+vol-down quickly. Oh, the relief! After that, I managed to update recovery to TWRP but then all sorts of trouble not being able to update ROM using TWRP Install because "Unable to read zip file" and "Not enough space" using FASTBOOT UPDATE option. Even though it was not allowing my PC to write to the internal storage forever, finally, as if by magic while I was typing my reply here earlier (as mentioned above), I was able to copy the odexed HTC 3.28.401.7 ROM (from the ARHD site) to the phone's internal storage. When I then used the TWRP Install, it managed to install as expected. Another moment of relief!
Anyway, I now seem to have sensible versions showing up for the phone, WiFi working and music playing through the speakers. Happy days!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you to all who helped and tried to help alike. It was a nice experience being here at the XDA forums
Prologue:
So there I was, caressing my shiny and smooth M8.
At the beginning of the year I S-Offed, and added DigitalHigh's awesome Beyond Stock...
Later on, I used a standard RUU GPE Rom.
After repeated Wi-Fi password amnesia, I wanted Beyond Stock Back.
Flashing "GPE_5.1_M8_DH_080215.zip" gives me an "Error 7" even with repeated wipes... hehe... wipes
Searching didn't give me a coherent answer.
So I though, let's update TWRP... and...
Now
The thing's only usable in Bootloader.
If I go to recovery or ANYTHING, the "Google" logo stares at me in disgust.
Odd detail: I'm using fastboot and when it's stuck on the "Google" logo, entering "adb devices" detects the phone in recovery mode.
I flashed TWRP 2.8.7.0, but all I see is the "Google" logo. (I can still feel vibrations on the screen as if I'm hitting a menu button)
I also tried to "fastboot -w" and it gave me the "remote: not allowed" result.
Actually, I tried to fastboot a lot of things and the result came the same.
Anyways, I'll give a detailed log as soon as I remember how, but the reason I post this is 'cause searching for this doesn't give an understandable or reliable result.
Thanks
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
Give the output of :
Fastboot getvar all
But delete the serial and imei before posting ! If you have an old bootloader you have to use the 2.7 series of TWRP. if you have the latest bootloader (3.18-3.19) you have to use 2.8 series of TWRP !
OOOOOOOOOHHHH, Where I get new M8 bootloader?
Hold Up, going to work, will post 'getvar' later today.
It's there, brah.
Take a look if you can.
It's an AT&T device, you are using it with AT&T ? And you fully converted it from sense to GPE ? You could also :
1: run the GPE ruu again. It will get you on GPE stock again and since you are s-off that should not be a problem of any kind.
2: convert back to sense (original AT&T with software number x.xx.502.x)
i am not sure if the AT&T RUU will cover the "back to sense conversion" so this might be interesting too as it involves the standalone flashing of the firmware first (you need a AT&T firmware, NOT the one posted there !!!)
here is more conversion info :http://forum.xda-developers.com/showthread.php?t=2733523
and here you can get firmwares : http://forum.xda-developers.com/showthread.php?t=2701376
if you want number 2 here is more info with a download link to the latest android L RUU : http://www.theandroidsoul.com/download-att-htc-one-m8-lollipop-ruu-4-28-502-1-75822/
Didnt want to start my own thread due to the shame..
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mike
Sheriff1972 said:
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
Click to expand...
Click to collapse
Your case is different and you should start your own thread but there are many same case as yours.
Here is one and the solution is in there.. run RUU - http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
Anything you're not sure, ask there. Don't hijack this thread.
UPDATE: Thanks to ckpv5 and the links that were provided i was able to complete the reinstall - thank you so much!!
Opps - sorry - didnt mean to offend!
Will take a look.
Thanks
Mike
The RUU got me an OS and, right now, that is all I need.
Thank you!!
First of all thanks for anyone who can help me.
I'm quite desperate after spending countless hours on XDA trying to get my phone to work.
I received the phone (international HTC one M8) in a somewhat broken state and I am trying to fix it.
Originally the phone had a 4.4 rom on it which caused the phone to reboot constantly, I couldn't get the rom to update either so I decided to flash it to Marshmallow.
Set S-off, I flashed TWRP and installed the latest Skydragon rom. Wifi wasn't working though so I flashed ruu firmware 6.12.401.4b. The rom worked, Wifi worked, but only downside, it only booted while being charged with a cable, and the sudden reboots started occurring again. So I think the battery might be shotty too. Anyway, I got a device tree warning too, so I reflashed a different Ruu, reboots started occurring even when trying to get to recovery. So I went back to the 6x ruu, tried to flash Skydragon again and then I spiraled into real trouble. Each time I tried to flash a rom, the phone reboots while installing. I even tried the MeID changer to make sure it fits with the firmware.
Long story short, the reboots got worse, I can't get into recovery without rebooting. If I run recovery over fastboot, I get into the recovery, but it reboots when I try to flash anything. I also tried Phil's revovery but same problem.
I can get into fastboot, hboot and bootloader just fine though.
Any help is greatly appreciated.
Need more info to proceed. Please do a fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Sure Thing! Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: XF SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: 3XXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Vprnl said:
Sure Thing! Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: XF SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: 3XXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
It is indeed an M8_UL which is the GSM/Int version.
However version-mics shows: XF SHIP S-OFF
M8_UL_XF is something I have heard of before on a forum (few pages back, there's a thread with a similar case).
Anyway, an ordinary M8_UL will show 'PVT SHIP S-OFF'.
XF is either a 'different' variant or some type of engineer/prototype device.
What do you think @redpoint73?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Here is the getvar all from my M8.
Notice the version-misc.
Thanks @murtaza02, I finally got the damn thing to work because of your comment I realized my CID was bogus and wasn't corresponding with the MID, so I fixed that using fastboot, flashed the EU 6x FUU and the corresponding RUU (https://www.androidfilehost.com/?fid=24369303960687057). And behold, It booted into Marshmellow!!
Now though, the phone still keeps shutting down (not even rebooting) and won't start android without being plugged in. Could this be software related at all? Getvar says the battery is good and when it craps out, (most often when trying to enable WIFI) it shows the battery charging just fine. I still see the device tree warning on boot btw.
Vprnl said:
Thanks @murtaza02, I finally got the damn thing to work because of your comment I realized my CID was bogus and wasn't corresponding with the MID, so I fixed that using fastboot, flashed the EU 6x FUU and the corresponding RUU (https://www.androidfilehost.com/?fid=24369303960687057). And behold, It booted into Marshmellow!!
Now though, the phone still keeps shutting down (not even reboting) and won't start android without being plugged in. Could this be software related at all? Getvar says the battery is good and when it craps out, (even when plugged in) it shows the battery charging just fine. I still see the device tree warning on boot btw.
Click to expand...
Click to collapse
As I said, yours is XF and a normal M8 is PVT.
Your device will accept a MM firmware, however there may be a SLIGHT difference in partition/partition sizes hence the device tree error and irregular behavior.
Your CID was not bogus, it was just SuperCID which is used to bypass the CID check during an RUU/FUU flash.
I'm still trying to figure out why (and how) yours is different.
Sent from my Nexus 6
murtaza02 said:
As I said, yours is XF and a normal M8 is PVT.
I'm still trying to figure out why (and how) yours is different.
Click to expand...
Click to collapse
I don't know much about the XF variant, either. But I recall @ckpv5 pointing out the difference to an XF user a week or 2 ago. So maybe @ckpv5 can jump in and give some advice here?
@redpoint73, Thanks but I fear @ckpv5 might not have any more info to go on. I found his post where he referred to the XF variant. He said it's quite possible a US variant, definitely has different partitioning than the PVT version, but didn't know more. I've also seen posts of people suggesting it's a Canadian version.
I bought it on Aliexpress if that is any lead. But in all honestly, I'm really starting to worry I have an expensive paperweight.
One more potential clue, the Alie page suggests the phone only has WCDMA, no LTE, could that be a lead? Ow and one more clue, the model number on the back of the phone is: OP6B100x
Vprnl said:
@redpoint73, Thanks but I fear @ckpv5 might not have any more info to go on. I found his post where he referred to the XF variant.
Click to expand...
Click to collapse
Can you link the post, so I can take a look? I remember reading the postat the time, but the details are foggy; and maybe there is something useful there.
redpoint73 said:
Can you link the post, so I can take a look? I remember reading the postat the time, but the details are foggy; and maybe there is something useful there.
Click to expand...
Click to collapse
Sure thing! Thanks again!
http://forum.xda-developers.com/htc-one-m8/help/ruu-warning-device-tree-totally-matched-t3356722
Verstuurd vanaf mijn Nexus 6P met Tapatalk
i have htc one m8 using cm nouget latest but suddenly phone got off because of low battery and after that i am not able to get any signal and my phone is not showing any IMEI and baseband is unknown.
i have tried to install others roms but not succeeded.
i have tried to restore to stock from twrp nandroid backups from below thread but my phone is still showing baseband unknown and not showing any IMEI
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
my bootloader is unlocked and s-on.
i am trying to find ruu file.
if anyone can help to find ruu file or can tell me how to get rid of this Imei problem(not getting any signal) that would be great
my htc one m8 get var all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4xxxxxx639
(bootloader) imei: 35244xxxxxxxx19
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
please help me to get my phone usable .
i can use stock rom or any other rom.
here is the RUU,zip
https://www.androidfilehost.com/?fid=24591000424941691
and here is how to flash do all the steps ( use the RUU from the link above )
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Htc one m8 whl
I have been facing a trouble with HTC ONE m8 WHL
when the device came to me wireless is working but there is no traffic
I tried to flash the phone but the problem was still but in addition there is no baseband
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.654.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------
(bootloader) imei:--------
(bootloader) imei2: Not Support
(bootloader) meid: -------
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B7****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6400afe2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This is the device information
Anyone can help me please
I tried a lot of RUU flash files kitkat or lolipop when the device is running for the first time
hands free activation was required and i passed it throw up the TWRP recovery
snow_man026 said:
I have been facing a trouble with HTC ONE m8 WHL
I tried a lot of RUU flash files kitkat or lolipop when the device is running for the first time
Click to expand...
Click to collapse
You shouldn't be trying "a lot" of RUUs. You should be trying only the correct RUUs for the Sprint M8. Flashing RUUs for other versions is dangerous, and can lead to permanent damage to the Sprint version M8.
https://forum.xda-developers.com/showthread.php?t=2729173
Did you buy this phone? And you received it with cell data not working? If so, you should return it to the seller (if possible) rather then messing around with it (possibly breaking it worse, and voiding any possibility of return to the seller).
Also, you should delete IMEI, serial number, and MEID from your post. These are unique to the device, and should never be posted online.
All the RUU files that i had tried for the same model ONE M8 WHL
No I didn't buy the phone but it's my job to make a software for the phones
When I received the phone cell data was working but the problem was there is no traffic when you turned on the wireless
But my problem now there is "no baseband"
snow_man026 said:
All the RUU files that i had tried for the same model ONE M8 WHL
Click to expand...
Click to collapse
This still doesn't tell me which RUUs you tried. There are 14 RUUs on the thread I linked. Which ones exactly did you try, and in what order? Did you use the exe or zip method (and if the latter, was it by htc_fastboot, or SD card method)? Did the RUU(s) install completely and successfully, or were there error messages? If there were error messages, what did they say exactly?
Basically, your posts are short on details. You should be specific and detailed as possible, when asking for help.
snow_man026 said:
When I received the phone cell data was working but the problem was there is no traffic when you turned on the wireless
Click to expand...
Click to collapse
Understanding that English may not be your native language. But I don't know what that means "there is no traffic". Can you try to explain another way (again, more details may help).
snow_man026 said:
But my problem now there is "no baseband"
Click to expand...
Click to collapse
Where are you seeing "no baseband". In the getvar you posted, it says baseband number 1.09.20.0119
You also did not delete the personal details (serial number, IMEI and MEID) from the getvar output, as I previously advised.
I'm so sorry for being late
I flashed the phone at the last time with this RUU
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3
This is my phone information while the phone is ON by XTC2CLIP
Reading information...
Using ADB mode...
CID list: [SPCS_004]
Main CID: [SPCS_004]
Model ID (MID): [0P6B70000]
Project: [M8_WHL_M60_SENSE70_SPCS_MR]
System version: [6.20.654.3]
Chipset: [msm8974]
Hardware: [qcom]
Serial no: [FA45PSF03010]
Release: [HTC/htc_m8whl/htc_m8whl:6.0/MRA58K/buildteam01071632:user/release-keys]
Bluetooth chipset: [Qualcomm WCN3680]
Buildline: [M8WHL_Sprint_WWE_M60_CRC_Sense70_Stable_MR2_harman]
Sense version: [7.0]
SKU: [Sprint WWE Harman]
Signed: [release-keys]
Android version: [6.0]
Android patch [2016-01-01]
Disk enecryption: [unencrypted]
Device: [htc_m8whl]
Read information completed.
and this the information while the device in the fastboot mode :
Reading common information
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.654.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ---------
(bootloader) imei: -----------
(bootloader) imei2: Not Support
(bootloader) meid: -----------
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B7****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Now the device state is : There is no Baseband when checked it from the system it means that there is no cell network in addition there is no imei in the normal mode
thank you very much
snow_man026 said:
I flashed the phone at the last time with this RUU
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3
Click to expand...
Click to collapse
Is that the only RUU you tried? Before you said you tried "a lot of RUU flash files kitkat or lolipop " and when asked which RUUs you tried, you list only one. So one of those statements is incorrect or incomplete.
Hard to diagnose the issue (or may give incorrect advice) is we don't know exactly, step-by-step, what you did, and the state of the device at each step.
One important example of this: Are you absolutely sure you only flashed Sprint RUUs? It's a known problem, that if you tried to flash a non-Sprint RUU or radio baseband, that it will result in a radio brick (possibly permanent, but usually can be fixed).
snow_man026 said:
Now the device state is : There is no Baseband when checked it from the system it means that there is no cell network in addition there is no imei in the normal mode
Click to expand...
Click to collapse
I am still wondering about the original state, where you said: "When I received the phone cell data was working but the problem was there is no traffic"
I asked before, what you meant by this. You still haven't explained (only given the current state).
Again, it's hard to properly troubleshoot the issue, when it's pretty clear we've only been given a portion of the info.
Thanks for keeping in touch
These are the RUU files that I had tried before
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WW
E_Harman_4.20.654.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418492_signed_2
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.20.654.10_Radio_1.09.20.0119_NV_SPCS_1.52_003_release_418492_signed_2_2
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_Harman_4.25.654.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426233_signed_2
According to XTC2CLIP support all of M8_WHL flash files are Sprint or sprint and harman
then I tried this file
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6 .20.654.3
I'm so sorry maybe I didn't explain my problem exactly when I posted it
"" I am still wondering about the original state, where you said: "When I received the phone cell data was working but the problem was there is no traffic"
I meant there was no traffic when you connected to wifi there was no data transfer and this problem was solved by flashing the latest file
Now my problem is there are no imei and baseband in the normal mode but in the fast mode are exist
Try the older RUUs, like 2.16 or 3.30, and see if that fixes the "no baseband' issue. If so, try to RUU back to a more current version (6.20) and see if the fix "sticks".
Of try to flash the firmware only, and see if that helps (not exactly the same as flashing an RUU, so be sure to read the instructions on how to flash firmware). Firmware and instructions are on the same thread as the Sprint RUUs, which I linked earlier.
redpoint73 said:
Try the older RUUs, like 2.16 or 3.30, and see if that fixes the "no baseband' issue. If so, try to RUU back to a more current version (6.20) and see if the fix "sticks".
Of try to flash the firmware only, and see if that helps (not exactly the same as flashing an RUU, so be sure to read the instructions on how to flash firmware). Firmware and instructions are on the same thread as the Sprint RUUs, which I linked earlier.
Click to expand...
Click to collapse
I know how to flash firmware thanks for help
I will inform you with the result
thanks a lot