Sorry if this has already been posted somewhere, but I'm on a friend's phone and he doesn't have the XDA app and the site isn't being very cooperative with his phone.
I took the recent OTA this morning and now I'm stuck in a boot loop at the Moto logo. Prior to installation, my phone was completely stock and not rooted. I can get into fastboot in the short time that the M logo is off, but it kicked me right back out seconds later and begins attempting startup again. I did a factory reset from stock recovery and it still loops.
Is there an fxz out for this yet, or does somebody have a link to download the new OTA so I can adb push it onto my sd card to try to install it again?
I'm in the same boat, took OTA from 4.1.2 and now bootlooping. My phone was rooted prior to the OTA but I can live without it.
How does the saying go? If I had a penny for every ...
Anyways, this is a prevalent issue so I'm surprised no one seems to be able to find it as it is the most common issue since this OTA has come out, so for the umpteenth time, here is the link to fix you up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
PLEASE read it carefully and then re-read it again and then read it one more time BEFORE you even attempt to do it.
Good luck!
iBolski said:
How does the saying go? If I had a penny for every ...
Anyways, this is a prevalent issue so I'm surprised no one seems to be able to find it as it is the most common issue since this OTA has come out, so for the umpteenth time, here is the link to fix you up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
PLEASE read it carefully and then re-read it again and then read it one more time BEFORE you even attempt to do it.
Good luck!
Click to expand...
Click to collapse
That's the download I needed. Thanks.
Should be able to install it manually from the phone if you push the OTA to your sd card (if you're stock) to avoid having to go through rsdlite
Related
Hey guys, I somehow managed to soft brick my verizon GS3 this afternoon. I just need a little help in getting the thing back up and running and possibly an explanation on were I went wrong. I thought I had unlocked the bootloader and then rooted the phone. I managed to install TWRP 2.5.0.0 and do a backup. Then I installed a custom ROM and got the infamous "Software not authorized" message with the yellow triangle.
1st, is it possible to get this far with the bootloader still being locked??
2nd, If I understand correctly, I need to use ODIN to go back to stock and start over. Correct? Or is there another way to salvage this situation. If I have to go back to stock, can someone point me to the latest files? I've found links to a lot of different ones and I don't want to make a bad situation worse. BTW, I can't get into recovery but I can get into ODIN mode.
Any help is greatly appreciated!!
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
scheirere said:
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
Click to expand...
Click to collapse
Yea, I soft bricked once and was able to boot into recovery by holding volume up, power, and home at the same time while the phone was off. I thanked my lucky stars I had a nandroid backup. I would make sure you unlocked the boot loader properly. When I first started rooting YouTube was great for instructions. I would post a link to a YouTube video but it won't allow me until I have ten posts, I swear some of these rules are retarded. Anyway search in YouTube having visual and audio guide helps a lot. good luck!
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
CreativeSin said:
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
Click to expand...
Click to collapse
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to . Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
CreativeSin said:
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to .
Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
Click to expand...
Click to collapse
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
CreativeSin said:
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
Click to expand...
Click to collapse
Well now that you're back and rooted, if you're planning on doing any more flashing any time soon then I recommend you install boot menu manager. If you've previously installed safestrap or bootstrap, clear their data and uninstall them before installing bmm.
With that done, you've just made your phone a little safer from bricking because bmm allows multi rom booting, which are somewhat independent of the primary system. Refer to this thread for more info on how to make systems, etc.: http://forum.xda-developers.com/showthread.php?t=2115715
The first thing you'd want to do is make sure your apps/data is always backed up at all times with apps like titanium backup. Create 2 or more systems so that you can try the bmm compatible custom ROMs which are in the dev section if you want to try any of them. But please, read all instructions, warnings, requirements, etc. carefully before attempting any flashing in general.
The thread I posted in my earlier post above will have links to the specific custom ROMs. If you're doing any other kind of flashing, make sure to again, read instructions carefully and take your time with learning all of this.
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
kunal2711 said:
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
Click to expand...
Click to collapse
Use boot menu manager instead of bootstrap recovery
Sent from my MB865 using XDA Premium 4 mobile app
i recently used rsd to flash back to stock after a failed rooting/unlocking attempt. i believe the flash was successful, and the phone seems to be preforming just fine. the problem comes up when i try to check for the kit kat update. the phone says that it needs me to set up a motorola account. when i press setup it says connecting to servers please wait. i dont believe it will ever actually connect to the server though since ive waited upwards of ten minutes with no results. if there is anything to fix this? any help would be greatly appreciated, and my apologies in advance if this is a stupid question. im currently on 9.30.1.xt926.verizon.en.us
I left my experience getting to kitkat with my post here helping someone. http://forum.xda-developers.com/showpost.php?p=52696764&postcount=5
Since you already have 9.30.1 firmware, you skip to the KIt ota zip download and follow the directions from the post I left if you want to sideload the OTA. Otherwise it should notify you of an update. I got a update notification but already had the OTA on my sd card so went ahead and did that way instead.
pmccarthy7745 said:
i recently used rsd to flash back to stock after a failed rooting/unlocking attempt. i believe the flash was successful, and the phone seems to be preforming just fine. the problem comes up when i try to check for the kit kat update. the phone says that it needs me to set up a motorola account. when i press setup it says connecting to servers please wait. i dont believe it will ever actually connect to the server though since ive waited upwards of ten minutes with no results. if there is anything to fix this? any help would be greatly appreciated, and my apologies in advance if this is a stupid question. im currently on 9.30.1.xt926.verizon.en.us
Click to expand...
Click to collapse
UOTE=yujikaido79;52720878]I left my experience getting to kitkat with my post here helping someone. http://forum.xda-developers.com/showpost.php?p=52696764&postcount=5
Since you already have 9.30.1 firmware, you skip to the KIt ota zip download and follow the directions from the post I left if you want to sideload the OTA. Otherwise it should notify you of an update. I got a update notification but already had the OTA on my sd card so went ahead and did that way instead.[/QUOTE]
Thanks man, I think I'm just gonna wait until the update is sent to my phone, I'm a little gun shy after my last experience flashing anything
Hi,
So I've taken the time to create some videos showing exactly what my problems are, and I'll start with the first one.
Ever since the last update for KK was released, I have been unable to update (due to a second issue we'll get to in a bit) so I've just been delaying the update until I've had the time to troubleshoot the other issue. However, I believe not updating is causing the update screen to randomly attempt to appear and then disappear really quick, you'll see it in the video. It mostly happens when I'm watching videos, or using the browser at all. It's super annoying as it stops videos and just generally interrupts anything I'm doing.
Non-the-less, here is the video.
http://quickvid.org/watch.php?v=3SLcUguDAyT
In addition to this, I cannot currently update as my recovery is either corrupt or just not working right.
Here is a video of what happens when I try to boot into recovery...
http://quickvid.org/watch.php?v=RvnxD-fXrUu
Since the recovery is not working, when I try to do the update, it reboots the phone, attempts to go into recover (sits at the moto logo for 2 mins then boots the phone like normal). It does this about 5 times then it just fails the update.
I've tried to flash multiple recoveries, and this all started when I flashed Clockwork mod recover (which obviously did not work). I've even tried flashing back to stock recovery, but with no luck.
Any help is appreciated!
-------------
Oh and as a side note, in case anyone is wondering where these videos are uploaded to, it's a website that I own called QuickVid. It's essentially Imgur, for videos. So if you ever need to upload a video to post on the forums or something, feel free to use the service
masters1222 said:
Hi,
So I've taken the time to create some videos showing exactly what my problems are, and I'll start with the first one.
Ever since the last update for KK was released, I have been unable to update (due to a second issue we'll get to in a bit) so I've just been delaying the update until I've had the time to troubleshoot the other issue. However, I believe not updating is causing the update screen to randomly attempt to appear and then disappear really quick, you'll see it in the video. It mostly happens when I'm watching videos, or using the browser at all. It's super annoying as it stops videos and just generally interrupts anything I'm doing.
Non-the-less, here is the video.
http://quickvid.org/watch.php?v=3SLcUguDAyT
In addition to this, I cannot currently update as my recovery is either corrupt or just not working right.
Here is a video of what happens when I try to boot into recovery...
http://quickvid.org/watch.php?v=RvnxD-fXrUu
Since the recovery is not working, when I try to do the update, it reboots the phone, attempts to go into recover (sits at the moto logo for 2 mins then boots the phone like normal). It does this about 5 times then it just fails the update.
I've tried to flash multiple recoveries, and this all started when I flashed Clockwork mod recover (which obviously did not work). I've even tried flashing back to stock recovery, but with no luck.
Any help is appreciated!
-------------
Oh and as a side note, in case anyone is wondering where these videos are uploaded to, it's a website that I own called QuickVid. It's essentially Imgur, for videos. So if you ever need to upload a video to post on the forums or something, feel free to use the service
Click to expand...
Click to collapse
If your bootloader is locked, you won't be able to flash a custom recovery. Depending on what version you are on, you want to get the correct FXZ to retrieve the recovery.img file and flash that. Flashing anything else could result in issues.
First things first, please let us know the answer to the following questions:
What version of Android is your system on?
Is your bootloader unlocked?
Hi thanks for taking the time to reply.
1. Kitkat 4.4.2 183.46.10.XT926
2. Yes my bootloader is unlocked.
masters1222 said:
Hi thanks for taking the time to reply.
1. Kitkat 4.4.2 183.46.10.XT926
2. Yes my bootloader is unlocked.
Click to expand...
Click to collapse
Then you just need to get the correct FXZ, extract the recovery.img file from it and then reflash it to your phone from your PC with the following command:
fastboot flash recovery recovery.img
You can get the FXZ from here -> http://sbf.droid-developers.org/download.php?device=5&file=902
I will try this, I believe I have done this in the past, but I'll try again and post results.
Okay so I just flashed that recovery, and now I have an android guy laying down with a red ! triangle coming out of the chest. Doesn't sound good.
Maybe I am flashing wrong?
I am booting into the bootloader, with USB connected, then using fastboot with the following command flash recovery recovery.img and it is finishing.
masters1222 said:
Okay so I just flashed that recovery, and now I have an android guy laying down with a red ! triangle coming out of the chest. Doesn't sound good.
Maybe I am flashing wrong?
I am booting into the bootloader, with USB connected, then using fastboot with the following command flash recovery recovery.img and it is finishing.
Click to expand...
Click to collapse
OH wow come to find out this is the stock recovery. I just need to hit up + power button to get the menu. Okay great this might have fixed the issue then.
I'll try and do the update now and see how it goes.
Edit: The update took! Seems that I was just flashing the wrong thing the whole time.
Now to just find out how to restore root via flashing.
iBolski said:
Then you just need to get the correct FXZ, extract the recovery.img file from it and then reflash it to your phone from your PC with the following command:
fastboot flash recovery recovery.img
You can get the FXZ from here -> http://sbf.droid-developers.org/download.php?device=5&file=902
Click to expand...
Click to collapse
Oh and I don't think I ever said thanks, so thank you! this worked and the update took!