Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
Related
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
So, I am new to this site and to the android community. I apologize if I sound stupid to any of you but if you aren't going to help I'd appreciate it if you just ignored me.
Anyway, I got my Atrix a couple days ago on AT&T and started learning about rooting and such. Everything on it is still stock, last night I upgraded to Gingerbread from Froyo and I'd just like to know if there's any specific rooting program, method I can use right now for 4.5.91 Also, when I upgraded I lost my music player widget, is there I can get it back without going back to Froyo?
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
will there be any severe consequences if I screw up?
Use gingerbreak.
Sent from my MB860 using XDA App
TheToiletSpaula said:
Use gingerbreak.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I've read that gingerbreak doesn't work with this version. I'll look it up though.
phobos512 said:
follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my mb860 using xda app
Click to expand...
Click to collapse
^^^^^ only way to root gb and probably the best way if there are other methods
savier420 said:
^^^^^ only way to root gb and probably the best way if there are other methods
Click to expand...
Click to collapse
cool, just one question. Am I supposed to have the device connected to my computer the whole time? and if not between which steps should I connect/ disconnect it? also, when I put the root.img in the C: folder, do I put the zip file or just the .img inside of it?
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
PSY0NIC said:
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
Click to expand...
Click to collapse
Since this is the 1st time I've seen some one say it this way....
If you are just trying to "root" your phone only, YES, this is the best method.
Brand new phone, all stock... just want root.... use gingerbreak?
Sent from my MB860 using XDA Premium App
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
hambone123 said:
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
Click to expand...
Click to collapse
I'm about to try it but I'm still confused about a few things like when exactly to connect or disconnect my phone and what to do after I've entered all the commands on my computer, will it install by itself? This is my first time rooting a phone, and my first time even owning an android so I want to make sure I know exactly what I'm doing
I hear you man, it's nerve wracking to worry that you're going to brick your phone. I did the gingerbreak on the last release and it worked perfectly. I'm sure this method will work fine as well, as you said I just want to be sure I'm doing the right thing for my goal: stock phone/downloaded updates/rooted. Best of luck, and thanks to anyone who gives us noobs some more reassurance.
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got, before i updated to the OTA GB i had BL unlocked and rooted, just flashed back to 1.2.6 to be rid of root and unlocked BL, then just went throught the OTA updates to get to GB and im loving it, dont really care to flash any other custom roms, BUT BEWARE DOING THE OTA TO GB AND UNLOCKING THE BL THEN TRYIN TO FLASH BACK TO A STOCK ROM WILL HARD BRICK SO DO YOUR RESEARCH so if u dont want a hard bricked phone dont do the ota stick to custom roms and ignore all OTA'S
so I got through the fastboot reboot command, phone booted back up automatically, then put the phone into debug. Then typed in the adb shell code and said the specified path could not be found.
Now I was still in the command prompt that said the c:/root
What did I do wrong?
So, adb says it is a bad path?? Do this instead..it is easier and it works -- I did it this way last night!
After "moto-fastboot reboot", once your phone has completely rebooted, go to the Android Market and download and install "Terminal Emulator." Once it is instslled and you have opened it, enter the EXACT SAME commands that you were going to type into the Adb Shell..once again, type in the commands VERBATIM. After the last command, there should be a message saying (in terminal emulator) that it was successful! Congrats, you have achieved root access on the AT&T issued stock Gingerbread 2.3.4 build! I hope it works for you!
~Eric
savier420 said:
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got.
Click to expand...
Click to collapse
I'm very vanilla. I root pretty much entirely for free wireless tethering and being able to delete bloatware.
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
aroca1978 said:
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
Click to expand...
Click to collapse
Updating to GB won't brick your phone. After updating to GB you can't down grade to older OS (like the one your on right now) that would brick your phone. So as long as you don't plan on going back to a past OS version (and I don't know why anyone would) you'll have no problems at all. As for Rooting >follow this link< and follow the instructions there after you update to GB. It works perfectly, you don't have to unlock your BL or anything else like that to just have Root on GB. Hope this helps.
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
For Questions about BL Unlocking
aroca1978 said:
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
Click to expand...
Click to collapse
Click on the link below, that thread will give you the answers and files your looking for.
> Click Here <
Hey guys I have some questions regarding updating the firmware!
I am running the latest build of Viper rom (with the updated firmware) but before that i didn't actually update the firmware, I was told this could cause problems if you flash a rom with a new firmware. I haven't had any problems besides my camera not working (crashes when opened) but I'm hoping that updating the firmware properly can fix this.
So basically I'm wondering how can I update the firmware on my phone? I have hboot 1.4 on my phone, would simply flashing this zip:
http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
work? should I do a full system wipe then flash this? It wouldn't remove root or cause any other problems right?
Sorry, I know I'm a noob but I'd rather risk looking like a noob before attempting anything myself and screwing it up. I'm really hoping to get my camera working and I hope this can help.
Thanks a lot!
Bacardi222 said:
Hey guys I have some questions regarding updating the firmware!
I am running the latest build of Viper rom (with the updated firmware) but before that i didn't actually update the firmware, I was told this could cause problems if you flash a rom with a new firmware. I haven't had any problems besides my camera not working (crashes when opened) but I'm hoping that updating the firmware properly can fix this.
So basically I'm wondering how can I update the firmware on my phone? I have hboot 1.4 on my phone, would simply flashing this zip:
http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
work? should I do a full system wipe then flash this? It wouldn't remove root or cause any other problems right?
Sorry, I know I'm a noob but I'd rather risk looking like a noob before attempting anything myself and screwing it up. I'm really hoping to get my camera working and I hope this can help.
Thanks a lot!
Click to expand...
Click to collapse
FYI...you would update this via bootloader not recovery. I updated the firmware with no issues. Jut remember to delete the file after updating.
Should I do a full wipe before or after (or at all) updating the firmware?
Bacardi222 said:
Should I do a full wipe before or after (or at all) updating the firmware?
Click to expand...
Click to collapse
that is the zip I used and i'm also on viper's rom...
DON'T FLASH IT put it on your sd card and reboot into bootloader and it will pick it up and update, no wipe needed or at least I didn't...
oh, don't put it in any folders or anything, just the main part of your sd...
twister99403 said:
that is the zip I used and i'm also on viper's rom...
DON'T FLASH IT put it on your sd card and reboot into bootloader and it will pick it up and update, no wipe needed or at least I didn't...
oh, don't put it in any folders or anything, just the main part of your sd...
Click to expand...
Click to collapse
Thanks mate, doing that now, just needed a little reassurance! +thanks
Bacardi222 said:
Thanks mate, doing that now, just needed a little reassurance! +thanks
Click to expand...
Click to collapse
your welcome, I know it took me a while to finally take the plunge myself and a lot of reading lol
What does updating the firmware actually do for us? I'm also using newest ViperRom and everything is working pretty flawlessly. What would I gain by updating?
I would like to try this new radio update, but let's say its not as strong for me; would I be able to go back to the radio I have now? (0.97.00.0518)
Update
Hi, everyone. I have a rooted Evo3D running software ver 2.08.651.2 with HBOOT 1.4. I am not running any particular rom other than stock. Clicking on the link provided above, gave me Freeza's convenient all-in-one recent ota update. Just to confirm, all I need to do is put into root directory of my sd card and go into bootloader and it will automatically update? Would it update my HBOOT 1.4 to 1.5? Anything else I need to install? Thanks.
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
CavyS said:
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
Click to expand...
Click to collapse
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
scott500 said:
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
Click to expand...
Click to collapse
Yeah that might as well have been written in Arabic. I think that might be one of the methods I tried though?.. Except when I put the Nandroid backup in TWRP/backups then rebooted my phone into recovery the backup wasnt showing in there no matter what I did, and the other way just got an error.
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
CavyS said:
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
Click to expand...
Click to collapse
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
redpoint73 said:
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
Click to expand...
Click to collapse
Lol I know, idk why I have to have to OTA either. Its just an OCD thing. I think its because I know that what I'm getting from OTA is clean and is a 100% working squeaky clean release by Android. Opposed to a ROM that someones put together themselves. I'm sure there is nothing wrong with the ROM or that there is any kind of malware or viruses in it. But its just an OCD thing were I would never stop thinking about it. And first thing my phone crashes or runs into a bug regardless of the problem I would blame it on the ROM. Lol now I sound like a sociopath
CavyS said:
now I sound like a sociopath
Click to expand...
Click to collapse
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
redpoint73 said:
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
Click to expand...
Click to collapse
Quick question. I put the Nandroid backup in the TWRP/backups/ folder. It doesnt show up in "Restore" but it shows up in "Install" in TWRP Recovery. When I click on it in "Install" it asks me "Swipe to Confirm Flash" Is it okay to flash Nandroid backup from the "Install" location or does it have to be done through "Restore"?
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
twiggums said:
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I just updated with RUU, I'll re-root again once 4.4.4 gets pushed out.
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.