Not sure if its posted but I have been asked a bit about keeping root. I took the OTA from Verizhon not Kies so I am not sure if that makes up for anything. Anywho, I took the plunge with both Voodoo and SU Pro backing up my root and kept it. I know there are root methods out there for it already so its not horrible if you have lost it. Just letting you know, Voodoo, SU Pro works.,,
ddemlong said:
Not sure if its posted but I have been asked a bit about keeping root. I took the OTA from Verizhon not Kies so I am not sure if that makes up for anything. Anywho, I took the plunge with both Voodoo and SU Pro backing up my root and kept it. I know there are root methods out there for it already so its not horrible if you have lost it. Just letting you know, Voodoo, SU Pro works.,,
Click to expand...
Click to collapse
Voodoo does work.
I can attest to that. The biggest issue with updates after ME7 is now the knox warranty flag is included in the boot loader.
I see the knox status when I go into download mode and it was not there before.
I'm already rooted so the flag didn't trip.
Be careful with this update, only do it via OTA so that Voodoo can restore root.
If you do it vie Kies or Verizon software, you will lose root *AND* re-rooting may flip the flag.
tech_head said:
Voodoo does work.
I can attest to that. The biggest issue with updates after ME7 is now the knox warranty flag is included in the boot loader.
I see the knox status when I go into download mode and it was not there before.
I'm already rooted so the flag didn't trip.
Be careful with this update, only do it via OTA so that Voodoo can restore root.
If you do it vie Kies or Verizon software, you will lose root *AND* re-rooting may flip the flag.
Click to expand...
Click to collapse
Voodoo worked from me from rooted ME7 via OTA update. I got the "Custom" lock symbol on reboot after Voodoo restore, but Triangle Away seems to have corrected that. What is the Knox status? I'm not familiar with that so I don't know how to check that? Could you elaborate?
Reboot into download mode and read the tiny text
Sent from my SCH-I545 using Tapatalk
so i tried to use Voodoo and keep my root. took the update and restarted. on boot it goes to download mode and says "could not do normal boot" in red above odin mode. help me get out please.
tech_head said:
Reboot into download mode and read the tiny text
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks. I see the same thing, Knox 0x0.
rossida said:
so i tried to use Voodoo and keep my root. took the update and restarted. on boot it goes to download mode and says "could not do normal boot" in red above odin mode. help me get out please.
Click to expand...
Click to collapse
Did you use Kies or just the OTA? As I said in my post I used the OTA from the phone. Kies may be doing something additional to the phone.
Worse case scenario is you will need to reflash ME7/ MI1 from odin and root again using the "root de le vega" method
http://forum.xda-developers.com/showthread.php?t=2487142
Yeah I still have the "custom" with the unlocked lock but its an easy fix. I just have not bothered yet,
I did the other update
Sent from my SCH-I545 using Tapatalk
---------- Post added at 02:58 PM ---------- Previous post was at 02:57 PM ----------
OTA not Kies.
Sent from my SCH-I545 using Tapatalk
did any of you lose your wifi tether?
I just got the notification for the update but did not download Su pro or voodoo prior to. Now they error out while trying to download. Is it because of the update lurking?
Sent from my SCH-I545 using Tapatalk
Imprezive13 said:
did any of you lose your wifi tether?
Click to expand...
Click to collapse
No still working
mattamous said:
I just got the notification for the update but did not download Su pro or voodoo prior to. Now they error out while trying to download. Is it because of the update lurking?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
DO you have TiBu and freeze/ deleted bloat and stock apps? If that's the case depending on what it was it will error. Like I said I took mine over the phone after checking for it the other day manually. If manual doesn't work Kies will update it when plugging into your PC.
Hopefully if anything was deleted a backup of stock was made and you can reload it. If not, just try unfreezing everything thing. Assuming you are using or have used TiBu.
After unfreezing several Verizon apps and 3 battery pulls, I was able to download and attempt to install the update only to have it fail at install...
Sent from my SCH-I545 using Tapatalk
mattamous said:
After unfreezing several Verizon apps and 3 battery pulls, I was able to download and attempt to install the update only to have it fail at install...
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Have you deleted anything not just freeze? If there is a fail on install its usually a self check fail... something it's looking for is missing.
I have the stock ME7 image and could upload it to drop box so you could reflash on odin, LMK. To me it sounds like a app or stock system piece is missing. I've seen OTAs fail on Motorola phones simply because the yahoo app was deleted. I know, it doesn't make sense, but its what the phone self checks before installing the download.
Titanium doesn't sow any apps deleted but I did have Samsung watch set to user app. Adjusted that back and still nothing. Going to try pulling SD card tomorrow and try the update again. Guess we'll see what happens
Sent from my SCH-I545 using Tapatalk
mattamous said:
Titanium doesn't sow any apps deleted but I did have Samsung watch set to user app. Adjusted that back and still nothing. Going to try pulling SD card tomorrow and try the update again. Guess we'll see what happens
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I still think a clean slate wipe is in order. Other people even on the Root De La Vega report a taking OTA it working and keeping it as well.
Like I said, I froze but never deleted, but if if you deleted the backups stored in TiBu at one point, the deleted app its not going to show in TiBu. Thats why I always make a backup first of the fresh phone and upload it to drop box before even freezing things.
I may end up going that route. Good thing we can backup apps to the moon with tibu! Have u noticed improvements on the new update?
Sent from my SCH-I545 using Tapatalk
mattamous said:
I may end up going that route. Good thing we can backup apps to the moon with tibu! Have u noticed improvements on the new update?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Nothing has caught my eye. Others are reporting the 4G is now operating off another/additional frequency or something like that, l and getting better reception but I have never had a problem where I live.
Did u happen to backup all your apps before rooting? I'm thinking I must have an app that was deleted and not backed up. I found that NFL was that way so installed and changed it to a system app with tibu
Sent from my SCH-I545 using Tapatalk
I'm trying to take the ota update but i'm a newb and didn't read about ME7's inability to flash roms and used ROM Manager to flash CWM. I think i need to restore the "stock" recovery in order to take the ota update.
Long time reader, first time poster.
Three questions.
1) For the "root de le vega" method, can I use 'Odin Mobile Pro'?
I don't have a PC so I can't easily use 'Odin' and i'm not sure how 'Odin Mobile Pro' relates to 'Odin'.
Is it the same thing but internal?
2) I have frozen tons of apps.
From my understanding from earlier posts, I need to unfreeze them all or this will fail?
3) After the Mi1 OTA, will my hotspot not work? or my wifi all together?
Thanks in advance
Related
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
SoCoolAZ said:
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
Click to expand...
Click to collapse
If you want to apply the ota, grab ota rootkeeper from the market. Open the app, save root, then go to town updating. No need to unroot. Once updated, open the app again and hit restore root, as the ota will remove root.
That's pretty much it. As it stands that is the only way to get root on the latest ota so if for some reason you run into an issue and lose root, you will have to sbf back to 2.3.4.
Sent from my MB870 using xda premium
SoCoolAZ said:
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
Click to expand...
Click to collapse
I'm sorry but are you on pre 2.3.4 on your X2? If so why haven't you had to update before now? Just curious.
SoCoolAZ said:
My participation in this forum saved my ars on some weird behavior my rooted x2 had been exhibiting lately. update: Nandroid backup saved me. Now, after a few days my phone is bugging me to OTA upgrade to 2.3.4. I see that this gingerbread has considerable benefit on ye ole ROM front.
Can someone help me out with a step-by-step upgrade on my rooted device? Do I need to unroot first? I have to admit to an unroot prior to my problems. Something with an app I need to get upgrade. Thanks in advance for the help.
Click to expand...
Click to collapse
I made this thread just for cases like this.
Although if you search (when working of course lol) there's tons of info on this I just compiled it together
http://forum.xda-developers.com/showthread.php?t=1757854
Sent from my DROID X2 using Tapatalk 2
So i am trying to run the update to no success. It goes into shut fown mode, comes back to a box with an arrow pointing to the android guy, it gets 20% or so and the box turns to a explanation point. X2 reboots to home screen, update failed. Tried both plugged to power and unplugged to same affect.
Cant find pete root tools but installed rom manager and rootkeeper. My root is intact and stable...i just cant get it to frickin' update from 2.3.3 .
Sent from my DROID X2 using xda app-developers app
SoCoolAZ said:
So i am trying to run the update to no success. It goes into shut fown mode, comes back to a box with an arrow pointing to the android guy, it gets 20% or so and the box turns to a explanation point. X2 reboots to home screen, update failed. Tried both plugged to power and unplugged to same affect.
Cant find pete root tools but installed rom manager and rootkeeper. My root is intact and stable...i just cant get it to frickin' update from 2.3.3 .
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
Have you modified the system
Sent from my ThunderBolt using Tapatalk 2
SoCoolAZ said:
So i am trying to run the update to no success. It goes into shut fown mode, comes back to a box with an arrow pointing to the android guy, it gets 20% or so and the box turns to a explanation point. X2 reboots to home screen, update failed. Tried both plugged to power and unplugged to same affect.
Cant find pete root tools but installed rom manager and rootkeeper. My root is intact and stable...i just cant get it to frickin' update from 2.3.3 .
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
For updating to the latest release you can't have changed any of the system files (ie frozen), and if you are rooted it's best to do a temp unroot (with a Voodoo backup of course) and make sure you boot into the Stock Recovery and attempt to flash that way. Should go without saying that you have to be on the stock rom.
GL!
SlimMan said:
For updating to the latest release you can't have changed any of the system files (ie frozen), and if you are rooted it's best to do a temp unroot (with a Voodoo backup of course) and make sure you boot into the Stock Recovery and attempt to flash that way. Should go without saying that you have to be on the stock rom.
GL!
Click to expand...
Click to collapse
Slim, i have ignored the OTA upgrade notification for 9 months. If its not broken, dont fix it theory. I had tweaked the phone with root only so that i could barnacle my tablet to the internet. Since i just saw how easily i recovered my phone back to my last nandroid backup, i figured i would try to upgrade and ROM this thing as it seems ive gotten it this far. Can someone link me to an easy to follow, step by step on "flashing stock recovery mode"? I can unfreeze programs with titanium backup and then unroot with ota rootkeeper. Just lrt me know how to stock recover, ie: phone plugged in? Unzipped file locations? External or internal sd card? I appreciate the help.
if update is failing
try unrooting with rootkeeper (keeps backup) like slimman suggested
if that doesn't work it's time to flash 2.3.4 sbf
http://forum.xda-developers.com/showthread.php?t=1317707
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
a little surprised, that you made it 9 months and phone didn't try to install overnight after several notices
I know that has happened with other moto phones like D2 and D2G
Guys root has nothing to do with not being able to receive ota.
Nothing.
Lol
It sounds to me like you need to sbf back 2.3.4
Make sure your phone is fully charged.
Do you have usb debugging enabled?
Forget about guessing games, sbf back to 2.3.4.
Root your phone via Pete's. Do not use zerg.
Install recovery
Install superuser etc. If you feel the need but Pete's su. Works fine.
Install voodoo rootkeeper.
Make the back up.
Again with these phones root has NOTHING to do with receiving or not receiving ota.
If your ota is borked there's somthing else going on. You must have removed (bad idea) or froze something
Just sbf and follow my instructions again.
Hope that helps.
As I said in my guide, all updates were done with root, and I went from2.3.3>2.3.4>2.3.5
All rooted each time all retained root via rootkeeper.
Hope that helps
Sent from my DROID X2 using Tapatalk 2
temp unroot hurts nothing, and some reported success, after failed attempts to update
Sent from my DROID2 using xda premium
sd_shadow said:
temp unroot hurts nothing, and some reported success, after failed attempts to update
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Never said it did just saying it doesn't have anything to do with not receiving updates.
What ever works right?
sd_shadow said:
temp unroot hurts nothing, and some reported success, after failed attempts to update
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
I have been there, not sure why but it has happen.
freakboy13 said:
Never said it did just saying it doesn't have anything to do with not receiving updates.
What ever works right?
Click to expand...
Click to collapse
Agree, was just trying to cover all bases but if the are gonna SBF any ways then your right, just do it and go with it.
Id just sbf and be done with it personally, i dont like otas
cm7dx2
sd_shadow said:
[/COLOR]a little surprised, that you made it 9 months and phone didn't try to install overnight after several notices
I know that has happened with other moto phones like D2 and D2G
Click to expand...
Click to collapse
LOL - I ignored it almost daily for the first three months. Okay, unfroze everything and unrooted...still can't get the update. SBF time...I'll keep ya'all posted.
My point is that, the update, can install it's self
At least that is what other user have claimed of other moto phones
Sent from my DROID2 using xda app-developers app
I have a 769 on T-mobile, Jellybean 20d. I haven't been able to successfully update to 20f using the OTA (red icon). I realize there's an upgrade file to update manually with CWM, but after reading about the various issues, I'd really rather let the OTA take care of it. I've read through the forums and done the following things before trying the OTA...
1.) Remove all links and uninstall link2SD
2.) Uninstall busybox
3.) Unfreeze all bloatware
...but it still fails as soon as it starts a system check:
"file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache"
Unless someone has more suggestions on how to "fix" my phone for the OTA, I'm thinking of trying either:
1.) Offline Lelus method, reflash 20d with root, OTA
2.) Offline Lelus method, downgrade to 10g with root, OTA
Anyone have recommendations on anything to try to get the OTA to work without flashing? If not, should I reflash to 20d or revert back to 10g?
Thanks in advance.
zaxscd01 said:
I have a 769 on T-mobile, Jellybean 20d. I haven't been able to successfully update to 20f using the OTA (red icon). I realize there's an upgrade file to update manually with CWM, but after reading about the various issues, I'd really rather let the OTA take care of it. I've read through the forums and done the following things before trying the OTA...
1.) Remove all links and uninstall link2SD
2.) Uninstall busybox
3.) Unfreeze all bloatware
...but it still fails as soon as it starts a system check:
"file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache"
Unless someone has more suggestions on how to "fix" my phone for the OTA, I'm thinking of trying either:
1.) Offline Lelus method, reflash 20d with root, OTA
2.) Offline Lelus method, downgrade to 10g with root, OTA
Anyone have recommendations on anything to try to get the OTA to work without flashing? If not, should I reflash to 20d or revert back to 10g?
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't be uninstalling busy box... It'll mess everything up. And have you deleted any bloatware? That will interfere with the update... If you want to force the update the do the following trick.. Go to settings>apps then slide to the "All" tab and look for Google services framework and tap that. Then clear data>force stop>clear data. Do that for 3-4 times. After that reboot your phone and do the trick again once and check for update.
Sent from my LG-P769 using Tapatalk 4 Beta
---------- Post added at 04:47 AM ---------- Previous post was at 04:42 AM ----------
And please search the forums or at least the T-Mobile support forums... You're lucky i even helped you. Because i don't help people with problems that are easy to resolve... They make me think they're retarded.
Sent from my LG-P769 using Tapatalk 4 Beta
geeshiet said:
You shouldn't be uninstalling busy box... It'll mess everything up. And have you deleted any bloatware? That will interfere with the update... If you want to force the update the do the following trick.. Go to settings>apps then slide to the "All" tab and look for Google services framework and tap that. Then clear data>force stop>clear data. Do that for 3-4 times. After that reboot your phone and do the trick again once and check for update.
Sent from my LG-P769 using Tapatalk 4 Beta
---------- Post added at 04:47 AM ---------- Previous post was at 04:42 AM ----------
And please search the forums or at least the T-Mobile support forums... You're lucky i even helped you. Because i don't help people with problems that are easy to resolve... They make me think they're retarded.
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
General consensus on the forums which I already searched through for hours state that link2sd and busybox need to be removed or else the OTA will fail due to changes in build.prop. I already stated I searched the forums and followed several posts. First of all, I attempted the update before uninstalling busybox, and yep, I got the red icon. I attempted the update each time after removing anything related to root. I also already stated I unfroze all the bloatware, meaning I didn't delete anything. Also I'm well aware of the trick to force OTA.
In any case, you made a lot of assumptions that were not correct, and you were rude to boot. That said, I still appreciate your reply. Guess I'm a sucker.
zaxscd01 said:
General consensus on the forums which I already searched through for hours state that link2sd and busybox need to be removed or else the OTA will fail due to changes in build.prop. I already stated I searched the forums and followed several posts. First of all, I attempted the update before uninstalling busybox, and yep, I got the red icon. I attempted the update each time after removing anything related to root. I also already stated I unfroze all the bloatware, meaning I didn't delete anything. Also I'm well aware of the trick to force OTA.
In any case, you made a lot of assumptions that were not correct, and you were rude to boot. That said, I still appreciate your reply. Guess I'm a sucker.
Click to expand...
Click to collapse
Hm, okay the only .apk's that should only be frozen is Lookout security and LGSetupWizard. Did you accidentally unfroze those?
Sent from my LG-P769 using Tapatalk 4 Beta
geeshiet said:
Hm, okay the only .apk's that should only be frozen is Lookout security and LGSetupWizard. Did you accidentally unfroze those?
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I unfroze everything. I assumed the OTA would want everything in default form, meaning no frozen applications.
Also, be sure to completely uninstall the locked bootloader cwm. (If that is you installed it)
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
BioDesigner48 said:
Also, be sure to completely uninstall the locked bootloader cwm. (If that is you installed it)
sent from my locked rooted P769 v20f
I'm on YouTube (BioDesigner48)
Click to expand...
Click to collapse
No, I didn't install any cwm after installing jellybean; I did have a copy when I was on ICS, but I removed it before the upgrade (OTA). I'm guessing that while I was messing around with applications, I probably downloaded something that modified the build.prop.
I'll go ahead and flash the v20d kdz and try the OTA again, I don't see any posts that recommend going back to v10g.
Thanks for the replies, I'll post again if it works or not just to give this thread closure.
zaxscd01 said:
I unfroze everything. I assumed the OTA would want everything in default form, meaning no frozen applications.
Click to expand...
Click to collapse
Thats why i said (should be only frozen)... Keep those 2 frozen because it's supposed to be frozen. Then try to update after.
Sent from my LG-P769 using Tapatalk 4 Beta
geeshiet said:
Thats why i said (should be only frozen)... Keep those 2 frozen because it's supposed to be frozen. Then try to update after.
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK, I'll give it a shot, then try the flash.
zaxscd01 said:
OK, I'll give it a shot, then try the flash.
Click to expand...
Click to collapse
Give me the results..
Sent from my LG-P769 using Tapatalk 4 Beta
geeshiet said:
Give me the results..
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Still status 7, debuggered etc even without unfreezing those two apks.
I went ahead and flashed v20d with root / busybox, stupidly forgot to load up Voodoo before update, and ended up with 20f no root. Tried Jcase apk twice, but didn't work likely since I already had remnants of SuperSU. Can't remove, can only revert to a previous version. *facepalm*
Flashed v20d stock (no root) and completely uninstalled SuperSU.
Repeated v20d with root / busybox, root was not successful, although busybox installed, so the kdz procedure was correct. Tried Jcase apk twice again. Failed the first time, succeeded the second time. Didn't stupidly forget to load up Voodoo, updated to 20f, restored root, and done.
I certainly made that harder than it had to be, but nevertheless: :victory:
Thanks for the advice!
Whenever I try to take the Verizon OTA update it goes into TWRP and doesn't do anything. When I reboot back it says there was an error and nothing changed. It then continues to prompt me for the update and this is very annoying. Is there any way I can manually update it or stop it from downloading and prompting me to update?
The Verizon OTA update will lock your bootloader. You've gotten lucky that you haven't been able to install it. Google around to find out how to get the service to stop bugging you to update.
Believe it or not, the answers to your questions have been covered ad nauseum. Your update fails because you are not stock. If you want to stop the nag, freeze SDM. Take the update, and you will lose the ability to use a custom recovery, kernel, or any flashable mods. Do your homework.
Sent from my Nexus 7 using Tapatalk 4
najaboy said:
Believe it or not, the answers to your questions have been covered ad nauseum. Your update fails because you are not stock. If you want to stop the nag, freeze SDM. Take the update, and you will lose the ability to use a custom recovery, kernel, or any flashable mods. Do your homework.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Tried other Roms, like the functionality of Touchwiz but hate the UI so for the time being I'll stick with the stock ROM. How do I freeze the SDM though?
Titanium backup or root toolbox pro have freezing options. If you dont want to buy tibu or rtp use es file explorer to rename it to sdm.apk.bak
Sent from my SCH-I545 using Tapatalk 2
Green Fox said:
Tried other Roms, like the functionality of Touchwiz but hate the UI so for the time being I'll stick with the stock ROM. How do I freeze the SDM though?
Click to expand...
Click to collapse
Personally, I use Titanium Backup. Rom Toolbox Pro can also freeze it, I believe. SDM.apk is what you'll be looking to freeze or remove.
Sent from my Nexus 7 using Tapatalk 4
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
bunklung said:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
Click to expand...
Click to collapse
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
Surge1223 said:
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
Click to expand...
Click to collapse
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
He isnt rooted though, so would have to root right away. If he rebooted before the update started deleting/patching files and changining permissions then it might be ok. I just would rather have no chance of the update patching the recovery or the kernel. The odin image would format the partitions and would delete the update it shouldny brick the phone because the bootloader and firmware arent patched until literally the screen shows 95.39% of the update is complete.
set_progress(0.953849);
ui_print("Patching hidden files...");
ui_print("Patching NON-HLOS modem image...");
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name
Etc..etc
And rooting is a long process? Hes going to have to root regardless if he wants to cancel it out. No reason to take an extra step to do the same thing.
Sent from my SCH-I545 using Tapatalk 2
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
Sent from my SCH-I545 using XDA Premium 4 mobile app
bunklung said:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
Click to expand...
Click to collapse
Boot and pull the battery at the same place you did before, after about 9 or 10 times the phone will tell you update failed. Then root immediately. Do not pass go do not collect $200
Sent from my BNTV250A using xda app-developers app
Surge1223 said:
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hear ya there.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
bunklung said:
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
Click to expand...
Click to collapse
Wasnt for sure if the odin decline would work but if it would have it would of saved you a lil bit of time. Glad you got her up and running.
Sent from my SCH-I545 using Tapatalk 2
bunklung said:
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
Click to expand...
Click to collapse
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
Party_Grunt said:
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
Click to expand...
Click to collapse
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
Surge1223 said:
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
Click to expand...
Click to collapse
Thanks, it did work. Unfortunately the last time this happened I was on vacation with no computer available so I was forced to take the OTA update or have no phone for two weeks. I had only rooted the week before and had not gotten around to putting in a custom recovery and bootloader, so I was SOL. Didn't even know root had been found for ME7 until last week. My timing seems to suck on this.
Now time to root and delete the upgrade files.
I'm having an issue with my OTA software update. I can download the update, but when it gets to the installation process, it just reboots into download mode. Currently running VRUAME7.
I had SafeStrap and root, but got rid of both of them, thinking that might be causing the problem. Still happening though. Any suggestions?
Did you reinstall any bloatware you and removed? Also when you removed SS did you remove it completely or just uninstall it? I had to remove it completely in order for update to take. Also if you want to keep root there is a thread that shows the way to do it. If not it should be as simple as plugging into PC running Kies and then doing a emergency recovery. Then the update will take without any issues. Hope this helps.
Sent from my SCH-I545 using Tapatalk
mdorrett said:
Did you reinstall any bloatware you and removed? Also when you removed SS did you remove it completely or just uninstall it? I had to remove it completely in order for update to take. Also if you want to keep root there is a thread that shows the way to do it. If not it should be as simple as plugging into PC running Kies and then doing a emergency recovery. Then the update will take without any issues. Hope this helps.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I never removed any bloatware. Only rooted so I could use Xposed Framework. I think I removed SS completely - the uninstall option in the app wouldn't work, so I removed it manually with terminal commands, and the SS splash screen no longer shows during boot. Also uninstalled the app for good measure. I'll try the Kies trick.
joehillier said:
I never removed any bloatware. Only rooted so I could use Xposed Framework. I think I removed SS completely - the uninstall option in the app wouldn't work, so I removed it manually with terminal commands, and the SS splash screen no longer shows during boot. Also uninstalled the app for good measure. I'll try the Kies trick.
Click to expand...
Click to collapse
Here's something interesting: after a deeper look, it says the update failed and gave and Error Code of 410. Anybody know what that means?
From what I can tell error 410 and 404 both mean that a needed resource is gone or removed and cannot be found
Sent from my SCH-I545 using Tapatalk
joehillier said:
I never removed any bloatware. Only rooted so I could use Xposed Framework. I think I removed SS completely - the uninstall option in the app wouldn't work, so I removed it manually with terminal commands, and the SS splash screen no longer shows during boot. Also uninstalled the app for good measure. I'll try the Kies trick.
Click to expand...
Click to collapse
Pretty sure Xposed is causing your problem. You might have to Odin back to stock.
Sent from my SCH-I545 using Tapatalk 4
riker147 said:
Pretty sure Xposed is causing your problem. You might have to Odin back to stock.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
So is there no way to do a clean uninstall of Xposed? I've looked into this and haven't found anything yet.
riker147 said:
Pretty sure Xposed is causing your problem. You might have to Odin back to stock.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Also, is it even possible for me to flash the stock ROM with Odin? I though the locked ME7 boot loader meant I couldn't do any of that stuff. Sorry, super noob.
joehillier said:
So is there no way to do a clean uninstall of Xposed? I've looked into this and haven't found anything yet.
Click to expand...
Click to collapse
You don't need to uninstall it. Just run the Xposed Installer, and click "Uninstall (restore app_process)".
That'll restore the altered file.
Hopefully you'll keep root through the update (I didn't) and can reinstall after the update completes.