I have converted my AT&T M8 to stock Dev Edition following this thread. Worked a treat.
http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
I'm going on a vacation and want to use my phone as a transfer spot for photos taken with a DSLR. To do that, I will need to be able to copy/move files from the camera's SD card onto my phone's SD using USB OTG.
I understand that if I keep the stock recovery, loader, etc and only achieve root, then I will be able to get any OTA that becomes available. I will also be able to use one of the methods to enable writing to the SD of the phone.
So, the question is, how to get root without changing anything that will impact the OTA ability?
Hope I was clear in what I have and what I'm looking for.
No Direction?
Nobody?
GHammer said:
Nobody?
Click to expand...
Click to collapse
I've never heard of anyone wanting just root, so I'm not sure. But if your bootloader is unlocked you can try TowelRoot and see if that works and just install SuperSu through the playstore.
Unique
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
GHammer said:
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
Click to expand...
Click to collapse
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
DanGeorges said:
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
Click to expand...
Click to collapse
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
GHammer said:
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
Click to expand...
Click to collapse
I had a rooted device (4.4.2) and when I wanted the OTA to 4.4.4, I kept the root, but re-fastbooted the stock recovery so that the OTA would work. It kept my root (I think), and then I just re-installed TWRP so that I could still do backups..
I hope that someone with more knowledge than I will chime in if I'm wrong (or right).
DanGeorges said:
I kept the root, but re-fastbooted the stock recovery so that the OTA would work.
Click to expand...
Click to collapse
This is what I would suggest. There may be other ways (root without custom recovery). But I know for certain that the following will work: flash TWRP, flash SU or SuperSU to root. Than flash back to stock recovery.
You will be on stock recovery, have root, and should not impact OTA (provided all system files are also stock and not altered by root).
You can also try to fastboot boot TWRP (and then flash SU/SuperSU) without actually flashing TWRP. I'm not certain this will work, but I think it does under LP. I think something on 4.4.4 broke this ability, but then it came back.
Weekend Project
I will try the boot TWRP method first, and if that fails, I'll flash TWRP, get root, then go back to stock recovery.
This is now just an exercise to see which method works as the stock File Manager reads the USB and can copy files to the SD. I had not tried since 4.4.4. but did yesterday and it works for any kind of file.
Related
I have the sprint EVO3D. I unlocked it and its rooted, but at the moment I'm still running the stock image. I keep trying to install the latest OTA update from HTC (the one that removes CarrierIQ) but it keeps failing to install...no message, no error, essentially the phone just reboots when I tell it to install the update.
Does it have something to do with CWM being flashed for recovery? I'd like to have CarrierIQ removed. Is there a way around this that anyone knows of?
I had CM7 and MIUI installed at one point, but I wanted the 3D camera that I don't get with either of those.
DarkNemesis618 said:
I have the sprint EVO3D. I unlocked it and its rooted, but at the moment I'm still running the stock image. I keep trying to install the latest OTA update from HTC (the one that removes CarrierIQ) but it keeps failing to install...no message, no error, essentially the phone just reboots when I tell it to install the update.
Does it have something to do with CWM being flashed for recovery? I'd like to have CarrierIQ removed. Is there a way around this that anyone knows of?
I had CM7 and MIUI installed at one point, but I wanted the 3D camera that I don't get with either of those.
Click to expand...
Click to collapse
If you're running into issues applying an OTA while on a rooted ROM, my first suggestion would be to suggest you grab a rooted stock ROM which already contains the OTA.
The steps to installing an OTA are fairly simple, but if done improperly whether due to lack of following directions or any other myraid of reasons, COULD damage the device or at least set the user back a few hours.
In order to process an OTA with 100% certainity, the stock recovery should be loaded. Manufacturers ARE able to add and use edify scripting language which could only be interperted and executed probably by a stock recovery image as they are not required to release the source code to their recovery image.
With that said and no mention of htc official unlock or revolutionary unlock, the process I would take on my own personal EVO 3D which would be unlocked with revolutionary is as follows:
1) Flash stock recovery image from most recent RUU via Flash Image GUI while in normal android mode.
2) Accept OTA and allow to fully process.
3) Flash custom recovery back using a PG86IMG.zip file.
4) Boot into custom recovery and via adb shell chmod 4755 /system/bin/su.
5) Reboot and everything should be set.
Another word of caution will be at step 2 to understand this will remove root access by removing the setuid flag on the /system/bin/su binary. This will be restored by step 4.
These steps might have to be tailored/changed for an HTC unlock device. Probably step 3 can be replaced by the fastboot flash recovery c:\recovery.img command.
Hope that helps!
Yes, it is because of CWM. You need the stock recovery to update officially.
Where would I download the stock recovery? I tried googling for it, but wasn't getting any straight answer that I could understand...
http://forum.xda-developers.com/showthread.php?p=22554153#post22554153
There you go
Just download a stock rooted rom zip and flash it. Much easier, and much less hassle than trying to go back to the stock recovery.
Thanks everyone, got stock recovery flashed and update is installed...now to get my apps reinstalled
sitlet said:
Just download a stock rooted rom zip and flash it. Much easier, and much less hassle than trying to go back to the stock recovery.
Click to expand...
Click to collapse
I agree, but the man wanted the stock recovery, so the stock recovery is what he got lol
DarkNemesis618 said:
Thanks everyone, got stock recovery flashed and update is installed...now to get my apps reinstalled
Click to expand...
Click to collapse
Glad it all worked!
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.
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
It is amazing with most of the searching I have done about this update, VS98026A, on how they say that this is the KitKat 4.4.4 update. When it isn't and we are still at 4.4.2.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
Rooted vs98024a and did OTA to vs98026a and still have Root. Pretty neat we didn't lose Root.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
lukester01 said:
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
Click to expand...
Click to collapse
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
wait for new ioroot?
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
RobertVanHagar said:
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
Click to expand...
Click to collapse
lukester01 said:
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
Click to expand...
Click to collapse
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Stump root worked on LG G2 26A
Stump root worked. It auto used the brute forth method like you said. Thanks.
Finally I can program my bluetooth call button back to use google now voice search instead of LG voice command.
snellc001 said:
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Click to expand...
Click to collapse
I used stump root successfully on my 26A as well.
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
Simply remove the modified mobile hotspot from system/app. That should allow you to take the OTA
Sent From The Trail Of Untold Truths
you will not be able to take any OTA if you add a custom recovery
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
If you add a custom recovery you will not be able to take any OTA updates.
lukester01 said:
If you add a custom recovery you will not be able to take any OTA updates.
Click to expand...
Click to collapse
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Correct, you don't need one. Note however you won't be able to do image (nandroid) backups/restores or flash images. So be very careful with your root privileges ?
Sent from my VS980 4G
custom recovery
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Custom recovery allows you to flash roms, make nandroid backups, and do several other things. But it will make the phone so that you cannot get OTA updates. To apply updates when you have a custom recovery you will have to wait for someone to make the OTA update into a file you can flash.
TWRP
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
MFR73 said:
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
Click to expand...
Click to collapse
I'm not familiar with TWRP commands, but sounds to me like the update tried to install by booting to recovery, but since it was not the stock recovery it could not update. Having a custom recovery in my experience has always made it so you can not take OTA updates. You would use the LG Mobile Support Tool to "upgrade recovery", that will basically restore the stock recovery. You will lose root. But you can update to 26A, and then use Stump root to get root again.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
had that happen
nicknjg88 said:
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
Click to expand...
Click to collapse
Look back a page. I had the same problem. You need to use the LG Mobile Support Tool and upgrade your recovery. Then take the over the air update. Then root again using Stump root.
I got the 0x1111004 error, and then the 0x1117008 error when trying to take the 25B and 26A update. I tried removing all of my framework and changes, but it didn't seem to help. Resorted to full KDZ wipe to 24A, then ioroot before taking the 26A update. It updated just fine and now I'm running the latest. Now to remove all the bloatware and restore my backups...
I'm hoping they don't push out any more OTA anytime soon unless it's L.
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.
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.