Database Develop

[Q] Cannot update to Gingerbread

Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.

rawrzar said:
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
Click to expand...
Click to collapse
You may not have updated like you thought. V6 should have gotten rid of root for you. I had to do a factory restore, wipe the data and image, all of it. When I went back to do all that stuff, I still had the Bionic splash screen, and it is because of that little change, that I was not able to update myself. You may have something similar going on with your phone, just in a different place. Anything beyond doing that, just ask, but it should take care of you. Make a backup first, just in case. You will have to set everything up again.

markapowell said:
You may not have updated like you thought. V6 should have gotten rid of root for you. I had to do a factory restore, wipe the data and image, all of it. When I went back to do all that stuff, I still had the Bionic splash screen, and it is because of that little change, that I was not able to update myself. You may have something similar going on with your phone, just in a different place. Anything beyond doing that, just ask, but it should take care of you. Make a backup first, just in case. You will have to set everything up again.
Click to expand...
Click to collapse
Thanks for your reply. I have performed a factory reset, but the update still fails. I also notice that after the reset, SuperUser is still listed under my installed apps.

rawrzar said:
Thanks for your reply. I have performed a factory reset, but the update still fails. I also notice that after the reset, SuperUser is still listed under my installed apps.
Click to expand...
Click to collapse
Does the update fail, or does it just say no update available?
Sent from my VS910 4G using xda premium

mtmichaelson said:
Does the update fail, or does it just say no update available?
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It fails. the update downloads, and reboots to install. But about half way through the installation, the phone reboots again. when the home screen comes up, a screen pops up saying "update failed or incomplete".

I had the same problem. Did you reinstall the stock recovery program? I also had the bionic boot image from revolt1.5, which was messing things up. Once I reverted back to the stock boot image, the update went through.

JohnnyAn said:
I had the same problem. Did you reinstall the stock recovery program? I also had the bionic boot image from revolt1.5, which was messing things up. Once I reverted back to the stock boot image, the update went through.
Click to expand...
Click to collapse
How would I go about reverting back to stock image? sorry , I don't know much about this.

rawrzar said:
How would I go about reverting back to stock image? sorry , I don't know much about this.
Click to expand...
Click to collapse
The cubed had a stock revo file that he posted somewhere in the dev forum. Just flash that with CWM and you should be good to go.
Sent from my VS910 4G using XDA App

I am in a similar situation but when I try to update to gingerbread it says there is no update available. I too still have supreuser installed after reflashing from revolt 1.5 to thcubed zv4 rooted stock and then updating its to zv6. How can I get my phone to download zv7?
Sent from my VS910 4G using XDA App

jdleider said:
I am in a similar situation but when I try to update to gingerbread it says there is no update available. I too still have supreuser installed after reflashing from revolt 1.5 to thcubed zv4 rooted stock and then updating its to zv6. How can I get my phone to download zv7?
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Apparently the update hasn't been pushed to all phones yet...there's several of us on xda that still don't have it. Jackpot08 is working on a .tot but until then, we just have to wait.
Some people have called Verizon and they can't force the update to your phone, so don't bother with that.

JohnnyAn said:
The cubed had a stock revo file that he posted somewhere in the dev forum. Just flash that with CWM and you should be good to go.
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Thanks! Found it and got it working. Just waiting for the update now.
jamRwoo said:
Apparently the update hasn't been pushed to all phones yet...there's several of us on xda that still don't have it. Jackpot08 is working on a .tot but until then, we just have to wait.
Some people have called Verizon and they can't force the update to your phone, so don't bother with that.
Click to expand...
Click to collapse
Thanks for the info, guess the update hasn't been pushed to my phone yet.

I have been on stock for a week now, and its been horrible. I forgot how slow this was before devs streamlined the system, and how many rooted apps/functions I used.
I am going back to revolt today. I will see GB when the .TOT is available.

rawrzar said:
Hey everyone. I rooted my phone a while back (around June), but it got unrooted during the update in July and I haven't bothered rooting it again. But now, when I try to update to Gingerbread, I always get a message saying "Update failed or incomplete" after downloading and rebooting. I noticed I still have SuperUser installed, so I tried unrooting with SuperOneClick, but SuperOneClick is stuck on "Waiting for Device". I have also tried to reset to factory settings, with the same result. Does anyone know how to fix this? Thanks.
Click to expand...
Click to collapse
Were you attempting to update to gingerbread by using the TOT? Or was there an update available though your service provider?
If you were getting a failure through the network, it's likely because you haven't gone back to stock recovery and still have ClockWorkMod Recovery installed. Use DevToolKit to fix this.
If you are using the TOT and getting a failure, do a checksum on the TOT file.

