Database Users

EA28 OTA

I just activated my girlfriend's phone and immediately it prompted for update, so I did. To my surprise it was not DL09, but instead EA28. So after some google searches I found this:
http://phandroid.com/2011/02/03/samsung-fascinates-ea28-update-coming-to-fix-emergency-calling-bug/

The site is basically right, they repackaged dl09 with the emergency calling bugfix and pushed it out with a new build number.

just got mine... I'm gonna have a seizure in a public place to test it out.

Does any one know if one click root will work with this update
Sent from my SCH-I500 using XDA App

Deathbeaver said:
Does any one know if one click root will work with this update
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It worked for me on DL09 and this isn't that much different so I'd say yes.

Skrazz said:
just got mine... I'm gonna have a seizure in a public place to test it out.
Click to expand...
Click to collapse
Youtube...

The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Sent from my SCH-I500 using XDA App

Deathbeaver said:
The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
There is a thread on ODIN. Simple directions, I thought.
Sent from my SCH-I500 using XDA App

So how does one "Make instantaneous emergency calls from a locked device in a time of need"?

Deathbeaver said:
The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Just as a side note if your having to redo the phone from scratch make sure to put the pit file in the pit on odin otherwise the phone will not activate!
Click to expand...
Click to collapse

One Click root works just fine! Just completed root!

I believe I was able to root successfully but when I try to flash ClockwordMod, it doesn't seem to be working. ROM manager says its flashed and has the latest version, but when I boot into recovery it is definitely not ClockwordMod. I cannot do backups or choose a file from SD to install.

PantsOnFire said:
I believe I was able to root successfully but when I try to flash ClockwordMod, it doesn't seem to be working. ROM manager says its flashed and has the latest version, but when I boot into recovery it is definitely not ClockwordMod. I cannot do backups or choose a file from SD to install.
Click to expand...
Click to collapse
When you flash a new ROM it overwrites CWM, so you'll have to re-install it with Odin.

What is pit in general and why it is needed?

CNemo7539 said:
What is pit in general and why it is needed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=771426
may answer some questions
http://forum.xda-developers.com/showthread.php?t=723596
may answer others
the search tool is great. google works too.

Update broke my phone!
I just saw a screen forcing the update upon my phone. I clicked "OK" but when the EA28 update installed itself on my phone, it locked my phone into a cycle of trying to install it again and again. The baseband version shows S:i500.04 V.EA28, the Build number shows SCH-I500.EA28, but the update keeps trying to install the update. It gives a Prompt to Install-Reboots Phone-Prompt to Install-Reboot Phone... I managed to get it to stop for a little while by scheduling a deferral of the update until tomorrow. Does anyone know how I can keep the update from trying to install?

Yeah I just went to ask if there is an update and it said yes. Afraid to update because who knows if it'll break root....
Sent from my SCH-I500 using XDA App

Why suggest people to mess with pit in odin? You do NOT need to do this. Geez, people make this mistake enough on their own. Pda, choose file, press start... thats it.
Sent from my stock 2.1 unrooted, fully bloated Fascinate

