Database Users

Problems Installing Latest Atrix Update

I kept getting a pop up message on my phone saying a new software update is available for my device. It appears to be an Android update MB860 v4.5.141. So I downloaded the update with no problems but the update won't install.
When I clicked Install the phone shut down as it's supposed too. But the update fails and I keep getting a black screen with Android & an exclamation point inside a Triangle. I have to pull the battery and restart but once the phone boots up it shuts down again to attempt to Install the update and again I get the black screen with the Android and exclamation point. The phone is unusable at this point. Any ideas?
My Atrix is NOT rooted.

I just tried the manual update and it won't work because the phone can't start up long enough, it shuts down before I can do anything. How can perform a factory reset if the phone shuts off before I can get into the menu to select factory reset? Will a factory reset even fix this problem?

Hi,
check this:
http://forum.xda-developers.com/showpost.php?p=22636544&postcount=5
Good luck

Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.

NY Yankee Pride said:
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you flashed a custom recovery? If you have, boot into it by holding volume down after turning the device on. Then hit volume down until you have selected recovery. Then hit volume up to boot into recovery. From there, wipe the cache partition and reboot.
If you haven't flashed custom recovery... I dunno what to tell you. It's strange that the OTA update isn't working on a non-rooted, non-unlocked phone.

I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.

NY Yankee Pride said:
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
Click to expand...
Click to collapse
Make sure phone is off.
Press and hold the volume down button, then press the power button.
When text appears on the screen, release the down volume button. Then press the down volume button again and watch the text change... keep going until text reads "Android Recovery". Press up volume button. IF YOU go to far (too many down presses) keep pressing down and it will cycle back...don't press the up volume expecting to go back.
You are now in recovery...if you have a screen with a big triangle and an exclamation point, press both volume buttons at the same time. A menu will appear. Use volume buttons to move to the option you want and the power button to select it. Most likely, you'll want "factory reset". do that.
If you end up with any other screen (not the triangle) then you have a custom recovery and you knew everything I just told you...

Yeah it looks like a factory reset is my only option at this point, I was hoping to avoid that. Thanks for all the help and tips.

I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?

NY Yankee Pride said:
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
Click to expand...
Click to collapse
No. Factory reset does not clear out rooting, unlocking, or any modifications to the bootloader or recovery.
for root: There's a root checker app in marketplace to test root access. If you do have root access you need to unroot before applying the update.
for unlocked: the only way I know to tell is when you power on the phone the word "unlocked" will appear at the top of the screen.
bootloader and recovery: if you have a locked bootloader than you should have stock bootloader and recovery = ok to apply OTA update. If you're unlocked, do NOT apply the OTA update. A few people have succeeded somehow, many do not.

Thanks Gnac. I just noticed when I turn the phone on it does say "unlocked" at the top left of the screen, I never noticed that before. I know for sure the previous owner was using it on AT&T so I don't know why he would have unlocked it. I think I'll just skip the update to avoid any further problems.

I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.

NY Yankee Pride said:
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
Click to expand...
Click to collapse
titanium backup's freeze function (you need to buy the paid version) can fix this. Just freeze Updater to stop the pop up.

Thanks for the suggestion but that won't really work for me since I have no experience in rooting and I'm way too worried about bricking it to even try that.

You say you bought your phone used, and haven't rooted or modified it. Are you on AT&T? If so, and were it my phone, I'd be taking it to an AT&T store and having them check it out.
We are great at looking for alternate routes to fix our own stuff and using "official routes" as a last resort (as it requires putting it all back to stock first), but to me, this is a clear case of their own update screwing up for some arbitrary reason -- totally not your fault.

I don't think that will work because the bootloader is unlocked so I have to assume the previous owner rooted the phone. When I start up the phone it says "unlocked" in the top left corner during start up.

Wait for the update but I know that come in 2013 when android world will be jelly bean
Inviato dal mio MB860 usando Tapatalk

Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.

NY Yankee Pride said:
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
Click to expand...
Click to collapse
Actually you could probably do this yourself.. search for "Petes Motorola root" then download and follow instructions in how to "unroot"..
Sent from my MB860 using XDA