I've been working on this actively as I have a revolution. LG has informed me the update push completed on November 2. Nobody at VZW or LG can tell me why some Revolutions haven't gotten the push.
VZW Engineering has apparently been alerted, but LG has been unresponsive to me to-date.
I'm not waiting and putting together a one-package manual update kit, but I do want to give LG and VZW time to give me an update. Thing is, it's been over 72 hours now and there hasn't been one, so my patience is wearing thin.
It's disappointing that LG hasn't responded to any of my inquiries... I'm asking the right people behind the scenes.

hatoncat said:
I've been working on this actively as I have a revolution. LG has informed me the update push completed on November 2. Nobody at VZW or LG can tell me why some Revolutions haven't gotten the push.
VZW Engineering has apparently been alerted, but LG has been unresponsive to me to-date.
I'm not waiting and putting together a one-package manual update kit, but I do want to give LG and VZW time to give me an update. Thing is, it's been over 72 hours now and there hasn't been one, so my patience is wearing thin.
It's disappointing that LG hasn't responded to any of my inquiries... I'm asking the right people behind the scenes.
Click to expand...
Click to collapse
I'm in Rochester NY and never got one. I gave it til 2 days ago and threw on the TOT.

Madert said:
I'm in Rochester NY and never got one. I gave it til 2 days ago and threw on the TOT.
Click to expand...
Click to collapse
Yeah, I'm leaning towards drafting an idiot-proof TOT guide, it's just going to be really upsetting if I have to do that. If this was Apple, and not LG, we wouldn't even have this thread right now.
Option-click .ipk and done... not that Apple would even let ~1-5% of a device "miss" an update.

So, I've confirmed a few things with LG officially:
1) The ZV7 update has not been pulled.
2) LG was not aware of this issue until I reported it.
3) LG is just now starting the process of investigating.
I can't flash a TOT on mine right now, as LG may want to capture my unit for evaluation. I'll know more soon, hopefully by Monday.

Verizon was trying to push an update on me back on the 11th. It was the V6 update, as I was running V4. It failed, and I manually ran the tot through with LGNPST. Since thecubed had posted the V7 tot as well, I ran that through as well.
I probably did not need to go from V4 to V6 to get to V7, but I figured it wouldn't hurt.
But as I said, the only push I had received was on the 11th, well after the 2nd.
As a semi-newbie, it was easier to push the tot on than anything else.

LG Engineering is at least listening... they have agreed to capture my unit and send me a brand new Revolution simultaneously.

