Related
Hello everyone,
Well might as well say hi. I'm Ryukouki. I use this handle on a lot of forums, so if this is familiar you most likely know me elsewhere. So, anywho! I purchased a VZW Samsung Galaxy S4 two weeks ago, and I'm really curious. I rooted my phone, installed Clockwork Mod and backed up my data (I THINK) and I'm looking into ROMs for the Galaxy S4. What is the best mod for speed and performance, with good ease of use, and does not require a data wipe on installation? And is there a tutorial to go about doing this? I'm kind of new to the whole smartphone thing (used a feature phone for seven years!!), but I'm not too afraid to try new things out.
Ryukouki said:
Hello everyone,
Well might as well say hi. I'm Ryukouki. I use this handle on a lot of forums, so if this is familiar you most likely know me elsewhere. So, anywho! I purchased a VZW Samsung Galaxy S4 two weeks ago, and I'm really curious. I rooted my phone, installed Clockwork Mod and backed up my data (I THINK) and I'm looking into ROMs for the Galaxy S4. What is the best mod for speed and performance, with good ease of use, and does not require a data wipe on installation? And is there a tutorial to go about doing this? I'm kind of new to the whole smartphone thing (used a feature phone for seven years!!), but I'm not too afraid to try new things out.
Click to expand...
Click to collapse
No ROMs 'require' a data wipe per se. You may, however, run into problems with any ROM if you don't completely wipe data when installing (especially the first time you go from stock to a ROM).
Why are you so afraid of wiping data? You could very easily download a few backup apps and have everything back up and running in 20 minutes.
trebb said:
No ROMs 'require' a data wipe per se. You may, however, run into problems with any ROM if you don't completely wipe data when installing (especially the first time you go from stock to a ROM).
Why are you so afraid of wiping data? You could very easily download a few backup apps and have everything back up and running in 20 minutes.
Click to expand...
Click to collapse
I assume that this requires backup to my SD card though? And can you explain how I go about doing this? Do I just pick up things like App Restore and Backup (I think it's the other way around...) and then backup and restore? I don't want to screw this up, because I have a few apps where I've dumped a couple hundred dollars into and if I delete it or wipe it, I lose all the data, and I for sure as hell don't wanna do that!
You are rooted, so grab Titanium Backup, and use it. Just don't backup up system data. App data is fine (at least it always has been on AT&T).
I haven't seen a ROM yet that is stable enough to flash, IMHO. Give it a couple of weeks. I ran AOKP on my GS2 for a long time, and am looking forward to it here.
Sent from my SCH-I545 using xda premium
If I was you man , I wouldnt never install a rom without a full wipe. That will keep you from running into problems. I know that from experience. Like Sbreen say, no wipe , no gripe
DroidHead214 said:
If I was you man , I wouldnt never install a rom without a full wipe. That will keep you from running into problems. I know that from experience. Like Sbreen say, no wipe , no gripe
Click to expand...
Click to collapse
Very well then, I guess a wipe it is.
Now, let me get this straight. I rooted my phone. I have TWRP Custom Recovery on my phone, and I have backed up the thing in the recovery menu to my micro SD card. I also Titanium Backup'd my system with apps and whatnot. So when I decide to flash my phone to a new ROM, I'd first wipe the data, factory reset, and wipe the dalvik cache, then flash it, do the setup garbage, and then from there, redownload Titanium Backup and restore whatever I want to restore, correct?
Ryukouki said:
Very well then, I guess a wipe it is.
Now, let me get this straight. I rooted my phone. I have TWRP Custom Recovery on my phone, and I have backed up the thing in the recovery menu to my micro SD card. I also Titanium Backup'd my system with apps and whatnot. So when I decide to flash my phone to a new ROM, I'd first wipe the data, factory reset, and wipe the dalvik cache, then flash it, do the setup garbage, and then from there, redownload Titanium Backup and restore whatever I want to restore, correct?
Click to expand...
Click to collapse
You got it! However the "factory reset" option in TWRP actually wipes data/cache/dalvik, I believe. (It tells you at the top of the screen what its going to wipe) Once you got your new rom you're all set to start restoring your apps with TB and enjoy the smoothness. After the setup process when your phone goes to the home screen, it's a good idea to let it sit for 5 to 10 minutes. (some developers advise this)
whiskerz said:
You got it! However, the "factory reset" option in TWRP actually wipes data/cache/dalvik I believe. (It tells you at the top of the screen what its going to wipe) Once you got your new rom you're all set to start restoring your apps with TB and enjoying the smoothness
Click to expand...
Click to collapse
I'll try it either tomorrow...or, later in the week if my courage decides to run away. Now, in the worst case scenario, let's say I completely screw up and get stuck with a bootloop or, I just completely hate the ROM itself. To restore to my current configuration do I just go back to TWRP and hit restore, and it basically reverts itself? I'm so sorry if I'm asking really stupid questions, I just REALLY want to do it right, and not have any hassles whatsoever. I am extremely careful and I really want to feel comfortable doing this.
Some guides I see mentioned backing up the IMEI information on the phone. Do I really need to do that, or is that all automated and I shouldn't run into issues? And is there a GApps.zip file thingy that I need to download for the "stock" applications? But wait a second, TB should take care of all of that correct?
Ryukouki said:
I'll try it either tomorrow...or, later in the week if my courage decides to run away. Now, in the worst case scenario, let's say I completely screw up and get stuck with a bootloop or, I just completely hate the ROM itself. To restore to my current configuration do I just go back to TWRP and hit restore, and it basically reverts itself? I'm so sorry if I'm asking really stupid questions, I just REALLY want to do it right, and not have any hassles whatsoever. I am extremely careful and I really want to feel comfortable doing this.
Some guides I see mentioned backing up the IMEI information on the phone. Do I really need to do that, or is that all automated and I shouldn't run into issues? And is there a GApps.zip file thingy that I need to download for the "stock" applications? But wait a second, TB should take care of all of that correct?
Click to expand...
Click to collapse
Yes, if your phone goes into a bootloop or you absolutely hate the rom, then pull the battery and boot into recovery. (If you just hate the rom no need to pull battery just power off)Make sure you have a backup of your system created within TWRP with the "backup" option. If you have a backup in TWRP you would just hit the "Restore" button and find your system backup and wait for it to restore. I've never heard anything about backing up IMEI info, you will probably not run into any issues. I've flashed tons and tons of roms on numerous devices and have NEVER had to do any of that. Gapps (google apps) are ONLY needed when you're going to run an AOSP rom. That means when the rom doesn't have the touchwiz skin over top of it. AOSP roms are pure vanilla android and have zero touchwiz features. You can find the touchwiz based roms in the "Android development" section while the AOSP roms are found in the "Original development" section. Also, it's fine to ask questions. That's how you learn!
whiskerz said:
Yes, if your phone goes into a bootloop or you absolutely hate the rom, then pull the battery and boot into recovery. (If you just hate the rom no need to pull battery just power off)Make sure you have a backup of your system created within TWRP with the "backup" option. If you have a backup in TWRP you would just hit the "Restore" button and find your system backup and wait for it to restore. I've never heard anything about backing up IMEI info, you will probably not run into any issues. I've flashed tons and tons of roms on numerous devices and have NEVER had to do any of that. Gapps (google apps) are ONLY needed when you're going to run an AOSP rom. That means when the rom doesn't have the touchwiz skin over top of it. AOSP roms are pure vanilla android and have zero touchwiz features. You can find the touchwiz based roms in the "Android development" section while the AOSP roms are found in the "Original development" section. Also, it's fine to ask questions. That's how you learn!
Click to expand...
Click to collapse
Awesome. Phew, I was like what why do I need to backup my IMEI information? I'm planning on installing Hyperdrive, is that a touchwiz based rom by any chance? And hah, yeah I know, I usually have really meticulous instructions for myself when I flash video game consoles, so I know the routine like the back of my hand.
Ryukouki said:
Awesome. Phew, I was like what why do I need to backup my IMEI information? I'm planning on installing Hyperdrive, is that a touchwiz based rom by any chance? And hah, yeah I know, I usually have really meticulous instructions for myself when I flash video game consoles, so I know the routine like the back of my hand.
Click to expand...
Click to collapse
Yes, Hyperdrive is a touchwiz based rom! The file is going to be a little over a 1gig, and already includes all of the apps you'll need.(Don't flash Gaaps) I'm heading off XDA for the night if you have anymore questions/concerns feel free to PM me and I'll try to help
whiskerz said:
Yes, Hyperdrive is a touchwiz based rom! The file is going to be a little over a 1gig, and already includes all of the apps you'll need.(Don't flash Gaaps) I'm heading off XDA for the night if you have anymore questions/concerns feel free to PM me and I'll try to help
Click to expand...
Click to collapse
Oh good! And at least my internet is reasonable now, so 1GB shouldn't be too bad. ;D I should head off too, its a bit late over here. Thanks for your help, you've answered a lot of my concerns!
Please read forum rules before posting
Questions and help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
All ROMs are the best and data wipes are always recommended
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
DeadlySin9 said:
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
Click to expand...
Click to collapse
Thank you for the information.
remainnameless said:
Thank you for the information.
Click to expand...
Click to collapse
Just make sure you have the Odin tar file for your phone just in case something goes wrong. Me and a few others ran into some issues messing with the stock slot. Good idea to have that anyways.
Sent from my SCH-I545 using Tapatalk
Just in case someone comes across this in the future:
Everything worked as planned. No issues to report.
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Click to expand...
Click to collapse
And yet people are wiping and flashing to stock fine?
Cool, I will try that
Sent from my SCH-I545 using XDA Premium HD app
DaGamer12345 said:
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
And yet people are wiping and flashing to stock fine?
Click to expand...
Click to collapse
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
reason why its called safestrap...and has saved me many times able to get back to my stock rom slot...but we all have our own levels of risk but hashcode made safestrap the way he did for a reason.
I run 3 roms on my S4 and have no issues with memory limitations
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
DaGamer12345 said:
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
Click to expand...
Click to collapse
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
k1mu said:
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
Click to expand...
Click to collapse
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
DaGamer12345 said:
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
Click to expand...
Click to collapse
Whew. I thought "Oh I remember you" was going to be followed by ".. you're that jerk that... " :laugh:
Have a good weekend.
remainnameless said:
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
Click to expand...
Click to collapse
I just installed hyperdrive to the stock slot and everything works perfect.
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
You should get it. But if any system files are changed by root, the OTA will not install. Otherwise, you should be good to go.
BTW, the Dev Edition 4.4.3 ROM is already posted in Development.
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
Make sure you restore all the bloatware as well or it won't update. I found this out with the last update. I would hold off on the update until you know it's safe to proceed without losing root unless you want to confirm it first for us. [emoji16]
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
volcalstone said:
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
Click to expand...
Click to collapse
redpoint73 said:
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
Click to expand...
Click to collapse
I got this nandroid (1.12.502.18 - TWRP 2.6.3.3 Thanks to Wonders_Never_Cease) from http://forum.xda-developers.com/showthread.php?t=2701376 and tried to restore, it ends abruptly leaving wifi and boot screen broken. Phone still boots in ARHD 10.1 but doesn' work perfectly. I put the folder from rar file under TWRP Backup folder and it picked up fine but won't restore. Maybe because I have TWRP 2.7.1.0?
I just picked up the phone and it is S-ON with bootloader unlocked/tempered. I'm trying to get back to stock till we have RUU to convert it to DE eventually like the M7.
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested. I also tried the HBOOT no PC required version of RUU but it would end abruptly at parsing. Maybe because I'm S-ON? I checked the MID and CID, they are both AT&T stock.
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
noobsquared said:
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested.
Click to expand...
Click to collapse
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
redpoint73 said:
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
Click to expand...
Click to collapse
Thanks for the links and everything man but the whole reason I'm trying to go back to completely stock is that I feel there is something wrong with my phone or maybe this is normal for M8. When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone. Tap on restart and it took a minute. First boot took well over 5 minutes. Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own. I may try the full AT&T 4.4.3 ROM since it's very close to stock. If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
noobsquared said:
When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone.
Click to expand...
Click to collapse
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
noobsquared said:
First boot took well over 5 minutes.
Click to expand...
Click to collapse
Totally normal on the first boot after any ROM flash.
noobsquared said:
Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own.
Click to expand...
Click to collapse
Ummm, not sure what is being said here "pimp on it's own". I'm guessing a typo or darned auto correct!
noobsquared said:
If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
Click to expand...
Click to collapse
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
redpoint73 said:
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
Click to expand...
Click to collapse
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on. I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
I will try to update the firmware and try to get on that AT&T Rom bandwagon to see how it goes. Thanks for all your help and input. I wish it wasn't so complicated with M8. M7 was so easy to mess with or maybe I got used to that lol
noobsquared said:
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
Click to expand...
Click to collapse
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
noobsquared said:
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on.
Click to expand...
Click to collapse
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
noobsquared said:
I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
Click to expand...
Click to collapse
FYI, as long as you are a current account holder, AT&T doesn't give a darn what you change in software, they will still honor the warranty if there is a hardware issue.
redpoint73 said:
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
Click to expand...
Click to collapse
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
Just an FYI- the black screen is a common problem with aroma installers and is well known.. All the other issues? I haven't a clue.
Hello!
I'm using 2.22 WWE version stock rom with 4.4.3, but I have long boots of device with old AT&T firmware.
Is there any way to update firmware?
I'm s-on, and firewater doesn't works.
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Thanks guys for all the help and support. I messed with the phone quite a bit and tried quite a few things and all the posts here help me learn a lot too. I was able to go all stock after s-off using that RUU method. I tried a couple other roms and finally back to dev edition stock for now. Was able to convert completely to stock with all the info and so far so good.
Once again, thanks a bunch everyone
Sent from my HTC One_M8 using XDA Free mobile app
iArtisan said:
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Click to expand...
Click to collapse
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
cachookaman said:
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
I had to do the same thing but given that what a pain it is without s-off, I'm not complaining. $25 is a small fee to pay for the peace of mind that you ha e almost full control of the device now.
Sent from my HTC One_M8 using XDA Free mobile app
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I downloaded 5.0. Was NOT satisfied and put KitKat back on. No problems doing that at all but I an NOT rooted.
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
elesbb said:
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
Click to expand...
Click to collapse
Yeah I avoided lollipop all together. People seem to be having too many problems with it.I installed NK2 via Odin and now rooted/exposed. Runs smooth and I can flash other Roms.
But I do have this one issue. My auto rotation rodent seem to be working I tried everything I can think of. At first boot it works for 10 minutes or 5 sometimes. Than it shuts down completely. Accelerometer isn't working either. No temple run movement or asphalt 8 (sucks). I did sensor firmwate update and ran samsung diagnostic. The sensor seem to be at 0,0 on x and y axis. At first boot they work fine though. Any help please. I even tried different kernel and software Roms to no Vail. And I don't think it's hardware cause it works for brief moments.
Sent from my SM-G900T using XDA Free mobile app
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
tri0xinn said:
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
Click to expand...
Click to collapse
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Did the trick, thanks!
muniz_ri said:
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Click to expand...
Click to collapse
Does downgrading like this trips Knox?
Thanks
chiquito3 said:
Does downgrading like this trips Knox?
Thanks
Click to expand...
Click to collapse
I downgraded my wife's phone using the official 4.4.2 firmware from sammobile, and it did NOT trip knox.