Related
Hi, I installed VillainRome 10.3.0 and now I keep getting errors and cant make or receive calls, so for now I would just like to roll my phone back to 1.5.
How can I do this?
I tried the home + back button thing, but it just resets the 2.1 that's on here..
Sorry I'm quite a n00b at this so any help would be appreciated
Hi
i was using BeHero (actualy my girlfriend did) after a while the device was very slow and wanted to return to 1.5
for me it was quite a pain to return to the original. on my PC i found an old nandroid backup (1.73) but was unable to restore that with RA-revovery 1.6 so i downgraded that to 1.5 again through adb
then i was able to restore the old backup
from that backup i upgraded to 2.73
when the phone got internet (wifi or 3G) the first part anounced itself and was installed very quickly
my girlfriend is happy with 1.5+ (a pitty for some lack of features) i hope HTC will real ota the update soon
Just use one of the RUUs on the first post to get everything back.
RUU didn't work from Behero 1.3.2, "error 170 unable to connect"
willumpie82 said:
RUU didn't work from Behero 1.3.2, "error 170 unable to connect"
Click to expand...
Click to collapse
Same for me from Cronos 1.7.1
hi ok, so I got the RUU from shipped-roms:
RUU_Hero_HTC_WWE_2.73.405.66_WWE_release_signed_NoDriver.exe
but when I try running it it says conection error and wont go on
what am I doing wrong?
Make sure you have HTC sync installed.other than that search Google how to extract Android rom.zip from ruu the link to a blog will tell you how then fastboot flash the system and boot
If you update to VR 10.3.3 you will most likely get rid of the problem you are having. The VR team push updates out extremely quickly. You should check the VR site out more (and join the IRC channel they have, people can help you solve issues there)
Hi all tx for the advice.. I really need my phone during the day so I had to act quickly lol
I ended up flushing with:
HeroDroid07-signed.zip
Everything is running smoothly now and its working great
hadez2000 said:
hi ok, so I got the RUU from shipped-roms:
RUU_Hero_HTC_WWE_2.73.405.66_WWE_release_signed_NoDriver.exe
but when I try running it it says conection error and wont go on
what am I doing wrong?
Click to expand...
Click to collapse
I´ve the same problem, but i installed htc-synk on my old lapptop with Win XP, then all worked Ok.
Hero_RUU_Hero_HTC_WWE_2.73.405.6_R_WWE_release_signed_NoDriver.exe + OTA from HTC
Moved as not Android Development.
I think i worked it out
when i got the connection error i did the following:
a. make shure you download the correct RUU installer from your local HTC website
b. get the Android SDK tools
c. make sure your phone is charged (beyond 51%)
1. run RUU installer and continu until you got the error, don't click OK yet
1. go to temp folder (win7: C:\Users\[username]\AppData\Local\Temp\)
2. copy the files HTC RUU extracted (some wierd folder name, sort on date/time) to a safe place
3. in the RUU folder, replace the adb and its DLL with the one from the SDK tools
4. start RUU from the new folder.
5. it should be fine now
hi
i have problem in my wifi
i trued to flash Rogers rom by fastboot and when its start its flashed the boot.img and recovery.img only and stop to flash the system.img
after that my WIFI starting give me error and i cant swith it on
so please any one can upload the boot.img for AT&T version so i can able to reflash it again
is that how its called? boot.img?
i can't seem to find such a file (in root explorer)
do you know where can i find it?
Here you go...
I extracted these from the PG09IMG_Puccini_LTE_Cingular_US_1.17.502.3_Radio_1.04.550I.15v2_30.60.550I.10_release_210183_signed ROM file... hope it helps.
boot.img
wifi_htc_bcmMFG248_ag_tx_rx_swap.img
yes you can use it from footballs topic. or the puccini leak topic. extract from the zip file. btw. I cannot flash that whole zip anyhow.
Thanks i have done from the boot. mg from PG09IMG_Puccini_LTE_Cingular_US
I dont know why we cannot download an official RUU for ATT devices. WHY? it will makes thing easier. If your device went wrong, you can easily flash it back to factory state.
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
cx5 said:
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
Click to expand...
Click to collapse
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Thanks finniest, I have performed…Fastboot flash boot boot_signed.img
And solved temporarily. Got wifi not to say error. Allows me to turn on, but then immediately shuts off and display error again.
On another note, i also relocked bootloader. Run RUU, but error 155, means I can't restock.
Currently has TWRP, root, SU, all OK. Able to change custom rom anytime. But wifi error. CWrecovery flashed doomlord's wifi fix but not working.
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Sent from my GT-P1000 using xda app-developers app
cx5 said:
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Click to expand...
Click to collapse
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
It is good to know that you are familiar with unlocking bootloaders and have a custom recovery. That gives us a lot more options to solve this.
As far as I know the wifi module paired with the kernel by DooMLoRD is incompatible with all other kernels. So if you aren't using that kernel then you will have to use whatever bcm4329.ko file is included with the ROM that you are using. It is easy to forget that his custom wifi module is still in your /system/lib/modules directory when you flash a new kernel.
I suggest trying El-Diablo ROM and the boot.img that comes with it. This is a known working kernel and ROM pair. If you install them then first make certain to format /boot, /system and /data in whatever ways TWRP allows you to.
You should also consider that there might be something wrong with your wifi hardware. This is most likely if you have gotten your tablet wet and/or dropped it.
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
finniest said:
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
Click to expand...
Click to collapse
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Where to read step by step?
cx5 said:
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Click to expand...
Click to collapse
---
Kernel (ZIP) or Kernel as an Kernel Folder (organized like Linux kernel release 2.6.xx). I do not know how to use this last one
BTW, I am stuck whit my WiFi since a few weeks... Accidentally I wiped the System(Original) and other stuff, and happily installed the Diablo Version make my Jetstream to come alive. but never never can make the wifi work again.
I read a lot of Android and lear a bit about it, but I can't find the way to make WiFi works again. So Please... A jetstream whitout WiFi is like a die tablet... I need some help.
I need those links where they say how to, and the link to dowload IMG or ZIP. or a page teaching step by step how to install this Kernel (Organized like folders in a Linux like). thank in advance.
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
It said FAIL...
guru_shastri said:
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
Click to expand...
Click to collapse
Thanks for Helping.
I reboot into recovery using TWRP and tried to install it from Install Options. it said [FAIL]
Surely I'm just learnig about Android, I should use a commad from bootloader like this?
<fastboot flash recovery Stock_wifi_modules.zip> or
<fastboot flash boot Stock_wifi_modules.zip>
or something like this?
or perhaps use another tool instead TWRP...
flashing thru recovery should have worked. maybe the file is corrupted, I can't really tell
I downloaded and visually inspected the contents of the archive that @guru_shastri provided and everything looks okay. If you want to revert to revert to the stock WiFi module then this appears to be what you need.
Be aware that I have frequently witnessed instances where transfers to internal_sdcard via USB mount caused the file(s) to be corrupted. You should verify that a transfer worked by using MD5, cmp or (at least) a visual inspection.
WiFI OK!, SIM, not!
finniest said:
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Click to expand...
Click to collapse
Finally.. WiFI Works!... but not exactly with described... I had to read pretty much about all the things that concerns to adb/bootloader/flashing/installig>img>zip/ partition of each thing and so on before being succesfull with WiFi...
Not totally Sure, but the process that worked was:
WIPE all but recovery (using TWRP toosl)...
INSTALL el Diablo (zip) ROM Posted into the forums...(do not reboot)
INSTALL Stock_wifi_modules.zip
reboot into system...
Using USB debbuging reboot into bootloader.
Flash boot_signed.img >[fastboot flash root boot_signed.img]
(in this point the prompt said <waiting for device>, so I reboot into bootloader using Volume and Power buttons...)
Once flashed, reboot...
Now WiFi is working. Happily!
----
BTW... My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
I mean, the Sim Card appear to be reconigzed bye the system, but I don't get signal from the Phone Network (Like if it was from an unreconized carrier.. and my phone is Unlocked). I tried the sim in other phones and works well. What Can I Do at this point?
----- Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Adolyep said:
My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
Click to expand...
Click to collapse
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
Adolyep said:
Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Click to expand...
Click to collapse
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Silly me! I did not realize look at this!
finniest said:
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Click to expand...
Click to collapse
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Adolyep said:
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Click to expand...
Click to collapse
You will need to enable the MMI Code setting in the build.prop using root explorer. Without that MMI Codes do not work.
I have a HTC One m7 which I bought about 6 months ago on eBay. It came rooted and running AICP.
I do not really understand how rooting or flashing works so I just kept it as it was. I did not install any updates and I wasn't sure what they would do or whether I needed to do anything else to have them work.
Just today, I installed the latest update after it appeared in a notification. It downloaded, installed, rebooted and seems to have generally worked, the phone now looks like Lollipop rather than Kitkat etc.
The AICP OTA gives system info as:
ROM version: 10.0 NIGHTLY0 (20151007)
Google apps version 0.0 (0)
With help from Zelendel I also installed GApps successfully.
I am not receiving text messages (I'm using the 'Messaging' app) and when I press to send a text message, the message does not appear on the conversation and no text is sent.
Can anyone enlighten me as to what I need to do to get it my text-messaging working, or where to find a guide on where to do that (as a complete noob to all things rooting). I assume it is something basic that I just didnt know to do when updating the AICP (all I did was click install on the notification...).
If you have updated from a Kit Kat to Lollipop rom, then most likely you will need to update your firmware as well. The method to do so will vary depending if you are S-On or S-Off. If you aren't sure, then boot to the bootloader screen and it will say (power off then power on by holding power and volume down).
Have you tried other text messages apps too? I would try Hangouts as well since that should already be installed from the Gapps package.
My device is S-on, how can I update the firmware?
Hangouts also doesnt receive texts I'm afraid.
Many thanks!
It's a bit of a hassle... You would have to relock the bootloader and run the official RUU for your variant of the M7. This will wipe everything off the phone and return it to stock. Then you would need to unlock the bootloader again, put TWRP back on and re-setup AICP again.
Alternatively, you can make a nandroid backup and try another rom to make sure it isn't something specific to the version you are using. This would be an easier course of action, however, it is typically recommended to be on Lollipop firmware for Lollipop roms for most HTCs. So if you don't want to roll back to a Kit Kat rom, it would behoove you to go through the steps to make sure everything is set up correctly and matched. Doing this will also help you understand more about how everything is setup and the RUU is handy to have when you need to return to stock or if something happens and you softbrick or something of that nature.
Ok, I think I would be fine reverting to the stock software.
Could you explain how to find the appropriate RUU for my phone and what to do with it (or point me to a guide which does this)?
I really appreciate your help!
Depends on which variant you have. It should be readily available in the subforum for your variant here on XDA. There are usually stickies at the top of the General subforum that should provide the relevant info. RUUs should be linked there in the how to guides or in the Development forum. Basic idea is to relock the bootloader and use the RUU to do everything else. The RUU (Rom Update Utility) is a Windows application, just double click it and follow the instructions. The RUU will erase everything on the phone, including internal storage, so make sure you copy anything you need to the PC first.
I've been asked by lots of folks on how to convert the HTC 10 unlocked US version into a full-featured Verizon version so I figured i'd write an all encompassing guide on how to complete the process.
After following this guide, your phone will effectively be a fully-functioning Verizon variant. IMS, advanced calling, wifi calling and all other Verizon features will work flawlessly!
Note: I am purely compiling this information. I had no part in discovering this process, I simply followed multiple guides and other random posts on XDA to accomplish this! Credits go to @jcase, @beaups, @dottat, and any others that were involved with testing this process. Please make sure to thank these guys for the work they've done.
Step 1: Unlock bootloader and acquire s-off
In order to modify the CID/MID and change the radio, we must first acquire s-off. The easiest way to do this is to follow jcase's well-written guide.
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Move on to step 2 after finishing the above guide to completion.
Step 2: Change CID and MID
2a) Download this link, and extract into your directory of choice
https://www.androidfilehost.com/?fid=24545065934258327
2b) Boot your phone into download mode via the button combo (down + power) or by using adb reboot-bootloader with USB debugging turned on and then selecting download mode
2c) Issue the following command while in download mode:
Code:
htc_fastboot oem writecid VZW__001
2d) Issue the following command while in download mode:
Code:
htc_fastboot oem writemid 2PS650000
2e) Reboot phone back into download mode and verify the CID and MID have changed and are correct.
Step 3: Flash Verizon RUU to phone
Now that we have s-off, unlocked bootloader and the proper CID/MID on our device, now we just need the Verizon stock ROM and radio on our device. The Verizon RUU will handle both of these for us in a relatively hassle-free manner.
3a) Download the following .exe file to your local machine (big thanks to @dottat!)
Verizon Stock RUU exe (dottat)
3b) Boot phone into download mode (or Android OS w/ USB debugging enabled) and run the executable file
3c) Follow onscreen instructions and wait for process to finish
3d) Reboot phone (it may take a while to boot so BE PATIENT! mine took about 4-5 minutes if I recall)
After your phone boots, it will be a fully functioning Verizon phone. At this point, you can go activate your phone and it will work. You will be able to take Verizon official OTAs and it will behave identically to the true Verizon variant due to the RUU re-flashing stock recovery and an unmodified system.
OPTIONAL -- Step 4: Re-root phone
The RUU that you deployed on your phone was an unrooted system image with stock recovery. In order to get root back, you will need to re-do steps 1-10 in jcases's Root/s-off guide from step 1.
Here's the link again in case you're too lazy to scroll back up
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Reminder: your phone already has s-off so you ONLY NEED TO DO STEPS 1-10! Running Sunshine again will likely just report that your phone already has s-off so no worries if you accidentally do the entire guide again.
Step 5: Activate your phone
This step can be very straightforward or a moderate pain the ass depending on what you have available to you.
There are two ways to activate the HTC 10 now that it's running stock Verizon firmware/software:
1) Pop an existing, activated nano-SIM with your current phone number on it in the device and reboot. Voila!
2) Take your device to a Verizon store and convince the employee that your phone is in fact, a true Verizon phone.
I would highly suggest using an already active nano-SIM if you have that available. I, unfortunately, did not as I was coming from the Verizon LG G4. I had to go three different Verizon stores to convince them to finally activate the device. Your IMEI on your unlocked 10 will not show up in Verizon's IMEI database. The store clerk actually had to pull an IMEI from a display model HTC 10 so that she could get the nano-SIM activated for my 10.
noahjk said:
Good post! I think you're looking for this link: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
Click to expand...
Click to collapse
Good catch, thanks. I updated the links.
Tried this twice, both times my phone gets stuck on 'Preparing your phone...' after flashing and rebooting on the setup wizard.
edit: worked fine after removing SIM. Run through the setup without SIM for anybody having issues. I know this isn't explicitly stated in OP but if you're having issues, make sure you try this.
If anyone is having connection issues after putting in your SIM, you have to change your Preferred Network mode from Global to LTE/CDMA.
Other than that, everything's working great! Even comes with free VZW bloatware
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
codelinx said:
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
Click to expand...
Click to collapse
Haven't seen that before. What did you do to setup your Hotspot?
DoctorB0NG said:
Haven't seen that before. What did you do to setup your Hotspot?
Click to expand...
Click to collapse
That error would be the ota downloader.. what anything frozen I would ask the person who posted
Sent from my HTC6545LVW using Tapatalk
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Zooks97 said:
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Click to expand...
Click to collapse
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Looks like all the stock information, RUUs, roms, and recoveries are here.
Has the MID/CID for stock there as well. Hope this makes it into the OP.
When I have access to a desktop/laptop I'll update the guide. Thanks for the suggestions.
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
hunteditor said:
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
Click to expand...
Click to collapse
Yep that's the fix. The vzw ruu does not wipe.
Sent from my HTC6545LVW using Tapatalk
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Did you pick up a 10 yet?
aer0zer0 said:
Did you pick up a 10 yet?
Click to expand...
Click to collapse
I did.
It's prepared to be sent to Mr. @beaups when they are back doing devices again on May 22nd.
(In my signature below, in green are the devices I currently own, and the ones striked out are previous devices I had but are sold).
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Light1984 said:
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Click to expand...
Click to collapse
Did you activate those features on your account using the menu on the phone?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Did you activate those features on your account using the menu on the phone?
Click to expand...
Click to collapse
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Light1984 said:
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Click to expand...
Click to collapse
Take some screen shots.
Sent from my HTC6545LVW using Tapatalk
Here is my advanced calling menu with Wi-Fi calling now showing up. Haven't tested, but it seemed to let me set it up. I have Wi-Fi tether enabled via default.xml edits. The one feature I'd really like is LTE on call. Had this without problem on my M7 but I think thats because it had multiple radios and didn't have to share a radio while on call. My noob guess anyways.
Maybe it's a setting in the hidden dialer menu *#*#4636#*#*? However, when I enter that into the dialer, nothing happens, the entered numbers just disappear and nothing happens. Thoughts?
Check your OnePlus updater.
mingkee said:
Check your OnePlus updater.
Click to expand...
Click to collapse
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
S build based on Color OS and even the font changed.
I think I can deal with mine, but the most important of all, there's no player error on rooted N200 with S
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
The12thJuror said:
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
Click to expand...
Click to collapse
Yeah, I called OP three times got the same promise from OPs customer service and they never got back with me. I've never dealt with a less enthusiastic company when dealing with a serious product defect. The tech support people at first acted like the didn't believe me when I described the problem. Then once I had (I think) convinced them the problem was real, their response was like "oh well, too bad, so sad". OP offered no solutions or even ideas of what to try to do to fix the problem.
Do they test anything before pushing out an update?
I had a two day window left for returning the devices for a refund so now they're gone, and I'm gone as an OP customer, I can't just do without a phone while they fumble around trying to figure out the details for some (maybe) upcoming patch.
Good devices, terrible customer service. Never settle, nope, never again.
Scragge said:
According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
Try this
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Travisholt92 said:
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Click to expand...
Click to collapse
Do you know where to download the A12(or at least the latest A11 update so I can update to A12 via OTA) stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Tyreethetruth said:
Do you know where to download the A12 stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Click to expand...
Click to collapse
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Travisholt92 said:
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Click to expand...
Click to collapse
Thank you! I been stuck on the same update like 4-5 updates ago
On this build (metro/TMobile version converted. I can't keep android auto connected. I went into developer options and selected the default to transfer files/ android auto and all the other options but it just connects for a few and then disconnected and says device unsupported.
Rooted device and using a alpine iLX-w650
Tyreethetruth said:
Thank you! I been stuck on the same update like 4-5 updates ago
Click to expand...
Click to collapse
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Travisholt92 said:
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Click to expand...
Click to collapse
So I get on computer and go on bootloader and type "adb logcat"?
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Travisholt92 said:
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Click to expand...
Click to collapse
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Tyreethetruth said:
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Click to expand...
Click to collapse
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Travisholt92 said:
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Click to expand...
Click to collapse
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Tyreethetruth said:
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Click to expand...
Click to collapse
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Travisholt92 said:
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Click to expand...
Click to collapse
Gotcha, one last thing how do I flash using fastboot enhance? Idk what to pick to flash the A12 OTA
EDIT: Nvm I extracted the update and found the payload
Magisk patched boot.img for this release: https://drive.google.com/file/d/1A2x8YbnnO6SJq-R-1rdZZ18CU673Z2-Y/view?usp=sharing