Database Users

May'13 - Unlock Bootloader, Flash Recovery, Install ROM on Atrix 4G AT&T 4.5.141

The best feature of Android - It's open. You can modify Android to have the best performance from your phone. My previous Atrix's hardware had some problem. So I didn't root my/unlock my Atrix. However, after seeing the upcoming CM10 for my set &; a battery friendly ROM yet 100% stable ROM, I finally decided to flash a custom ROM. What's great? I'm successful.
Yesterday, I was determined to unlock my bootloader & flash MROM on it. But I was afraid if I do anything wrong, my phone will not boot. I've not any other phone other than this & it's very precious to me. It's my beloved Atrix. I was unrooted, unlocked. Meant - I didn't do any modification at all. If you're on AT&T 4.5.141 (OTA Upgraded) then this tutorial is for you. (Bell/International users close your tab now!)
I'll not be responsible if you do any harm to your device
(You know the drill )
How to Unlock Motorola Atrix Bootloader (4.5.141) AT&T
I'm a noob. So I was searching for a perfect & easy tutorial. The automatic bootloader unlock seems really confusing to me. So I decided to do it manually. It's more easy &; clear than the automatic version.
I'll be writing this tutorial only for AT&T Atrix running 4.5.141 - Android 2.3.6 version. This tutorial will also work for AT&T 4.5.91 version.
But don't try this on AT&T 4.5.145/Bell/other international version. Once you flash CM7, don't flash Motorola's ROM with SBF. It'll brick the phone..
(Means your phone is dead!)
{
"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"
}
We'll be flashing a custom ROM directly after unlocking the bootloader. So please download a custom rom &; it's Google Apps to your internal memory/SD Card. The main purpose of unlocking bootloader is to flash roms. So I don't care whether Motorola's buggy, laggy, sluggish, default blur ROM works or not.
Pre Requirements
We'll be needing a couple of tools.
We need the drivers for Atrix 4G. Download &; install it from here*(31.60 MB)
We'll need fastboot to unlock. Download fastboot from here (4.73 MB)
We'll need RSDLite. Download RSDLite 5.3.1 (4.33 MB)
Only for AT&T Atrix running 4.5.91/4.5.141 -*We'll need the 1.1 MB Unlocker Only SBF for AT&T Atrix. This tool will make ready your smartphone to unlock via fastboot command.
How to Unlock Bootloader Now?
If you've rooted already, take a backup of your apps with Titanium Backup. If not, then you're gonna loose all your apps.
Unlocking Atrix 4G Bootloader 4.5.141 Step-by-step
First of all, install RSDLite & extract the file*4547-fix-try2.sbf on your desktop.
Extract fastboot to C://fastboot.
Open RSDLite.
Power off your phone. Press power button+volume down together. You'll see a text "fastboot". Then start pressing the volume down again &; and again until you see "RSD". Once it comes, press volume up button. It'll say "Starting RSD Protocol"
You'll see that RSDLite has detected your phone in the menu. (SE Olympus or something like that)
Now Click the "..." button in RSDLite &; navigate the*4547-fix-try2.sbf file from your desktop.
Click Start.
Wait 5/6 minutes It'll restart your phone. You'll maybe see a boot error. (Just ignore it. Cause we're gonna flash a new ROM anyway).
After waiting some minutes, it'll say it's saying "starting fastboot protocol"
We're half done. We've extracted our fastboot files in C://fastboot
Open Command Prompt with Admin Privilege
Code:
Type "cd.."
Code:
Type "cd.."
Code:
Type "cd fastboot"
Type "
Code:
fastboot devices
".You'll see if your devices gets recognized or not.
Now type "
Code:
fastboot oem unlock
it'll give you a unique ID to unlock your phone.
Type "
Code:
fastboot oem unlock "XXXXXXXXXXXX (Unique ID)"
BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!
Flashing ClockWorkMod Recovery
(I've downloaded the latest recovery from romracer from here & placed it into the fastboot folder already)
Reboot your phone into fastboot mode again. (If power button doesn't do it, do a battery pull. To get into fastboot, Press power button+volume *down together until you see fastboot &; then press volume up)We're in the command prompt still.
So write*
fastboot erase recovery
Then write
fastboot flash recovery recovery.img
YAY!!! BOOM! We've flashed unlocked the bootloader & flashed recovery!
To flash a rom now, go to recovery mode (Press power button+volume *down together until you see*fastboot*&; then keep pressing volume down &; until you see "Android Recovery". Once you see it, press volume up.
The ROM flashing guide is easy. Choose install zip from SD card &; select your rom package &; it'll be installed. Reboot to enjoy your first custom ROM
Previously Published on my site http://saifhassan.info!

Emergency AT & T Atrix 4g (2.3.6) 4.5.145 Original 4547-fix-try2.sbf
Friends, let me urgent need to file 4547-fix-try2.sbf. Phone "failed to boot one" has failure. then the first term is no longer soft.As I understand it from RSD lite rom (4547-fix-try2.sbf) need to install. I'm searching, but I could not find. Links are broken. URGENT PLEASE HELP
(I'm sorry for my english is bad.)

saiftheboss7 said:
...BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!...
Click to expand...
Click to collapse
Finally) I'm done! 10ks!

Help please
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks

ukmed said:
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks
Click to expand...
Click to collapse
try "fastboot devices" to make sure your device is connected and recognized.

lehjr said:
try "fastboot devices" to make sure your device is connected and recognized.
Click to expand...
Click to collapse
Tried that, nothing happens...
Help!?

ukmed said:
Tried that, nothing happens...
Help!?
Click to expand...
Click to collapse
Make sure you download the USB Driver for WIndows. I posted the link in the OP. Read it thoroughly.

i need help
all my volume buttons are not functioning, how can u help me unlock........

If you have root, you might be able to use adb and the internal reboot command to reboot into various modes (recovery, fastboot...).

Tonyanaky said:
all my volume buttons are not functioning, how can u help me unlock........
Click to expand...
Click to collapse
Just flash TWRP after download, rename it to recovery & replace with the one that comes with fastboot extracted folder.

help
my 4547-fix-try2.sbf failed to work......what do i do???

Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?

Xfire68 said:
Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?
Click to expand...
Click to collapse
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!

Xfire68 said:
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!
Click to expand...
Click to collapse
there is a set of drivers that are for win 7 64 bit that i found early this morning via the droid x forum. I'm not at home right now, but i will post the link here when i do get home. hopefully it helps with issues with this os setup
Edit
File uploaded. even thought it says droid, it should still work

Works for 4.5.141 ?
Hi! Does this method work for Atrix 4G AT&T 4.5.145 as well? I want to get bootloader unlocked of my phone and install any ROM which supports 2-way Call Recording. Kindly suggest a stable ROM also that supports call recording function.
I am bit confused as the thread title says for 4.5.141 only.
Thanks in advance!!! :good:

Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Enviado desde mi MB860 usando Tapatalk 2

andresrivas said:
Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Click to expand...
Click to collapse
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.

sony108 said:
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.
Click to expand...
Click to collapse
yes, its called read post #1 and delete the recovery.sh in your phone before flashing cwm

[Q] Baffling fastboot issue

I know fastboot issues are probably a common thing to be asked, but I've had fastboot issues before and I've always been able to fix them. This time I just can't and I've been trying to fix it for several hours now to no avail.
I can't get my Nexus 4 to be recognized by adb in Fastboot mode. I've managed to figure out that it's definitely an issue on the Nexus 4's side, cause I can get my Nexus 7 to be recognized in fastboot mode. I've installed the latest Google drivers, uninstalled them, reinstalled them over and over again, tried installing drivers through Nexus Root Toolkit, EVERYTHING. But nothing seems to work. It recognizes fine when it's running a ROM itself. typing "adb devices" shows the device find, I can reboot into the bootloader with "adb reboot bootloader", all that works fine, but once in the bootloader it just doesn't work. I've made to sure to reinstall the drivers while in the bootloader, and nothing seems to do the trick.
What's interesting is that I did a driver test with Nexus Root Toolkit, and it actually recognized it while it was in Fastboot mode and went through the whole test successfully. It reset out of bootloader mode and booted up, so I'm confused as to how it recognized it but I can't.
I tried flashing the Kit Kat factory image through Nexus Root Toolkit, and I thought it worked, but then it gave a random error at the end and rebooted and I was still running the ROM that I flashed a few days ago.
I'm really at a loss for what I can do. Without fastboot the device is stuck on custom ROMs. Nothing seems to work. I'm honestly baffled, I can usually figure this stuff out on my own but NOTHING is working anymore.
Any ideas?

Try turning off MTP
Sent from my Nexus 4 using xda app-developers app

This is just a wild guess, but maybe its between your bootloader version and the fastboot version. Try to use the latest ADT package from Google. If you post the exact error the toolkit give might be easier to diagnose. Also when you connected the N4 in bootloader mode, what is the name of it in Device Manager? Mine is "Google Nexus 4 Bootloader Interface" under the category of "Android Device", using the latest Universal Naked Driver. If your isn't the same try reinstalling it with UND.

kboya said:
Try turning off MTP
Click to expand...
Click to collapse
Nope. Plus I don't see how that would effect it, considering the MTP/PTP is only for toggling between accessing the full storage and having the device recognized as a camera from my understanding. In bootloader mode it wouldn't even recognize which mode it's in. At least I think.
Regardless, tried it in both and it didn't work.
eksasol said:
This is just a wild guess, but maybe its between your bootloader version and the fastboot version. Try to use the latest ADT package from Google.
Click to expand...
Click to collapse
Redownloaded the whole adt package. Didn't help.
eksasol said:
If you post the exact error the toolkit give might be easier to diagnose.
Click to expand...
Click to collapse
It was kinda weird, I think it thought it was flashing the factory image but it wasn't actually doing anything. I'm pretty sure the the error was just some weird error in the program itself, it didn't really say anything usefu;.
eksasol said:
Also when you connected the N4 in bootloader mode, what is the name of it in Device Manager? Mine is "Google Nexus 4 Bootloader Interface" under the category of "Android Device", using the latest Universal Naked Driver. If your isn't the same try reinstalling it with UND.
Click to expand...
Click to collapse
"Android Bootloader Interface" under the category of "Android Device". Drivers are the official ones from Google. I don't think I've tried the Universal Naked Driver. I'll try that and report back.

Tried installing the Universal Naked USB Drivers from this thread, and got this error:
{
"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"
}

Ashanmaril said:
Tried installing the Universal Naked USB Drivers from this thread, and got this error:
Click to expand...
Click to collapse
It means you are using Windows 8 and is trying to install an unsigned driver (not sanctioned by the almighty Microsoft). You need to restart Windows 8 into Advance Startup and press F7 at the menu to disable driver signing: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/

Ah, okay. Thanks, I'll try that tomorrow. Heading to bed right now.
Sent from my Nexus 5 using Tapatalk

Ashanmaril said:
Ah, okay. Thanks, I'll try that tomorrow. Heading to bed right now.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually here's the link to the latest UND version which has Nexus 5 support as well: http://forum.xda-developers.com/showthread.php?t=2513339

Alright, managed to install the driver, but it still won't recognize the Nexus 4.
The driver DID manage to make adb notice my Nexus 7 in adb sideload mode so I was able to update to Kit Kat on that.
I'm really at a loss for what to do on the Nexus 4 though...

Ashanmaril said:
Alright, managed to install the driver, but it still won't recognize the Nexus 4.
The driver DID manage to make adb notice my Nexus 7 in adb sideload mode so I was able to update to Kit Kat on that.
I'm really at a loss for what to do on the Nexus 4 though...
Click to expand...
Click to collapse
stopped Reading here "I can't get my Nexus 4 to be recognized by adb in Fastboot mode". adb never Works on fastboot mode, if it Works then its a oem modified bootloader to work with that.

Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4

Ashanmaril said:
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
facotry images use "fastboot flash partitonname file".
Example, fastboot flash system system.img or fastboot flash bootloader bootloader-mako-z30i.img

Ashanmaril said:
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
No he's right, it's called bootloader mode actually and it only work with fastboot, ADB only work in custom recovery. Fastboot is the main method to flash factory image.
sent from xda premium app

Oh, shoot. Sorry, I just realized I've been calling it fastboot mode this whole time. I meant bootloader mode.
Either way, yeah. Still haven't figured out what's going on.

Ashanmaril said:
Oh, shoot. Sorry, I just realized I've been calling it fastboot mode this whole time. I meant bootloader mode.
Either way, yeah. Still haven't figured out what's going on.
Click to expand...
Click to collapse
bootloader mode where u can select between power off,rstart,start,recovery ?

Yep. Typing "adb devices" never shows the device while it's in the bootloader. It works fine when it's powered on, I can even do commands like "adb reboot bootloader" and whatnot and they work fine, but it just doesn't work in bootloader mode.

Ashanmaril said:
Yep. Typing "adb devices" never shows the device while it's in the bootloader. It works fine when it's powered on, I can even do commands like "adb reboot bootloader" and whatnot and they work fine, but it just doesn't work in bootloader mode.
Click to expand...
Click to collapse
that is fastboot mode(it dosent looks like a normal fastboot mode because google modified it)but.as i said adb never worked on dat because its disabled, if u wanna adb on dat mode, either u get another phone or install modified bootloader(im using unlocked bootloader from att lg og because i like lg logo + adb Works on dat, but u cant install any 4.4 rom or kernel :/)

But it works with all my other Nexus devices. And it used to work.
Watch the video I linked earlier. He demonstrates using adb commands in the bootloader to flash a factory image. I've done it multiple times.
Sent from my Nexus 5 using Tapatalk

Ashanmaril said:
But it works with all my other Nexus devices. And it used to work.
Watch the video I linked earlier. He demonstrates using adb commands in the bootloader to flash a factory image. I've done it multiple times.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that is not nexus 4 + he only used FASTBOOT commands, i seriously didnt see any adb command, can u gimme the time? he showed the .imgs on folder he showed the nexus(it looked like the 10) and he done fastboot flash blablabla.
print: http://prntscr.com/24fbm0

Oh. My. Gosh.
I am so stupid.
This whole time I've been typing "adb devices" to test to see if it was recognizing the devices. I was supposed to be typing "fastboot devices"
I have no words. I tried every complex solution I could think of... And it was just me being stupid...
Sorry about that. I guess this is solved. I'm gonna go hit my head against the wall for a bit.

[Solved] Stuck in Boot Loader

* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
{
"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"
}
Image of recovery that I can not get to.
Current state of device. can not get anywhere else.
Close up of date.
Picture of odin failing. I tried to flash using the option called PDA by the way.
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
solved - cant find where to set this thread to solved thought.
Any help is greatly appreciated.

Nyreb said:
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
View attachment 2637629
Image of recovery that I can not get to.
View attachment 2637596
Current state of device. can not get anywhere else.
View attachment 2637598
Close up of date.
View attachment 2637611
Picture of odin failing. I tried to flash using the option called PDA by the way.
View attachment 2637622
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Shoot me a email at [email protected]... We can talk more about your issues there..... Thx lj

Solution
Thanks to lj50036, my nexus now actually works.
Here's what he told me to do:
----------
1.) start here http://forum.xda-developers.com/showthread.php?t=2588979
This will install abd fastboot and the drivers for your tablet just follow instructions.
2.) Now open cmd as admin and type
fastboot
should see commands and options listed
3.) now type
cd /
this will move root to c drive.
4.) plug in tablet, boot into bootloader (holding down power, volume up and down I think) and type
fastboot devices
this output serial number of device and then type of device (Fastboot)
5.) go to https://developers.google.com/android/nexus/images#mantaray or google factory images and find Nexus 10. use what ever version you want. download, unzip and you should see something along the lines of this (the kot49h will be what ever version of the image you used.)
6,) move everything but the 2 .sh files to root of c drive (c:/)
and then in cmd prompt type
dir
this will print out file names, data, and other information of c:/. make sure you see the 3 files you moved from the factory image you unzipped.
7.) if so, make sure tablet is in bootloader still, and type
flash-all.bat in cmd prompt.
--About halfway through it reboots your nexus and because my nexus wont reboot its self, and will only come on when its plugged into wall outlet for a bit, I just did that and plugged in and it worked fine.
-- once the whole process runs, my nexus rebooted into recovery mode, and after a minute rebooted correctly and I was able to start setting up.
----------------
Thank you again to lj50036

