EDIT: Pre-OTA MyTouch 4G's now have the ability to be rooted! http://forum.xda-developers.com/showthread.php?t=843428
For those of you who never received the OTA update that brought 2.2.1 to the MT4G, you have probably noticed by now that you are having problems or you are not able to root your MT4G.
When trying the rooting process by grankin01, the MT4G will freeze during this command:
Code:
dd if=/data/local/hboot_dhd.nb0 of=/dev/block/mmcblk0p18
This happens for reasons currently unknown. I figured I would make this thread to answer the questions of the people stuck in this situation.
If you figure out a way to perm-root your Stock MT4G, please use this thread to document what you did to perm-root it.
EDIT: When running *#*#CHECKIN#*#*, this is what I get in logcat:
Code:
11-11 16:06:40.620: INFO/CheckinTask(1609): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
11-11 16:06:40.630: INFO/CheckinService(1609): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
11-11 16:06:40.640: WARN/ActivityManager(1311): Permission Denial: broadcasting Intent { act=android.server.checkin.FOTA_CANCEL } from com.google.android.gsf (pid=1609, uid=10003) requires android.permission.HTC_FOTA_UPDATE due to registered receiver BroadcastFilter{470209c8 ReceiverList{47025b30 1311 system/1000 local:46f73288}}
Not sure why I get a Permission Denial from the checkin service.
I agree, having to wait for this stupid ota update sucks!
Sent from my HTC Glacier using Tapatalk
Already got AN ota update. What does it change? Where do I check to see if I'm updated?
Phateless said:
Already got AN ota update. What does it change? Where do I check to see if I'm updated?
Click to expand...
Click to collapse
The OTA updated your MT4G from Android 2.2 to 2.2.1.
Also, the Software number went from 1.14.531.1 to 1.17.532.2.
You can check under Settings > About Phone >Software information
No wonder I was having issues. Thx
Sent from my HTC Glacier using Tapatalk
travisjames said:
The OTA updated your MT4G from Android 2.2 to 2.2.1.
Also, the Software number went from 1.14.531.1 to 1.17.532.2.
You can check under Settings > About Phone >Software information
Click to expand...
Click to collapse
Yup, I'm up to date.
Phateless said:
Already got AN ota update. What does it change? Where do I check to see if I'm updated?
Click to expand...
Click to collapse
It updates to Android 2.2.1
To check go to Settings -> About Phone -> Software Information and check Android Version
Hope this helps
macfan74318
EDIT: Looks like travisjames beat me to the punch.
Someone really needs to have aLogcat rolling when they get their OTA so we can get the link for manual updates.
I swapped mine out last night and now I'm waiting on the OTA with it going.
unremarked said:
Someone really needs to have aLogcat rolling when they get their OTA so we can get the link for manual updates.
I swapped mine out last night and now I'm waiting on the OTA with it going.
Click to expand...
Click to collapse
Good idea, let us know if you get the link. We might still have a problem applying the update though.
We have the OTA, but when we try to apply the package via the stock recovery, it throws an -Invalid Operation- error/exception.
I error out before then. Insmod throws an error on the ko file (other than the one it should). Searching the forum basically lead me to believe it was because it's for the wrong kernel/architecture.
Genocaust said:
I error out before then. Insmod throws an error on the ko file (other than the one it should). Searching the forum basically lead me to believe it was because it's for the wrong kernel/architecture.
Click to expand...
Click to collapse
You're probably using the OTA kernel module. I suggested to grankin01 (the guy who wrote the rooting tutorial) to remove the Pre-OTA module because it failed to work.
We're not sure why it doesn't work.
Has anyone tried to recompile the files for the Pre-OTA ROM?
travisjames said:
You're probably using the OTA kernel module. I suggested to grankin01 (the guy who wrote the rooting tutorial) to remove the Pre-OTA module because it failed to work.
We're not sure why it doesn't work.
Click to expand...
Click to collapse
Yeah, I am, it's the one pulled from that thread. Once I read up on the error figured the module was specific to the pre/post OTA builds. Oh well .
Also, why performing a manual checkin is useless:
I/CheckinService( 1557): Preparing to send checkin request
I/CheckinTask( 1557): Sending checkin request (608 bytes)
I/CheckinTask( 1557): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 1557): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
W/ActivityManager( 1308): Permission Denial: broadcasting Intent { act=android.server.checkin.FOTA_CANCEL } from com.google.android.gsf (pid=1557, uid=10003) requires android.permission.HTC_FOTA_UPDATE due to registered receiver BroadcastFilter{47128c60 ReceiverList{4712ae68 1308 system/1000 local:470ccae0}}
Click to expand...
Click to collapse
macfan74318 said:
Has anyone tried to recompile the files for the Pre-OTA ROM?
Click to expand...
Click to collapse
Yes, we have recompiled the kernel module for pre-OTA MT4Gs, the Hboot is fine the way it is.
It still fails.
Can't you manually update somehow?
cal3thousand said:
Can't you manually update somehow?
Click to expand...
Click to collapse
No one has the link to the OTA on Google's servers.
Hopefully when I get mine, I'll be able to pull it out of aLogcat.
sweet mine just started downloading
Piss battery is too low lol
Sent from my HTC Glacier using Tapatalk
bblanski said:
sweet mine just started downloading
Piss battery is too low lol
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
did you log it?
pack said:
did you log it?
Click to expand...
Click to collapse
Sorry didnt. Ended up having to do a factory restore
Sent from my HTC Glacier using Tapatalk
Try calling T-Mobile Technical support, they told me if I did not get mine in 2 hours to call them back and they would manually put me on the list to OTA update. I got mine in less than 2 hours. It's worth a try. And if your in your 14 days you could tell them if you don't get it your returning the device due to poor battery usage and failure to get OTA update to fix the problem. Get you a new device.
Related
AT&T just SMSed me that the update is coming soon and I should press OK when prompted.
Quote, "AT&T FREE MSG: AT&T is providing a free update for your phone. When asked to install the update, please select OK. Thank You."
FYI
Sent from my SAMSUNG-SGH-I897 using XDA App
nirvani said:
AT&T just SMSed me that the update is coming soon and I should press OK when prompted.
Quote, "AT&T FREE MSG: AT&T is providing a free update for your phone. When asked to install the update, please select OK. Thank You."
FYI
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Uhhh, you are about 1 week to late for this information. Thanks though.
I was rooted, no lagfix when I tried to update. It got to 100% then it said failed. My baseband says I897UCJH7. Kernel 2.6.29 [email protected] #2.
Did the update work or not?
Flashman, how did your OTA update go? Any issues us rooted/unlocked folks should be worried about?
My instinct is to delay the update until I stop seeing posts about hot it F'd up people's phones.
Sent from my SAMSUNG-SGH-I897 using XDA App
nirvani said:
Flashman, how did your OTA update go? Any issues us rooted/unlocked folks should be worried about?
My instinct is to delay the update until I stop seeing posts about hot it F'd up people's phones.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you rooted and removed anything from stock rom, you're pretty much guaranteed to fail on OTA update. In order to make the OTA download package as small as possible, Samsung uses a diff patch based on the bit differences between stock JF6 image and new JH7 image. So, if you touched the JF6 in any unauthorized way, the patch won't work.
Luckily, you can now use the newly released Kies Mini to do a full ROM update which should be more reliable as you have the entire ROM image downloaded to your desktop and then flash to your phone.
foxbat121 said:
If you rooted and removed anything from stock rom, you're pretty much guaranteed to fail on OTA update. In order to make the OTA download package as small as possible, Samsung uses a diff patch based on the bit differences between stock JF6 image and new JH7 image. So, if you touched the JF6 in any unauthorized way, the patch won't work.
Luckily, you can now use the newly released Kies Mini to do a full ROM update which should be more reliable as you have the entire ROM image downloaded to your desktop and then flash to your phone.
Click to expand...
Click to collapse
What does it mean if Kies mini says Firmware version: unregistered device?
rcm921 said:
What does it mean if Kies mini says Firmware version: unregistered device?
Click to expand...
Click to collapse
Quoted by Samsung "The program can report this message if it detects a software build other than the official launch software of JF6."
You need to FLASH STOCK JF6 using ODIN ONE CLICK, Follow this Guide:
http://forum.xda-developers.com/showthread.php?t=794363
Colton5419 said:
Quoted by Samsung "The program can report this message if it detects a software build other than the official launch software of JF6."
You need to FLASH STOCK JF6 using ODIN ONE CLICK, Follow this Guide:
Click to expand...
Click to collapse
If my settings say i'm at JH7, does that necessarily mean the OTA update was completely successful? It reached 100% then said failed.
foxbat121 said:
If you rooted and removed anything from stock rom, you're pretty much guaranteed to fail on OTA update.
Click to expand...
Click to collapse
What do you mean removed anything from stock rom? I rooted and removed a bunch of the bloatware and did an OTA update with no issues.
I failed along with most other rooted and flashed guys. Luckily I didn't brick my phone in the process. I will wait until some beret update comes along before trying anything ota again.
Sweet life
Nevermind, I guess it didn't update fully cause some of the implemented changes aren't there. I really didn't want to have to run a master clear and have to reinstall all my stuff.
rcm921 said:
Nevermind, I guess it didn't update fully cause some of the implemented changes aren't there. I really didn't want to have to run a master clear and have to reinstall all my stuff.
Click to expand...
Click to collapse
Did you try to update with mini kies?
Colton5419 said:
Did you try to update with mini kies?
Click to expand...
Click to collapse
Trying to figure out a way to do it without having to wipe everything right now. But no luck.
rcm921 said:
Trying to figure out a way to do it without having to wipe everything right now. But no luck.
Click to expand...
Click to collapse
Do you have TouchWiz as your default launcher? and make sure you're on your home screen when you connect your USB cable.
If that doesn't do it you need to get back to JF6 only way or another because Mini Kies will continue to tell you that you have an "unregistered" device until it is at JF6
The reason is because your update failed partially :/
are you guys talking about a new update or just JH7?
We're talking about JH7, some people are still having difficulties getting it on their phone as the OTA is still failing - and if you've failed the OTA you need to reflash to stock before mini kies will work.
when i did the update i was rooted an it didn't fail on install or bootup or anything.
but then again i'm just rooted and nothing else has been touched.
wade7919 said:
when i did the update i was rooted an it didn't fail on install or bootup or anything.
but then again i'm just rooted and nothing else has been touched.
Click to expand...
Click to collapse
Exactly, I don't think root causes any issues. I was able to check for update on a rooted ROM.
It's when you have a custom kernel etc.
flashman2002 said:
Uhhh, you are about 1 week to late for this information. Thanks though.
Click to expand...
Click to collapse
Not really. AT&T has said that the real update will be sent out via SMS text message link, not through the "update software" menu in android.
Engadget just had that yesterday.
derek4484 said:
Not really. AT&T has said that the real update will be sent out via SMS text message link, not through the "update software" menu in android.
Engadget just had that yesterday.
Click to expand...
Click to collapse
It's the same thing.
I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
jasondhsd said:
I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
Click to expand...
Click to collapse
Flash a custom recovery/ROM. That should do it
But I'm not sure what else if the fwupgrade freeze didn't work
Yes. How do I stop this crap!?
I have 2 of these both rooted and hers keeps trying to install it. Its already downloaded on hers. I interrupted mine by killing the internet connection as soon as I saw it start downloading.
I'm sure when I'm sleeping it will try to install itself. So ill just shut my phone off.
Grr...
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
jasondhsd said:
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
Click to expand...
Click to collapse
Thats an issue with no-sympathy.... Most ROM's block the OTAs so you don't even need to worry about them.
This is actually the first ROM i've heard of that allows OTA's to even show up on the prompts.
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
You would have to ask the ROM's developers. Refuse it, and flash to another ROM that does it automatically for you. Obviously No Sympathy didn't think of an OTA... whynot I dunno. But every other developer did.
jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
Install an old version of synergy?
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
jasondhsd said:
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
Click to expand...
Click to collapse
I just did that. sdm 1.0 frozen. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from my Land Line using xda premium
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Blue6IX said:
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Click to expand...
Click to collapse
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
shuura said:
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
Click to expand...
Click to collapse
So far so good on freezing SDM. We'll see tomorrow morning.
Congrats to all those looking forward to the 4.1 OTA. I'm happy for you. However, I just got my Razr Maxx HD and I'm happy with it as it is.
If I root using these instructions: http://forum.xda-developers.com/showthread.php?t=1943851 will that stop my Maxx from getting the pending OTA?
If not, what else will I need to do?
Thanks in advance to all willing to help.
ThanksToXDA said:
Congrats to all those looking forward to the 4.1 OTA. I'm happy for you. However, I just got my Razr Maxx HD and I'm happy with it as it is.
If I root using these instructions: http://forum.xda-developers.com/showthread.php?t=1943851 will that stop my Maxx from getting the pending OTA?
If not, what else will I need to do?
Thanks in advance to all willing to help.
Click to expand...
Click to collapse
OTA aren't automatic... You have to accept the download. So just don't accept it. Easy enough.
EdwardN said:
OTA aren't automatic... You have to accept the download. So just don't accept it. Easy enough.
Click to expand...
Click to collapse
Thanks for the response, but I've been told OTAs can't be continually refused (like after the 5th decline, they will update automatically). You seem to be stating that if I decline the OTA, it will not update ever.
If I'm understanding you correctly and I decline the OTA, will it continually prompt me to do it?
ThanksToXDA said:
Thanks for the response, but I've been told OTAs can't be continually refused (like after the 5th decline, they will update automatically). You seem to be stating that if I decline the OTA, it will not update ever.
If I'm understanding you correctly and I decline the OTA, will it continually prompt me to do it?
Click to expand...
Click to collapse
Looks like there's a few ways to block OTA updates. Installing a custom rom does, but you want to keep it stock, obviously.
You can edit your build.prop file to "spoof" the current version so it doesn't try to update you. Do a search for editing build.prop, I don't have the exact details on hand.
The specific line is ro.build.fingerprint= but you'll have to wait until someone has the update installed to find out what the new information after the = is.
EdwardN said:
Looks like there's a few ways to block OTA updates. Installing a custom rom does, but you want to keep it stock, obviously.
You can edit your build.prop file to "spoof" the current version so it doesn't try to update you. Do a search for editing build.prop, I don't have the exact details on hand.
The specific line is ro.build.fingerprint= but you'll have to wait until someone has the update installed to find out what the new information after the = is.
Click to expand...
Click to collapse
Those running the leak, would they have the correct "after the =" ?
ThanksToXDA said:
Those running the leak, would they have the correct "after the =" ?
Click to expand...
Click to collapse
The leak might not, but the soaktest should. I would imagine it'll be on some phones in the next few days. Just make sure you get the line from someone with the same provider.
Having said all this, I have my older Defy running JB and it's an improvement over ICS. I personally am looking forward to the update. I feel a little like they didn't do as much optimization on ICS as they could have just because they knew JB was coming soon after launch.
EdwardN said:
The leak might not, but the soaktest should. I would imagine it'll be on some phones in the next few days. Just make sure you get the line from someone with the same provider.
Having said all this, I have my older Defy running JB and it's an improvement over ICS. I personally am looking forward to the update. I feel a little like they didn't do as much optimization on ICS as they could have just because they knew JB was coming soon after launch.
Click to expand...
Click to collapse
Thanks for the help.
I decided to wait over night to see if I recieved any other options here. This morning I found an "An update has been downloaded..." message.
EdwardN said:
OTA aren't automatic... You have to accept the download. So just don't accept it. Easy enough.
Click to expand...
Click to collapse
Wrong! Wrong! Wrong!
I still had the option to install now or later. I chose later.
Edit for better info: The download, "Update (0.7.2.en.US) has been downloaded and is ready to install."
Can I still root using the prev mentioned method if I install this?
Any other options to prevent the JB OTA?
ThanksToXDA said:
I decided to wait over night to see if I recieved any other options here. This morning I found an "An update has been downloaded..." message.
Wrong! Wrong! Wrong!
I still had the option to install now or later. I chose later.
Edit for better info: The download, "Update (0.7.2.en.US) has been downloaded and is ready to install."
Can I still root using the prev mentioned method if I install this?
Any other options to prevent the JB OTA?
Click to expand...
Click to collapse
My error, I meant to say "You have to accept *to install* the download." I did read that it'd download anyway, unless you already had the version spoof in place. If you intend to root, root first, then use VooDoo OTA Rootkeeper (from market) to backup your root before update, and restore after update.
ThanksToXDA said:
Congrats to all those looking forward to the 4.1 OTA. I'm happy for you. However, I just got my Razr Maxx HD and I'm happy with it as it is.
If I root using these instructions: http://forum.xda-developers.com/showthread.php?t=1943851 will that stop my Maxx from getting the pending OTA?
If not, what else will I need to do?
Thanks in advance to all willing to help.
Click to expand...
Click to collapse
Not sure the reluctance to dl jb. It's faster than Ics, and you can keep root.
Sent from my DROID RAZR HD using Tapatalk 2
JB is nothing but pure improvement. Absolutely no downsides. That's why people are foaming at the mouth for it. And 0.7.2.en.US is just an ICS update.
BinarySauce said:
0.7.2.en.US is just an ICS update.
Click to expand...
Click to collapse
I appreciate the info on (0.7.2.en.US)
From another forum, I found this advice:
"I renamed my OTACERTS.ZIP file to otacerts.zip.bak ... and this stopped updating on my DI2.
The OTACERTS.ZIP file can only be modified by ROOT users, and it's located in: system/etc/security/otacerts.zip"
Would this work?
ThanksToXDA said:
From another forum, I found this advice:
"I renamed my OTACERTS.ZIP file to otacerts.zip.bak ... and this stopped updating on my DI2.
The OTACERTS.ZIP file can only be modified by ROOT users, and it's located in: system/etc/security/otacerts.zip"
Would this work?
Click to expand...
Click to collapse
yes, but the problem with that solution is that it will keep downloading the update over and over, it'll just fail the certification process prior to install, and it'll eat your battery doing all the repeated downloads. You are welcome to try it though, and report back your results please.
EdwardN said:
yes, but the problem with that solution is that it will keep downloading the update over and over, it'll just fail the certification process prior to install, and it'll eat your battery doing all the repeated downloads. You are welcome to try it though, and report back your results please.
Click to expand...
Click to collapse
LOL, I'll take your word on this one (thanks again).
OK, next idea: Use Tit Backup to freeze updater.apk
or
FOTA Kill
What do you think???
Today i rooted my droid razr hd using matt groffs Droid razr hd utility belt. I successfully sent it back to ICS and rooted it. I downloaded the voodoo root keeper and updated the binaries on superuser. When i go to update the phone through system update to get it back on jb a popup comes and says....info an unexpected error has occured. Please try again later. Any help?
mitch xyx said:
Today i rooted my droid razr hd using matt groffs Droid razr hd utility belt. I successfully sent it back to ICS and rooted it. I downloaded the voodoo root keeper and updated the binaries on superuser. When i go to update the phone through system update to get it back on jb a popup comes and says....info an unexpected error has occured. Please try again later. Any help?
Click to expand...
Click to collapse
I'm having the exact same issue. I even fast booted again and tried updating to 0.7.2 before rooting. No dice.
Sent from my DROID RAZR HD using Tapatalk 2
Mine is too. Maybe something is up with the update server????
stooley said:
Mine is too. Maybe something is up with the update server????
Click to expand...
Click to collapse
Ditto here too, spent half the day trying to figure this out. I noticed some DNS errors coming from the phone while doing the update. Maybe they have figured out a way to block the 0.7.2. update for just us? Anyone know of a way to load just the 6 meg update to the phone manually and force the update?
Some behaviors I've noticed:
1. erase data 4G only get error mentioned above: "Please try again later"
2. turn on wifi (and 4G off) get no message but no update.
3. turn off wifi and "download suspended" appears (and never changes)
4. reboot to 4G only, get "An unexpected error has occured. Please try again later."
Stuck.
UPDATE:
My router shows a request to ws-cloud434-blur.svcmot.com from my phone. If I change my DNS to OpenDNS (hijackers) and try to update I see references to the "website not found" garbage that OpenDNS injects. Unfortunately I dismantled my squid setup so I can't see the exact url that is being attempted only the DNS error when OpenDNS injects it. I'm tempted to bring squid up just so I can figure out what is actually being requested on the update server.
Yea I can update to the latest via the computer, but then I cannot restore root so guess I will be waiting. I piicked a great time to do this ha ha.
stooley said:
Yea I can update to the latest via the computer, but then I cannot restore root so guess I will be waiting. I piicked a great time to do this ha ha.
Click to expand...
Click to collapse
How did you "via the computer"?
BTW, I did throw squid back in the full urls:
h t t p://ws-cloud434-blur.svcmot.com/blur-services-1.0/ws/upgrade/2/check_for_upgrade/(hex/dec numbers)
h t t p://ws-cloud434-blur.svcmot.com/blur-services-1.0/ws/upgrade/1/report_upgrade_status/(hex/dec numbers)
Both are POSTS and both return "file not found" when I try them from the browser.
Using the Motorola Device Manager. There is an option to update device. But it goes straight from the original ICS to Latest JB. Was not able to get root back afterwards. Voodoo did not even give the option. Tried the RestoreRoot script as well without success.
stooley said:
Using the Motorola Device Manager. There is an option to update device. But it goes straight from the original ICS to Latest JB. Was not able to get root back afterwards. Voodoo did not even give the option. Tried the RestoreRoot script as well without success.
Click to expand...
Click to collapse
That's a great try, shame it doesn't let you just install the 0.7.2 update. Did you set Voodoo to temp un-root during the update?
RRRRyan said:
That's a great try, shame it doesn't let you just install the 0.7.2 update. Did you set Voodoo to temp un-root during the update?
Click to expand...
Click to collapse
Yes. Temp Unroot then flashed with Device Manager. Went to Voodoo and SuperUser had to be reinstalled. Did that, still did not give me an option to re-root.
Files posted in this forum. All credit goes to that guy.
http://www.droidrzr.com/index.php?/topic/10926-Unable-to-download-system-update
Sent from my DROID RAZR HD using Tapatalk 2
orcsbane13 said:
Files posted in this forum. All credit goes to that guy.
http://www.droidrzr.com/index.php?/topic/10926-Unable-to-download-system-update
Click to expand...
Click to collapse
YES!!! Thx, that did the trick. Credit to you for updating us to that thread. I called mot too and got blaa.
Thanks!! That was exactly what I was looking for. Google was not my friend in trying to find those ha ha.
stooley said:
Thanks!! That was exactly what I was looking for. Google was not my friend in trying to find those ha ha.
Click to expand...
Click to collapse
Yeah mine either. I looked for about 3 hours before I gave up. Thankfully someone had the file. I won't be deleting that ever again lol.
Sent from my DROID RAZR HD using Tapatalk 2
RRRRyan said:
That's a great try, shame it doesn't let you just install the 0.7.2 update. Did you set Voodoo to temp un-root during the update?
Click to expand...
Click to collapse
But... I think it did. I just updated two devices using the Device Update tool. This is from memory but...
1) Connect, right click your taskbar and click check for updates.
2) It will say there is a 6MB download available to go to 0.7.2, accept it.
3) Updater downloads it, reboots your phone, applies it, etc.
4) Once fully booted, it prompts again, there's a new update available.
[do your rooting here]
5) Accept this update. It will download now a much larger file (200+ MB if i recall) to get you to the latest version
6) It reboots, applies the update, reboots, etc.
Unfortunately, I was too eager to get on the latest and greatest ROM before dropping by, so I did it from a vanilla new-phone upgrade. I did not root the device.
So I just got a notification for my update. If any developer wants it just let me know and I will send you a link to my Google Drive.
Does it tell you what the update version is. That is very helpful to them. My guess is its J which they have already.
DarkestSpawn said:
Does it tell you what the update version is. That is very helpful to them. My guess is its J which they have already.
Click to expand...
Click to collapse
Really? I didn't check or know how. I used the kdz for 10i a couple of weeks ago and I took the 10j update. Rooted from there and have only been flashing 10j roms. That's why i thought it was new. How do i check?
If so I feel retarded, haha. I thought I was helping out.
kcsevo said:
Really? I didn't check or know how. I used the kdz for 10i a couple of weeks ago and I took the 10j update. Rooted from there and have only been flashing 10j roms. That's why i thought it was new. How do i check?
Click to expand...
Click to collapse
If you click on the notification it should give you more info on it (Haven't actually clicked on one since JB so don't quote me on that lol) or you can pull the update from /cache and upload it to google drive and send me the link so I can look at it. (Dont put the link in the forums cause people tend to flash first, question later why they leap before they look).
DarkestSpawn said:
If you click on the notification it should give you more info on it (Haven't actually clicked on one since JB so don't quote me on that lol) or you can pull the update from /cache and upload it to google drive and send me the link so I can look at it. (Dont put the link in the forums cause people tend to flash first, question later why they leap before they look).
Click to expand...
Click to collapse
K, I'll send it to you shortly. Man i thought I was special! Hahaha.
But wouldn't it be kind of weird for me to get that update? Since I'm already on 10j?
I just sent it to you check your p.m.
kcsevo said:
I just sent it to you check your p.m.
Click to expand...
Click to collapse
I just checked my pm. Didn't see a message other than my old ones. But I'm guessing its a disappointment for me?
@Tilde88 or another will have to look at this. I tried numerous ways to extract this (I'm on Windows and am not familiar with messing with python on it, keep getting Command "bsdiff" is not valid, don't have dual boot on Windows 10 for a Ubuntu OS to do android related things yet, haven't had any motivation for anything these days) but I at least see it checks in the updater script if your system is NRD90M before it proceeds.
I just cant see an update so soon after J. We all know how good LG is at updates as well as source.
DarkestSpawn said:
@Tilde88 or another will have to look at this. I tried numerous ways to extract this (I'm on Windows and am not familiar with messing with python on it, keep getting Command "bsdiff" is not valid, don't have dual boot on Windows 10 for a Ubuntu OS to do android related things yet, haven't had any motivation for anything these days) but I at least see it checks in the updater script if your system is NRD90M before it proceeds.
I just cant see an update so soon after J. We all know how good LG is at updates as well as source.
Click to expand...
Click to collapse
Ok thank you man. I'm sorry I didn't mean to stir this up.
Could be a security patch.
Tilde88 said:
Could be a security patch.
Click to expand...
Click to collapse
The zip was downloaded today by OTA. Hopefully not security for preventing root but security for bettering the system.
No update on this?
Sent from my LG-H918 using Tapatalk
darkjedi said:
No update on this?
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
I'm on Ovrdrive's 10j rom and I just went to the update center and checked for an update. It say my phone is up to date. I'm on Tmo H918.
androiddiego said:
I'm on Ovrdrive's 10j rom and I just went to the update center and checked for an update. It say my phone is up to date. I'm on Tmo H918.
Click to expand...
Click to collapse
But remember with OTA updates people get them at different rates.
jameslapc2 said:
But remember with OTA updates people get them at different rates.
Click to expand...
Click to collapse
You are right, but I also remember with 10j, everyone seemed to get it within a day on TMO.
But you may be right if another one is out.
What size is the zip file?
It's strange why I would see an update on my phone. I am on 10j everything (bootloaded and all) and still got that update.
whats the model after the update
This was the update i took. Also, you can still root just fine.