EA28 broke my phone
knmb323 said:
I just saw a screen forcing the update upon my phone. I clicked "OK" but when the EA28 update installed itself on my phone, it locked my phone into a cycle of trying to install it again and again. The baseband version shows S:i500.04 V.EA28, the Build number shows SCH-I500.EA28, but the update keeps trying to install the update. It gives a Prompt to Install-Reboots Phone-Prompt to Install-Reboot Phone... I managed to get it to stop for a little while by scheduling a deferral of the update until tomorrow. Does anyone know how I can keep the update from trying to install?
Click to expand...
Click to collapse
I managed to get my phone to stop rebooting every 3 minutes by ending the InnoPath Active Care process and clearing the cache. But when I woke up this morning, the phone was at the emergency recovery screen. It went into a cycle of rebooting that made it as far as media scanner. I got it to stop rebooting by turning ON wifi (I suppose that's because Active Care needs WiFi off to do an OTA). Does anyone have any suggestions on how to stop this "Feature" that is rebooting my phone?

You tried pulling the battery (soft reset) i presume? After that theres factory rest, then odin back to stock
Sent from my stock 2.1 unrooted, fully bloated Fascinate

Freaking out here might have bricked my phone...

So I was told to install the deodexed [sp] of the GB leak, so I did on top of my rooted, non deodexed version, without wiping. After this I wiped my data a few times, as I heard it would be best to do. Well, after doing so... my phone won't stop bootlooping. I can't access the bootstrapped bootloader, only the stock Moterola one, and I cleared my data with it hoping it would work too...
Help please? How do I "sbf" back to stock or whatever?

Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.

I hope its ok to post this link here:
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html

I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml

tried flashing it again, same thing happened. It failed at "switching phone to BP pass through" apparently. help me please

thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Now just do the system only sbf.it will work
Sent from my DROIDX using XDA App

Do you have the latest drivers installed? Try using RSDlite 4.9!

thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day

z06mike said:
Do you have the latest drivers installed? Try using RSDlite 4.9!
Click to expand...
Click to collapse
i found rsdlite 4.9 didnt recognize my phone but 4.8 did

itzjen said:
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
Click to expand...
Click to collapse
Like what did you say to them?

tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
this is totally being lazy AND the reason why everyone is raising their prices on insurance and why ppl like motorola are locking bootloaders. if it is too much or you're too lazy to do it. dont do it in the first place. sbf isnt hard there are a gazillion guides to sbf'ing. not trying to be rude but seriously?

Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.

thewanton said:
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
Click to expand...
Click to collapse
you have to sbf to .340 use z4 root to root then install DX bootstraper reboot to recovery flash gbrooted.zip if you get stuck in bootloop go into factory recovery and wipe data reboot download and install D2 bootstrapper yes D2, boot into recovery and flash gbrooteddeodexed.zip and let it try and boot it SHOULD bootup after a couple of minutes, if it doesnt get into stock recovery and wipe data, reboot
also it could bootloop because of corrupt downloads

tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...

slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.

itzjen said:
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
Click to expand...
Click to collapse
which is a problem that was caused by YOU because you take that and sbf

thewanton said:
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
Click to expand...
Click to collapse
most ppl overlook that as a typo

Funnyface19 said:
which is a problem that was caused by YOU because you take that and sbf
Click to expand...
Click to collapse
Yes it was a problem that I caused but at that momment I got scared and wasn't sure what I was suppose to do,and because I have no internet at home because i'm never home I use wireless tether when im there and my phone was messed up so wasn't able to look at guides to fix it.....So the easiest thing I thought of is calling them.I wouldn't have mind fixing it but again I wasn't able to at that momment.

I had the same thing happen. Put the letter p at the end of the file name and move it to c:\ this worked for me on rsd lite 4.8 I just kept pulling the battery and retrying until it went through
Sent from my Xoom using XDA Premium App

meshdub said:
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
Click to expand...
Click to collapse
I'd just like to point out that you don't actually need rsd lite 4.8 or higher. 4.7 has worked perfectly for me the several times I have SBF'ed

Can't Upgrade to 4.1.83 AT&T

Hello,
I have the version 1.4.57 with GingerBlur 2.5 and try update via OTA to version 1.4.83 and when you start the installation restarted fourth bar and it appears the doll with a warning sign and not much else happens, I have to remove the battery to power off and restart the operating system, anyone know how I can fix it?
Greetings!

Flash the sbf for 1.83 found here in the forums. Over in the development section there is a guide on flashing with Rsd lite.
Sent from my MB860 using XDA App

You cannot install the update over any mods, you have to sbf first.

And if I use the Restore GingerBlur Bloatware?

i had this same problem cause i was rooted, instead download the motorola updater on your computer and use that to update, then when its done your phone might say installation failed, but it actually really didnt fail, if you check the phone settings it shows your on 1.8.3 on 2.2, thaT WAY YOU STILL HVE ALL YOUR OLD APPS AND ETC.

unnkown95 said:
i had this same problem cause i was rooted, instead download the motorola updater on your computer and use that to update, then when its done your phone might say installation failed, but it actually really didnt fail, if you check the phone settings it shows your on 1.8.3 on 2.2, thaT WAY YOU STILL HVE ALL YOUR OLD APPS AND ETC.
Click to expand...
Click to collapse
Uh, but you don't know what may have failed about the update. Just cos the phone settings say 4.1.83 and 2.2.1 doesn't mean all is ok!
Also, you can update over root. You can't however update over deodexed files as with GingerBlur or GreyBlur!
OP, flash 4.1.57 sbf, then update OTA, or try flashing 4.1.83 sbf right off the bat, then Gingerbreak and install GingerBlur again.
Sent from WinBorg 4G using XDA Premium App

Um...where is the 4.1.83 sbf download?

[Q] 4.5.621 uprgrade failed

I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack

Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision

rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack

Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk

update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.

From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.

4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe

Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2

missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.

Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error

Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app

palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help

Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time

Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk

deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk

Droid Razr M xt907 Kitkat Update Failed

I'm using a droid razr m xt907 by verizon. Yesterday an update was released for 4.4.2 kitkat, my phone is still rooted and i can't find the safest way to unroot it so i can get the update. Does anyone know the best way to unroot and make sure everything's normal again so that the 4.4 update will work this time? It stops at around 25% into the update. Thanks for any help.
Edit: I've tried a factory restore, i unrooted completely. My kernell is normal, my stock recovery is normal. The update just isn't working, and i don't know the best way to fix it. My bootloader is locked, so there was never any custom recovery or ROM's installed.

I'm having the same problem. I unrooted before the update but still not working. The update get's to about 25% of install then fails. I've tried about 4 or 5 times today. Factory rest and uninstalling root didn't help either

mikegt11 said:
I'm having the same problem. I unrooted before the update but still not working. The update get's to about 25% of install then fails. I've tried about 4 or 5 times today. Factory rest and uninstalling root didn't help either
Click to expand...
Click to collapse
Exactly, i can't figure out what i'm supposed to do. Ive tried about that many times, and i've tried factory restoring, i've wiped the cache, etc.

Factory reset.
RSD to stock 4.1.2 in case some system app is missing.
Skip setup.
Try the update again.
Or just RSD to the new version.
Those would be my next steps.
Sent from my Nexus 7 using XDA Free mobile app

Coronado is dead said:
Factory reset.
RSD to stock 4.1.2 in case some system app is missing.
Skip setup.
Try the update again.
Or just RSD to the new version.
Those would be my next steps.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try this tomorrow when i have a chance, thank you for responding.

Coronado is dead said:
Factory reset.
RSD to stock 4.1.2 in case some system app is missing.
Skip setup.
Try the update again.
Or just RSD to the new version.
Those would be my next steps.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
do you know any good tutorials for how to use rsd for this? cuz i want to just rsd to the new version if you can help me find the files to do that, i have rsd lite already.

help
shadowwolfsl said:
do you know any good tutorials for how to use rsd for this? cuz i want to just rsd to the new version if you can help me find the files to do that, i have rsd lite already.
Click to expand...
Click to collapse
i got same problem. after download 446 mb update. try to instal. work about for 30 percent then suddenly restart and says that update failed
my device is rooted. then i remove root from the SU menu and keep failed to update
what should i do?

supercahyo said:
i got same problem. after download 446 mb update. try to instal. work about for 30 percent then suddenly restart and says that update failed
my device is rooted. then i remove root from the SU menu and keep failed to update
what should i do?
Click to expand...
Click to collapse
Personally i just modified the .xml file and loaded it via RSDLite.

shromy said:
Personally i just modified the .xml file and loaded it via RSDLite.
Click to expand...
Click to collapse
same thing that i did

Im mid process but heres the only answer ive found....
THERE IS HOPE HERE LOLZ
If ya all do let me know how the full strip and downgrade went....
If u find another way pls share info w me as well...
Lj-
Sorry all being a new user they would not let me post a link so I cut it up.......Still would not le5 me send it but u can email me directly and I'll gladly send u a direct copy or look on andromods the answer is there
---------- Post added at 08:15 PM ---------- Previous post was at 07:54 PM ----------
supercahyo said:
i got same problem. after download 446 mb update. try to instal. work about for 30 percent then suddenly restart and says that update failed
my device is rooted. then i remove root from the SU menu and keep failed to update
what should i do?
Click to expand...
Click to collapse
Step by step on andromods...and how to reroot there as well
Lj-
Sorry won't let me post links yet....

droid razr M kitkat update fail
I would like to know a solution, I'm tired of trying and do not get even with rsd lite.
this is my mail: [email protected]

galestz said:
I would like to know a solution, I'm tired of trying and do not get even with rsd lite.
this is my mail: [email protected]
Click to expand...
Click to collapse
because you have not modified the xml file after decompressing the entire zip.

It just won't work !
shadowwolfsl said:
I'm using a droid razr m xt907 by verizon. Yesterday an update was released for 4.4.2 kitkat, my phone is still rooted and i can't find the safest way to unroot it so i can get the update. Does anyone know the best way to unroot and make sure everything's normal again so that the 4.4 update will work this time? It stops at around 25% into the update. Thanks for any help.
Edit: I've tried a factory restore, i unrooted completely. My kernell is normal, my stock recovery is normal. The update just isn't working, and i don't know the best way to fix it. My bootloader is locked, so there was never any custom recovery or ROM's installed.
Click to expand...
Click to collapse
I also had a Razr M. i unroot it by SuperSU, but it won't update properly, same like others, 25%, then fail.

Steve977 said:
I also had a Razr M. i unroot it by SuperSU, but it won't update properly, same like others, 25%, then fail.
Click to expand...
Click to collapse
i got it functioning after rsd lite back to stock after a factory restore

shromy said:
because you have not modified the xml file after decompressing the entire zip.
Click to expand...
Click to collapse
I have found the solution, you have to edit the XML file that is in the ROM. and delete the lines containing the words ("oem" and "var"). then you put the phone in fastboot mode and use the rom with the modified file will have only about 18 steps then when the last file billboards will ask you turn on the phone manually and status, restart your phone and enter mode fastboot again and finished well. NOTE: remember to put the usb debugging before starting everything. everything you do will be at your own risk, but so what I Realize, and it worked and I have my razr m with kitkat and before I could not for the same reason of the root. thank you all

shadowwolfsl said:
I'm using a droid razr m xt907 by verizon. Yesterday an update was released for 4.4.2 kitkat, my phone is still rooted and i can't find the safest way to unroot it so i can get the update. Does anyone know the best way to unroot and make sure everything's normal again so that the 4.4 update will work this time? It stops at around 25% into the update. Thanks for any help.
Edit: I've tried a factory restore, i unrooted completely. My kernell is normal, my stock recovery is normal. The update just isn't working, and i don't know the best way to fix it. My bootloader is locked, so there was never any custom recovery or ROM's installed.
Click to expand...
Click to collapse
:victory::victory::victory::victory::victory:
I can resolve if u want reply me

Does it work while it is Rooted ?
galestz said:
I have found the solution, you have to edit the XML file that is in the ROM. and delete the lines containing the words ("oem" and "var"). then you put the phone in fastboot mode and use the rom with the modified file will have only about 18 steps then when the last file billboards will ask you turn on the phone manually and status, restart your phone and enter mode fastboot again and finished well. NOTE: remember to put the usb debugging before starting everything. everything you do will be at your own risk, but so what I Realize, and it worked and I have my razr m with kitkat and before I could not for the same reason of the root. thank you all
Click to expand...
Click to collapse
I'm sorry, but dows it work while my phone is rooted ? before i noticed your solution, i had to delete all root apps and SuperSU (along with the root) to update it. And Failed.

galestz said:
I have found the solution, you have to edit the XML file that is in the ROM. and delete the lines containing the words ("oem" and "var"). then you put the phone in fastboot mode and use the rom with the modified file will have only about 18 steps then when the last file billboards will ask you turn on the phone manually and status, restart your phone and enter mode fastboot again and finished well. NOTE: remember to put the usb debugging before starting everything. everything you do will be at your own risk, but so what I Realize, and it worked and I have my razr m with kitkat and before I could not for the same reason of the root. thank you all
Click to expand...
Click to collapse
im getting phone returned fail y

solution
Adriantech said:
:victory::victory::victory::victory::victory:
I can resolve if u want reply me
Click to expand...
Click to collapse
plz help me iwant your help

djdrews4357 said:
im getting phone returned fail y
Click to expand...
Click to collapse
princeabdullah1555 said:
plz help me iwant your help
Click to expand...
Click to collapse
We can't help either of you, if you don't give us details.
Sent from my HTC6525LVW using Tapatalk