Hello,
I am currently with Freedom Mobile, but my phone was purchased through Rogers, has the open Network Bands to use the Freedom network, and a new P6 Freedom Mobile SIM Card. My phone is also running as HTC_001.
Before modifying my phone and having to re-do everything I may have done in the past:
Can anyone on either Freedom Mobiles network with their stock RUU confirm they have the Wifi Calling option and it works?
To be able to use services of a carrier, like WiFi calling etc, you MUST be using a firmware that came from that carrier. If freedom issue a specific firmware for the m9 you must use it. If they don't and their phones come "network unlocked/debranded", ie using the 401 firmware, then you should be able to access the WiFi etc on any device. Another example is if you want to use tmobile features then you need a tmobile firmware.
So the question you need to find the answer to is "does freedom carrier have a branded firmware for the m9".
You are correct. Based on my research earlier, I came across that same conclusion.
I think the best/only way to test this however, is a) if someone has a latest version of their branded firmware and can check this or b) I get a TWRP restore and install this on my phone (I assume this is possible and not IMEI restricted) or c) I find another way to get to a stock firmware.
I changed my CID back to the Freedom Mobile one and downloaded the stock TWRP backup from the old Canadian Stock ROM thread, but it is either too large or possibly too old and incompatible with my phone.
I had to use ADB commands through computer to restore, and it looked like it would accept. However, the computer was stuck at "unlock phone screen to continue" and TWRP said "MTP enabled."
Those backups are most likely too old. You can try to find a suitable RUU on easy-firmware or you need to contact llabtoofer's RUU service since at the moment there is no freely available RUU for your phone. The links can be found in the FAQ of the ReadMe thread.
Sent from my Motorola XT1572 using XDA Labs
Just a quick update. I ended up aborting this "project" of mine.
Despite using Mac OS, encountering corrupt zip files and other files issues where I would get an 22 RU_HEADER_ERROR, I ended up finding my biggest issue.
My MID was set to OPJA10000, instead of 0PJA10000. This issue caused multiple hours of frustrations. I have now flashed my phone back to stock 4.28.401.3. I will most likely have to reinstall TWRP and restore my previous backup.
On another note, is anyone else unable to find the HTC Mail app in Google Play store? Mine crashes every time I try to reply to emails or create a new one. Google Play Store on the computer shows my M9 is not compatible.
Get rid of Google Chrome. I don't know what's exactly the reason but current chrome versions break the HTC Mail app.
Sent from my HTC One M9 using XDA Labs
Same for me. Not compatible.
Just an update to this.
They released a new version of HTC Mail v10.70.1031252.
Based on quick trials, this has resolved the recent issues regarding HTC Mail and Google Chrome being at the latest version, regarding crashing when creating a new email or replying, but I have not tested it extensively.
I know this should be a new thread with a proper title instead of piggybacking on an old one, so if a mod can create one (or prefers I do), that would be great.
Related
Hi. I recently switched over to android and bought an M8 GPE hoping to use it with ISIS on T-Mobile. I used to use an iPhone on T-Mobile so I couldn't use ISIS. I've been trying for the past few days to get ISIS running, but nothing has worked (Market Helper, I tried to restore a T-Mobile M8 Nandroid backup, which failed, sideloading APK's, replacing the build.prop with one from T-Mobile, flashing it with a T-Mobile RUU, etc).
Does anyone know how I can flash a T-Mobile Rom on my GPE M8? (Unfortunately I got the OTA update to 4.4.4 so I don't think I can get S-OFF, does that matter?)
You could still flash ROMs without s-off. There's a few T-Mobile based ROMs available, check out the T-Mobile forum. Also insertcoin and viperone has the option to choose the T-Mobile bloats. I haven't tried isis myself so i can't help you in that department. I don't have the "isis sim"
Sent from my HTC One_M8 using XDA Free mobile app
Teo032 said:
You could still flash ROMs without s-off. There's a few T-Mobile based ROMs available, check out the T-Mobile forum. Also insertcoin and viperone has the option to choose the T-Mobile bloats. I haven't tried isis myself so i can't help you in that department. I don't have the "isis sim"
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. I actually had already tried to install ViperOme, but it failed. I believe there was an errror when trying to create a symlink in /system/bin, due to missing permissions. Can I simply install a T-Mobile firmware like this one : http://www.androidfilehost.com/?fid=23487008491964290 from http://forum.xda-developers.com/showthread.php?t=2754063 by booting into TWRP Recovery mode and selecting Restore? Or do I need to select "Install" instead? What about using something like ROM Manager, could I use that?
I am just guessing because I had problems with OTA's on my T-Mobile m8 to EU m8 conversion. You probably need to convert your model id to 13000 for everything to flash smoothly. I had to change my model id to 10000. Beware. I hope you understand what you're doing when you start changing cid's and mid's. Took me a few days to figure ota issue because of the model id making flashes fail.
BTW, I think you're downgrading if you goto a T-Mobile rom. I would convert to an EU ROM and then use google wallet. Less bloat and ram management is so much better. Less loading from save state and apps just pop up because they're still in ram.
Sent from HTC One_M8 using hofo app.
@rbiter said:
I am just guessing because I had problems with OTA's on my T-Mobile m8 to EU m8 conversion. You probably need to convert your model id to 13000 for everything to flash smoothly. I had to change my model id to 10000. Beware. I hope you understand what you're doing when you start changing cid's and mid's. Took me a few days to figure ota issue because of the model id making flashes fail.
BTW, I think you're downgrading if you goto a T-Mobile rom. I would convert to an EU ROM and then use google wallet. Less bloat and ram management is so much better. Less loading from save state and apps just pop up because they're still in ram.
Sent from HTC One_M8 using hofo app.
Click to expand...
Click to collapse
ISIS is still kinda eh... i havent gotten it to work properly on viper rom. you have to basically swap everything though. i would swap to a tmobile firmware make sure your CID is changed to tmobile as well as install the tmobile TWRP backup and just factory reset after that. then it should startup like a brand new tmobile phone.
My guide should give some pointers on changing GSM M8 variants see my sig
There is another thread regarding converson from GPE however :good:
Hi guys, I can't update my stock AT&T m8. The ota software update isn't showing up at all. I unlocked the phone with a code I bought online Since Iam no longer using an AT&T sim. I switched to lycamobile. is that the reason I can't see the update? Is there anywhere I can download the ota file? I don't want to root my phone.
gabriox said:
I switched to lycamobile. is that the reason I can't see the update?
Click to expand...
Click to collapse
Yes and no.
Its correct that you will not receive updates for the AT&T version M8 if you aren't on AT&T's network. Some folks here may disagree, that aren't familiar with AT&T (most HTC phones will usually update fine OTA regardless of network). But AT&T is the oddball, you have to be connected to their network, or no OTA.
The other thing is, that the AT&T version hasn't updated to Lollipop yet, and no release date given (but hopefully soon). So even if you were connected to AT&T's network, you wouldn't be able to update to LP.
The latest official software for the AT&T version is Android 4.4.4. If you aren't on that version, you can download the RUU and update with it. Then wait for LP to release as RUU. RUUs are linked in my AT&T specific Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Your other option is to mod the phone and s-off in order to install LP firmware and run a stock or custom LP ROM. Or fully convert the phone to another carrier version (change CID).
redpoint73 said:
Yes and no.
Its correct that you will not receive updates for the AT&T version M8 if you aren't on AT&T's network. Some folks here may disagree, that aren't familiar with AT&T (most HTC phones will usually update fine OTA regardless of network). But AT&T is the oddball, you have to be connected to their network, or no OTA.
The other thing is, that the AT&T version hasn't updated to Lollipop yet, and no release date given (but hopefully soon). So even if you were connected to AT&T's network, you wouldn't be able to update to LP.
The latest official software for the AT&T version is Android 4.4.4. If you aren't on that version, you can download the RUU and update with it. Then wait for LP to release as RUU. RUUs are linked in my AT&T specific Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Your other option is to mod the phone and s-off in order to install LP firmware and run a stock or custom LP ROM. Or fully convert the phone to another carrier version (change CID).
Click to expand...
Click to collapse
i got the the latest at&t update. so should i wait for at&t to release the update or? i dont want a custom rom. just want a stock phone.
gabriox said:
i got the the latest at&t update. so should i wait for at&t to release the update or? i dont want a custom rom. just want a stock phone.
Click to expand...
Click to collapse
Its up to you to make that decision. LP release on AT&T is rumored by a decently reliable source to be "soon", but who knows what that means?
My personal opinion, there is absolutely no good reason to be on AT&T stock software if you aren't even on their network or in the US. Personally, I can't stand AT&T's bloatware and gimped features (you may notice that WiFi tethering is disabled). So converting to another (stock) version to me is highly preferable (or running a custom ROM for that matter).
Not sure what region or country you are in, but you may consider converting to Euro or "international" version (which would still be "stock" just stock international unbranded instead of AT&T). Not only will you get rid of AT&T software branding, but once you fully convert, you will also be able to get OTA updates. Plus, international M8 gets updated much earlier than AT&T.
To "convert", you need to s-off and change CID and MID. From there, you can convert your phone to any other version: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
Honestly I agree with you. Is there way I can convert to the international version or preferably Google edition without all my files being deleted? btw Iam in the United states. And can you guide me on the process? Thanks
gabriox said:
Is there way I can convert to the international version or preferably Google edition without all my files being deleted?
Click to expand...
Click to collapse
Not that I am aware. Your best bet is to backup your data, then restore it (as appropriate) after you convert. Which you should absolutely do anyway, before undertaking any such major mods. Even if they were supposed to "keep" user data, as nothing is ever a "sure thing" and its always best to back up and avoid regret.
There are different methods to backup, and it also depends on exactly what data you want to keep. I personally have my contacts on Gmail, and don't use any other email on my phone aside from Gmail (so my contacts and Gmail are all just on the cloud). So for me, its mostly just app data that I want to backup, so I use Titanium Backup for that purpose. You can also use Titanium to backup and restore your SMS and call log; at least between Sense ROMs (don't know if this will migrate to GPE). Don't use Titanium to migrate any system data (will often cause bugs if you are moving between any ROMs that are significantly different). I just customize system settings manually after ROM flash, etc. Don't know what other files you may want to keep. If its just media (songs, pics, video) you can just copy those to your computer or removable SD as means of backup. Or there are a variety of cloud options you can use to backup pics and other files.
So, I ordered a refurb sm-p600 Wifi-only tablet from Amazon, but I received a Verizon sm-p605v. Now they show out of stock on the Wifi model. Am trying to arrange a swap, but don't know how successful I'll be.
It's my first tablet and I absolutely LOVE it and don't want to give it up.
So, it's basically the same thing, but there are issues:
1.) Has Verizon junk all over it.
2.) Complains about no SIM card - if I put in a SIM card it complains about activation. (These don't appear to ever go away)
3.) Have to keep it in airplane mode or it will drain the battery trying to connect, if I keep it in airplane mode, at least one app (Accuweather) complains about no network
4.) And this is the biggest issue - can't check for new updates - I really want Lollipop so it matches my phone, but it basically says update is unavailable. I assume Verizon has it set up so that you have to pull updates only from them.
I'm never going to put this on a mobile plan and I'd really prefer to have the non Verizon tablet, but if I can't, is it possible to flash the stock wi-fi sm-p600 firmware onto this so that it thinks it's a sm-p600 - or is this a recipe for brick making?
I also haven't been able to find a sm-p605v lollipop image, so I may be out of luck assuming the answer is no.
I'm in a similar situation. I purchased what I thought was a SM-P605 (international version) and I got shipped a SM-P605V (Verizon edition). In my case, the vendor listed the device as an SM-605, but it was an SM-P605V. Further down in the listing it listed it as a Verizon edition, so that's the reason they declined the return.
Unfortunately, you cannot use SM-P600 firmware, as it is a different processor.
There is a way to update it to 5.1.1 though. When plugging the tablet into the PC, there is a Verizon utility for Windows on the tablet that lets you update the software. (it's based on Samsung Kies). I just did it yesterday. Works fine. I'm trying to figure out if I can put a non-Verizon factory Samsung image on it so I can at least have the option to put my own custom image on it (the Verizon edition has a locked bootloader, which prevents you from putting non-Samsung ROM images).
I personally am sick of vendors customization of Android to the point where it is not recognizable. Give us the option for stock Android...
After 3 attempts I finally got them to send me the correct Wifi only model, which works great!
I am sorry if this has happened to 40 other people and mentioned every day but I am at the end of my patience trying to figure this out and have too many tabs open with redundant info!!!
I attempted to unlock my bone-stock up-to-date (v6.0.1) one m9 developer edition using this link http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133 but after following all the directions when it was time to restart it just gave me the screen with the red development only warning for about 2 or 3 seconds then reset and repeated.. it says it may do this a few times but it did it like 10+ times so I figured there was a problem. Since then I have tried many different files from many different places.
I do not have a working backup copy of my phone (my bad) but I did make a backup of the system image onto my sd card.
As of now, if I reboot it sends me to the white bootloader screen after trying to follow another similar page with directions to root (specifically mentions android v6.0 in the title).
The phone is now S-on.
LK-1.0.0.00000
Radio 01.01-U11440892_97.00.51203G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.617.12
The recovery mode loads to TWRP 2.8.7.1_CPTB-B1
Eventually my main goal was to get this phone to work "correctly" with Tmobile US (wifi calling and fastest available internet connection) but for now I just want it to load back up to my system (hopefully without losing the data that is currently in it!!!)
Can anybody recommend which files I need to put on and which way you recommend?
Thanks in Advance!!!!
-AshayinFLA
You can't root Android M with a different SuperSU version than 2.64 or 2.65. (Keyword: system-less root)
There's backup for your version in my thread. Instructions how to correctly restore it can be found in my google sheet (linked in the 5th post or my signature).
I'm not 100 % sure but I guess you need to flash the T-Mobile firmware if you want to use their WIFI-calling. For that you need S-OFF. Otherwise you can't change the firmware. (Wouldn't it have been easier to buy a T-Mobile branded phone than buying a dev edition, paying for either Sunshine or someone who has a java card and convert the phone to the T-Mobile version? )
This may seem like a weird question, but is there is way to convert back to the T-Mobile firmware? Mostly I would like to avoid having to install the modem manually with every update. If this is no longer the case and there is a permanent modem solution then that's all I would need. I found a lemonade tar.gz for the T-Mobile firmware supposedly, however, I don't know how to make that a installable ROM. The link is a github link here, OnePlus 9 Pro Firmware. I've never swapped off of the carrier firmware and had to manually reinstall the modem with every update before. The most annoying part of that for me would be keeping the bootloader unlocked. That's only a minor issue for me as I play Pokemon Go and unlocked bootloader/root can cause issues with that. I don't generally tweak my phones much anymore. I prefer the non carrier ROM to have more current updates. To recap, is it possible to either go back to T-Mobile ROM or is a permanent modem fix for the conversion?
MSM is the easiest way. Just use the MSM tool for LE2127 and you'll be on your way.
I have a flash-all script that you put in a fastboot flashable stock rom zip, and it'll make it so the radio (modem) persists through OTA's. Just gotta dig around for it and see what I did with it.
Thank you both. If I could get back to T-Mobile firmware then swap back to global again that would be great. I think I may be up the proverbial creek though. In my search I came across what seems like an older thread first and I used the India MSM to flip to global. This unfortunately means the T-Mobile MSM is unable to flash to my phone as it sees it as an India phone. I found the other global MSM, and I am able to see the Target directory and choose O2, however, the MSM fails to download. Param Preload error, device not match image.
I've made peace with not being able to get back to T-Mobile firmware, I may have to research the persistent modem more for a fix that will work with India. Is there a modem install for OOS12 that doesn't brick the phone? I use the ones I have from the T-Mobile files, and they work fine for OOS11, but they immediately brick 12 after install.
Bumping this post to ask again about the modem for Android 12. Also, my Bluetooth audio cuts in and out, it's very crackly. This only started after jumping from the T-Mobile ROM.
Edit: Also the voicemail doesn't show in the Phone app. Voicemail service is listed as "Your Carrier" and I can't do anything with it. There are no options that I can toggle at all.
I was looking at the repo of builds for the 9 Pro. I see there is an Android S for all regions in there. Could that possibly change the region of the firmware to, more or less, not associated anywhere and allow a restore to the T-Mobile firmware?
I'm not entirely sure how, but I did manage to get off of the India firmware and onto the EU firmware. At least from there I should be able to get the persistent modem. Working on that process now.
All right, everything has been running fine on the EU firmware, the only thing I'm still having an issue with is Bluetooth. Not connectivity at all, just on phone calls and in one vehicle for audio. It's incredibly choppy. It didn't used to be an issue, it only started after I left the T-Mobile firmware. Is there something I need to flash for the Bluetooth or a setting I'm missing?