Hey guys. I need some big help here. I am on hboot 1.55 s-on. I tried flasing back to stock rom after cyanogenmod broke my voice/data signal, and now im stuck. I can get into bootloader/recovery, but dont have a valid rom installed and my storage either got erased or corrupted. So now I dont have any backups and cant get my storage to mount. Any ideas what I can do, or do I have to wait for a 3.04 ruu to come out?
You can sideload a rom from twrp
adb sideload romname.zip
Or
adb push romname.zip /sdcard/
Thanks for the response. I tried sideload and push. It says that there is no device available. For some reason it will only acknowledge that my phone is connected in fastboot. I can flash images/recoveries without any issues.
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar usually one of the first couple choices
Select MyHTC install and you should be good
Awesome. Thanks much for the help! I ended up using Universal Naked Driver and with your instructions was able to sideload a stock rom.
Now I just have the issue that caused all this headache in the first place. Im not getting any data/voice signal. I checked the PRL version and it is 00000. Any idea what I have to do to get a legit PRL back on it?
Have you tried updating your profile and prl?
Sent from my ElipticNexus7
Yeah. Updated both. Still nothing. PRL version changed to 1.
Actually it looks like data is working with PRL 1 but no voice. If I turn Airplane mode on/of it switches me to PRL 55016, but as soon as I update the PRL it goes back to version 1.
jjmckaskie said:
Actually it looks like data is working with PRL 1 but no voice. If I turn Airplane mode on/of it switches me to PRL 55016, but as soon as I update the PRL it goes back to version 1.
Click to expand...
Click to collapse
Sounds like something is borked.
Make sure it was a good download by checking to make sure the MD5 matches if it does I would suggest a full wipe
cache/dalvik cache/system/data
bigdaddy619 said:
Sounds like something is borked.
Make sure it was a good download by checking to make sure the MD5 matches if it does I would suggest a full wipe
cache/dalvik cache/system/data
Click to expand...
Click to collapse
Yeah. I have tried complete wipes and flashing other stock ROMs with no luck. This seems to be a common issue with the newest "stable" Cyanogenmod on HTC One. I will try to get some help on their forums since it seems like that is what caused the issue in the first place. Thanks for the help.
Stuck on fastboot
jjmckaskie said:
Awesome. Thanks much for the help! I ended up using Universal Naked Driver and with your instructions was able to sideload a stock rom.
Now I just have the issue that caused all this headache in the first place. Im not getting any data/voice signal. I checked the PRL version and it is 00000. Any idea what I have to do to get a legit PRL back on it?
Click to expand...
Click to collapse
jjmckaskie what ROM did you use?, I have same problem with M7WLS, Hboot 1.55, I can't mount usb on any recovery, and I'll try slideload.
resolved
Slideload works. :laugh:. I' we flash Viper ROM. and repair partition.
spanusorin2005 said:
jjmckaskie what ROM did you use?, I have same problem with M7WLS, Hboot 1.55, I can't mount usb on any recovery, and I'll try slideload.
Click to expand...
Click to collapse
To be honest I don't really remember. I went from stock rooted to cynagenmod. That jacked up my mobile network, so I tried to flash back to stock, but may have used the wrong stock version in my haste to fix the network issue.
jjmckaskie said:
Yeah. I have tried complete wipes and flashing other stock ROMs with no luck. This seems to be a common issue with the newest "stable" Cyanogenmod on HTC One. I will try to get some help on their forums since it seems like that is what caused the issue in the first place. Thanks for the help.
Click to expand...
Click to collapse
^^^^ was the CM from the Sprint forum?
bigdaddy619 said:
^^^^ was the CM from the Sprint forum?
Click to expand...
Click to collapse
No, it was direct from the CM site.
jjmckaskie said:
No, it was direct from the CM site.
Click to expand...
Click to collapse
That could be the problem I don't use CM so not 100% if it makes a difference
flash
for my phone I found on XDA an firmware with full stock ROM and radio , M7wls works perfectly .
Resolved
bigdaddy619 said:
That could be the problem I don't use CM so not 100% if it makes a difference
Click to expand...
Click to collapse
Yeah. So, it turns out my problem was a setting that is only available in Cyanogenmod. If anyone else has this issue here's what I did to resolve.
Full wipe. Flashed the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back, you may need to Activate the phone again and update the profile/PRL to get back to 100%.
The issue appears to happen when RUIM/SIM subscription mode is selected instead of NV for Sprint phones in CM. Once you flash a different ROM these settings are no longer available, but are still locked in place and are not replaced by any amount of flashing of ROMs/radios etc. I'm not sure if CM is automatically switching this setting, or if it was accidentally switched, but it appears that the changing of this setting is causing issues for a bunch of people. So basically Sprint network = NV. If you have a Verizon phone and are experiencing similar issues, you may need to do the opposite and switch from NV to RUIM/SIM. Hope this helps other people in the same situation.
I dont mean to high jack your thread OP but I am having a similar issue. However I have been about to flash a new rom via ADB I still have no signal and after about a min or two my phone reboots.
I've tried wiping everything and starting over. I have a back up on my computer but when i restored it (long before i use adb) i had all of my stuff but still had no signal and reboots.
Any ideas?
Similar Issue
I am having a similar issue. I must have installed a non compatible ROM and some how erased all of SD Card. It even deleted TWRP. I did manage to get that back through fastboot but I can not flash a ROM. I keep getting this message:
C:\android-sdk>fastboot flash boot viperROM_One_v1.1.0.zip
< waiting for device >
sending 'boot' (776879 KB)... OKAY [ 45.619s]
writing 'boot'... FAILED (remote: image error! (BootMagic check
fail))
finished. total time: 45.641s
Any help with this issue would be greatly appreciated.
Related
wifi stopped working i believe right after i flashed to the latest cyanogen mod, or shortly after. Today i flashed back to rogers stock froyo and still wifi does not work. Wtf is going on, did my router block access to it after cyanogen was installed or something?
any advice is appreciateed
3g still works.
stavs said:
wifi stopped working i believe right after i flashed to the latest cyanogen mod, or shortly after. Today i flashed back to rogers stock froyo and still wifi does not work. Wtf is going on, did my router block access to it after cyanogen was installed or something?
any advice is appreciateed
3g still works.
Click to expand...
Click to collapse
Try some troubleshooting first.
Reset your Access Point/Router, or try a different router/ap. Flash back to 100% stock and do a "master clear".
I also find it useful to clear out the /efs partition after returning to Samsung ROMs after using CyanogenMod. Of course ONLY do this after you have a tested and safely stored a backup of your current "nv_data.bin" file. You have been warned.
Take out your battery and just let your phone chill for a few hours. That sometimes helps too.
Anyway, if after a complete flash to stock and master clear, and some troubleshooting with different access points you still get no WiFi signal, something may be wrong with your hardware...
From there you might either need to send it into a Samsung service center, or find a very technically minded XDA member to help you further. Good luck!
I flashed my phone HTC one to page using DFS and I pretty much just copied everything from the donor but everything works but I just cant make outgoing calls. I get a message telling me that there was an Error and i should turn my phone off then back on. Do you have any idea of what went wrong ? I tried changing prls and radios and restarting the whole flashing back to zero and even resting the phone back to zero with the RTN menu. i flashed this phone the same way to Verizon and worked fine but outgoing calls not working. Anyone have an idea what could be the problem ?
Wipe everything and flash again – dont forget to backup user apps
android_smiley said:
Wipe everything and flash again – dont forget to backup user apps
Click to expand...
Click to collapse
Did that Already, I even used ##RTN# just so it can really wipe it all back to stock
pimix2009 said:
Did that Already, I even used ##RTN# just so it can really wipe it all back to stock
Click to expand...
Click to collapse
Well... thats weird ...
Hello
Make sure you have the correct ESN in the phone. Also make sure your phone number is attached to that ESN.
I'm having an issue with my HTC One. I had been on Paranoid Android, working fine for several weeks (so I didn't flash the wrong version for my Sprint hardware). Last week, I was suddenly showing roaming, with an empty triangle for the signal bars. I tried messing with the RUM/SIM/NV settings, but it didn't resolve the issue. I ended up reflashing back to stock 1.29 via the RUU, but still showed an 'x' next to my signal bars. I then let it update to 1.31 (damn...) but that didn't solve the issue either. If I go into the Network info under About phone, I show 0 signal strength if LTE is disabled. If I enable LTE, then I get signal, and data. Only CDMA is not working.
If I go into the MSL menu (##<MSL>#), it shows 'No' for both MDN and MSID. If I try to enter them, I get a message "Commit Failed" when I try to save them.
Support at the Sprint store wouldn't even look at it because the bootloader was unlocked.
Has anyone had issues with the CDMA radio failing? Anything else to try?
beanpoppa said:
I'm having an issue with my HTC One. I had been on Paranoid Android, working fine for several weeks (so I didn't flash the wrong version for my Sprint hardware). Last week, I was suddenly showing roaming, with an empty triangle for the signal bars. I tried messing with the RUM/SIM/NV settings, but it didn't resolve the issue. I ended up reflashing back to stock 1.29 via the RUU, but still showed an 'x' next to my signal bars. I then let it update to 1.31 (damn...) but that didn't solve the issue either. If I go into the Network info under About phone, I show 0 signal strength if LTE is disabled. If I enable LTE, then I get signal, and data. Only CDMA is not working.
If I go into the MSL menu (##<MSL>#), it shows 'No' for both MDN and MSID. If I try to enter them, I get a message "Commit Failed" when I try to save them.
Support at the Sprint store wouldn't even look at it because the bootloader was unlocked.
Has anyone had issues with the CDMA radio failing? Anything else to try?
Click to expand...
Click to collapse
I would take it back to another Sprint store. They are suppose to take your phone and run the RUU. There was a posting from a Sprint employee a few weeks back with the internal company policy - which was to do a reset or run the RUU to put the phone back to stock to determine if it is a software or hardware issue. If hardware issue, Sprint is suppose to then replace the phone.
All androir 4.3 based rom have some data or signal issues with cdma ... I just go back to 4.2, everything is fine. If you have a signal issue with stock rom you should ask for a hardware replacement.
sent from my m7spr using tapatalk 4
I've never had a 4.3 ROM on this phone. Was on a 4.2 AOSP ROM, and now I'm back on HTC One 1.29 (after upgrading to 1.31, and then RUU'ing back to 1.29 again). No CDMA reception on anything. I'll try another Sprint store. The guy at the one I went to was pretty pompous. He asked if the phone had been rooted. I figured honesty would be best, since he would know that the bootloader had been unlocked as soon as he went into HBoot.
j_rivers said:
All androir 4.3 based rom have some data or signal issues with cdma ... I just go back to 4.2, everything is fine. If you have a signal issue with stock rom you should ask for a hardware replacement.
sent from my m7spr using tapatalk 4
Click to expand...
Click to collapse
beanpoppa said:
I've never had a 4.3 ROM on this phone. Was on a 4.2 AOSP ROM, and now I'm back on HTC One 1.29 (after upgrading to 1.31, and then RUU'ing back to 1.29 again). No CDMA reception on anything. I'll try another Sprint store. The guy at the one I went to was pretty pompous. He asked if the phone had been rooted. I figured honesty would be best, since he would know that the bootloader had been unlocked as soon as he went into HBoot.
Click to expand...
Click to collapse
Try changing the mobile network mode to something else in the setting page, then change it back, sometimes it works ...
sent from my m7spr using tapatalk 4
Airplane mode on and then off. This fixes the issue.
Sent from my HTCONE using xda app-developers app
Issue solved
Closing the loop. I found the issue. I must have somehow changed from NV to RUIM/SIM in the Mobile Subscription settings while on a CM based ROM. When I reflashed to stock using the 1.29 (and then 1.31) stock RUU, it doesn't change this setting in the radio. And then there is no access to this setting to correct it in the stock ROM (as far as I could find... maybe there's a hidden ## option). To fix the issue, I had to reflash back to a CM based ROM so that I could access the mobile subscription settings, change it back to NV, and then reflash back to stock and let it do the Handsfree activation. After that, everything is working again.
beanpoppa said:
Closing the loop. I found the issue. I must have somehow changed from NV to RUIM/SIM in the Mobile Subscription settings while on a CM based ROM. When I reflashed to stock using the 1.29 (and then 1.31) stock RUU, it doesn't change this setting in the radio. And then there is no access to this setting to correct it in the stock ROM (as far as I could find... maybe there's a hidden ## option). To fix the issue, I had to reflash back to a CM based ROM so that I could access the mobile subscription settings, change it back to NV, and then reflash back to stock and let it do the Handsfree activation. After that, everything is working again.
Click to expand...
Click to collapse
Would you be able to walk me through that process? I am having the same issue. Where would I find those settings after flashing over to a CM based ROM?
edit: NM Pretty easy to find on a CM based ROM.
Hi all! I have a droid 4. i just flashed it with CM10.2.1 and then updated to CM11. in both version sms is not working. I type a new text and it fails: i get the red triangle and message not sent.
I looked around and I found it's a common issue and if you remove "voice+" sending sms is available again. I removed "voice+" going to system>app>voiceplus.apk and deleting it as i saw in a thread and reboted, many times. still not working.
then I also went to the *#*#4636#*#* menu and checked the SMSC. I tried both the +39 and the 079193 version but still nothing.
I have to add I'm using the phone in italy over a GSM network. Phone calls and data network (3G) works perfectly!
How can I fix this? CM11 is a stable on this phone, strange to have such a big problem!
Thank you for help!
teto.1991 said:
Hi all! I have a droid 4. i just flashed it with CM10.2.1 and then updated to CM11. in both version sms is not working. I type a new text and it fails: i get the red triangle and message not sent.
I looked around and I found it's a common issue and if you remove "voice+" sending sms is available again. I removed "voice+" going to system>app>voiceplus.apk and deleting it as i saw in a thread and reboted, many times. still not working.
then I also went to the *#*#4636#*#* menu and checked the SMSC. I tried both the +39 and the 079193 version but still nothing.
I have to add I'm using the phone in italy over a GSM network. Phone calls and data network (3G) works perfectly!
How can I fix this? CM11 is a stable on this phone, strange to have such a big problem!
Thank you for help!
Click to expand...
Click to collapse
Have you installed the GSM patch as discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=2394689
Cheers,
Scott
stashcroft said:
Have you installed the GSM patch as discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=2394689
Cheers,
Scott
Click to expand...
Click to collapse
I think so, but I installed it again. So that now I have another issue: http://forum.xda-developers.com/showthread.php?t=2635270
I get no GSM signal...
teto.1991 said:
I think so, but I installed it again. So that now I have another issue: http://forum.xda-developers.com/showthread.php?t=2635270
I get no GSM signal...
Click to expand...
Click to collapse
Installing the patch twice uninstalls it.
Install it again and then reboot.
If you upgrade the ROM at any point in the future you don't need to install the patch just reboot again.
So, first reboot after a ROM upgrade will leave you with no GSM signal but another reboot will bring it back.
Cheers,
Scott
stashcroft said:
Installing the patch twice uninstalls it.
Install it again and then reboot.
If you upgrade the ROM at any point in the future you don't need to install the patch just reboot again.
So, first reboot after a ROM upgrade will leave you with no GSM signal but another reboot will bring it back.
Cheers,
Scott
Click to expand...
Click to collapse
I did it and in the 4636 menu I have GSM but still does not get signal...
Have you tried using an alternative SMS App? Hangouts maybe?
So I managed to solve the problem. This is the way:
-deleted rom slot 1.
-recreated a partition in rom slot 1
-wiped everything in slot 1
-flashed cm 10.2.1
-flashed gsm patch
-booted
-flashed gapps
Now everything is fine!
ok let me first start by saying that my htc one has the latest firmware as well as twrp recovery (2.7.0.1 Official). I had Gruesomes latest GPE 4.0.5 installed with Thinklizards GPE kernel. I wanted to try another kernel so i flashed Lunar latest GPE kernal for sprint htc one and now i lost network signal. Ive *#*#4636#*#* to see if that was the problem..it was on WCDMA but then i switched it to LTE/CDMA...it would stick but then sometimes go to unknown or back to WCDMA. I tried flashing another rom....asop and such boot but still have no signal/data and i get no fc's...sense roms take forever to boot...i finally got bad boyz rom 4.4 to boot after several random reboots. I tried updating prl but saying it cant update and to check back later. Also the rom keeps rebooting after certain amount of time. I get dialer fc's and vDM client fc's. I have tried everything i could think of but no solution. Any info will be appreciated. Thanks for your time.
Sluggerz said:
ok let me first start by saying that my htc one has the latest firmware as well as twrp recovery (2.7.0.1 Official). I had Gruesomes latest GPE 4.0.5 installed with Thinklizards GPE kernel. I wanted to try another kernel so i flashed Lunar latest GPE kernal for sprint htc one and now i lost network signal. Ive *#*#4636#*#* to see if that was the problem..it was on WCDMA but then i switched it to LTE/CDMA...it would stick but then sometimes go to unknown or back to WCDMA. I tried flashing another rom....asop and such boot but still have no signal/data and i get no fc's...sense roms take forever to boot...i finally got bad boyz rom 4.4 to boot after several random reboots. I tried updating prl but saying it cant update and to check back later. Also the rom keeps rebooting after certain amount of time. I get dialer fc's and vDM client fc's. I have tried everything i could think of but no solution. Any info will be appreciated. Thanks for your time.
Click to expand...
Click to collapse
Try re-flashing the latest radio
BD619 said:
Try re-flashing the latest radio
Click to expand...
Click to collapse
Thanks for your help. I just reflashed the whole firmware and everything is up and running. Thanks again.