Database Users

[Q] OTA 2.2.1 update manually

I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!

remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
Call T-Mobile customer service and verify with them that the IMEI number they have in your account is the correct one. This is the number one reason for not getting the update. I had a phone for over a month and they never changed the IMIE # until I called. The IMEI is on your box or under your battery.

Please post questions in the Q&A section.

remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading This was on the same page you posted.... have you by chance read it?

I'd recomend using the force method...I spent almost three weeks waiting on it after being put on a "push list", verifying IMEI, and other things. Some phones "won't update" for whatever reason and they will eventually tell you to swap it. I did the manual update from the thread linked above without issue after T-Mo was unable to resolve my issue and I wasn't willing to swap for a potential refurb after having to pay full $450 retail price on the phone.

I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.

remijenkins said:
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
Click to expand...
Click to collapse
THE update is in the post... if you want to try and copy it to every folder on your phone fine... try it... but it is in that post
and if you want you could turn s-off to flash it then turn s-on when you're done... and you won't be rooted after the update applies so you won't have to unroot

If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?

remijenkins said:
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
Click to expand...
Click to collapse
there is more than one file posted there... The one named "PD15IMG.zip" is part of the update. It replaces the kernel and some other system files, but does not include the patches from the update, which is why wifi breaks. The one labeled The OTA is the full OTA pulled from a phone and the filename is "update.zip" I could not get the full update to flash with S-ON because it has to do some commands on the system to let it know it's going to flash becuase the phone temporarily disables the write through in place... (not sure if i explained that right). My solution is to flash the partial update which gets your kernel up to date then patch the kernel (turning s-off) and then flashing the entire update. If you're really against root you can undo all the root stuff and S-Off after the update hits... but what's wrong with root? You should still get new updates if you're still running stock, but are rooted. BUT, if you uninstall programs the updates will most likely not take (I recommend a nandroid be made before removing things so you can flash back to it get the update, make a new nandroid, then reremove software.)

Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.

remijenkins said:
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
Click to expand...
Click to collapse
Why the aversion to rooting? it's really not that hard and there are at least 4 or 5 of us in irc that will walk you through it

Rooting is nasty
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Flash PD15IMG-->temporary root-->permanent root (lot of jibberish)-->flash rest of update-->unroot
This is an intimidating process which is nowhere given in simple and complete steps but yet is often described as "simple" or "took minutes." Maybe for some, but the "simple" suckers in a lot of people who stumble along the way.
As I did; all I wanted was an unrooted phone with 2.2.1 and I had given TMo a couple of weeks to do it. A few hours into the process and a few steps beyond trashing WiFi I realized I didn't want a rooted phone and decided either to pay somebody who knows a lot more about this subject than I do to fix it or, preferably to convince TMo to give me a new one. So I went to sleep.
And guess what? At 6AM TMo said they wanted to do a firmware update, to which I agreed, and the legit OTA over-rode that damned PD15IMG and cajoled my WiFi back to life. And as far as I know Tmo doesn't have my IMEI either, because they say on their site they don't know what kind of phone I have.
And none of that snarky "if you don't know what we're talking about you shouldn't be here," either. If she didn't know she could get pregnant from it she shouldn't have done it. The whole rooting business is nasty: there are no simple comprehensive directions, there are too many ROMs and there is too little honest description of where they fail.
It would be nice also if Google would save up its incremental improvements and let them loose at longer intervals, as Apple does, to reduce the frustration of those interested in Being First. It would also be nice if the Google open system had required carriers to be able to absorb the latest updates within a fixed time, regardless of whatever crud they lay over the basic Android. The software may be "open" as far as Google and Tmo are concerned, but between TMo and me the relationship is different.

ecdy said:
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Click to expand...
Click to collapse
I'm sorry you had problems, but when doing anything that has a set of instructions it is wise to read the entire thing before starting. This will ensure you are fully prepared instead of lost in the sauce halfway through... Piss Poor Planning leads to Piss Poor Performance.

[Q] Can't update after deleting stock apps

I've been trying to update from 4.1.2 to 4.2.2, but I deleted some stock apps and now the update is failing. I've tried flashing it manually and OTA, and various other things, but nothing has helped so far. Has anyone else had this problem?

The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.

bftb0 said:
The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.
Click to expand...
Click to collapse
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.

wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
My post tells you that you have the wrong expectation about what OTAs are capable of... and that you are probably the 200'th dude to come in here and say
"Wahhh! The OTA doesn't work on my heavily modified stock ROM!".
If you want it to work without exerting any mental effort, return the /system, boot, and recovery partitions back to 100% pure stock corresponding to whatever release your original ROM was based upon, and run the update. Then re-flash your recovery and re-perform all your /system mods, starting with a flash of the same root kit you started with.
Note that the the update you are contemplating also includes a bootloader update - performed the safest way possible (signature checking performed by the existing boot loader). Doing it the manual way (via fastboot) is quite dangerous, even for experts. If you have a 3g version there is also a radio update which also should not be attempted in any other way than via a pure stock OTA install including use of a stock recovery.
Make a full Nandroid backup before you begin anything - and get a copy of that backup off of the tablet as well as a failsafe measure. If you screw things up moving forward, at least you will be able to start over from where you are right now.
If you have been operating using best practices, you should already have a nandroid backup of the pure-stock /system & boot images. TWRP allows you selectively restore individual partitions. Few users seem to know how to actually make a backup of stock recovery partitions, but you can get that out of oldblue910's archive site - find the link in the OTA thread.
good luck

wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
He's telling you the plain and simple truth. Want the OTA- as it stands, you're out of luck. Either return to stock and then flash the OTA, or flash the 4.2.2 factory image. That's it. Nothing more. That anyone even bothered to answer this uselessly redundant thread is a miracle in and of itself.
Sent from my Nexus 7 using Tapatalk HD

[How-To] Install OTA Update on after Root/Custom Recovery

*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.

jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.

trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.

Thank you for the info! Does sound like an awful lot of work though

jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.

I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.

shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.

jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english

Does sound like an awful lot of work though

greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.

How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium

I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.

trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...

With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.

sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.

Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!

I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.

jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app

deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.

I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?

[Solved] Did I hose myself (Knox poblem?)

So, the other day, as samsung was pushing more bloat to my phone, I decided I had had enough Redit told me I could just delete most things from root, I did so by following the instructions from a google search of how-to-root-and-flash-cwm-recovery-on-sprint-galaxy-s4-on-android-4-3-tutorial (except, of course, the back up part)
then, without paying attention to the list of removable apps, I took out Samsung hub, And then the problems start. The phone still works: Except every second or so, i get told that the hub has stopped. The phone isn't bricked, but it is basically worthless with the message popping up constantly.
According to my settings, everything is still stock (L720VPUFNAE) Although I think just rooting it was enough to pop the Knox bubble. I'm not working on getting that rom to try to re-flash back to stock (I thought i had did this over night, but it seems like i had slightly different roms when I was doing this early in the morning)
I also tried installing the Samsung Hub apk, but I get an error stating that X app wasn't installed. I have not been able to find a source for this app while googling.
I've tried finding a custom rom to use, but most of the ones I THINK are good/will work, don't install via odin, and for some reason when I try to boot into recovery, it just sits indefinitely @ the samsung galaxy screen.
Am I just stressed and frustrated, or am I truly hosed?
Edit: I'm currently working through http://forum.xda-developers.com/showthread.php?t=2307531 as my next attempt
Edit: for some reason Philz recovery isn't ever entering a recovery mode for me, it just sides @ the samsung screen forever

Akuthia said:
blablabla I deleted something what I shouldn't and now my phone is faulty, but I do not want/can reflash using Odin and CWM :crying::crying::crying:
Click to expand...
Click to collapse
You still can install Mobile Odin from google Play, copy ROM to SD card and try to flash it in that way...

spamtrash said:
You still can install Mobile Odin from google Play, copy ROM to SD card and try to flash it in that way...
Click to expand...
Click to collapse
I get it, i deserve the sarcasm, I broke rule 1 of upgrades. (one of) the problems I'm having though is finding the right file to flash to. Just looking for a little bit of advice as to what files I need to get back to " Normal" I know I should be able to flash to another rom, why when I use Philz Recovery it doesn't do what it's supposed to, is beyond me right now. Odin mobile requires the PDA file, correct? That seems fine to getting back to stock, but most of the custom roms I've found or are at least interested in are just files that are installed via recovery...which for some reason I don't have access too, right?

Akuthia said:
That seems fine to getting back to stock, but most of the custom roms I've found or are at least interested in are just files that are installed via recovery...which for some reason I don't have access too, right?
Click to expand...
Click to collapse
Correct. If I'd be you, I'd go to sammobile.com, and I'd start from full stock flash. It shall restore recovery. It it would work - you'd be OK to go with custom.

spamtrash said:
Correct. If I'd be you, I'd go to sammobile.com, and I'd start from full stock flash. It shall restore recovery. It it would work - you'd be OK to go with custom.
Click to expand...
Click to collapse
Ok, Sammobile has been efforting for about an hour. Has an hour to go. I also got CWM and am going to see if I can flash a rom with it. Transfer of those files is taking a while as well.

Akuthia said:
Ok, Sammobile has been efforting for about an hour. Has an hour to go. I also got CWM and am going to see if I can flash a rom with it. Transfer of those files is taking a while as well.
Click to expand...
Click to collapse
Got back to stock. Text messages gave me a fright for a bit was sending me a message they were undeliverable via another code text # one of those 4 or 5 digit things)

Akuthia said:
Got back to stock. Text messages gave me a fright for a bit was sending me a message they were undeliverable via another code text # one of those 4 or 5 digit things)
Click to expand...
Click to collapse
Good. Now, a small lesson for the future, if I can:
if you want to remove something, DO NOT delete software, use Titanium Backup and freeze apk first instead.
This will give you opportunity to check if you have frozen something important. :good:

spamtrash said:
Good. Now, a small lesson for the future, if I can:
if you want to remove something, DO NOT delete software, use Titanium Backup and freeze apk first instead.
This will give you opportunity to check if you have frozen something important. :good:
Click to expand...
Click to collapse
Thats the thing, i HAD made a backup in titanium of all my system apps, just so i could roll it back, but for some reason, it wasn't listed when the fan got hi by you know what.

Akuthia said:
Thats the thing, i HAD made a backup in titanium of all my system apps, just so i could roll it back, but for some reason, it wasn't listed when the fan got hi by you know what.
Click to expand...
Click to collapse
I DID not mentioned BACKUP.
I mentioned FREEZING.
Backup is another copy, which you may, or may not install.
FREEZE is that all files are present, but the application is not listed in system.

How do I fix a bootloop?

The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.

Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!

SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img

WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.

I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?

arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)