Related
I tried to root my Moto G4, and oh boy that was a big mistake. After successfully installing TWRP, I went to install SuperSu. Now, my phone can do one of two things: be at the bootloader menu or boot up TWRP. And so to fix this I downloaded the official Motorola imgs for my device and was planning on flashing them to my Moto G4. But now, in the bootloader adb won't recognize my device. In TWRP, it's recognized, but I cannot run any fastboot commands, so I can't flash the stock image. Any idea how to fix this monstrosity of a situation? I just want to have my phone back; I don't even care if it gets rooted anymore...
bootloader = fastboot, Adb has nothing to do there. You flashed TWRP and didnt you make a backup after? Oh god big mistake
Kyle.Donoghue said:
I tried to root my Moto G4, and oh boy that was a big mistake. After successfully installing TWRP, I went to install SuperSu. Now, my phone can do one of two things: be at the bootloader menu or boot up TWRP. And so to fix this I downloaded the official Motorola imgs for my device and was planning on flashing them to my Moto G4. But now, in the bootloader adb won't recognize my device. In TWRP, it's recognized, but I cannot run any fastboot commands, so I can't flash the stock image. Any idea how to fix this monstrosity of a situation? I just want to have my phone back; I don't even care if it gets rooted anymore...
Click to expand...
Click to collapse
First of all - don't panic and do something to make things worse. The fact you can get to TWRP is very encouraging. While in the bootloader, and with your phone connected to your PC open a command line window in your directory that contains the fastboot and adb files. type the command "fastboot devices" and see if your phone shows up. If it does then you can flash the stock image for your phone. It can be found on various posts in these forums.
Did you root your phone following the proper procedure found here? - https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592 I am guessing you didn't since you soft bricked your phone.
---------- Post added at 05:20 PM ---------- Previous post was at 05:11 PM ----------
lerg96 said:
bootloader = fastboot, Adb has nothing to do there. You flashed TWRP and didnt you make a backup after? Oh god big mistake
Click to expand...
Click to collapse
Seriously? This is all you have to offer??? Not much help dude!
pastorbob62 said:
Seriously? This is all you have to offer??? Not much help dude!
Click to expand...
Click to collapse
I just wanted to make difference between both :laugh::laugh:
But he dont give us enough information
Root method? Android OS? And bro bootloader with adb? theres two things I guess he did, he confused the terms and instead of typing 'fastboot' he wrote 'adb' OR, he really tried to flash a .zip or img with adb inside the bootloader
PD: come, dont get mad at me. Give me a hug
Kyle.Donoghue said:
I tried to root my Moto G4, and oh boy that was a big mistake. After successfully installing TWRP, I went to install SuperSu. Now, my phone can do one of two things: be at the bootloader menu or boot up TWRP. And so to fix this I downloaded the official Motorola imgs for my device and was planning on flashing them to my Moto G4. But now, in the bootloader adb won't recognize my device. In TWRP, it's recognized, but I cannot run any fastboot commands, so I can't flash the stock image. Any idea how to fix this monstrosity of a situation? I just want to have my phone back; I don't even care if it gets rooted anymore...
Click to expand...
Click to collapse
You forgot to flash ElementalX, dummy. Maybe if you read the instructions you wouldn't have issues.
Since you have TWRP installed I recommend using one of the optimized stock ROM builds over on the G4 Plus forum (everything for the G4 Plus can be flashed on the G4).
If not, then you need to know that fastboot =/ adb- you need fastboot installed. If you're on Windows, Minimal ADB and fastboot is the way to go. If you're on a debian based distro, run "sudo apt-get install fastboot". You also need Motorola Device Manager drivers installed.
Hi guys,
I am a total noob with flashing etc.
Can somebody please be so nice to post here the right tutorial for my case? I want the Original Firmware.
I have read so many threads but they all sound different for me. :silly:
I have got an Motorola X Pure Edition from Ebay. It has Android 6.0 installed. I want to update to 7.0 but when it downloads the new firmware it will reboot and TWRP starts. I have downloaded the firmware 7.0 manually and tried to run it with TWRP but I get always error messages.
According to Bootloader:
Product: clark XT1575 32G P3C
Devise is unlocked
Status Code: 3
Software Status Modified
Do you need information about Baseband Version, Kernel and so on?
Appreciate your help :victory:
Nougat firmware for XT1575 is on androidfilehost.com linked to this thread. The linked thread includes instructions on how to use fastboot to flash the update. Updated baseband, kernel and all that are included in the full firmware package.
You'll need a PC setup for flashing too. Assuming you're using a windows PC you'll need to moto drivers you can get from here, and a minimal fastboot installation you can get from here.
Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.
Muffycheeks said:
Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.
Click to expand...
Click to collapse
No, you don't need to worry about returning to stock 6.0 to get an XT1575 to 7.0 anymore. Motorola-Firmware-Team released a leaked full firmware package for clark_retus-user 7.0 NPH25.200-22 linked to that acejavelin thread that I linked to. It isn't an incremental update, it is the whole package. Thanks to that, you don't have to return to fully stock 6.0, take or sideload an OTA, and hope for the best anymore.
Motorola Device Manager - Windows 10
Thanks guys for your comments.
Unfortunately I have already problems with the Motorola Device Manager (MDM). Seems like the drivers wont install.
Fastboot message = waiting for any device
I have run the MDM as an admin, activated USB Debugging and MTP but after installation of the MDM i get the congratulations message but i cant open the program.
I have installed the Media Feature Pack for Windows 10 and tried it again without success.
When i open the Motorola_Mobile_Drivers_64bit file from the Temp folder i can Repair or Remove Motorola Mobile Drivers Installation 6.4.0 but I can`t run it.
Other cable and USB Port does not help either.
Device Manager: Android Device --> Motorola ADB Interface
Any ideas how to fix this issue?
Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson
dzidexx said:
Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson
Click to expand...
Click to collapse
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found
Jonasson said:
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found
Click to expand...
Click to collapse
https://youtu.be/3Q8b0SuGvmI
https://www.google.pl/search?q=inst...1ZHYAhVN2aQKHSi7AoIQ_AUIESgB&biw=1056&bih=660
https://www.google.pl/search?biw=10...k1j0i8i30k1j0i8i13i30k1j30i10k1.0.Pe-SF0MQFkc
Go to movies in google results.
Thanks to all of you. I finally understood how it works. :angel:
Android 7.0 on it :good::victory:
Hi guys,
I did the update with above tutorial to Android Version 7.0. (Android security patch level: 1.September.2017)
But now they ask me to download new Android security updates . (New system software: 25.201.1 (8,0 MB)
Unfortunately when it is doing the restart it shows the error message:
Error!
And it shows a dead Android Robot.
Any ideas what has gone wrong. Not sure why I get the Software-update failure after doing the upgrade successfully from 6.0 to 7.0.
Moto X Pure Edition
Probably you forgot something, I think:
fastboot flash recovery recovery.img
dzidexx said:
Probably you forgot something, I think:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks dzidexx..it does finally work
hello . i need NPH25.200-22-1 android for moto x pure;
any idea?
morvarid said:
hello . i need NPH25.200-22-1 android for moto x pure;
any idea?
Click to expand...
Click to collapse
No full images were ever released/leaked for anything newer than:
Style: NPH25.200-15
Pure: NPH25.200-22
You either need to get one of those to work for you, or move on to something else or a custom ROM. Sorry, but the version you have was never released as am image (that -1 sub version probably never was a full image internal to Moto either, most likely an OTA only) and no later version has ever leaked out. You can stop asking in multiple threads, the answer is the same.
Solved (update)
In the end I finally understand that it was possible reinstall a stock rom with Android Nougat, the hard part was find the correct stock rom, then with fastboot method, one command at the time I managed to get back my phone with stock Nougat and solve the reboot issue.
Now I will wait if the official Oreo update comes for this phone too and see if it can be updated.
High everybody's, I see there's few trend that talk to the same problem I'm experiencing with my moto g4, but none one get a solution to this, so I try too.
First, I'm using a resurrection remix rom (nougat), when I reboot or turn off and then on again the phone goes always in recovery (twrp). So I have to select reboot to bootloader and from there select start to properly boot the phone.
I already try using this command from my PC with the phone connected in fastboot mode:
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
But nothing happened.
I can change the ROM if it worth to solve the problem, also I see there's a resurrection remix with android Oreo or wait for official Oreo ota that could possibly be on line soon.
Second, in case I can't solve it with a custom rom, there's a way to come back to the original ROM (android 6), and wait for the official update or the downgrade it is impossible?
Thanks to anyone that can give me any advice or help.
Well, how did you fix the recovery boot issue?
shadymnms said:
Well, how did you fix the recovery boot issue?
Click to expand...
Click to collapse
Hi, thanks to the help of @echo92 in this forum, here the link of the topic: https://forum.xda-developers.com/mo...e-nougat-to-marshmallow-t3487201?goto=newpost
He share the proper and last official nougat stock ROM NPJS25-93-14.7-8, is specific to XT1625/XT1644 my device it's XT1625.
Then connecting my device to my PC and using fastboot command I reinstall each part of the stock firmware.
If you search the way to use fastboot command here one of the topic where explain it: https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Bye
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
akhil520c said:
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using Tapatalk
If you can't install TWRP on pie, try reverting to Oreo with AFT and then flash TWRP in fastboot. Also make sure you have unlocked the bootloader whether by the official tool or the unofficial method. THIS WILL DELETE ALL DATA SO BACK UP.
Thanks arko. Is there Asus Flash Tool available for Linux also? Will try and revert. Thanks :svetius
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
akhil520c said:
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
Click to expand...
Click to collapse
Windows 10 ? Its bcuz Driver Signature Enforcement
Disable it and reinstall adb and fastboot drivers, it will work for sure.
Windows driver security wouldn't accept drivers without proper Signatures,so like i said, just disable it and you are good to go.
:good:
Tried steps you mentioned, doesn't work. In fastboot mode, #fastboot devices gives me no output. Looks like my pie ROM is buggy. Basically, I need to install lineage on the phone.
Hi all,
Finally got everything done in about 5 mins I booted up Ubuntu Mate (32 bit) on my other laptop, and found I'd already installed adb and fastboot on it from the repositories (not from google). I booted my phone in fastboot mode, and tried the #fastboot devices command, and voila, my phone got detected! After that, it was a matter of a few minutes, following the installation instructions (of twrp and lineage) from the lineage website. Thanks for all your inputs and help
P.S: I realised (again), after more than 2 decades, that windoze mighty sucks lol.
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.