Looking for some help. Trying to install new update, but keeps failing with the android logo and a triangle with exclamation mark after attempting to install. Not sure what I hit but when taking battery out got the following screen. I was on 1.57 with gladroot. Had to sbf flash during the original update process some time ago as didnt get run scripts correctly first time through
Flash back to 26, then 57, then 83. Clean and fresh update is what you need.
Sent from WinBorg 4G using XDA Premium App
had a feeling that is what was going to be said.. going to leave it until I have more time, dont feel like sitting and setting my phone back to how I want it.
When the triangle and exclamation appears you don't have to take out the battery. Only touch the right low corner of the screen and the reboot display appears. I had the same problem at first but the information appeared indicated me what was the problem. Once corrected the update ran well.
logichoops said:
had a feeling that is what was going to be said.. going to leave it until I have more time, dont feel like sitting and setting my phone back to how I want it.
Click to expand...
Click to collapse
I've done it so many times myself now, but I like tinkering. The day I got beta I flashed back to 4.1.26 three times while at work before I ended up being successful with everything because I kept making "operator errors"! I planned for this and took my wall charger to work so I could boot into recovery. Took me over an hour each time to get fully updated! lol
Yeah, you have to flash to a clean version. Most likely you have a mod installed on your phone, and you can update with a mod on your phone.
Are either enabling sideloading or adding the tethering apn that gladroot does for you considered a mod? Just curious what I'm in for when I try to go from rooted 1.57 to 1.83 OTA
Related
So, im trying to install an update that i received a notification for...i believe its the one that helps with 3g connectivity and what-not. But while trying to install it, I rebooted to a black screen with a ! inside a triangle and the little android standing next to it...what does that mean?
I let it sit for a GOOD long while, yet nothing happened. Does this mean i can never update?
***This has been solved. My last post in the thread says what i did.***
If you are rooted and you tried to do the OTA then you'll brick your phone.
i was rooted with stock. the OTA came up while i was texting and normally i hit reject, but i accidently hit ok while texting and now every time i start up, it says "Powering Down..."
Any OTA flashed over a rooted device will brick it, I believe.
Edit: Well I found this. May help.
http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Superthrust said:
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Click to expand...
Click to collapse
Glad to hear you're good to go!
Don't flash OTAs when you're rooted next time!
^_^_^
I have an unlocked AT&T Atrix running on another carrier (GCI of Alaska) that I rooted with WeaselyBreak (yes, that is a Harry Potter joke, I actually used GingerBreak). I have been trying to do an OTA upgrade to GB with no luck. I have not done anything with my bootloader. I have cleared the Superuser App data before the attempts as well as stopping it before one attempt. I went into Titanium Backup and unfroze all of my bloatware as well. Still no luck. I have downloaded the update four times now and everytime it gets ~25% through the unpacking screen before it changes to "Danger Will Robinson!!" android screen. And I have to reboot to a "Update Failed!" message.
Any ideas?
Banger_AK said:
I have an unlocked AT&T Atrix running on another carrier (GCI of Alaska) that I rooted with WeaselyBreak (yes, that is a Harry Potter joke, I actually used GingerBreak). I have been trying to do an OTA upgrade to GB with no luck. I have not done anything with my bootloader. I have cleared the Superuser App data before the attempts as well as stopping it before one attempt. I went into Titanium Backup and unfroze all of my bloatware as well. Still no luck. I have downloaded the update four times now and everytime it gets ~25% through the unpacking screen before it changes to "Danger Will Robinson!!" android screen. And I have to reboot to a "Update Failed!" message.
Any ideas?
Click to expand...
Click to collapse
Flash 1.8.3. SBF and try again?
If the update is failing that early it's probably where the update is checking to see if all of the 'system' files match up. You have something non-stock on your phone's 'system' files. It does not have to be bootloader related to throw that warning icon. Do you have swype beta installed? hdmi mirroring? webtop mod? If so you'll get the Android warning icon if you try to apply the update.
I haven't flashed before and was going to avoid starting (I hear it's hard to stop).
I finally gave up on the OTA route and wired my phone to my PC so that the Motorola website could have manglefication access to my phone. It did some stuff, my PC made a lot of noises (some of which my phone seemed to respond to), and
a few awkwardly erotic minutes later my phone looks vaguely the same as it did before. I say vaguely because it appears the update actually worked and it does look a bit different.
If it hadn't, I would have had to learn how to flash, which I understand may involve heavy drinking and a trench coat. I appreciate your response, but I have learned to stick to the adage my IT geek friends have taught me "Doing what is easy is not always right, but it is always easy."
Thanks!
After countless hours of research, I decided to unlock my bootloader and to root my Motorola Atrix 4G. With success, I was happy to have everything working and installed the Darkside Custom Rom. I let a friend borrow my phone, and they saw the AT&T system update and they decided to install it. They bring back the phone and the system update has finished and was installing. The phone powers off and starts to install the update. 10% into the install, it stops, and I got the little green droid man with the /!\ behind him. I take out my battery, place it back in after 30seconds. It powers on, boots up, powers off and tries to load the update again. I restart it, but this time quickly going into RomManager and starting it up in Recovery Mode. I go to restore the phone using the file I backed up from the TitaniumBackUp app, everything backs up except the system. I plug my phone into my laptop, and everything is in the folder. I performed a system/factory reset, downloaded the last Gingerbread update, but nothing helps. Anything I try to load it says "Installation aborted". No matter if it's the original update or a ROM I download. Looking up other forums, I notice others that have downloaded the Darkside ROM have had the same; if not similar issues. I apologize for the length of this message, but I wanted to put in as much detail as I could so you know exactly what the issue is. I look forward to hearing from someone, and thank you in advance!!!
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
nickdeal said:
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
Click to expand...
Click to collapse
Thanks a ton! How would I go about doing that?
You need to download motorola RSD app to you computer. Search XDA for stock firmwares and download one. You will then need to use the button combo to get in to RSD. Connect the phone to your computer and make sure it recognizes. I had an issue where one of my laptops would not recognize the phone for anything. I had to use a different laptop. Once it's done you should be back to stock. The bootloader should be unlocked still. Just root and flash your ROM of choice.
Sent from my MB860 using XDA App
The phone was working great, other than the noise cancelling mic cancelling out my voice, but I thought since the update was available, I might as well do it. Once I got on ICS I was having quite a few issues: overall slower, delay in the screen turning on, hotter battery, longer time to charge, wallpaper would flash on before the HTC screen when booting up, there were more just can't remember right now.
I hear about the Global update and think it may fix some of the problems I was having, but they got worse. Now I still have everything I did before (except maybe the hot battery) Also have 3 new issues now: the screen doesn't come back on when I take it away from my ear during a call, browser goes white when going to a new page and I have to reload the page, can't post on any forums in the browser.
Here's the process I went through getting the Global (copied from another forum that I was updating as I was going)
I downloaded it from android police, got to step 6 of the directions, looked away from the phone to see what step 7 was. The phone vibrated and is now on the screen with the green down arrow and 2 in a circle around it. Says "Updating Software from Verizon Wireless" with a green progress bar. Hope I did it right.
That went through rebooted to HBOOT, pressed vol. up twice. It checked everything. Rebooted. Pressed. Vol. up to install. Upadated everything. Pressed power to reboot.
Took a little while on the white HTC screen, now says "Andoid is upgrading..." "Optimizing application [some number] of 77." I think I did it right.
Just checked and everything is right. Woo-Hoo! Not that I'll ever use global, I was hoping it may have fixed some of the bugs I was having, but no
Also of note, I didn't pull the battery. My case is hard to get off, so I just turned off fast boot and that worked.
Click to expand...
Click to collapse
What do I do at this point? My phone is getting less usable by the day as I keep noticing all these bugs.
Wipe your phone clean and use the RUU that android police posted today to install the latest patched OTA clean. That's what I'd try anyway.
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
VooDooCC said:
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
Click to expand...
Click to collapse
There are plenty of knowledgeable members here to walk you through it if you just shoot someone a pm. It's all very simple.
As for your problem, try the ruu hopefully that works I'm not sure about the mic canceling out your voice that might be a hardware problem let's hope not
Sent from my ADR6425LVW using xda app-developers app
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
VooDooCC said:
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
Click to expand...
Click to collapse
The RUU should wipe it but you can go into recovery and wipe /data and /system to remove the current rom.
Making sure I got all this right, but won't be trying until tomorrow afternoon. Only at 40% charge and going out of town in the morning and need the phone.
1. Rename the Android Police download to PH98IMG.zip and copy to sd card (don't have to extract anything out like I did on the .1)
2. Boot into recovery (vol. down and power)
3. Let it start flashing (If it starts automatically, how do I get to the wipe /data and /cache options?) I know it should be wiped auto. but I want to do it myself to make sure.
4. Pray to Andy that there's no bugs this time.
You need to boot into bootloader, not recovery, that will happen when you do the battery pull then start it volume down + power. I'm pretty sure the RUU will wipe everything so you should be good.
Problem with newest ICS
The new ICS has a problem with the browser. Links are squirrelly when touched; sometimes
no reaction, sometimes checks every box on the page. Just does not feel right when moving
around on web pages.
Seems ok to me, I'd recommend Chrome over stock unless you need Flash support anyway.
Sorry, I got the terms confused on the terms. I knew it was vol. down and power though
I finally got around to flashing the RUU, all is well so far, will report back if anything changes.
I'm s-off but my bootloader is unlocked. Do I need to relock the bootloader before flashing the RUU.
Sent from my ADR6425LVW using xda app-developers app
There is a tradition on rezounds to always install an RUU two times in a row, then let it boot up normally before installing custom things like hboots, recoveries, or ROMs.
I used to read posts of people saying that it must be done twice to assure everything gets installed right, and to avoid problems.
So, I recommend doing the ruu twice in a row, especially if your phone was not stock beforehand.
Howard
p.s. my favorite browser is opera mobile.
If s-off and unlocked, there is no need to relock to install an RUU.
Turns out I got a little too anxious. I thought stuff was working, but that was just because I was thankful that I installed the RUU right, still new to this. Still having all the same problems though
When you say install twice in a row, should I just try installing it once again tomorrow or twice since I downloaded an app or two?
Also, you say twice, then boot up normally, when I installed this it just booted up after the install was finished. Is there a way to install it again before it boots for the first time?
method
Make sure the Android Police 3.14.605.12 renamed PH98IMG.zip on your sdCard.
Boot up with Volume down, Power to get into hboot. It will ask your permission with a
Volume up and then run the update. I think they mean after 1st boot, answer English,
and get out of setup with No and default until steady. Do a factory reset in Settings,
Storage and boot up again. Then shut her off again and restart as previously to run that
PH98IMG.zip again.
After the next boot up, insert actual information like Google etc. to start Google Play
and fetch your favorite apps. Then you're running 100% stock.
noticed the same thing with in calls. Pull the phone away from your ear and the screen should come back on, but it seems delayed. I usually have to tap the power button twice to get the screen back on.
Running simplistic 3.0 which is based on the newest leak, after flashing the leak.
FWIW I have the issue with the screen not coming back on after pulling the phone away form your ear as well, however I'm on the ICS OTA, not the global.
I never had the problem on the ICS OTA, but I also only had that for a couple of days before getting the global (.1) from Android Police.
In the process of doing the second flash. As per michaels instructions.
I went to Verizon yesterday and tried seeing about exchanging the phone, since it's having all these problems, and was told no. That it's so common and pretty much every phone has the same things, so it's considered to be working and I just have to wait on a patch. He then told me that if I wanted I could void my warranty and s-off it to go back to GB. I found that kind of odd. Then he tried pushing the Razr on me, I said no I like HTC so then he told me that the Droid 4's are having the same problems too.
Sooo.... I had the OTA to kitkat, lost my root, decided i wanted it back. Downgraded to 4.3 and rooted, safestrap all of that succesfully. Ran it for about 2-3 weeks, figured i'd go and follow the rest of the directions to get back to kitkat, turns out i messed it up good. I still have the nc5 build but the mk2 baseband and 4.3.
Now, whatever the heck i did, i tried a factory reset then tried to flash a stock 4.3 over it just to really clean it up, turns out, it didnt like that. Now kies will not even recognize the device, and when i tried surge's mk2 restore, it fails. I haven't been able to find a 4.4.2 stock to re-odin and try that. I obviously did search and still am searching at this moment but i must be blind or something.
Now i have a phone that says "firmware failed, please connect to kies and run a repair" or whatever. When i try to odin to the mk2, it says "sw rev. check fail : fused 6 binary 5" which i assume has something to do with the build number/bootloader for kitkat thats still on my phone. Am I screwed or is this recoverable? Thanks peoples.
I really need my phone for work. It's used numerous times to make calls because i'm in a service technician position. I can't go without it for even 1 weekday, if i can't get this figured out by sunday at noon, i will have to bite it and get a new phone. Cannot be phoneless on monday. It would literally cause me to lose my job.
Odin this full wipe http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
joshuabg said:
Odin this full wipe http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
Click to expand...
Click to collapse
I've tried it about 4 times now, 1 time it got to about 80% done then failed at write for persdata or something of the sort. The other 3 times it stops within 10 seconds. I'm not sure what else to do. It doesn't seem like there is anything else i can do to be honest. I might be effed.
On try #21, still no go. Ugh
BlueForce64 said:
On try #21, still no go. Ugh
Click to expand...
Click to collapse
Are you trying the same file over and over again? If so, maybe you got a bad download. Did you check the MD5 checksum to see if it matches? Maybe you could try downloading it again.
Sent from my NCC-1701
Yeah i am, but it fails at different points. The same 3 different points though. I'll try to re-dl it and try again. Anything is worth a shot at this point. Otherwise someone can get a free broken s4 if they want lol
Finally achieved success. It took about 40 times but it finally went through. The last 10 were tried with a new dl, i just didnt give up, the one time it worked i made sure i ran odin in administrator. I had an odin going without administrator so i loaded up a new one with it on and right when the 1st one failed i started the second one up and it had the blue progress bar go all the way to the right side of the screen and come back around through the left eventually running into itself, as soon as the progress bar began to overlap the screen it was also saying invalid response for bar length or something in the upper left text until that went down screen and started back on the top. In any case, woohoo it's working! Thanks guys, guess i won't need a new phone yet.