@Nyreb
Change the forum name to include (SOLVED)

@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.

spudsmac said:
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
Click to expand...
Click to collapse
Shoot me a email.... Sounds like you need some help....

So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!

spudsmac said:
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
Click to expand...
Click to collapse
What happen in android some time, and I may be way off in left field here but, it has happened this way on the tf700, tf300, tf201, and the nexus 10... Just what I have help people with is that....
The storage no matter what command you issue in fastboot e.g
Code:
fastboot erase boot
fastboot erase system
fastboot -w
It just will not erase everything, and by doing these commands your really only telling the tab and or phone that you are going to be putting other
data in those partitions, so if you just flash exactly what was already on the tablet it does not like it...
@spudsmac had upgraded to 4.4.2 and was trying to install cm11 when things went wrong
So by us trying to reset the tablet to factory 4.4.2 firmware it would not take it... Just froze at android guy with x
So when, we went one version older on the firmware... Magic happened and he was golden....
Thx Josh

Need Help! Tablet Stuck and Fastboot Not Working

I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"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"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.

If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.

share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?

NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.

share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.

Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.

I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.

I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.

answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks

aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.

[Q]Stuck on Google splash

OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.

a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"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"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck

joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.

a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?

I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.

joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck

a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.

joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...

a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.

joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(

Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)

ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.

Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...

ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.