Thank you for that suggestion. Since I don't have any experience in rooting I'm a little nervous but it seems pretty straight forward. How do I verify steps 1 & 2?
1. Make sure the Motorola drivers are still installed.
2. Make sure USB Debugging is still selected.
3. Connect your Bionic to your computer.
4. Run the Pete's Motorola Root Tools.exe.
5. Select UnRoot My Phone at the bottom.
6. Your phone will reboot 3-4 times as the program goes through all 4 steps in the process.

How do I flash back stock? v.SignatureMismatch,BootLoop,etc

We have a handfull of TF300T's and I am sure the answer is on here somewhere but I keep searching and can't find exactly what I am looking for.
I have some tablets that boot loop, some that turn on and say signature mismatch, and some that just stick on ASUS and one that says unlocked at the top in small text but that's it. What's the one thing I can do to all of them to just reflash them back to factory state? Everything I search involves getting back to rooted and unlocked.
Thanks guys.

New motherboard
Or
Sell it for parts
Or
Test to get rma with asus
Sent from my TF300T using xda app-developers app

okrasitna said:
New motherboard
Or
Sell it for parts
Or
Test to get rma with asus
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Really? There's no way around that? They really reach a point where they're not flashable?

kmad86 said:
Really? There's no way around that? They really reach a point where they're not flashable?
Click to expand...
Click to collapse
You would need to take each as an individual and find what access you have (bootloader, recovery(stock, cwm, or twrp), adb, fastboot. At this time the only way to treat them as a group would be rma to Asus.
Yes they reach a point where we don't have methods to recover them and there are many hoping that will change in the future.
Take a unit, verify the conditions and I am sure you will find many threads for each case. Some meet with success and others don't. If time is a controlling factor you could try ebay for motherboards as mentioned in the post above. My understanding the cost of a motherboard on ebay is much less then an rma to Asus.
Good Luck!

tobdaryl said:
You would need to take each as an individual and find what access you have (bootloader, recovery(stock, cwm, or twrp), adb, fastboot. At this time the only way to treat them as a group would be rma to Asus.
Yes they reach a point where we don't have methods to recover them and there are many hoping that will change in the future.
Take a unit, verify the conditions and I am sure you will find many threads for each case. Some meet with success and others don't. If time is a controlling factor you could try ebay for motherboards as mentioned in the post above. My understanding the cost of a motherboard on ebay is much less then an rma to Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate it. I'll see what I can figure out. Right now my first obstacle to tackle is the "signature not matched" on boot.
While I am thinking about it, what's the actual proper way to get a firmware update? It prompted me on the 4017, but I've been told there's a 4020 but my tab won't find it if I just search for update.

kmad86 said:
I appreciate it. I'll see what I can figure out. Right now my first obstacle to tackle is the "signature not matched" on boot.
While I am thinking about it, what's the actual proper way to get a firmware update? It prompted me on the 4017, but I've been told there's a 4020 but my tab won't find it if I just search for update.
Click to expand...
Click to collapse
Signature mismatch occurs when the bootloader in the tablet and the one being flashed don't match or the one most recently flashed. There are three bootloaders for this unit. ICS (4.0), JB (4.1), and JB 4.2 (4.2) each of these have associated firmware. Not like 4017 or 4020. Instead: ICS = 9.4.3.29 or 9.4.3.30 - JB 10.4.2.9 or 10.4.2.13 or 10.4.2.17 or 10.4.2.18 or 10.4.2.20 - JB 4.2 10.6.1.8. I don't know what the numbers you listed represent.
Some units never seem to get updated ota(over the air). Assuming the unit boots into the os look in Settings/About Tablet/Build number. I don't suggest updating to 4.2 at this time -if you should the tablet should be on 10.4.2.20 beforehand.
Download firmware one numeric higher than the one listed in settings. Unzip once and place the resulting zip on your internal sdcard or place on your micro sdcard and copy to the internal sdcard. Sometimes the file will be accepted on the external sdcard. Watch notifications in lower right -you are looking for a triangle to appear. If it doesn't appear in a minute or two reboot the tablet and wait again. If it appears accept the update and wait about ten minutes for completion.
If the above fails download the firmware and unzip once as above. Name the resulting zip EP201_768_SDUPDATE.zip and place on internal sdcard and follow the above directions. If that fails power tablet off, power on while holding power and volume down -when the icons appear press volume up while on the RCK icon - stock recovery should take over and accept the update.

tobdaryl said:
Signature mismatch occurs when the bootloader in the tablet and the one being flashed don't match or the one most recently flashed. There are three bootloaders for this unit. ICS (4.0), JB (4.1), and JB 4.2 (4.2) each of these have associated firmware. Not like 4017 or 4020. Instead: ICS = 9.4.3.29 or 9.4.3.30 - JB 10.4.2.9 or 10.4.2.13 or 10.4.2.17 or 10.4.2.18 or 10.4.2.20 - JB 4.2 10.6.1.8. I don't know what the numbers you listed represent.
Some units never seem to get updated ota(over the air). Assuming the unit boots into the os look in Settings/About Tablet/Build number. I don't suggest updating to 4.2 at this time -if you should the tablet should be on 10.4.2.20 beforehand.
Download firmware one numeric higher than the one listed in settings. Unzip once and place the resulting zip on your internal sdcard or place on your micro sdcard and copy to the internal sdcard. Sometimes the file will be accepted on the external sdcard. Watch notifications in lower right -you are looking for a triangle to appear. If it doesn't appear in a minute or two reboot the tablet and wait again. If it appears accept the update and wait about ten minutes for completion.
If the above fails download the firmware and unzip once as above. Name the resulting zip EP201_768_SDUPDATE.zip and place on internal sdcard and follow the above directions. If that fails power tablet off, power on while holding power and volume down -when the icons appear press volume up while on the RCK icon - stock recovery should take over and accept the update.
Click to expand...
Click to collapse
Thanks for the great info! However, I can't get into it to verify what software it has at all. In that case what would I do?
Also, where do I download the firmware? Sorry for all the questions, trying to wrap my head around all this and a the stuff I've been reading in search is all about modified software/roms. Not a lot of information on stock stuff that I could find.

kmad86 said:
Thanks for the great info! However, I can't get into it to verify what software it has at all. In that case what would I do?
Also, where do I download the firmware? Sorry for all the questions, trying to wrap my head around all this and a the stuff I've been reading in search is all about modified software/roms. Not a lot of information on stock stuff that I could find.
Click to expand...
Click to collapse
Here is a link for downloading the firmware and most other things you may need to download or references to things you might need to know. Look through at least the first three posts.
[INDEX]13 Mar 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides
Not knowing what firmware is in each unit I believe I'd try 10.4.2.20 as my base line. That is the newest JB (4.1) firmware.
Note: The firmware numbers I have used relate to TF300T units and US skus.
The methods I gave for updating firmware all assume stock recovery is installed which is the best place to start.
mismatch in general section - http://forum.xda-developers.com/search.php?searchid=163947942
mismatch in Q&A - http://forum.xda-developers.com/search.php?searchid=163948372
bootloop in general - http://forum.xda-developers.com/search.php?searchid=163948615
bootloop in Q&A - http://forum.xda-developers.com/search.php?searchid=163948785
Note 2: If you are unable to get into the os the only method above that is useful is the last.
If the above fails download the firmware and unzip once as above. Name the resulting zip EP201_768_SDUPDATE.zip and place on internal sdcard and follow the above directions. If that fails power tablet off, power on while holding power and volume down -when the icons appear press volume up while on the RCK icon - stock recovery should take over and accept the update.
Holding power and volume down is a attempt to get into the bootloader (apx is useless). See my signature for a link about getting into the bootloader.
If you don't have drivers properly loaded for this tablet and you are on windows see my signature for a link to get them properly loaded.

tobdaryl said:
Here is a link for downloading the firmware and most other things you may need to download or references to things you might need to know. Look through at least the first three posts.
[INDEX]13 Mar 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides
Not knowing what firmware is in each unit I believe I'd try 10.4.2.20 as my base line. That is the newest JB (4.1) firmware.
Note: The firmware numbers I have used relate to TF300T units and US skus.
The methods I gave for updating firmware all assume stock recovery is installed which is the best place to start.
mismatch in general section - http://forum.xda-developers.com/search.php?searchid=163947942
mismatch in Q&A - http://forum.xda-developers.com/search.php?searchid=163948372
bootloop in general - http://forum.xda-developers.com/search.php?searchid=163948615
bootloop in Q&A - http://forum.xda-developers.com/search.php?searchid=163948785
Click to expand...
Click to collapse
Wow, I really appreciate this! I'm going to check it over.

kmad86 said:
Wow, I really appreciate this! I'm going to check it over.
Click to expand...
Click to collapse
Reread my last post as I added some useful info.
We were overlapping posts and I see I had not finished typing when you responded.
I'll be offline for an hour or two but I'll check later.

tobdaryl said:
Reread my last post as I added some useful info.
We were overlapping posts and I see I had not finished typing when you responded.
I'll be offline for an hour or two but I'll check later.
Click to expand...
Click to collapse
none of the links work for me. they bring me back to the main forum.
mismatch in general section - http://forum.xda-developers.com/sear...chid=163947942
mismatch in Q&A - http://forum.xda-developers.com/sear...chid=163948372
bootloop in general - http://forum.xda-developers.com/sear...chid=163948615
bootloop in Q&A - http://forum.xda-developers.com/sear...chid=163948785
Click to expand...
Click to collapse

tobdaryl said:
Reread my last post as I added some useful info.
We were overlapping posts and I see I had not finished typing when you responded.
I'll be offline for an hour or two but I'll check later.
Click to expand...
Click to collapse
Ok, so I tried the Power+down with the SD card and the zip file on one that had no touch at all. IT WORKED!
At first I thought it was messed up and it froze on the android on it's back with the red triangle. I reset it after 5 minutes and it went to ASUS with a blue progress bar and then worked.
One problem fixed!

kmad86 said:
Also, I tried the Power+Down and booted with the SD card in it and the .zip. It seems like it started to work and about two minutes in with the android and the red triangle, everything seemed to freeze and never unfroze.
Click to expand...
Click to collapse
Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices
each will return the unit serial number or all zeros when working
I'm sorry to do a piece at a time but there are so many options etc
Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.

tobdaryl said:
Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices
each will return the unit serial number or all zeros when working
I'm sorry to do a piece at a time but there are so many options etc
Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.
Click to expand...
Click to collapse
a piece at a time is fine for me. I'm learning! I really do appreciate the help.
I don't have any software downloaded but the ASUS sync program. I need to download cwp and twrp as now I am realizing those are programs.
I tried the same MicroSD trick on another tablet with touch problems, and it went through the process but booted back to a really weird screen and I still have no touch.
Picture of Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kmad86 said:
a piece at a time is fine for me. I'm learning! I really do appreciate the help.
I don't have any software downloaded but the ASUS sync program. I need to download cwp and twrp as now I am realizing those are programs.
I tried the same MicroSD trick on another tablet with touch problems, and it went through the process but booted back to a really weird screen and I still have no touch.
Picture of Screen
Click to expand...
Click to collapse
That's an interesting screen I have never seen. I don't know what it is but may be useful.
I forgot to cover something in my last post.
The android lying on his back is stock recovery with no file to process. We need to get adb and fastboot working properly. We can use adb to push our file to the internal sdcard and let stock recovery process it for us.
Tell me about your pc! Windows 7, 8, linux, mac?

tobdaryl said:
That's an interesting screen I have never seen. I don't know what it is but may be useful.
I forgot to cover something in my last post.
The android lying on his back is stock recovery with no file to process. We need to get adb and fastboot working properly. We can use adb to push our file to the internal sdcard and let stock recovery process it for us.
Tell me about your pc! Windows 7, 8, linux, mac?
Click to expand...
Click to collapse
I have a windows 7 laptop that I can use. I am primarily mac but I know Windows is best for these.
I just tried another, and got the same screen as above with no touch.

kmad86 said:
I have a windows 7 laptop that I can use. I am primarily mac but I know Windows is best for these.
I just tried another, and got the same screen as above with no touch.
Click to expand...
Click to collapse
Good choice!
Read your pm and let me know what I have forgotten or anything you don't understand.
For the moment let's use the tablet you began with and finish the thread for any who are watching or come later. We'll need to consider another communication vehicle for the remainder.

tobdaryl said:
Note 2: You need to think about getting adb and fastboot working properly.
adb can be accessed when powered on and just sitting there
and when booted into cwm or twrp
fastboot get into the bootloader (power and volume down) press volume down to choose the usb icon then volume up to select - this would be on the 4.0 and 4.1 bootloader - if you have the 4.2 bootloader there is no usb icon and the tablet if left will auto turn on fastboot (look in upper left for the message) (DO NOT USE WIPE DATA IN THE BOOTLOADER)
test if adb is working by typing
adb devices
test if fastboot is working by typing
fastboot devices
each will return the unit serial number or all zeros when working
I'm sorry to do a piece at a time but there are so many options etc
Searching
go to general (example) without choosing a thread look in the upper right for search to the right of this there is a gear select that (advanced search) - in search by keyword type mismatch (example) - scroll to the bottom and click search.
This example searches all general threads and all posts within these threads.
Click to expand...
Click to collapse
In my years of computer experiences, usually my friends come to me to help them out. With this, I am so lost and feel so hopeless as I am starting to understand how they feel most of the time.
Anyhow. I am really lost with the CWM and TWRP thing. CWM seems to need to be installed through the tablet in the android store and runs on it? TWRP also seems to need installed on the tablet and used on it. I was assuming I would install something on the windows computer that communicates with the tablet to get it going. I think that's why I am so off track here.
When you say type "adb devices" to verify it's working. Where am I typing that? In the SDK kit somewhere?

kmad86 said:
In my years of computer experiences, usually my friends come to me to help them out. With this, I am so lost and feel so hopeless as I am starting to understand how they feel most of the time.
Anyhow. I am really lost with the CWM and TWRP thing. CWM seems to need to be installed through the tablet in the android store and runs on it? TWRP also seems to need installed on the tablet and used on it. I was assuming I would install something on the windows computer that communicates with the tablet to get it going. I think that's why I am so off track here.
When you say type "adb devices" to verify it's working. Where am I typing that? In the SDK kit somewhere?
Click to expand...
Click to collapse
Sorry that is one I missed. Forget CWM. Both CWM and Twrp are custom recoveries used to replace stock recovery. They can be used to flash stock rom or custom rom, root, and etc.
Let's stick with the this thread for now as we are overlapping. Go to android-sdk/tools and run android.bat. Install Android SDK Platform-tools. This will add the android-sdk/platform-tools directory and inside you will find adb and fastboot. They should be run as administrator with cmd (terminal - cmd - command prompt).

tobdaryl said:
Sorry that is one I missed. Forget CWM. Both CWM and Twrp are custom recoveries used to replace stock recovery. They can be used to flash stock rom or custom rom, root, and etc.
Let's stick with the this thread for now as we are overlapping. Go to android-sdk/tools and run android.bat. Install Android SDK Platform-tools. This will add the android-sdk/platform-tools directory and inside you will find adb and fastboot. They should be run as administrator with cmd (terminal - cmd - command prompt).
Click to expand...
Click to collapse
One more thing, is all of this for signature mismatch, or the no touch ones?
I'm slowly grasping this!

[q] such agonizing frustration

Well, here's my story.
Trying to install custom rom for my Note 3. I have version N900V for verizon. I'm assuming whatever I use I can use the N9005 because that's the only one that ever seems to come close to my model number based off the qualcomm chipset? Just a side note I guess. I've currently had success in rooting via one of the "one click" apps called Kingo. Very nice and easy and breezy. The real problem is trying to install a custom recovery via cwm. No matter what I do or try nothing will work. I can gaurantee it.
Also tried looking into twrp but even their app wouldn't install recovery. So I've done many things from using multiple versions of Odin, to many different cwm's, and all making sure I follow the instructions just as outlined to no avail. EVERY single time is a failed attempted with Odin, never passes. I believe I've gotten every different error you could get (all derive from same method anywho so figure they mean the same).
I haven't broken my knox yet so I guess that's good. I'm just not sure why I can't seem to get a recovery installed so i can finally move onto getting the rom installed. Once in download mode with the whole "volume up/home button/ power button" thing I get a few errors in there too such as: Sys rev check fail: no signature, and magiccode check fail: (some error here). Something along those lines. Even when I first started it would say that the signature files couldn't be verified or something. Looked a bit different and I forget how/when I got those messages. Funny thing is when I press volume up and power button with home, I get a recovery that looks just like a cwm one....not sure if there the whole time by default or maybe a feature of the root? Not sure honestly but I tried forgetting the cwm and going to install the rom and of course my luck I wiped data/cache following directions hoping it'd install properly, and I still get errors while trying to do the rom.
So now i'm back at out of box settings(although rooted) and I'm nowhere. If any of you has the slightest idea that could help I can't give up now. Also an interesting tidbit is I don't have the option anywhere for "reactivation lock" being disabled. Not sure why if anyone knows that explanation. Already have USB Debugging enabled so lets get the obvious ruled out too. Also I know my drivers have to be installed correctly since I can get into my phones SD card just fine as well as Odin always recognizes it right away as being added or removed hence the color being either yellow or blue. Tried even ticking everything and nothing and just some. even tried adding the pit file too. probably not necessary. I've had to even try replugging into different USB ports without closing Odin as some have suggested would work, and also closed Odin doing the same thing. No avail. I fear I may not be able to flash cwm for some reason? I would be pretty upset if I couldn't install a custom rom.

ducky06 said:
Well, here's my story.
...
So now i'm back at out of box settings(although rooted) and I'm nowhere. If any of you has the slightest idea that could help I can't give up now.
...
Click to expand...
Click to collapse
Hints - read more, select the right forum:
http://forum.xda-developers.com/verizon-galaxy-note-3

IIRC Verizon uses a locked boot loader. This means you can only load software signed by Verizon onto your device. The error messages seem also to point in that direction.
Someone may correct me if I'm wrong.
---------- Post added at 12:20 PM ---------- Previous post was at 12:04 PM ----------
Another sidenote: You mentioned Kingo. This is suspected to be malware (I didn't follow the corresponding thread, however). Seems to spy IMEIs. Search here at xda for more.
Just a warning for those reading it.

[Q] SGH-I337 Download Mode Problem?

Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.

Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help

bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.

Samsung Galaxy S5 (G870A) Bootloop Fix!

I've recently found away to fix a Galaxy S5 Active stuck in a boot loop. (This method only works if your device is on lollipop 5.0! )
Note: This method only works on the OC5 update.
More firmware support coming soon.
What happened: I accidentally made my Galaxy S5 Active get stuck in a boot loop. I couldn't find a solution for the longest time because the bootloader is locked. Time passed and I eventually found away to fix the boot loop if your devices is running Lollipop 5.0!
Solution:
1. You should always try to fix the boot loop by booting into recovery mode by holding down the Home+Volume-Up Key+Power button. Once the phone logo pops up on the screen releases the power button only, but continue to hold the Home+Volume-Up Key. If it worked is should say "Booting into recovery." or something along those lines in blue letters.
Once you're into recovery use the volume keys to navigate Up and Down. Find wipedata/factory reset. Select it with the power key and navigate down to Yes. Wait till it finishes. Then see if that fixed the problem. If not proceed to next step
2. Since the boot loader is locked it's really difficult to flash any kind of Recovery, ROM, or Stock Rom unless your phone accepts it as a valid file. So here's what you do!: (Method 1)
Download this file and save it to your desktop: https://drive.google.com/open?id=0B3UBRFq3BojVQnBSc3lCSzloYUU
Download ODIN v(3.09): http://odindownload.com/Samsung-Odin/#.VgiJ_8tViko - Extract it to your desktop.
Put your phone in download mode. (Note: Before you do this, install the correct drivers for your phone to your computer.)Make sure your phone is completely off and Hold the Home+Volume Down+Power. You will get a warning message just press the volume up key to continue.
Go to desktop and launch ODIN. After ODIN pops up, plug in your device. (Make sure you have the correct phone drivers installed)
You should see a dialog box in ODIN that say 0:[COM6] in blue. Note: It might be different for everyone, just make sure it says COM.
After that, Under "File [Download]" click "AP" Then navigate to the file you downloaded earlier called "boot.tar"
MAKE SURE RE-PARTITION IS UNCHECKED!
Leave everything else alone then click start. Wait till it says PASS! in green letters in ODIN!
(Method 2):
Go to this link download it to your desktop and follow the instructions: https://drive.google.com/file/d/0B3UBRFq3BojVdXlSUE43VzJPbEU/view?usp=sharing
Done! Your device shouldn't be in a boot loop anymore! If you have any questions let me know!
Note: Once this process is complete, your phone will permanently show a warning in your notifications saying "Unknown action detected." This happens because your phone will detect that your kernel was modified so if you don't want this to happen, then I suggest you wait for a official lollipop OS release.
UPDATE!: You should now be able to download the "Boot.tar" file. Sorry about that!
UPDATE!: New files and instructions added if the first method didn't work!

Having some major issues
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.

Ghujii said:
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Click to expand...
Click to collapse
New method for you...

irontaco1 said:
New method for you...
Click to expand...
Click to collapse
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?

Ghujii said:
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Click to expand...
Click to collapse
I'm glad you got past your Bootloop! If you need anymore help let me know.

Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active

I'd say hold off for a while I did that exact 5 Hong with the s5 active and it bootlocks it. You need to, if you're going to do this install and use safestrap to di so and BACK UP EVERYTHING with safe strap to SD. As long as you follow those method you SHOULD be able to even soft brick it and come back from it.

shadavis08 said:
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
Click to expand...
Click to collapse
I haven't found any successful way to to go back to Kit Kat or 4.4.2 for this phone. In fact that's why this thread exist is because people who have tried to flash back to 4.4.2 have failed and got stuck in a Bootloop. So if you plan on trying to find away make sure you back everything up and if you fail you can use this tutorial to get your phone working again.
Make sure you have "USB Debugging" on
Make sure you have the drivers for your phone installed on your PC before you start the process of looking for a root.

Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2

shadavis08 said:
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
There should not be anything attempting to download when you boot into ''download mode'' if there is, its highly likely there are still particulates of the last bad flash. I would as he said above, enable USB debugging and the like, and install safe strap to be safe. After safe strap is done and youve followed the tutorial which you can find in another thread on this site, boot your phone down and then power it back on, safe strap should come up first, when it does so push the ''recovery'' option to enter safe strap( someone correct me if thats wrong, my phone is currently dead/charging so i cant check) From there you can back up to an SD card, make sure you enable compression when you do.
Once thats done, WIPE YOUR PHONE, and Cache,( maybe dalvik as well if you cant find it dont worry.)and its all on SD CARD, then attempt to dirty flash( I dont recommend), or clean flash your device WITH safe strap. This typically entails downloading a .zip file and opening it THROUGH safestrap, which is done the same way as backing up your data, only via another option in the menu. Simply put; Back up data with safe strap, after thats done push back and choose FLASH, it should show you all available items it can flash from/to, pick and pray. I didnt go this route when I tried, I attempted to brute force the Bootlocked S5A, and it caused some errors that I now have reversed after much pain. If I HAD safe strapped, It may have went smoother for me, and may for you. Safestrap for us Samsung users is the same as Clockwork Mod for the rest if you weren't aware.
I'll edit this when my phone charges and I can walk you through appropriately, if need be MSG me and Ill do it as soon as I receive the message via this thread if I have not already.

hi guys! good day! i have tried the new method twice! and odin fails everytime! the problem is with the modem.bin! is there any way to fix this?

Make sure you're running lollipop and not Kit Kat and make sure you have the correct phone model. If you don't meet both those requirements then it won't work.

it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1

abatoir said:
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
Click to expand...
Click to collapse
Yeah that information is correct. You might want to download the latest version of ODIN and try again. (Make sure you're putting the modem.bin file in the correct spot in Odin.)

I think I have the latest odin.. And modem can only fit in the cp field I think. Its just not working for me. I tried doing each part separately. And the modem flash always fail.
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
I used odin 3.10 and also tried with odin 3.7

Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.

abatoir said:
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
Click to expand...
Click to collapse
You might want to boot into recovery mode and try to factory reset it normally. If his phone is rooted you could also flash a custom rom to it and get it out of Bootloop.

I also forgot to mention you can't get ahold of the system.img because it's not released to the public.

Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?

abatoir said:
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
Click to expand...
Click to collapse
If you flash the Kit Kat system.img you might have to downgrade the kernel also. I would give it a try and see if it works.