Database Develop

[Q] Help me unbrick my htc one please?

im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:

ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.

ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.

Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19

Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..

Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.

Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA

still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.

1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.

stuck on slash screen, No recovery, Bootloop

Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001

profixit said:
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
Click to expand...
Click to collapse
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide

Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.

profixit said:
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
Click to expand...
Click to collapse
downgrading hboot is pretty easy
just follow the steps under ''If you’re on hboot which is above 1.44'' from nkk71's guide
then change cid
then run ruu.exe
but do not use a win 8.1 computer (compatibility issue with hboot 1.44)

Thanks for that last bit, what about Win8.
I've spotted the steps that apply to me, just playing them out in my head.
Out of curiosity after a downgrade the HBoot, will it be locked and s-on?

profixit said:
Thanks for that last bit, what about Win8.
Click to expand...
Click to collapse
windows 8.0 should be fine, but definitively not 8.1

alray said:
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Click to expand...
Click to collapse
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?

profixit said:
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
Click to expand...
Click to collapse
sry my bad
use this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/
1.28.401

No worries, Thanks.

Can you try fastboot erase cache from fastboot menu and re enter recovery?

Tried that, thanks
Sent from my HTC One using Tapatalk

OK, a little lucky positive progress.
I managed to flash clockworkMod recovery, don't ask me how, maybe erasing the cache lots of times did it, i'm sure it was a recovery I had already tried. I checked my download list and confirmed I did download it., so i would of tried to flash it two days ago. Funny.
Still stuck on splash screen, but can boot into recovery. (clockworkmod)
Please, what is the best way to proceed, I'm thinking nandroid backup, but like I said, I couldn't care less about orange. I would love to put Mike1986 stock rom 4.3 or 4.4
I'm unable or don't know how to get folders or files on the phone's internal SD card, because it doesn't boot up a rom any more. Y-cable?
I'm concerned with all the "can't" at the bottom of recovery screen.

phone wont boot

im not really sure what happened...
i was trying to root then s-off today. i got htcdev.com unlocked, was able to flash custom recovery (philz) and flash superuser. when i tried to s-off (firewater) i got the whelp this sucks error (im still not really sure why or what that means)
i tried to then flash a custom rom, and now it wont boot past the htc flash screen with the red text ( this may be because i didnt flash firmware with the rom i tried to install?)
i have tried to flash firmware, and run a ruu and nothing is doing anything...
please please please someone help

What firmware version do you currently have installed? What ROM were you trying to flash?
Take a look at this thread below for info on how to flash the latest RUU. If you have a HK version you'll need the HK RUU. After you run the RUU you'll need to reroot your phone. You'll also need to use the SunShine exploit to gain S-off (the "whelp" message means Firewater won't work on your device). I also recommend Captain Throwback's TWRP 2.8.0.0. recovery.
http://forum.xda-developers.com/showthread.php?t=2880328

im not sure which of these are the firmware...
hboot - 3.16.0.0000
radio - 1.05.20.0321_2
os - 1.54.654.9

Firmware is your radio version. Use the RUU from the link below. Follow the instructions for the manual system update. You'll need to relock your bootloader beforehand using the command "fastboot oem lock" while connected via Fastboot USB mode.
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/

ohh i forgot about having to relock for ruu
trying that now

I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader

knock.back said:
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
Click to expand...
Click to collapse
RUU's are run from the bootloader...make sure it says fastbootusb when connected to your PC.

it did say that

Make sure you have HTC Sync installed on your computer.

I have that installed too... I got it to boot, ended up flashing different recovery then a different rom and that worked... Never got the ruu to work tho... Anyway, thanks for your help

[Closed] How to Return to Stock Recovery for OTA Updates

Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)

You can install stock recovery using fastboot command.
However to apply OTA, if your phone is S-On, you must lock the bootloader.
You don't have to lock bootloader if your phone is Soff, for OTA, just stock recovery is good enough.

lyciansarpedon said:
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
Click to expand...
Click to collapse
Just flashing the stock recovery will probably not allow you to successfully install OTAs. You have to have stock rom, stock recovery and possibly some /preload/ files that were deleted when you unlocked your bootloader. The quickest way to stock for OTA would be to flash a RUU. I would propose this route:
Option A
Lock your bootloader
Flash RUU 3.17.502.3
Receive OTA updates if they are still available
Option B
Lock your bootloader
Flash in bootloader: firmware 4.18.502.7
Flash RUU 4.18.502.7
Flash in bootloader: firmware 5.12.502.2
Flash TWRP 2.6.3.3
Download Guru Reset 5.12.502.2 and place on your sdcard
Boot into TWRP and install GURU Reset
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery

Thanks for the feedback. I was a bit surprised to find out about needing to re-lock the bootloader even with stock recovery since a bunch of other places I looked said that I could use an unlocked bootloader as long as everything else was stock (just couldn't find a way to return to stock recovery without an RUU - which would require re-locking the bootloader - at the time). Used this (http://forum.xda-developers.com/showthread.php?t=2545227) from Majmoz's signature and got the relevant recovery.img from it. Since I had it, I figured I might as well try it before going through the process of re-locking the bootloader since being bounced out of the OTA and then going through the full process of relock-RUU-OTA anyhow was the worst that could happen. Turns out it worked.
So, for posterity's sake in case anyone else should come across a similar issue, everything I did (most of it probably unnecessary, but who knows):
-Made CWM backup (in case I happened to need to re-lock the bootloader which would wipe the device data to factory)
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
-Went into recovery from the bootloader, fastboot, plugged in the usb, and flashed the stock recovery (fastboot flash recovery [the downloaded stock recovery .img file in the platform-tools directory])
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
-Went into AT&T Software Update, let it download off the Wi-Fi, and let it apply. Did its thing with the image of the green downward arrow within the circulating arrows followed by reboot a few times, the "Android Update" screen where it runs through your applications, and voila, I am now on 4.4.2.
Updates:
-Have downloaded the updated stock recovery image.
-Flashed CWM Recovery back onto device
-Re-rooted via CWM (confirmed root)
-Made a new backup through CWM.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.

lyciansarpedon said:
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
Click to expand...
Click to collapse
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
Click to expand...
Click to collapse
no but again its a good practice to check if the recovery is working correctly.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
Click to expand...
Click to collapse
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Is your apn correctly configured?

alray said:
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
Click to expand...
Click to collapse
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
alray said:
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Click to expand...
Click to collapse
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!

lyciansarpedon said:
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
Click to expand...
Click to collapse
youre welcome glad it worked!