Database Users

[Q] Offical GB Wont install

Hello all,
I am usually a reader of this forum, first time post. I have done a search on this but I can't get it to install.
My current phone is running Froyo 2.2.1 system version 2.3.340. I have rooted it with the Z4mod root version 1.3.0.
Now, when I saw the update come down I uninstalled all my root applications and removed my root from my phone. It downloaded in no time flat. About 11 minutes yesterday morning at 9:49AM. (first attempt) And then I started the install and it shut down correctly and turned back on. When it turned back on it did what it was supposed to, had the unbox with android icon. The load bar gets to about 35% then the unbox changes to the triangle with the ! in the middle. Then it boots up Froyo and states the install failed. I attempted about 5 more times then said lets see what verizon says. This was probably the worst thing to do cause they did jack. The store I went to had 25 bricked droid X's yesterday. I was the only one to just have it fail and Froyo to work correctly. To quickly shorten this story they refused to assist in installing Gingerbread.
Any Ideas on getting it installed?

Try wiping data through stock recovery and if that doesn't work, you could try an SBF

Thank you for info. I ended up SBF'ing the phone. Says I need to re-activate the phone because there is a blue triangle next to the signal bars.
I know this is probably a repeated question but how do i re-activate the phone. Do I need to take it to Verizon?!

NVM, figured it out.

same thing happened to me. however i did not remove my z4root on froyo. install failed. did not try sbf, was hoping i wouldn't have to.

biggest reason ive found thus far amongst several different threads/ and friends with droids, root really didnt have much to do with it, as long as you were unrooted again the update went well, bloatware seemed to be the issue. myself i had uninstalled a lot of dumb memory eating stuff while i was on froyo such as the nfl and nfs games, blockbuster app so on, when i pulled the update originally it didnt detect that so it fubared me on getting the ota update. sbf the way to go, im so in love with my DX for being idiot proof atm i could dance lol

XXUAMDN or XXUAME2

Does anyone know which is newer, and what changed between the two?

I have XXUAME2, and I've updated my firmware through Kies. I don't remember what I had before. This one must be newer.
Haven't noticed any change, apart from the blue default background in the wallpapers is now a bit darker without the sun flare. I might've noticed a few very minor things in the settings, though I don't remember what they were.

Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.

StuartTheFish said:
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
Click to expand...
Click to collapse
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.

Tozenator said:
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Click to expand...
Click to collapse
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.

StuartTheFish said:
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
Click to expand...
Click to collapse
Interesting, very interesting. I might look into rooting one more time, then. Thanks!
Funny how you helped me instead of the other way around. Thanks again, I hope more people notice your thread and maybe you'll get your answer!

where is this new firmware xxuamdn, havent found anything about it..
im having camera, battery drain, slowness issuess still hope it fixes..
Sent from my GT-I9500 using xda app-developers app

I have none of those issues, but never did even on the older version. All I did was Google for galaxy s4 update and I found a download link for it along with Odin. But there's also XXUAME2 out there and I don't know which one I'd be better having. Unless the only difference is the radio depending on where in the world you are?

[Q] Hit a snag

Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks

tangler27 said:
Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
Click to expand...
Click to collapse
Utility is gonna take care of it for you...I'm certain. I cant think of anything that caused it though. That's kinda weird. But if I were you I would just stick with the stock ROM with that issue and just troubleshoot it and if it happens again...hit it with the utility again
Also if you don't mind losing camcorder the 4.2.2 ROMs are great and don't require safe strap as Kong as you unlock boot loader through the utility. But will void your warranty.
Good luck! And follow those instructions on Matt's utility perfectly!
Sent from my XT907 using xda app-developers app

I goofed, and I don't know how I did it

Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...

Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse

Accidentally soft-bricked moto g4 plus xt1644

If this has been answered somewhere in this forum I apologize and please direct me to the answer. Back when I got my phone in march I rooted my phone using one of the guides on this discussion page so I could have open wifi tethering. While I did have some hiccups not the least of which being soft-bricking my phone and having to flash what I thought was a stock rom but ended up being a android 7.0 rom that seemed to work fine on my phone. Learning my lesson I made a backup right then and there of the stock install as well as two afterwords once I got everything set up the way I wanted. Flash forward to today my phone is bugging me for a seemingly benign system update and after ignoring it all day I dumbly install it without thinking. Now no matter what I do booting my phone only takes me to the TWRP recovery menu. I have tried running all of my backups and nothing is working. Of course because this has been a couple months the image I used is gone so I can't use that. Would that even work, wtf did I do. Let me know if anyone has an answer I will be eternally grateful

Ok problem solved.... after whiping my phone several times I attempted an install of cypherOS. and well.... it worked. I think I'll stick to this . Just let this post die I guess... I am going to set my alarm and go to bed I am very tired and have work in the morning