I have been searching everywhere to try and find a way to load CM11 on my USC Galaxy Mega. All I can find is a ROM for the I9200/I9205. I have been in other forums that you can flash this CM11 release on a Metro PCS Mega. Is it possible to flash this on my USC R-960 Mega or have any of you here tried?
Depends on your phone setup. You will need an unlocked bootloader and should be running knox free firmware on your phone.
If the above criteria are met, then you can try flashing after backing up your stock rom. CM11 works on a lot of Mega versions.
Silesh.Nair said:
Depends on your phone setup. You will need an unlocked bootloader and should be running knox free firmware on your phone.
If the above criteria are met, then you can try flashing after backing up your stock rom. CM11 works on a lot of Mega versions.
Click to expand...
Click to collapse
Here is my setup.
I have rooted my device and have flashed CWM. Sounds like the boat loader is a different process than above? Also havent heard of knox free firmware, is that just something you flash with odin or something?
All the latest firmware releases come with Samsung's proprietary Security feature called knox. If you install a knox enabled firmware, then you will not be able to do the following.
Flash custom rom
Go back to a older stock rom
Go back to an older nandroid backup.
Trying to do any of the following will result in an insecure kernel error which can be rectified only by flashing a knox enabled firmware through Odin.
Post a snapshot of the bootloader screen.
is this what your talking about
Looks ok. First make a backup of your custom rom. Then you can try flashing a custom rom of your choice. You may/may not get LTE to work.
I presume you have not installed any ota update from your provider.
Silesh.Nair said:
Looks ok. First make a backup of your custom rom. Then you can try flashing a custom rom of your choice. You may/may not get LTE to work.
I presume you have not installed any ota update from your provider.
Click to expand...
Click to collapse
No ota updates, even when I checked manually I got a message saying you phone is modified or something.
dpetes262 said:
No ota updates, even when I checked manually I got a message saying you phone is modified or something.
Click to expand...
Click to collapse
Thats because your system status is custom. OTA's work only system and binary status are official.
Silesh.Nair said:
Thats because your system status is custom. OTA's work only system and binary status are official.
Click to expand...
Click to collapse
so I was able to flash/cm11 for i9200/i9205 and no touchscreen at all. I then flashed slimcat, same thing no touchscreen and accelerometer was acting weird. I then restored from the backup and touchscreen is back. I have 4g but its saying im roaming now. I wiped everything before all installs too. Any ideas?
dpetes262 said:
so I was able to flash/cm11 for i9200/i9205 and no touchscreen at all. I then flashed slimcat, same thing no touchscreen and accelerometer was acting weird. I then restored from the backup and touchscreen is back. I have 4g but its saying im roaming now. I wiped everything before all installs too. Any ideas?
Click to expand...
Click to collapse
So after I booted back to my backup,I had service but could not make calls or send texts. So what I did was a factory reset from with that ROM. This restored my service completely. Now I am just wondering why the touchscreen doesn't work on the other roms.
Silesh.Nair said:
Thats because your system status is custom. OTA's work only system and binary status are official.
Click to expand...
Click to collapse
Just a side note, when I flash either Phils CWM touch version, I get no touch or if I flash any other recovery, I get no touch functionality. Does this have something to do with the ROM not having touch?
Related
Some people like sticking with stock, and there isn't a huge issue with that as the stock ROM is pretty good on the Note 2. However, if you want to be stock and remained unlocked, it's quite difficult to do as every new OTA re-locks the bootloader. It's also difficult to stay stock and keep a custom recovery as it will be over-written on every boot.
Now, users that want to stay unlocked and have custom recovery have an option available. This will require you to be fully stock, if you've modified anything in /system, it won't work. The only change you can have is root, but if you've modified build.prop, the kernel, or removed any files, you need to restore. If you have any doubts, flash the alternate restore file (after extracting it) from here.
There is one other requirement for this, and that is you need a custom recovery installed. If you've unlocked, you'll already have one. If not, you'll need to be rooted and you can use ROM manager or GooManager to flash a custom recovery (after going back to stock of course).
Now you have the pre-requisites down, stock rom and custom recovery, so all you need are the files. There are two updates available, so there are currently two files to flash to be on the latest OTA. You can download them below, and installation is as simple as downloading them to your phone and installing them via recovery. If you went back to stock VRALJB, you'll start with the VRALJB to VRALL4 file, then flash VRALL4 to VRAMC3 to get to the latest system. It should be fairly easy to figure out.
If you have any errors when flashing, odds are, you did something to files in /system and caused a problem. If that is the case, start over and flash the alternate restore file and proceed from there. I'll continue to update this as new OTAs are released then as well.
[size=+2]Downloads[/size]
VRALJB to VRALL4
VRALL4 to VRAMC3
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Digbob said:
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
It updates everything except for sboot.bin, tz.img (both bootloader files), and recovery.
hey thanks for this!
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
it says you must be on completely stock rooted with a custom recovery. being you have a custom kernel is most likely the problem. anything modified in /system will cause a fail. flash back to vraljb alternate restore file, then upgrade...or boot into recovery and flash beans mc3 stock rooted .zip rom
either way you will most likely need to wipe data to upgrade...atleast thats normallya prerequisite when changing bases.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
imnuts said:
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
Click to expand...
Click to collapse
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Hey thanks for this! This'll make my wife very happy. I thought I'd have to clean install beans stock rom. She just loves stock.
Sent from my Note II using Tapatalk 2
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
OTA fails if you have a custom recovery.
Sent from my Note II using Tapatalk 2
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
FAUguy said:
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Click to expand...
Click to collapse
You're setting your phone up again either way.
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
Not everyone is running a custom ROM. Some people are unlocked and on stock rooted with custom recovery and that's it. This is meant so they can stay up to date and remain on stock, rooted, and custom recovery.
TonikJDK said:
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
Click to expand...
Click to collapse
This will be fully stock (minus recovery over-write). Beans did some other stuff to his ROM package from what I saw the last time I looked at the thread. Nothing major or groundbreaking, but it isn't as close to stock as this is.
pmazz850 said:
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
Click to expand...
Click to collapse
Really?
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Mac of York said:
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Click to expand...
Click to collapse
Yah, I think I'm gonna wipe/flash beans odex rom VRAMC3 & radio/restore data from NAND backup from VRALL4, hopefully it should be fine. Unless anyone would know otherwise?
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
What change for Wifi Tether?
imnuts said:
What change for Wifi Tether?
Click to expand...
Click to collapse
WifiTether_TrevE_Mod_11_22_2012.apk
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Installed Update, Re-rooted, re-installed TWRP
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
never mind I got it. I had a brain fart and was doing the process back words. I put it in download mode for the root.
hotspot mod
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
reesemtk60 said:
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
Click to expand...
Click to collapse
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Deodex or odex
thanks one more question how can i tell if my phone is deodex or odex
reesemtk60 said:
thanks one more question how can i tell if my phone is deodex or odex
Click to expand...
Click to collapse
well easiest way is. if its your stock ROM that came with the phone when you bought it. it is odex.
if you are rooted, you can use root explorer to go into your system/app file and see if it shows odex settings for apps
I did and had no problem rooting with kingo. What I cannot find is a way around sim lock without going through metro and that sucks.
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
is that rom odex of deodex because my is odex
reesemtk60 said:
is that rom odex of deodex because my is odex
Click to expand...
Click to collapse
deodex
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
Almost had a heart attack from this upgrade. My phone was already rooted when I applied the update from Kies. Everything went through fine except when it restarted, I couldn't turn on Wifi at all and I was getting an E in the cell signal. I managed to download the TWRP tar file and Kingo app to root again. I was able to restore my previous backed up image and everything was when I last left it! WHEW!
That's strange. I had no problem. wifi worked and I haven't seen E at all (only 4g lte or 4g). My signal appears to be stronger and more stable with this update than with the original firmware (most of the time I have full bars). As mentioned I don't know what changes were made (no change log around) but this is my observation so far.
Sent from my SGH-M819N using xda app-developers app
Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.
[QUOT1.0razykipa;50763526]Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.[/QUOTE]
This string is present on my phone in download mode:
BOOTLOADER RP SWREV: 3
I have no lines displaying anything about KNOX.
In titanium backup I froze knox 1.0, knox notification manager 1.0, and knox store 1.0.
So it appears that knox is in the rom somewhere but it's had no impact on me. I'm rooted, have twrp installed and have flashed multiple custom roms on my device (both tw and aosp based roms).
Perfect, thanks! Glad you guys got spared from the horrid new Knox bootloaders. There's a small chance that the M819 can be downgraded to the older bootloader to remove Knox entirely, but if the update came with the newest bootloader (I got stuck with it on my i527M) there is no hope at all of downgrading.
Thanks to whoever posted this and the creator of this rom
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
I have the sgh-m819n metro pcs model running the mk7 firmware. This was the only rom that worked 100% for me. Im running twrp recovery,super user and free hotspot. Not to mention all the extra cool apps that it comes with. Big props to the developers of this software may your days be blessed with many more hacks.
Must be unrooted to perform update thru kies without errors..
Galaxy Mega 6.3 On Liquidsmooth rom posted this
question to everyone....
ok not sure if am in the right area to post this but. I have a metro galaxy mega 6.3 (sgh m819n) successfully rooted with kingo. what im trying to find is how to put a custom recovery like twrp and how to do it like step by step. help would be greatly appreciated. or to point me in the right direction. thanks guys.
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
thanksss
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
Click to expand...
Click to collapse
ok thanks and this will work correct.... also before I add a new rom on the m819n I have another question... I used to get 4LTE every where and now I get only 4G or edge after rooting with stock rom. signal apps dont do crap. is there a way to fix this... I miss my LTE data speeds. if you know how to fix or anything please point me in the right direction thanks.
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
sduffy89 said:
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
Click to expand...
Click to collapse
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
I chose to bump up my android version cuz i friend another SIM card. I tether for my Hulu, Netflix, Amazon Prime, and whatever else, thankfully my laptop can get weak unsecured internet signals, but i'm walking my Note around the apartment trying to get good 1x reception Problems may be overlapping but next step is something basic from the Play Store to verify root.
I read of some luck with root for 4.3, just not bootloader. Am i correct?
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
sduffy89 said:
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
Click to expand...
Click to collapse
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
KuNiT said:
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
Click to expand...
Click to collapse
Correct. If you took the OTA it relocked your bootloader and you are stuck. You can still root the official 4.3 but you are stuck waiting until someone unlocks the bootloader. This means no custom ROMs/Recovery.
Which 4.3 firmware did you flash? If its the OTA then yes you're outta luck.
If you did follow the Alliance's rom thread. There is a 4.3 MJ9 firmware you need to flash. It doesn't have the locked bootloader. You are then able to boot up in the basic recovery and then flash either TWRP or CWM recovery.
Has anyone figured out how to apply this update on a rooted device running "official" ROM? For me the update downloads and reboots to recovery (twrp in my case). The update is not applied.
Thoughts?
tmknight said:
Has anyone figured out how to apply this update on a rooted device running "official" ROM? For me the update downloads and reboots to recovery (twrp in my case). The update is not applied.
Thoughts?
Click to expand...
Click to collapse
you need stock recovery, also i think (not completely sure about this) you have to unroot and maybe even relock your bootloader in order to apply the update.
reaper90 said:
you need stock recovery, also i think (not completely sure about this) you have to unroot and maybe even relock your bootloader in order to apply the update.
Click to expand...
Click to collapse
My phone is completely stock and I still can't download this update. Maybe because I live in Europe... This is awful.
R.Petrov said:
My phone is completely stock and I still can't download this update. Maybe because I live in Europe... This is awful.
Click to expand...
Click to collapse
you said, you've got TWRP recovery installed, so your phone's bootloader is definitely unlocked and you've got a custom recovery installed. The update only works if /system partition is completely stock, you've got stock recovery and your bootloader is (re-)locked.
if anything doesn't match your phones CID, the update won't install.
I did not say that. tmknight did.
I have this phone with an AT&T IMEI from China, but the ROM is not from AT&T, I guess its the Erupean version or somenthing... it came unlocked for any GSM company and thats why i bought it... I also know that the bootloades is locked.
I cant update it with the official AT&T ROM cause it does not find it... Im stuck in its Android 4.1.1 slow version, and I see many bugs on it.
Can anyone help me? PLEAAAASSSEEEEE!!!!
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.