antiwesley said:
Verizon was trying to push an update on me back on the 11th. It was the V6 update, as I was running V4. It failed, and I manually ran the tot through with LGNPST. Since thecubed had posted the V7 tot as well, I ran that through as well.
I probably did not need to go from V4 to V6 to get to V7, but I figured it wouldn't hurt.
But as I said, the only push I had received was on the 11th, well after the 2nd.
As a semi-newbie, it was easier to push the tot on than anything else.
Click to expand...
Click to collapse
Did you have clockwork recovery installed when you tried to get Verizon s update
Sent from my gingervolt`ed revolution

[Q] Is it possible to update if you flashed a different stock rom?

Hi!
Is it possible? I just bought a white Note Open Line but didn't noticed that it was released from India, My Blue one came from Singapore and already getting official update while the white one did not. Now my question is If I flash a stock ROM http://forum.xda-developers.com/showthread.php?t=1424997&page=3, would I be able to get an official update OTA? I wanna change the firmware the same as the blue one.
Many Thanks!

If you flash new firmware like LA4 you can't update using Kies .
Sent from my GT-N7000 using XDA App

ranjan.alva said:
If you flash new firmware like LA4 you can't update using Kies .
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Thanks for replying! I update mine over the air. Currently I'm on KL2, if I change the white note with KL2 same as mine will I be able to download updates over the air if there is new update? Or if I flash any of the stock rom even if there's an update I won't be able download official update over the air?
Thanks!
Sent from my GT-N7000 using Tapatalk

bratboo said:
Thanks for replying! I update mine over the air. Currently I'm on KL2, if I change the white note with KL2 same as mine will I be able to download updates over the air if there is new update? Or if I flash any of the stock rom even if there's an update I won't be able download official update over the air?
Thanks!
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Yes you will get updates. find the latest update available for your region then flash it.

What if your phone is rooted?
I would like to know if OTA updates are possible if you have rooted it. I gather from my experience in the past that you cannot. My phone now fails to connect to the server.
TBH, it is not a drama form me, I have no lag, and the phone seems to work brilliantly, apart from battery life. I had to root in order to get even reasonable battery life, as the bloatware was killing it.
The other issue is, as far as I can tell, we cannot get root access for stock LA4 OTA updates. Is this true, and can anyone say why? Of course, I may have that completely wrong.
Generally, after my attempt at using the Note without root for a month, I prefer root to a new ROM, at least until ICS. Even then, I think I'll wait until the bugs are ironed out, and then get an update that is rootable.
---------- Post added at 09:21 AM ---------- Previous post was at 09:09 AM ----------
OK, I have just read another of dr.ketan's most excellent and informative posts, and I think I can see the answer.
Real soon now, I'll have enough information and courage (and enough time) to start flashing custom roms at will!

After rooting phone you wont get OTA updates. and no warranty.

ranjan.alva said:
After rooting phone you wont get OTA updates. and no warranty.
Click to expand...
Click to collapse
I know many people in this forum who continue to have updates OTA with rooted phones.
Sent from my GT-N7000 using xda premium

You may get OTA after root,Only if you have selected right ROM for your region.
But remember if you update with OTA, you will lose Root. And now a days newer update is non rootable. so you cant root it again after update.

dr.ketan said:
You may get OTA after root,Only if you have selected right ROM for your region.
But remember if you update with OTA, you will lose Root. And now a days newer update is non rootable. so you cant root it again after update.
Click to expand...
Click to collapse
Thank you for this info! I just found out that my white note came from Samsung India and from what I heard they update pretty long. I won't mind if I will lose the root after as long as I got the white one the same firmware with my blue one so they will update at the same time. Thanks again!
Sent from my GT-N7000 using Tapatalk

What is the overall strategy for someone like me who is not intending (yet) to flash
dr.ketan said:
You may get OTA after root,Only if you have selected right ROM for your region.
But remember if you update with OTA, you will lose Root. And now a days newer update is non rootable. so you cant root it again after update.
Click to expand...
Click to collapse
Many thanks for that, but what is the overall strategy for someone like me who is not intending (yet) to flash ROMs? Should I wait until an OTA ROM is rootable, then unroot, get an OTA update, and the root again? Or should I go the whole hog and start flashing stock ROMs instead.
I am not (yet) talking about flashing custom ROMs. All I want is root access and the stock ROM.
BTW, I sincerely appreciate the time you personally have spent helping all of us with an enormous range of issues on this and related matters. I run my own support forums for a particular software product (which I was involved with writing) and I understand very well how much time and effort is involved with keeping up this level of support.

One thing i like to say what is wrong to update it manually rather then OTA?
OTA is the choice, who dont care Root. If you like to Root your device, just forget OTA, there is no guarranty wat thing when gets available, just try to use your device in best way with watever available right Now.
I dont see near future someone find out a method to root latest Or each n every ROM. this is hide n seek game, if someone find it, samsung will patch that thing in next update. so it become non usable.
What i believe is get Root n CWM/Mobile Odin Pro. Install any ROM, you like to try with Rooting function active. If you dont like just change it. Itz just simple.
Root also get you facility to keep Backup of your data n all.

dr.ketan said:
One thing i like to say what is wrong to update it manually rather then OTA?
OTA is the choice, who dont care Root. If you like to Root your device, just forget OTA, there is no guarranty wat thing when gets available, just try to use your device in best way with watever available right Now.
I dont see near future someone find out a method to root latest Or each n every ROM. this is hide n seek game, if someone find it, samsung will patch that thing in next update. so it become non usable.
What i believe is get Root n CWM/Mobile Odin Pro. Install any ROM, you like to try with Rooting function active. If you dont like just change it. Itz just simple.
Root also get you facility to keep Backup of your data n all.
Click to expand...
Click to collapse
+1 .. Totally agreed..

jeromepearce said:
Should I wait until an OTA ROM is rootable, then unroot, get an OTA update, and the root again? Or should I go the whole hog and start flashing stock ROMs instead.
I am not (yet) talking about flashing custom ROMs. All I want is root access and the stock ROM.
Click to expand...
Click to collapse
C'mon, mate, you're an Aussie: since when do the Aussies let others decide what they should or shouldn't do? You're going to wait for Samsung to let you have what you need when they see fit? Or are you going to take it yourself when and how you want?
Rooting is the way to go for the most people around here. That way you:
1. get the newest updates only a couple of days after they are released (good people in Dev section need just a day or two to let you download new stock Roms, already rooted)
2. get to play with lots of custom Roms out there - it's such fun, you wouldn't believe
3. get to backup your phone - system and data both - so you are safe to play on without fear that something bad is going to happen: you always have your backups to fall back on if it does
4. get to test various kernels, themes, rooted apps and whatnot to your heart's content
5. get enormous fun doing all of the above
Just follow the first link in DrKetan's signiture, read carefully, follow the instructions to the letter, and you'll never look back.

OK, I am getting the message
chasmodo said:
C'mon, mate, you're an Aussie: since when do the Aussies let others decide what they should or shouldn't do? You're going to wait for Samsung to let you have what you need when they see fit? Or are you going to take it yourself when and how you want?
Rooting is the way to go for the most people around here.
...
Just follow the first link in DrKetan's signiture, read carefully, follow the instructions to the letter, and you'll never look back.
Click to expand...
Click to collapse
OK, I am getting the message
BTW, I'm not just an Aussie, I'm an Aussie By Choice! Took me 10 years to get citizenship because my wife is disabled and they kept refusing us based on that (it went to the minister in the end). So, no, I definitely do not let others decide what I can and cannot do!

chasmodo said:
Just follow the first link in DrKetan's signiture, read carefully, follow the instructions to the letter, and you'll never look back.
Click to expand...
Click to collapse
Amen - this is all you need to know. Don't worry about getting updates from Samsung... your in better hands here.

Official Motoblur ICS for the Droid 4 possibly leaked

Just saw this thread at droidforums: http://www.droidforums.net/forum/droid-4-roms/208767-stock-motoblur-ics-droid4.html
Can anyone confirm if this is legit?
EDIT: Removed link to the update file for everyone's safety. This is not an update you want to install. It will take you off the update path and attempting to flash one of the currently available fastboot files will result in a brick.

I pulled the same thing by the cake method earlier today but was afraid to flash a unknown.

I tried, based on the instructions on the page, and as usual, cheesecake won't work for me. I get the "account needed" prompt. I'll try again tomorrow.

Thanks!
I'm downloading it now. I hope this works with Safestrap and I get to keep root. Or at least be able to re-root again. Have to be carefull. Need GSM to work

The day after I sold my T-Mo Sensation, and the day before I get my VZW Droid 4. Looks like the gods have decided not to smite me today.

Booted Safestrap. Flashed stock 215.
Can't update to 219 So no wonder I couldn't update to ICS... Here I go again...

It sounds like a couple of people over on DroidForums HAVE gotten this to load. To paraphrase what hashcode said over there, be very very careful with this guys. There are quite a few Razr owners now stuck outside of the upgrade path and unable to use fastboot to restore after flashing an ICS leak. I think I am going to hold off on this one personally. What I am REALLY hoping to see is some improvements to CM9, AOKP, and Gummy come out of this. Particularly the data issues.

Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.

Die Bruine said:
Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.
Click to expand...
Click to collapse
You are a brave man Try using OTA RootKeeper. It worked with the last update. I would be very interested to see if it works with the ICS update as well.

Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.

SGMD1 said:
Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.
Click to expand...
Click to collapse
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.

Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894

kwyrt said:
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.
Click to expand...
Click to collapse
Downloading .215 as we speak, but I'm not getting my hopes up. No big deal though, VZW is overnighting me a warranty replacement and I've got an old phone I'm using for the day.
EDIT: .215 failed at 6/18 as well.
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
Click to expand...
Click to collapse
There were a several things with this ICS build that were a bit disappointing (native ICS screenshot function didn't work, no "Charge only" mode when connected via USB to PC) but no root access was the dealbreaker. I knew flashing the .219 file was a risk based on what happened with the RAZR ICS leaks but I just figured I'd be the guinea pig
I had the same problem you did when attempting to install it, so I flashed the clean .219 fastboot file and then the ICS update was successful.

build.prop
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894
Click to expand...
Click to collapse
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop

build.prop 219
rumgool said:
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop
Click to expand...
Click to collapse
Okay... here is the 219 build.prop zipped

You gotta be kidding me pffffff. Those guys at Motorola check eeeeeeverything. Thnaks for the build.prop btw rumgool. But now it hangs on Motorola_XT894....3gp. Unbelievable...
Finally got it going. But like you said, had to flash SBF. That's some pretty scary **** . I'm used to Milestone / Droid 1 flashing and I've flashed a Razr before. This one takes twice as long. So for you wanting to flash SBF, don't be alarmed. It takes a while, a very loooong while.

Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case

GSM working!!!!!!
Yes!!!! audio over 3G GSM!!!!
Finally. Don't know what works and what doesn't. But audio works and you have GSM settings right from the get go. Now I'm gonna eat, then I'm gonna play and after that I'll tell you what I think of it.
Thanks guys!

podspi said:
Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case
Click to expand...
Click to collapse
The new fastboot files are nothing like the old sbf's. Wrong radio, different build number and many other things can cause it to fail. Then your stuck in fastboot mode with a soft brick.
Sent from my DROID4 using Tapatalk

This is a really nice build! I am not at all sorry to have risked being stuck, to be honest.
Everything appears to work very well so far and I am posting from Chrome Beta.
Still looking for the downside...

Update from zip aborted

In an attempt to go from ICS 206 to 215, I followed the instructions step by step and using the utility, when I get to the step where it says instill zip file from SD card, I navigate to "D4.6.16.215.zip", apply it, and it says update aborted.
My phone will now no longer boot beyond the M Dual Core screen. It is simply blank. Does anyone have any ideas?

i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)

icebear8 said:
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
Click to expand...
Click to collapse
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.

strakajagr said:
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
Click to expand...
Click to collapse
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.

strakajagr said:
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
Click to expand...
Click to collapse
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX

icebear8 said:
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
Click to expand...
Click to collapse
Tried that. Same result. I have to believe this has something to do with the 206 build that I'm on, though I don't know why that latest utility doesn't address this since the 206 sticking thing seems to be a problem that was addressed so long ago.

\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------
icebear8 said:
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
Click to expand...
Click to collapse
VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip this is the fastboot GB 219 files correct? my files are all over the place lol

I just booted to recovery and did a data wipe/factory reset, and I was back to stock 206. I didn't use that xml file because I'm not upgrading from GB.

well i just bricked my self on the update lol

Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.

jsnweitzel said:
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
Click to expand...
Click to collapse
In terms of names - are you using boot.img or ICSFIX.img for the name of boot on .215?

Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.

strakajagr said:
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
Click to expand...
Click to collapse
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.

mrAdvo said:
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
Click to expand...
Click to collapse
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app

If your using the modified D4 tool I made then you should name it ICSFIX. However I think we can shorten the process further and will try to work on that tonight.
Sent from my DROID4 using Tapatalk 2

azrael293 said:
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215

podspi said:
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
Click to expand...
Click to collapse
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol

azrael293 said:
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
Click to expand...
Click to collapse
Ok, I was just afraid for a moment I had wasted a bunch of nail-biting time or something
I think a lot of people get tripped up at the boot.img --> ICSFIX.img step. Especially because the instructions tell you to rename it to ICSFIX, not ICSFIX.img (which Windows may or may not do for you automatically, depending on your settings).
That being said, it is still incredibly easy to move from one leak to the other with the utility, it is incredibly awesome.(Thanks jsnweitzel!)

Safestrap won't open after install

I've been following the guide here to flash Jelly Bean onto my Atrix HD, so I could next flash the Batakang ROM as the guide recommends. I got Jelly Bean onto the device, but after I install Safestrap and try to open it, it immediately displays "Unforuntately, Safestrap has stopped working" and closes itself. I think I installed the right version (the one for Razr HD, tried both 3.04 and 3.05. I think it works with the Atrix HD as well). Voodoo OTA shows that all checkboxes under Status are checked, so I don't think it's a root issue.
I did a search for Safestrap and I didn't really see anything related to my problem. I'm kinda at a loss here. Maybe I got a bad flash and need to redo everything?

redphazon said:
I've been following the guide here to flash Jelly Bean onto my Atrix HD, so I could next flash the Batakang ROM as the guide recommends. I got Jelly Bean onto the device, but after I install Safestrap and try to open it, it immediately displays "Unforuntately, Safestrap has stopped working" and closes itself. I think I installed the right version (the one for Razr HD, tried both 3.04 and 3.05. I think it works with the Atrix HD as well). Voodoo OTA shows that all checkboxes under Status are checked, so I don't think it's a root issue.
I did a search for Safestrap and I didn't really see anything related to my problem. I'm kinda at a loss here. Maybe I got a bad flash and need to redo everything?
Click to expand...
Click to collapse
Try downloading safe strap again maybe you had a bad download.
Sent from my MotoAHD

Update superuser and binary
Sent from my MB886 using Tapatalk 2

Youngunn2008 said:
Try downloading safe strap again maybe you had a bad download.
Sent from my MotoAHD
Click to expand...
Click to collapse
SirHoover2010 said:
Update superuser and binary
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Updating Superuser and binary fixed it. I thought I had done that already, so I didn't think to try that. I feel kinda stupid now.
Thanks to both of you for your help.

Don't I did the same thing and got kinda mad for about 10 min till I checked that lol
Sent from my MB886 using Tapatalk 2

lost root
Had same problem and tried to up date Su Binary and lost root. Need Help. I am on ota 4.1.1 it said su has stopped and have not had root since. Any ideas?

fullpozzy said:
Had same problem and tried to up date Su Binary and lost root. Need Help. I am on ota 4.1.1 it said su has stopped and have not had root since. Any ideas?
Click to expand...
Click to collapse
You have voodoo ota root keeper with a backup of su? I'd restore root with that then make sure superuser is updated and move it to system/apps then update binary
Sent from my MotoAHD

Tried using voodoo and no success. Voodoo shows phone as rooted and have a back up of root, but doesn't have root access and no way of accessing back up of root. I can hit temp unroot but nothing happens. Any other suggestions?

I'm having this same issue with my Galaxy S4, build NC5. I rooted using Towelroot v3, then installed Safestrap (JFLTEVZW-3.71). Everything seemed to be working fine, I installed the recovery, rebooted, and now I can't open the app. This is frustrating because I decided I would rather use a different recovery, and want to remove Safestrap. I can get into recovery on boot, but no matter what I do the app won't open. SuperSU/binary seems to be up to date. Any ideas?

ahouse3733 said:
I'm having this same issue with my Galaxy S4, build NC5. I rooted using Towelroot v3, then installed Safestrap (JFLTEVZW-3.71). Everything seemed to be working fine, I installed the recovery, rebooted, and now I can't open the app. This is frustrating because I decided I would rather use a different recovery, and want to remove Safestrap. I can get into recovery on boot, but no matter what I do the app won't open. SuperSU/binary seems to be up to date. Any ideas?
Click to expand...
Click to collapse
I doubt you're having the same issue, because you have a completely different phone than the one contained within this thread. You posted your question in the forum for the Motorola Atrix HD.
Seeing as this is your first post, I will simply refer you to here: http://forum.xda-developers.com/galaxy-s4-verizon
Good luck over there.

quasihellfish said:
I doubt you're having the same issue, because you have a completely different phone than the one contained within this thread. You posted your question in the forum for the Motorola Atrix HD.
Seeing as this is your first post, I will simply refer you to here: http://forum.xda-developers.com/galaxy-s4-verizon
Good luck over there.
Click to expand...
Click to collapse
Sorry, I didn't think this sounded like a device-specific issue, and this was the only thread anywhere that seemed to address it. But anyway thanks for showing me the ropes . I ended up fixing it by changing SELinux from enforcing to permissive (I had done this to install Safestrap, but then it reverted back). Problem solved!

ahouse3733 said:
Sorry, I didn't think this sounded like a device-specific issue, and this was the only thread anywhere that seemed to address it.
Click to expand...
Click to collapse
Right, but you also should have noticed that the last post was back in December 2012. That's because the Atrix HD later had its bootloader unlocked, thus negating the need for anything Safestrap related on this phone. So if you really needed help, it's unlikely that anyone here would be able to help you, because no one is using Safestrap anymore. Which is why I was trying to steer you towards someone that could actually help.
Just another reason to use the correct forum. Otherwise, glad you figured it out.

I know this may be the wrong section.. But do u by any chance still have the safestrap apk because all of the downloads are bad now and I can't find one anywhere on the internet . I really need it.. My computer quit working so I can't unlock the bootloader right now.. I just need an easy recovery because I want to use xposed but I need recovery in case anything goes wrong. Any help will be appreciated