Related
Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris
when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf
Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks
I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.
So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
brandonc0526 said:
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
Click to expand...
Click to collapse
It won't relock.
It's like it's read-only.
rec71 said:
It won't relock.
It's like it's read-only.
Click to expand...
Click to collapse
Hmmm. Try booting into TWRP from the toolkit and flashing a rom. If that doesn't work just try wiping everything and toggling/untoggling all the mounts. I had this issue on my old galaxy S and wiping did the trick, although I had to flash my ROM again
Strange. TWRP asks for a password - is this normal? The device has never had encryption enabled. But if I skip this I still cannot mount or access any part of the storage.
Same error. Have you find any solution?
Hello, did you find any solution? I just had the same exact problem. I wiped it through fastboot but when I try to flash the image, I get the same error
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
Don't use a toolkit, use the guide posted in the general section, toolkits are often very faulty as they only tend to work on working devices
Sent from my Nexus 4 using xda app-developers app
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
This is likely an emmc hardware failure
I've seen something very similar happen a couple of times with people on the one x.
Bootloader magically relocked itself. All partitions only read only. Unable to flash anything or issue lock/unlock commands
Sent from my Nexus 4 using xda app-developers app
highessupremacy said:
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
Click to expand...
Click to collapse
I'm having the exact same issue. Going to try to warranty it but since it the bootloader can't be relocked I have the feeling I'm screwed.
remote flash write failure
Same issue here.
My phone was unlocked and rooted, with stock firmware. I haven't made any changes to my phone for months since I re-rooted after 4.2.2 was released.
Had some apps crashing yesterday afternoon, not a big deal I thought, I'll just reboot. When I rebooted, the phone got stuck on the nexus boot screen - left it for hours and nothing.
Tried clearing the cache and doing a factory reset, no effect at all. Today, I tried reflashing, erased all the partitions first, but couldn't flash anything. Tried stock firmware first, but also custom recovery partitions and custom boot roms. Nothing.
Same issue here. Can't flash anything, I always get "FAILED (remote: flash write failure)" I also cannot re-lock the bootloader. I guess I will have to send it back for warranty repair to Google/LG?
This is the only thread I could find on this issue, I wonder if some recent app update broke my N4?
nothing to add besides same issue here. I got a google services failed message that I couldn't clear so I turned off my phone and then stuck on X. Haven't even installed a new app or anything in a couple of weeks. I have tried command prompt method and toolkit and both give flash write failure. I have cleared everything via command prompt and same result. Always told you cannot brick a Nexus...
Did you try to connect via adb after fastbooting to CWM (or even on X logo)?
We could compare our kernel logs then, hope it might clarify something...
Had any luck this far? I've got my nexus bootloader unlocked but not rooted, and I fear it will happen to me too.
Same problem here.
I believe I was able to fastboot erase /userdata but every 'flash' command fails. I am able to relock it though so I will try to send it in.
Good thing I kept my Galaxy Nexus and I was able to fit my micro SIM into it
Am I screwed?
Hey guys, another affected Nexus 4 user checking in. Same exact symptoms: was charging, checked something on it, saw a cascade of force closes. Shut it down, then it wouldn't boot past the Google screen. At one point I got it past that to the X screen, but it was stuck there indefinitely (for hours).
I'm running stock 4.2.2 with an unlocked bootloader. Same issues when trying to do anything over fastboot. Had the same idea to flash back to stock with no luck.
So... am I just screwed out of a phone? Or has anyone had luck getting it replaced?
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Just got off the phone with Google Play support. They had me run through a few tests (boot to fastboot, go into recovery, try booting from there; boot to fastboot, go into recovery, factory reset, reboot). Same thing: stuck on the "x" screen. I mentioned I wasn't rooted, but they didn't ask about the bootloader being unlocked. They went ahead and treated it as a normal in-warranty RMA. They're sending a new Nexus 4, and then I send the defective one back once it arrives.
If you have this issue with a Nexus 4 bought from Google Play, I suggest you call Google Play hardware support at (855) 836-3987. They were super friendly and helpful. While I'm bummed something went wrong with my phone, I'm glad I don't have to buy a new one.
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
XsMagical said:
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't see a misc.img in the stock image from Google for the Nexus 4. But anything else I tried to do via fastboot failed, which I've never had before.
I had the same exact issue experienced with the original poster. The apps were crashing on me like crazy. I was at the dog park. I remember the only app that was being updated at that time was AirDroidv2 just literally like 2 minutes ago before the google apps started to go crazy. I started to shut it down and boot it back up. I got stuck on the "X" screen. after an hour, i went home and tried the toolkit. then i went manual with cmd. all i get is "FAILED (remote: flash write failure)" whenever i attempt to flash it.
after a while, the OS wasn't even booting up. No "google" logo or "X" logo. Only i got was the bootup into fastboot. Now it doesn't even power up unless i connect the usb.
curious, is anyone hearing any rattling sounds in their device and/or red led dot when connecting to usb? I fear it's a bad connection to the battery.
Count me in as one of the unlucky folks as well. I noticed my N4 was auto-updating some apps last night, then later when I went to pick it up I couldn't get the screen to turn on. Held down power until it rebooted, then was stuck at the Google logo and never got any farther. Bootloader mode works, trying to boot into recovery gives a black screen. Tried to re-flash recovery.img from stock but got the same error as others: "FAILED (remote: flash write failure)"
I called Play Support and they were helpful in getting the RMA process started. Unfortunately I expressed some concern about my cracked glass back affecting the return and the CSR mentioned that he'd have to escalate. (As a point of reference, my glass cracked a few months ago). We discussed how common cracked glass backs are with the N4 and how I hoped it wouldn't affect my RMA as the device has been working fine for months. He's waiting to hear back from the specialist before we can move forward.
Really hoping that everything works out.
UPDATE: Warranty claim denied due to the broken glass. Not sure what my next step is. :/
So, for a long time, my Nexus 7 never worked, because the charging port was too loose. So I decided to order one. It came in the mail today. Installation was easy. It started charging, but no charging icon appeared. The only thing that happend was the screen back light turning on slightly. So I let it charge more. The Nexus turned on!... But got stuck on the Google screen. So I try and use fastboot and starting it from there. "Boot failed". So, maybe no OS? Try using ADB to flash stock android onto the device. "Failed (Bootloader locked)". Ok, ill just unlock the bootloader. "Unlock failed (unknown error)" . Maybe flashing a new recovery will work? Nope, has to be unlocked. So far, nothing has worked. Spent 2 hours trying to flash, unlock and factory reset, and nothing but "failed" has come up. The device can't even go into recovery mode. When connected to adb, The list of adb devices is blank. It knows the device is connected, but it doesn't show the name or model.
Anyone know what to do?? (I have never tried to flash anything previous from today on this tablet.)
last night i got the notification to say that i was able to update to 7.0 and i was so excited that i kinda forgot about xposed and stuff and now
the phone is completely useless it wont turn on it just does nothing, when its charging the white light flashes but still nothing Please help
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
echo92 said:
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
Click to expand...
Click to collapse
nope not seeing it
Hmm, so you're not getting anything showing up in Device Manager (like in this thread https://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943 )?
I am not familiar with the procedure of how to unbrick a device like this, vache has uploaded a blank flash file (https://forum.xda-developers.com/showpost.php?p=70701015&postcount=1975), I hope someone else can guide you on the procedure to unbrick your phone if you need such a file.
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
thankyou it worked perfectly
The same here after update!
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
alemangioni said:
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
Click to expand...
Click to collapse
If fastboot still works, perhaps try this fastboot Nougat image, see if that'll flash? https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
It requires you booting into bootloader (so power down your device, wait 5 seconds then hold the volume down and power button, should then boot into bootloader), so it might flash a working recovery and system onto your device.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
I believe there are two possible reasons...
Either 2-3 minutes forces a fully hard reset.
Or
If you have a really really flat battery sometimes as it charges and then boots up it gets stuck in repeated reboot since effort to boot drains more than it can charge in that time, so holding power button holds boot sequence long enough for battery to gain enough charge to allow boot to work..
Both are just my opinions so might be completely wrong
I think it's Option no1, because in my case the battery was nearly full charged.
Nevertheless... One guy happy to have helped, the other guy happy to have reanimated his phone:laugh:
Good day to everyone.
Today I needed to factory reset my phone. When I did so, the phone booted to TWRP, and didn't let me finish booting. I learned that was because of Android Nougats boot protection, so I decided to update to Oreo while I was at it, following this guide (also relocked the bootloader as well}:
HTTPS://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Having finished updating, I restarted my phone, and the No Command screen was there. No problem, I thought. Having arrived at the Welcome Screen, I omitted giving any information, not even a WiFi connection (my phone screen is broken).
Afterwards, I decided to turn off the phone.
And here's the problem. When I either turn on the phone again, or even charging it, it boots straight into the fallen Android screen (No Command). No matter what I do, it always starts from there. To get the phone again into the Welcome Screen, I must go to the bootloader and press the power button on Start.
Any Ideas?
Comments will be severely appreciated.
Update: Also can't relock Bootloader
max19942012 said:
Good day to everyone.
Today I needed to factory reset my phone. When I did so, the phone booted to TWRP, and didn't let me finish booting. I learned that was because of Android Nougats boot protection, so I decided to update to Oreo while I was at it, following this guide (also relocked the bootloader as well}:
HTTPS://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Having finished updating, I restarted my phone, and the No Command screen was there. No problem, I thought. Having arrived at the Welcome Screen, I omitted giving any information, not even a WiFi connection (my phone screen is broken).
Afterwards, I decided to turn off the phone.
And here's the problem. When I either turn on the phone again, or even charging it, it boots straight into the fallen Android screen (No Command). No matter what I do, it always starts from there. To get the phone again into the Welcome Screen, I must go to the bootloader and press the power button on Start.
Any Ideas?
Comments will be severely appreciated.
Update: Also can't relock Bootloader
Click to expand...
Click to collapse
I'm exactly with the same problem as you mentioned don't know what else can i do !
Fixed following this
https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
ygoralmeida said:
Fixed following this
https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
Click to expand...
Click to collapse
Many thanks now, man. This absolutely worked!