Hey guys,
Is there a CWM Zip file out yet for the latest OTA update 4.5.145?
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
I posted one in a thread in the dev section a few days ago
http://forum.xda-developers.com/showthread.php?p=37763672
Sent from my MB860 using xda premium
Thanks, I searched but nothing came up before asking.
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
The OTA update zip will flash just fine thru CWM recovery.
I moved the zip from /cache to the internal sdcard /rom folder. Then ran opened ROM manager, Install from Sd Card, reboot into recovery.
Install went fine, CWM showed no errors, root and custom recovery remained untouched. When the phone reboots the first time the OTA update system will fuss that the update failed but About Phone shows you are updated 4.5.145.
See fixed my own stuff....
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
is 4.5.145 worth the install? I made the mistake of searching for updates, now i keep getting the reminder, so its either update or turn the reminder off. I just dont want to lose my root/unlock/webtop2sd
nicholetech said:
The OTA update zip will flash just fine thru CWM recovery.
I moved the zip from /cache to the internal sdcard /rom folder. Then ran opened ROM manager, Install from Sd Card, reboot into recovery.
Install went fine, CWM showed no errors, root and custom recovery remained untouched. When the phone reboots the first time the OTA update system will fuss that the update failed but About Phone shows you are updated 4.5.145.
See fixed my own stuff....
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
Click to expand...
Click to collapse
uisgdlyast said:
is 4.5.145 worth the install? I made the mistake of searching for updates, now i keep getting the reminder, so its either update or turn the reminder off. I just dont want to lose my root/unlock/webtop2sd
Click to expand...
Click to collapse
If someone know how to stop the "spam" about the update, I will be very thankful.
Sent from my MB860 using xda app-developers app
uisgdlyast said:
is 4.5.145 worth the install? I made the mistake of searching for updates, now i keep getting the reminder, so its either update or turn the reminder off. I just dont want to lose my root/unlock/webtop2sd
Click to expand...
Click to collapse
The update changes the radio from 37p to 38p, giving a better signal, improved GPS with Maps (possibly overall GPS improvement), kernel version remains the same, however it appears to be a different build, and a few security updates. See images for status changes
Note: I did flash the 38p radio separately before cwm flashing the update. Upon update, go ahead and get into root explorer and delete the google preloaded apps that appear in play store so you can free up room in /system. Then update superuser binaries, and redownload google preloaded apps from play store.
Sent from my MB860 using xda app-developers app
Related
So I woke up this morning and I noticed a little blue android man standing next to a caution symbol on my phone screen. I was stock rooted before this happened. I believe the recent update went ahead and updated itself while I was sleeping. Can someone help me get my phone back to stock root? If I press the menu button, it brings me to the Revolutionary CWM v4.0.1.4 screen where I have the options to "reboot system now", "apply sdcard:update.zip"... etc. I'm not really good with Revolutionary so before I do anything I would like the opinions and suggestions of others who are more experienced. Obviously I'd like to avoid a factory reset as much as possible. Thanks!
You have to get the stock ruu 2.11.605.5 and re flash it. It will remove root unfortunately because .9 is not rootable yet.
Flash back to non root stock by putting the ruu i mentioned above on your memory card (not in any folders) and rename it to PG05IMG then power off the phone.
Hold power and volume down for a few seconds and the phone will go to the Hboot screen, it will find the PG file and update itself. Once its all done, reroot with revolutionary and then go into the developement section here and get the rooted version of the 2.11.605.9 ruu file and just flash that in recovery.
You will have to flash the new radios as well. They have to be renamed to the same name I posted above and flashed the same way thru the Hboot screen
So even if I were to back up with My Backup Pro, I wouldn't be able to recover all my data, apk's, photos etc. because I wouldn't be able to root on the latest update, correct?
Try wiping cache and rebooting before you flash an RUU, lose root and your data. If it bootloops or is still otherwise non functioning THEN you will have to RUU it.
Sent from my HTC Thunderbolt
jumpman1229 said:
So even if I were to back up with My Backup Pro, I wouldn't be able to recover all my data, apk's, photos etc. because I wouldn't be able to root on the latest update, correct?
Click to expand...
Click to collapse
Your photo and apps should be backed up on your sd card. your setup will be wiped but all the stuff on the sd card will be fine. Just have to reinstall
as for what the post about wiping and rebooting, that will not help unfortunately because the update deletes root. If you want to get back to root, you have to reinstall.
go here for the exact process http://forum.xda-developers.com/showthread.php?p=20446596#post20446596
Thanks guys. I ended up flashing the stock rom on the link below. Apparently that got it working where it wont break your root anymore.
http://www.androidpolice.com/2011/1...n-volume-exchange-and-more-sorry-no-ics-here/
jumpman1229 said:
Thanks guys. I ended up flashing the stock rom on the link below. Apparently that got it working where it wont break your root anymore.
http://www.androidpolice.com/2011/1...n-volume-exchange-and-more-sorry-no-ics-here/[/QUOT
My buddy is having the same problem. How did you flash the new rom?
Click to expand...
Click to collapse
jeitzen said:
jumpman1229 said:
Thanks guys. I ended up flashing the stock rom on the link below. Apparently that got it working where it wont break your root anymore.
http://www.androidpolice.com/2011/1...n-volume-exchange-and-more-sorry-no-ics-here/[/QUOT
My buddy is having the same problem. How did you flash the new rom?
Click to expand...
Click to collapse
Just place the zip file on your SD card, then go into recovery and find the zip through there. Your new Rom should then begin flashing
Sent from my HTC Thunderbolt using XDA Premium App
Click to expand...
Click to collapse
*edit: Sorry, I misread the first post.
jumpman1229 said:
jeitzen said:
Just place the zip file on your SD card, then go into recovery and find the zip through there. Your new Rom should then begin flashing
Sent from my HTC Thunderbolt using XDA Premium App
Click to expand...
Click to collapse
Ok, we downloaded the said rom.
He gets a no app2sd partition found and signature invalid.
Click to expand...
Click to collapse
I've asked for help in the threads posted about the OTA update and I cannot get the help I need. I've seen people post similar questions that I have and they are largely ignored. I had to stay away from the forums because I was getting so damn angry.
I have root and I have S-Off. I have not flashed any ROMs on this phone. I want to apply the OTA update but I do not know how to do that.
There's mentions of flashing firmware, radios, PRIs, PRLs, ROMs, Deoxed, Oxeded, hboot, bootloader, recovery, TWRP, etc. All of that across multiple threads does not compute well in my head.
I've read a lot and I am not sure what to do. Can someone please help me out? I will be forever grateful. I could send you a case for your phone for helping me. I promise I am not being lazy. I'm just not getting it.
If you're rooted and you have S-Off, you should have TWRP. First verify that by booting into the bootloader (Power + Vol Down) and going to Recovery.
Once in TWRP, do a backup. Backup everything. This way if something goes wrong you can restore your previous ROM.
Next download this: http://d-h.st/d2a
It's the firmware zip, courtesy of Haus. Rename the file to remove all of the stuff after PJ85IMG. Then put it on the root of your SD card and boot into the bootloader. It will scan for a zip and find it, and ask you if you want to update. This step is optional; you can flash new 1.22 ROMs without the new firmware.
After flashing that through bootloader, you can choose a 1.22 ROM that looks good to you, and download it. Boot back into TWRP, do a factory reset and wipe System, and then install the ROM. If you download it to your external SD card (in other words, an SD card you put in yourself), you'll have to mount it by going to Mounts and choosing external SD. That way you'll be able to access files on it.
To install the ROM after wiping, just hit Install from the main menu of TWRP and navigate to the location of the ROM zip you downloaded. Install it and reboot, and there you have it, you're on the new firmware and using a ROM with the new fixes in it!
The firmware zip is optional, but recommended. If you aren't comfortable flashing it, don't bother.
Sent from my EVO using xda premium
SoraX64 said:
If you're rooted and you have S-Off, you should have TWRP. First verify that by booting into the bootloader (Power + Vol Down) and going to Recovery.
Once in TWRP, do a backup. Backup everything. This way if something goes wrong you can restore your previous ROM.
Next download this: http://d-h.st/d2a
It's the firmware zip, courtesy of Haus. Rename the file to remove all of the stuff after PJ85IMG. Then put it on the root of your SD card and boot into the bootloader. It will scan for a zip and find it, and ask you if you want to update. This step is optional; you can flash new 1.22 ROMs without the new firmware.
After flashing that through bootloader, you can choose a 1.22 ROM that looks good to you, and download it. Boot back into TWRP, do a factory reset and wipe System, and then install the ROM. If you download it to your external SD card (in other words, an SD card you put in yourself), you'll have to mount it by going to Mounts and choosing external SD. That way you'll be able to access files on it.
To install the ROM after wiping, just hit Install from the main menu of TWRP and navigate to the location of the ROM zip you downloaded. Install it and reboot, and there you have it, you're on the new firmware and using a ROM with the new fixes in it!
The firmware zip is optional, but recommended. If you aren't comfortable flashing it, don't bother.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you Sora! I am going to follow your advice this afternoon and will let you know how it goes.
http://forum.xda-developers.com/showthread.php?t=1770501
This way will not cause you to lose any data, and installs the update on top of what you already have. Still recommend a backup in TWRP first, though
Robbie_G said:
http://forum.xda-developers.com/showthread.php?t=1770501
This way will not cause you to lose any data, and installs the update on top of what you already have. Still recommend a backup in TWRP first, though
Click to expand...
Click to collapse
I would personally recommend staying away from that method. As a rooted user you should never accept an ota. Doing it that way might work this time, but in the future there's no guarantee you won't lose s-off and never be able to get it again
Sent from my EVO using Tapatalk 2
Rxpert said:
I would personally recommend staying away from that method. As a rooted user you should never accept an ota. Doing it that way might work this time, but in the future there's no guarantee you won't lose s-off and never be able to get it again
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I know "never OTA" is your and some other people's mantra, but being able to do this is one of the benefits of S-off. I agree it is possible they could turn you back to S-ON in a future OTA (maybe...), but since it works for this current update, I don't think you should be dissuaded if you don't want to completely wipe your phone.
Robbie_G said:
I know "never OTA" is your and some other people's mantra, but being able to do this is one of the benefits of S-off. I agree it is possible they could turn you back to S-ON in a future OTA (maybe...), but since it works for this current update, I don't think you should be dissuaded if you don't want to completely wipe your phone.
Click to expand...
Click to collapse
It's a bad habit to start, and all he has to do my way is flash a ROM..
Sent from my EVO using xda premium
SoraX64 said:
It's a bad habit to start, and all he has to do my way is flash a ROM..
Sent from my EVO using xda premium
Click to expand...
Click to collapse
My man.
Exactly.
Just look at all of the people who show up on here going "Oh crap I took the OTA and now I can't get S-OFF"! The fact of the matter is, people don't check here before taking the OTA. If they look here and see that thread that says to just put on teh stock recovery and you're A-OK, thats what they'll do from then on.
When it happens, I'm just going to sit back and say "toldya so"... and let everyone else deal with the support. Until then, I'm going to keep preaching that you should never take an OTA if you are rooted or EVER thinking about rooting.
Sora, I looked at your instructions. I flashed ROMs before on my EVO 4G. That process I was comfortable with. Basically, the developer did all the work for me. I wanted to keep my phone stock for a while but I do want the updates.
cubbieswin said:
Sora, I looked at your instructions. I flashed ROMs before on my EVO 4G. That process I was comfortable with. Basically, the developer did all the work for me. I wanted to keep my phone stock for a while but I do want the updates.
Click to expand...
Click to collapse
It really comes down to this, if you're still having problems:
If you have recovery, just flash a ROM with the new base. Just like you'd do on your old Evo.
Sent from my EVO using xda premium
SoraX64 said:
It really comes down to this, if you're still having problems:
If you have recovery, just flash a ROM with the new base. Just like you'd do on your old Evo.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Ok, so I will have to flash a ROM. Do you think I can flash the deodexed version of this [ROM][STOCK] --- Stock Rooted 1.22.651.3 Odexed & DeOdexed (7/14/12)--- over my stock-from-Sprint setup?
I flashed TWRP. I'm going to update the firmware next with the file you pointed me to. I'm trying to find the info on clearing Google wallet.
...then the ROM.
Clearing GW data should say something about resetting it. It'll be in the app settings.
Seems like you've got it down now, I'm glad to say. You'll be able to flash that ROM without any issues.
Sent from my EVO using xda premium
SoraX64 said:
Clearing GW data should say something about resetting it. It'll be in the app settings.
Seems like you've got it down now, I'm glad to say. You'll be able to flash that ROM without any issues.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Sora, how do you flash your ROMs? Do you use TWRP? or something like Goo Manager? I haven't used Goo Manager before, but I see it flashes ROMs.
Hello, I just upgraded to the new droid DNA on 1-13-2013. I got the bootloader unlocked and flashed the recovery without problems but, when I flashed the superuser files using recovery it fails and says md5 file or something like that was not found but with the failure to install, it still put the superuser, su and busybox files in the correct sytem folders. I booted my device and open supersu and it said I need to update the su file but that update failed too. I also did a full stock restore to see how it goes for me beause I hear people say once you do that you can't
re-unlock the bootloader but, I got the bootloader re-unlocked witout problems. I wanted to add that because people was asking if any body else was having problems re-unlocking. What I want to know is how can I get root? I still have my bootloader unlocked. Can I install a pre rooted stock rom using custom recovery or will that fail too since I cant get the supersu installed successfully?
Sent from my HTC6435LVW using xda premium
AndroidSmitty said:
Hello, I just upgraded to the new droid DNA on 1-13-2013. I got the bootloader unlocked and flashed the recovery without problems but, when I flashed the superuser files using recovery it fails and says md5 file or something like that was not found but with the failure to install, it still put the superuser, su and busybox files in the correct sytem folders. I booted my device and open supersu and it said I need to update the su file but that update failed too. I also did a full stock restore to see how it goes for me beause I hear people say once you do that you can't
re-unlock the bootloader but, I got the bootloader re-unlocked witout problems. I wanted to add that because people was asking if any body else was having problems re-unlocking. What I want to know is how can I get root? I still have my bootloader unlocked. Can I install a pre rooted stock rom using custom recovery or will that fail too since I cant get the supersu installed successfully?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Go check out the ROMs in the Android Development Section. Most, if not all, of the ROMs have the superuser and BusyBox built in. Try UKB.
Cheers!
Thanks, I did that but when I went to install it the install started but it didn't go through. The install started for about 1 second and it just just booted me. I had to rerun the full RUU.exe i found in the xda forum to reinstall. The only thing I want to do is just root to be able to delete bloat. I hope somebody comes out with a way to root without having to unlock boot loaders.
Sent from my Nexus 7 using Tapatalk HD
Sent from my ADR6425LVW using xda app-developers app
I have an s-off'd custom rom with AmonRa recovery... offered update??
I just want to have it ignore the update.
Apparently, the software doesn't know the
recovery system is not stock ... so it tries
and fails. I wonder if there is a way to extract
the new fingerprint to trick the update process
into thinking the updates already applied?
Or is there a way to just suppress it all together?
Well I'm pretty much chicken so I'm basically stock but rooted but the ota update keeps falling. I tried unrooting so the update could work but it still failed. Not sure why...
Sent from my ADR6425LVW using xda app-developers app
Same here
I am having the same issue, as well. Rooted, debloated stock sense. Recovery is Amon-Ra.
So I read another thread that made it seem like I needed to re-lock the bootloader so I did that and now when I try to update it goes into the bootloader menu instead of starting the update. Do I need to unroot or do another step for this to work?
Sent from my ADR6425LVW using xda app-developers app
Did you debloat at all? I was stock+root (no debloating) and the install went fine.
Sent from my ADR6425LVW using xda premium
Well, when the ota update downloads and you press the button to update, the updater immediately begins to check the system utilizing a checksum system for any modification, such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure all system/apps are still there and untouched and all the binaries are still kosher. If it detects something is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using Root Explorer or something similar, go to system/app and add bak to the end of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
I have an s-off'd custom rom with AmonRa recovery... offered update??
wildstang83 said:
Well, when the ota update downloads and you press the button to update,
the updater immediately begins to check the system utilizing a checksum system for any modification,
such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure
all system/apps are still there and untouched and all the binaries are still kosher. If it detects something
is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the
update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using
Root Explorer or something similar, go to system/app and add bak to the en
d of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
Click to expand...
Click to collapse
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
fuzzynco said:
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
Click to expand...
Click to collapse
Not to be a PIA, but why freeze if you can just add bak to the end of the file name and you will achieve the same thing? If you ever want to go back you just delete the bak?
So for me it sounds like I need to get back to a stock recovery to be able to successfully perform the update?
Sent from my ADR6425LVW using xda app-developers app
Gee thanx for the help people...
Sent from my ADR6425LVW using xda app-developers app
You must be on the stock recovery to take an OTA. The stock recovery performs the update. So flash the stock recovery and then do the update or deal with no update.
Is there a way to flash the stock recovery without it wiping my phone?
Sent from my ADR6425LVW using xda app-developers app
Unless you're running a completely stock rom (with nothing removed), you won't be able to install the update anyway...
If you want to stop it from trying to come down, delete or rename /system/etc/security/otacerts.zip.
As for re-installing the stock recovery, you probably would need to RUU your phone unless it's s-off.
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
If you are on a stock rom you should be able to flash the stock recovery from fastboot without wiping the phone. Just find the recovery.IMG from the 605.12 ruu and flash it in fast boot to your phone. Then take the update and when complete flash your custom recovery in fast boot again and flash su zip.
Sent from my Nexus 7 using Tapatalk HD
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
A restore would not overwrite any of the firmware on the phone, just the rom.
As dottat pointed out, you can download the latest RUU, extract the recovery image from it and flash that via fastboot. I'd still back up your rom with your custom recovery first in case the rom pieces in the update bork something...
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Check androidpolice.com, it's over there, should be able to search for it...
Need a copy of the stock recovery
I am S-On and unlocked. I need to reflash the stock recovery to apply the OTA firmware update, right? I cannot find a copy of it anywhere. Anyone know where I can get this? I downloaded the stock RUU and tried to pull it out, but I cannot unzip the file. I would be grateful for any help. Thanks.
I have looked through numerous threads to find an answer to my problem but cannot seem to find it anywhere. I have tried obtaining the new update both OTA and installing on my SD card and am getting the same problem all the time. My phone will reboot into recovery ( I have CWM) and the screen with say "Install this untrusted package?" I have to tap the volume down button to "install untrusted zip" and when I hit the power button I get the same error that it failed to verify the whole file signature. D: Error in /cache/fumo/OTApkg.zip
I am rooted completely stock with s-on.
Does anyone have any idea how to get this to work?
Thanks.
You have to relock the bootloader and be on stock recovery to accept the ota.
Sent from my ADR6425LVW using xda app-developers app
Yeah just relock the bootloader (hasoon2000 all in one is easy if you dont know the script), and name the file ph98img.zip, then boot to bootloader and accept the update.
edit:
I want to add you MIGHT need to do the update twice once you do what we both mentioned. I had it once require me to flash the ph98img file twice before it booted into htc stock ics, maybe because I was on one of the new JB roms
Ok apparently I don't know how to go back to a stock recovery. Could you explain.
Also, if I go back to stock recovery would this mean I would have to re root everything?
The only reason I am doing this is so my stupid phone will quit rebooting into recovery in the middle of the night.
Sent from my ADR6425LVW using xda app-developers app
roywood said:
Ok apparently I don't know how to go back to a stock recovery. Could you explain.
Also, if I go back to stock recovery would this mean I would have to re root everything?
The only reason I am doing this is so my stupid phone will quit rebooting into recovery in the middle of the night.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Only way i know of getting stock recovery is to flash the RUU but this will wipe the phone.
back up the rom you are on now.
back up internal partition
lock bootloader
flash RUU in hboot
this will get you 100% out of the box stock
accept the OTA update.
synisterwolf said:
Only way i know of getting stock recovery is to flash the RUU but this will wipe the phone.
back up the rom you are on now.
back up internal partition
lock bootloader
flash RUU in hboot
this will get you 100% out of the box stock
accept the OTA update.
Click to expand...
Click to collapse
First you need to delete your win32 folder and profit.
Rebooting to install OTA with custom rom and recovery
roywood said:
Ok apparently I don't know how to go back to a stock recovery. Could you explain.
Also, if I go back to stock recovery would this mean I would have to re root everything?
The only reason I am doing this is so my stupid phone will quit rebooting into recovery in the middle of the night.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I was able to get it to stop rebooting and failing by renaming /system/app/HTCdm.apk,
(after seeing that was what was doing the download). I then deleted the OTA zip file,
and rebooted. Since then it has not tried to reprocess the OTA.,
My feeling is that shouldn't have tried in the first place. But this workaround seems to work.