I hit the "OK" on the OTA box without thinking, and only realized my mistake when TWRP came up after it started it's process.
I can get all the way back into the Launcher, but after about 60 seconds is reboots.
I'm guessing all I need to to undo one thing, or maybe flash a new/stock bootloader, but I don't really know where to start. I am coming from Samsung phones, so the terminology is rather different with HTC.
I've already made a backup of boot, system, and data, from within TWRP and copied it off the phone. I also quickly moved the OTA zip off my phone as well in order to keep a copy of it. Lastly, I can boot into "Safe Mode" (which I discovered by accident) and it doesn't do the reboot thing.
Any help at all is appreciated.
Thank you.
EDIT: Success!
Turns out I needed to re-flash my SuperSU binary from TWRP. I re-flashed the version I had first which actually removed the SuperSU apk. I re-downloaded it from Play Store, then flashed the 2.01 update. Runs like a charm.
Thanks to everyone for the help.
Hi,if you already backup your ROM before OTA,just restore it
hdorius said:
Hi,if you already backup your ROM before OTA,just restore it
Click to expand...
Click to collapse
I only did the backup after I got into the reboot cycle.
I haven't tried restoring it, but I don't imagine that it will work.
Can u please post your cid?u can find the stock nandroid backup that linked at my signature
winnower said:
I only did the backup after I got into the reboot cycle.
I haven't tried restoring it, but I don't imagine that it will work.
Click to expand...
Click to collapse
No it will not work. Just delete the backup and save you the time and trouble messing with it. If you can grab a good backup from someone then you will be ok. Simply restore and all should be well. Then, make sure you remove your custom recovery prior to accepting the OTA.
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.
hdorius said:
Can u please post your cid?u can find the stock nandroid backup that linked at my signature
Click to expand...
Click to collapse
Ok, I need to do a bit of reading it seems.
I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.
Modding.MyMind said:
No it will not work. Just delete the backup and save you the time and trouble messing with it. If you can grab a good backup from someone then you will be ok. Simply restore and all should be well. Then, make sure you remove your custom recovery prior to accepting the OTA.
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.
Click to expand...
Click to collapse
Thanks, I kinda figured the backup wouldn't help.
I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
winnower said:
Ok, I need to do a bit of reading it seems.
I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.
Thanks, I kinda figured the backup wouldn't help.
I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
Click to expand...
Click to collapse
Just use the command "fastboot getvar all" it will read your CID and find the backup at Stock Nandroid Backup that match your phone and restore it
Edit: oops the thread that i linked is closed and all the links are removed
winnower said:
Ok, I need to do a bit of reading it seems.
I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.
Thanks, I kinda figured the backup wouldn't help.
I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
Click to expand...
Click to collapse
The recovery image is based for the new OTA. Won't necessarily be the same as what your device currently used but it should still work. If by any chance it does not then it is because of the Bootloader version you are currently running which is causing the problem. Which at that point you will need to grab the other stock recovery.img prior to the update.
---------- Post added at 09:56 AM ---------- Previous post was at 09:55 AM ----------
I don't have your device so I can't really provide any links to assist even further but I ca build you a foundation to go off of. The logic with this stuff is relatively universal across common android devices for the most part.
winnower said:
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
Click to expand...
Click to collapse
Since you have the OTA, can you put the details of android-info.txt that you have inside it ?? This will definitely help you to find the right recovery/backup.
Modding.MyMind said:
Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.
Click to expand...
Click to collapse
Have you actually seen this done? AFAIK stock recovery is required to install OTA; but perhaps I'm mistaken. In any case, its far easier to restore stock recovery if the intent is to install OTA. However, the current installed ROM must also have no system files altered, as this is also a requirement for OTA installation.
Another (probably easiest) way out of this loop would be to mount the memory, find the OTA file and delete it. The phone should then stop trying to find stock recovery to install the OTA (which is the cause of the bootloop).
@redpoint73, that is a valid question to ask. I have not seen any guides made available to the public however, I can vouch it works. I once did it myself many many many months ago once I did some extensive studies on how an OTA was applied. Though, I won't hesitate to mention that it's a tedious process and I wouldn't recommend it less it were your only absolute option since there are so many easier methods to use.
Modding.MyMind said:
@redpoint73, that is a valid question to ask. I have not seen any guides made available to the public however, I can vouch it works. I once did it myself many many many months ago once I did some extensive studies on how an OTA was applied. Though, I won't hesitate to mention that it's a tedious process and I wouldn't recommend it less it were your only absolute option since there are so many easier methods to use.
Click to expand...
Click to collapse
Good to know, thanks for the explanation. Interesting that custom recovery will actually work (technically) with an OTA, that its just security checks that keep if from happening.
As you mentioned, there are many much easier options to recovery; so what you mentioned is just a method of "last resort".
ckpv5 said:
Since you have the OTA, can you put the details of android-info.txt that you have inside it ?? This will definitely help you to find the right recovery/backup.
Click to expand...
Click to collapse
OTAfile/firmware.xip/android-info.txt:
modelid: 0P6B16000
cidnum: BM___001
cidnum: SASKT001
mainver: 2.23.666.2
btype:1
aareport:1
hbootpreupdate:12
hdorius said:
Just use the command "fastboot getvar all" it will read your CID and find the backup at Stock Nandroid Backup that match your phone and restore it
Edit: oops the thread that i linked is closed and all the links are removed
Click to expand...
Click to collapse
Ok, downloaded fastboot-win.zip from HTC's dev site.
C:\Android\m8>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
So, if those links are offline, do you have another source or just use the one I got with the OTA?
Did you try to just find the OTA file and delete it, as I previously suggested? This should get the bootloop to stop.
redpoint73 said:
Did you try to just find the OTA file and delete it, as I previously suggested? This should get the bootloop to stop.
Click to expand...
Click to collapse
Yes, the OTA is no longer on the phone.
It's not really "bootlooping", it boots normally into the Sense launcher, then after about a minute it restarts. It's not stuck on the HTC logo or anything; it's more like a restart-cycle.
Were you on a stock ROM, or custom before this OTA mess started? My recommendation would just be to pick a custom ROM of your choice on the phone (either via adb push or on the removable SD) and flash it in TWRP and forget this OTA business. Making it more complicated than it needs to be, and OTAs don't really have any business on modded phones anyway, for the most part.
redpoint73 said:
Were you on a stock ROM, or custom before this OTA mess started? My recommendation would just be to pick a custom ROM of your choice on the phone (either via adb push or on the removable SD) and flash it in TWRP and forget this OTA business. Making it more complicated than it needs to be, and OTAs don't really have any business on modded phones anyway, for the most part.
Click to expand...
Click to collapse
I was on stock Sense6. I had previously unlocked and loaded TWRP since I assumed I'd switch ROMs very shortly after getting the phone. I was coming from Samsung's world where running my own ROM was mandatory since TouchWiz was so awful.
The only thing keeping me from flashing a custom ROM right now is my data/apps. In my sleep deprived state, I didn't think to make a backup (or to not accept the OTA in the first place). If I can flash a customized Sense6 ROM and keep my apps/data then I will.
The phone isn't really working for more than a minute or so. So I'd just do a wipe and install a custom ROM. Something is broken now, so a clean slate is probably your best bet.
Yeah, I'm just trying a few last things.
I tried flashing the newest TWRP and the stock recovery.img I got with the OTA; no luck.
I still have the full OTA zip though... Is there any way for me to adb push that file on the /sdcard/ to force it to complete the update? That way I can just re-flash TWRP and SuperSu and keep my data.
Thanks for all the help.
Related
Go here for a much better proceedure:
http://androidforums.com/incredible...ng-nov-ota-rooted-incredible.html#post1876792
dsb9938 said:
Rooted Inc, otherwise factory ROM. S-OFF in effect.
If I flash a factory recovery, will the OTA update take?
Can I not simply reflash ClockWork after the update?
Thanks guys.
Click to expand...
Click to collapse
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Fretless said:
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Click to expand...
Click to collapse
What if I'm rooted without stock recovery?
thevoiceless said:
What if I'm rooted without stock recovery?
Click to expand...
Click to collapse
When you get the update nag, you ignore it, flash the stock recovery, which I am in process of getting now, then apply the patch, then reflash Clockwork.
Fretless said:
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Click to expand...
Click to collapse
Thanks, now to get the stock recovery from the RUU. Wee Haw!!!!
dsb9938 said:
When you get the update nag, you ignore it, flash the stock recovery, which I am in process of getting now, then apply the patch, then reflash Clockwork.
Click to expand...
Click to collapse
I'm still pretty new to this, how should I go about getting the stock recovery and flashing it? All I've done is use Unrevoked and Unrevoked Forever, then install ClockworkMod via Rom Manager, so pretty much everything has been done for me :/
thevoiceless said:
I'm still pretty new to this, how should I go about getting the stock recovery and flashing it? All I've done is use Unrevoked and Unrevoked Forever, then install ClockworkMod via Rom Manager, so pretty much everything has been done for me :/
Click to expand...
Click to collapse
I've asked in a couple places for the stock recovery. If/when I get it I will post a short how to.
I just don't want to lose everything on my phone to get this update.
I did a NAND backup and installed the update manually and there are several improvements I would like to have, such as significantly reduced charging time. But right now, without a custom ROM, the only way to get it is the RUU, and that wipes the phone.
Dennis
dsb9938 said:
I've asked in a couple places for the stock recovery. If/when I get it I will post a short how to.
I just don't want to lose everything on my phone to get this update.
I did a NAND backup and installed the update manually and there are several improvements I would like to have, such as significantly reduced charging time. But right now, without a custom ROM, the only way to get it is the RUU, and that wipes the phone.
Dennis
Click to expand...
Click to collapse
Awesome! Keep me updated
Please Hold.
dsb9938 said:
Please Hold.
Click to expand...
Click to collapse
What do you mean?
Go here for a much better proceedure:
http://androidforums.com/incredible...ng-nov-ota-rooted-incredible.html#post1876792
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
JDubbz said:
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
Click to expand...
Click to collapse
Having this issue with somebody else. I'm not sure if you can name it PB31IMG.zip or not, but you can try. Worst care, it doesn't load that way either.
I'm helping somebody else with the same issue right now, but his phone is totally hosed up, so I'm taking him back to stock 2.2 first. He has a good Titanium backup, so he won't lose anything.
If anybody else knows why the loader might ignore an update.zip please let me know.
JDubbz said:
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
Click to expand...
Click to collapse
Okay, I have confirmed that you may perform "install sd/update.zip" from ROM Manager. It does work.
I'm still confused; do I have to have the stock recovery to do this?
I am not sure of these steps because I have read the threads from here and the post you put on Android forums as well and both threads are mentioning some issues.
Some posts state payload-update is unneccesary.
Some posts state that these steps are failing.
The post I am most concerned about states that "Rooted STOCK ONLY" means you can't have removed any bloatware either before doing this update. I have several apps removed, do I have to restore them before I take these steps?
Also not sure why folks are asking if they must have stock recovery. The instructions don't say anything about that.
I have noticed that the nagging has stoped on my dinc however if I go to the about update section in setup I find it states that the update has been successfully downloaded and is ready to install. Will this try to install the next time I boot the phone or is OK to boot?
Edit: Forgot to mention Some posts state that the process fails and you have to wait a few hours to continue, that's confusing and not in the instructions.
In summary
1) Do you have to re-install bloatware to make these steps work?
2) Is payload-update really necessary? What does each install in these steps do?
3) Does the process fail at some point if you don't allow the device to sit for a while, if so what step should you let it sit? It would be nice if someone understood this part also, anyone have a possible reason for this requirement?
I was asking if stock recovery is required because I've been told that OTAs won't install correctly if you don't. I was wondering if that still applied.
I got the update notification tonight and I clicked for it to install, and it counted down from ten seconds and said it was going to reboot and install updates, but it never did reboot. I'm guessing this is because I have unrevoked recovery? My gf's non rooted phone did get the update tonight as well, and hers installed without a hitch.
Sent from my HTC Incredible «•» Rooted/S-off/Froyo 2.2 «•»
Rooted, Stock 2.2, S-off, Clockwork; some bloatware removed
Install initiated through clockwork halted on vznav.apk, so I'm guessing it needs the original bloatware. I know that I should have backed it up but I guess my hatred of VZ pushiness got the better of me. Anyone have a work-around?
BrooklynAlex said:
Rooted, Stock 2.2, S-off, Clockwork; some bloatware removed
Install initiated through clockwork halted on vznav.apk, so I'm guessing it needs the original bloatware. I know that I should have backed it up but I guess my hatred of VZ pushiness got the better of me. Anyone have a work-around?
Click to expand...
Click to collapse
I guess we need someone to share the bloat apk's; I removed some of them without backing up, too :/
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
I also am curious about this topic
snap213 said:
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
Click to expand...
Click to collapse
1. Download the stock recovery for your device from the recovery thread
2. Flash it through fastboot (as you did TWRP)
3. Apply the OTA
4. Reflash TWRP
5. Re-root the phone
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
snap213 said:
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
Click to expand...
Click to collapse
Not stock rom...stock recovery
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
spikeydoo2006 said:
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376 (under the nandroid backups section)
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
snap213 said:
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
Click to expand...
Click to collapse
here is my recovery backup from 1.54.707.7. https://www.dropbox.com/s/p2ht9dxns3ggcyk/recovery.img
Can you backup your radio.img for me? I forgot to backup when i convert my phone to GPE.
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Yes, you can! I did it exactly that way - and after OTA update reflashed TWRP and rerouted that way. Its a 4 minute job.
snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Learn to do it yourself, relying on toolkits is a false economy as if anything goes wrong you'll have no idea how to fix it...
EddyOS said:
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
Click to expand...
Click to collapse
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
anjaan said:
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
Click to expand...
Click to collapse
The OTA requires a 100% stock running Android build, so if you have removed any system apps it will just fail and reboot to the ROM you're running at the moment (so you should be safe). Basically, if the /system partition on the phone is ANY way different from how it was when you first bought it the OTA will fail
For example, other than S-OFF my phone is exactly how I received it, therefore the new OTA update installed successfully. If I had removed one system app (e.g. Hangouts), it would fail as it's looking for it and if it can't find it it'll just reboot
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
snap213 said:
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
Click to expand...
Click to collapse
If you're now on 1.54.401.10, you can manually extract it from the firmware package I uploaded HERE
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Black Antitoon said:
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Click to expand...
Click to collapse
I can see the apps that were removed during unlocking still working if installed as user apps as they're still on the /data partition. If they weren't there at all then it'd probably fail. Surprised that it worked with Xposed installed, but that's also a user app so it could very well work - logically it makes sense.
As a rule of thumb I'd only apply an OTA on a 100% stock system, that way you know it'll all be fine
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Lanthanide said:
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Click to expand...
Click to collapse
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
bruce7373 said:
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
Click to expand...
Click to collapse
It doesn't matter in general. But it matters in case that you used S-Off to uninstall system APPs Thus an OTA wouldn't succeed.
That's what I wanted to say in my post above
Sent from my HTC One_M8 using XDA Free mobile app
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
Click to expand...
Click to collapse
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
HTCNerdYoda said:
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
Click to expand...
Click to collapse
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
is the s-off really worth it?
Yuskow said:
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
Click to expand...
Click to collapse
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Yuskow said:
is the s-off really worth it?
Click to expand...
Click to collapse
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Click to expand...
Click to collapse
I had the Vivid as well and ended up with a 4.4.2 ROM which seemed to be the most current that was available at the time, but can't remember the name or the dev.
As for the M8, I've been on ARHD almost exclusively and think it's one of the best ROMs out there. I've tried Viper, MaximusHD, Renovate also, but always come back to ARHD.
http://forum.xda-developers.com/showthread.php?t=2694917
---------- Post added at 07:40 AM ---------- Previous post was at 07:33 AM ----------
HTCNerdYoda said:
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Click to expand...
Click to collapse
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
bruce7373 said:
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
Click to expand...
Click to collapse
That's a really good question. Regarding ViperOne I could tell that running 1.8.0 (which was on 1.54.xx base) with 2.22.xxx FW worked flawlessly. So I would guess this should work just fine.
At least it's worth a try. Maybe better ask in the ROM thread.
Used arhd on my vivid for a bit. Must say it was an ok rom but lots of issues in general with all new roms on the vivid. Hardware too outdated. Maybe I'll give it a shot. Really leaning to a de-senced one.
HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
Ok, that's encouraging.
My CID is HTC__621 although I don't think I need that for just flashing back to stock recovery. My version is 1.54.709.12, so I downloaded the matching recovery from here http://forum.xda-developers.com/showthread.php?t=2701376 and flashed it. I confirmed that the stock recovery was installed by booting to it and getting the red triangle etc.
Then I downloaded the OTA upgrade and told it to install. I didn't watch the installation progress, but eventually it went to the red triangle screen and finally rebooted. But I'm still on 1.54.709.12, so I take that to mean the OTA failed. When I go to system update, it checks and finds one available and offers to download it again, which I haven't done.
I'm wondering if 'disabling' the weibo program could have caused the update to fail? Or possibly I *did* actually uninstall a stock program or two that I mentioned at #6 and that's what's preventing the update?
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Lanthanide said:
Ok, that's encouraging.
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Click to expand...
Click to collapse
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
HTCNerdYoda said:
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
Click to expand...
Click to collapse
Ok, so I put on a stock nadroid backup for HTC__621, changed to stock recovery, but the OTA update is still failing at around the 30% mark.
Actually I've just noticed that the stock ROM I put on doesn't have the calc or flashlight apps, but when I originally bought the phone they were on there. I had subsequently installed them using the apps on this thread here: http://forum.xda-developers.com/showthread.php?t=2699906
But maybe that is what is preventing me from doing the OTA now?
Edit: Right, so doing some more reading, it seems that HTC included these 'stock' apps in the /data directory instead of /system, so when doing the HTCDev install, they get wiped. But there was a note in that thread saying that for the One M7, they would actually do a hash of those apps too and if they weren't there the update would fail.
Someone linked to this thread http://forum.xda-developers.com/showthread.php?t=2703759 which says the APKs in the first one were from the M7, and these are from M8, and it also included another one called Seven Digital (yet another bloatware app I don't care about, hence why I didn't notice it was gone). Anyway I installed those 3 apps, but the OTA update still fails at around the 30% mark. I notice that the thread says preload APKs for 1.54.401.5, but my phone is running 1.54.709.12, so if they really are doing hashing for all of these apps, the update might be expectly a slightly different version and therefore fail the hash check?
Resolved!
Right, posting as new post because I solved it!
I searched through the collection thread and luckily found someone else who has HTC__621 who wanted to do the 4.4.3 upgrade as well. ckpv5 stepped in to lend a hand with this post: http://forum.xda-developers.com/showpost.php?p=54598052&postcount=1514
The TWRP stock ROM he posted there includes the flashlight and calculator app, as well as another one that looks like it was missing - WeChat. So now the OTA update has applied as expected. :highfive
I'll suggest Mr Hofs remove the existing nandroid backup for HTC__621 that he has there because it isn't complete.
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Edit: More findings. In installing Xposed Framework on my phone, it can't do the 'classical' install because of S-on, instead it flashes it through recovery. So I suspect this could have been preventing the OTA update as well.
Lanthanide said:
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Click to expand...
Click to collapse
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
ckpv5 said:
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
Click to expand...
Click to collapse
Ok, at least there's an explanation for what happened, but I didn't at any point explicitly lock the bootloader. All I did was:
1. Flash TWRP recovery
2. Flash the ROM you provided
3. Boot the phone, going through the setup stuff to configure wifi etc
4. Booted to fastboot and flashed to stock recovery
5. Rebooted phone, downloaded and installed OTA update
6. Booted to fastboot and re-flashed TWRP, ran nandroid backup and then installed superSU when offered
At what point would the locking of the bootloader have occurred?
Lanthanide said:
At what point would the locking of the bootloader have occurred?
Click to expand...
Click to collapse
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
ckpv5 said:
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
Click to expand...
Click to collapse
Ok, well like I said, I didn't explicitly choose the lock the bootloader at any point, and the nandroid backup that you created *did* have the extra apps in there (I confirmed their presence at step 3 in my sequence).
Note that I'm not trying to be argumentative, just explaining my experience in case this might help others in the future.
Hello friends, I just got a new refurbished rogers(canada) HTC M8 GSM phone.Its totally stock at this moment and would like to do sim unlock,s-off and boot loader unlock. But before i would like to get full back up of my stock.Few questions:
1.How can i do full complete backup of my stock phone in case in future i need to revert back?
2. what are the steps to do s-off,sim unlock and bootloader unlock?
Right now phone says:
Android version 4.4.3
HTC sence version 6.0
software number 2.23.631.2
HTC SDK API level 6.25
kernel version
3.4.0--g523xxxxxx
baseband version
1.19.2133xxxxxxxx
build number
2.23.631.xxxxxxxrelease-keys
Thanks in advance...
Go to HTCDev.com to unlock the bootloader. The process is self-explanatory (just follow the website instructions). There is a writeup on the following guide, if you need help. But honestly, if you can follow instruction, the process is self-explanatory as I mentioned: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Then, to backup the stock ROM and recovery, follow the instructions listed on the following thread under "How do i backup the stock HTC recovery?" : http://forum.xda-developers.com/showthread.php?t=2701376
This process will boot custom recovery without actually flashing recovery it to the phone, allowing you to backup stock recovery as well as the stock ROM (if you flash custom recovery before doing this, stock recovery is over-written and therefore can't be backed up). Note that your version's stock ROM and recovery may already be uploaded to the above thread by another XDA user.
Then achieve root by your preferred method (flash custom recovery and flash SU/SuperSU, or use weaksauce, towelroot, etc.). Then use sunshine to achieve s-off (firewater s-off will likely not work, as it was patched some time ago): http://theroot.ninja/
Then after s-off, you can unlock SIM: http://forum.xda-developers.com/showthread.php?t=2708572
Thanks a lot redpont73 for your directions!!!Will follow your steps and let you know how things went..Thanks
Ok i unlocked my bootloader with htcdev.com and it says unlocked now.
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?please guide me.thanks
ninja_zx11 said:
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?
Click to expand...
Click to collapse
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
redpoint73 said:
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
Click to expand...
Click to collapse
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.Just trying to learn and don't want to brick my phone with any wrong move.thanks
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
ninja_zx11 said:
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
Click to expand...
Click to collapse
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
ninja_zx11 said:
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.
Click to expand...
Click to collapse
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
redpoint73 said:
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
Click to expand...
Click to collapse
Yes you are right...I will read more and i want to learn and will try to do it myself.If i will have some confusion, i will ask here.Looks like i need more reading.
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
ninja_zx11 said:
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
Click to expand...
Click to collapse
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
redpoint73 said:
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
Click to expand...
Click to collapse
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
BerndM14 said:
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
Click to expand...
Click to collapse
thanks BerndM14, i just copied supersu zip to internal storage as you said and installed it by booting into twrp from pc. and its done... thanks..
ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
Sounds like a brick in the making.
Make sure that you read and understand what you are about to do before you do it.
A nandroid won't always help you.
If I may make a suggestion, don't go S-Off.
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
ninja_zx11 said:
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
Click to expand...
Click to collapse
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
redpoint73 said:
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
Click to expand...
Click to collapse
thanks redpoint73 for giving me helping hand!! without your help i wouldn't have done it.....
Hi all, please correct me if I placed this at the wrong thread.
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it?
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so?
Can I flash back a lower version of ROM? For instance, 1.54.707.7
Thanks for helping in advance!
My responses below, in red font:
jkidz91 said:
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it? Totally normal, no need to worry.
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so? This is usually due to using an older version of TWRP (known bug). This number is useful for determining your current firmware version (hboot, radio, etc.) but you can also determine that by looking at the hboot number and radio numbers themselves
Can I flash back a lower version of ROM? For instance, 1.54.707.7 Yes. Usually, you want the ROM version (1.x, 2.x etc.) to correspond to your current firmware. But its usually been found that a higher number firmware will usually work with older (smaller number) ROMs
Click to expand...
Click to collapse
redpoint73 said:
My responses below, in red font:
Click to expand...
Click to collapse
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
jkidz91 said:
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
Click to expand...
Click to collapse
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
redpoint73 said:
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
Click to expand...
Click to collapse
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
jkidz91 said:
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
Click to expand...
Click to collapse
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
redpoint73 said:
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
Click to expand...
Click to collapse
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
jkidz91 said:
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
Click to expand...
Click to collapse
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
redpoint73 said:
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
Click to expand...
Click to collapse
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
jkidz91 said:
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave
Click to expand...
Click to collapse
Meaning you updated by RUU?
jkidz91 said:
as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
Click to expand...
Click to collapse
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
redpoint73 said:
Meaning you updated by RUU?
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
Click to expand...
Click to collapse
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
jkidz91 said:
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
Click to expand...
Click to collapse
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
redpoint73 said:
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
Click to expand...
Click to collapse
I need the Titanium backup to recover my apps and data ><
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
About the stock recovery, I am fully aware of this
I am really sorry if I keep causing trouble to you...I just want to double confirm...I have spent few days just to get my phone for working right...really exhausting to the mind ><
jkidz91 said:
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
Click to expand...
Click to collapse
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
jkidz91 said:
I am really sorry if I keep causing trouble to you...
Click to expand...
Click to collapse
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
redpoint73 said:
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
redpoint73 said:
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
jkidz91 said:
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
Click to expand...
Click to collapse
If the intent was to just backup a "stock ROM" than no need to backup user data.
If the intent is to make a recovery image, that you can just revert to and start using with no (or very little other actions) than backup data. But as you said, you can restore data (at least app data) with Titanium.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
jkidz91 said:
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
Click to expand...
Click to collapse
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
redpoint73 said:
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
Click to expand...
Click to collapse
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
jkidz91 said:
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
Click to expand...
Click to collapse
You can run the RUU until the cows come home, if you want.
redpoint73 said:
You can run the RUU until the cows come home, if you want.
Click to expand...
Click to collapse
What does that mean? >< i tried to do it...it failed...should I just download a stock 4.19.707.2 rom and flash it?