OnePlus 2 Permanently Screwed??? - OnePlus 2 Q&A, Help & Troubleshooting

So I've been sick of the freezing and glitches of the stock non-rooted OnePlus 2. So I decided to root and install custom ROM. All went well, unlocked bootloader and installed TWRP, then installed ROM. Easy, or so I thought...
The ROM I selected I ended up not liking, so I wiped and tried to install another, which failed in TWRP. I went to flash yet another ROM and while wiping, accidentally wiped entire SDCard. With ADB side load I loaded the Oxygen 3.0 Beta onto my device (which is now how I am typing to you).
The Beta OS somehow corrupted my TWRP recovery and now no longer boots. I tried following many DIY articles on restoring my recovery. But now my bootloader is locked and will not unlock, so I tried the DIY Qualcomm Diagnosis recovery, which doesn't work. I disable windows driver signing, then plug in the device, enter Qualcomm mode, and attempt to install the drivers. They don't work, Windows 8.1 tells me they are already up to date. So I uninstall the device via Device Manager and attempt to reinstall Qualcomm driver, which fails again. Somehow Windows 8.1 assumes again that the now unrecognizable USB device is up to date.
I use my phone for work purposes. It's working so I'm not in any rush, but the only way to boot my device now is to use Windows to issue the command: fastboot continue
I'm extremely irritated with this device. Someone please help before I buy a Nexus and take this POS outback with my handgun, lol

wallacengineering said:
So I've been sick of the freezing and glitches of the stock non-rooted OnePlus 2. So I decided to root and install custom ROM. All went well, unlocked bootloader and installed TWRP, then installed ROM. Easy, or so I thought...
The ROM I selected I ended up not liking, so I wiped and tried to install another, which failed in TWRP. I went to flash yet another ROM and while wiping, accidentally wiped entire SDCard. With ADB side load I loaded the Oxygen 3.0 Beta onto my device (which is now how I am typing to you).
The Beta OS somehow corrupted my TWRP recovery and now no longer boots. I tried following many DIY articles on restoring my recovery. But now my bootloader is locked and will not unlock, so I tried the DIY Qualcomm Diagnosis recovery, which doesn't work. I disable windows driver signing, then plug in the device, enter Qualcomm mode, and attempt to install the drivers. They don't work, Windows 8.1 tells me they are already up to date. So I uninstall the device via Device Manager and attempt to reinstall Qualcomm driver, which fails again. Somehow Windows 8.1 assumes again that the now unrecognizable USB device is up to date.
I use my phone for work purposes. It's working so I'm not in any rush, but the only way to boot my device now is to use Windows to issue the command: fastboot continue
I'm extremely irritated with this device. Someone please help before I buy a Nexus and take this POS outback with my handgun, lol
Click to expand...
Click to collapse
Did you try the FirstAid kit ?

As far as I know, with OOS3 beta, it uses a different firmware which causes the official TWRP to not boot. I believe you have to use a customized version of TWRP (should be somewhere on XDA or OP Forums) with OOS3. You should be able to flash that version of TWRP. Then, reboot into TWRP, flash OOS2, and then the official TWRP from within the custom TWRP. Then reboot to recovery and flash whatever you wish besides OOS3 or H2OS 6.0. Good luck!

As said above, here is a modified TWRP for OOS3 https://www.androidfilehost.com/?fid=24459283995297945
But by all means use any TWRP listed as OOS3 compatible, then push the .img file using the fastboot flash recovery command.

jbw716 said:
As far as I know, with OOS3 beta, it uses a different firmware which causes the official TWRP to not boot. I believe you have to use a customized version of TWRP (should be somewhere on XDA or OP Forums) with OOS3. You should be able to flash that version of TWRP. Then, reboot into TWRP, flash OOS2, and then the official TWRP from within the custom TWRP. Then reboot to recovery and flash whatever you wish besides OOS3 or H2OS 6.0. Good luck!
Click to expand...
Click to collapse
Benoys-Air:fastboot benoyanthony$ ./fastboot-mac oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Benoys-Air:fastboot benoyanthony$ ./fastboot-mac flash recovery OP2.img
target reported max download size of 536870912 bytes
sending 'recovery' (31501 KB)...
OKAY [ 0.710s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.727s
______________________
I am facing this issue, anybody pls help.

Follow this guide, you data would still be safe.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
for further help ping me.

Also, read up on OxygenOS 3 and HydrogenOS bootloader and compatible TWRP recovery.

jbw716 said:
As far as I know, with OOS3 beta, it uses a different firmware which causes the official TWRP to not boot. I believe you have to use a customized version of TWRP (should be somewhere on XDA or OP Forums) with OOS3. You should be able to flash that version of TWRP. Then, reboot into TWRP, flash OOS2, and then the official TWRP from within the custom TWRP. Then reboot to recovery and flash whatever you wish besides OOS3 or H2OS 6.0. Good luck!
Click to expand...
Click to collapse
Thank you very much I had no idea that 3.0 Beta used different firmware.Although the bootloader was still locked, I was able to finally get the damn drivers on my PC and used the full restore kit. That put me on Hydrogen OS, so I installed Oxygen 2.0 and stock recovery, it works again. Now Im re-updated to 3.0 Beta fully working and am now going to root it and back it up.

Related

Erased phones recovery

Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.
Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.
fixed it i was just being foolish, someone delete this thread it is of no use.
Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

TWRP on Nougat

I saw where someone said you could flash B20 bootloader and flash TWRP on Nougat, is this true? Is anyone working on a guide for Nougat TWRP and root. On another note I thought that I read that ZTE would be bringing Wifi calling for Nougat with carries such as T-Mobile? I was unable.to find it under options and assume that it is not possible, anyone have any idea about this.
Thanks
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
jim262 said:
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
Click to expand...
Click to collapse
I got TWRP 3.0.4 installed (as well as 3.0.3-1)... It installed sucessfully via Fastboot for me, I even flashed SU, but I couldn't get my phone to boot into the OS (tried with and without SU).......It just hung at the boot pre-boot screen (where it warns you the bootloader is unlocked). I'd restart it, and it always hangs at that screen..... Only way to fix it was to boot back into TWRP, revert back to B29 (using DrakenFX guide) and then update to Nougat again. I spent about 16 hours straight working on this on Tuesday, before I gave up and decided to keep it stock until a custom ROM comes out, soon (Z.A.D. v.4), hopefully?
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
xDaDeevellopar said:
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
Click to expand...
Click to collapse
You probably pushed the power button to "Start"? Try letting it sit there about 10-15 seconds, if it won't boot...This is the exact same problem I had. I had to go back to B29, then do the update again. There is now a B15 "return to stock" walk-through, that may be the quicker route.....But I know returning to B29, turning on OEM Unlock in Dev options and then taking the update via your SD card was what I did (3 times in one day).
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
bornlivedie said:
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axo...overy-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axo...-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
Click to expand...
Click to collapse
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
tele_jas said:
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
Click to expand...
Click to collapse
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
bornlivedie said:
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Click to expand...
Click to collapse
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
tele_jas said:
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
Click to expand...
Click to collapse
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
bornlivedie said:
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
Click to expand...
Click to collapse
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
tele_jas said:
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
Click to expand...
Click to collapse
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
bornlivedie said:
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
Click to expand...
Click to collapse
The MiFlash program found my phone, but failed every time I ran it.. So, I just bit the bullet and downloaded the latest TWRP 3.0.4-1 and flashed that.....And it worked! I then flashed SU, my fonts and changed my Emoji's....I'm about there with customization, and it's all booting up just fine!
But, yes the first few times I did allow system modifications......But I also did this last time too and it's working fine?

[Solved] HELP! Phone won't boot from twrp!

I've unlocked the bootloader, flashed twrp from pc and I was going to flash the supersu zip. Unfortunately, when I went in recovery (twrp) and flashed the supersu zip(installation process didn't show any problem) I clicked reboot and the phone didn't boot! It just turns off(no led or similar). I have fastboot and twrp access, I tried flashing omnirom using the adb sideload command, everything went fine but still when pressing reboot nothing happens! I even tried to boot manually (after flashing the ROM) with the physical button but still nothing(this time the led blinked twice).
I used the latest version of twrp for Athene, version 2.82 of supersu if this could help.
Edit: was it necessary to flash a different kernel, as it was a nougat rom? The rooting guide I followed didn't mention that.
Edit: Everything worked fine before Supersu, the problem must be related to Supersu but how can I solve?
Generally, on stock Nougat ROMs (not custom ROMs in general), you will need a custom kernel if you want to root. Else, the strict anti rooting protections in the stock Motorola kernel on Nougat devices will trip and stop you from booting your device.
You could try clearing the misc partition as described here (I've not tried it, so be very careful) https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 to try to reset the boot issue.
If that doesn't work, we may have to repair with a stock ROM flash via fastboot. Can you remember what stock ROM you last had?
I appreciate there are a lot of rooting guides (albeit most are out of date), for future reference, here's a guide that still works: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
echo92 said:
Generally, on stock Nougat ROMs (not custom ROMs in general), you will need a custom kernel if you want to root. Else, the strict anti rooting protections in the stock Motorola kernel on Nougat devices will trip and stop you from booting your device.
You could try clearing the misc partition as described here (I've not tried it, so be very careful) https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 to try to reset the boot issue.
If that doesn't work, we may have to repair with a stock ROM flash via fastboot. Can you remember what stock ROM you last had?
I appreciate there are a lot of rooting guides (albeit most are out of date), for future reference, here's a guide that still works: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
The stock rom was the stock one with android Nougat 7.0, I don't remember any other information Moreover there is a omni rom now, as i wrote before.
Edit:
The device is Motorola Moto G4 XT1622
Stefano Barbotto said:
The stock rom was the stock one with android Nougat 7.0, I don't remember any other information Moreover there is a omni rom now, as i wrote before
Click to expand...
Click to collapse
When you flashed omnirom via ADB side load, did you erase /system, /data, cache and dalvik before flashing omnirom?
Latest stock ROM for EU is here by the way https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
echo92 said:
When you flashed omnirom via ADB side load, did you erase /system, /data, cache and dalvik before flashing omnirom?
Latest stock ROM for EU is here by the way https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
No I didn't, I know I should have done this, though
Edit: So, should I try with the partitions or directly flash stock rom? What do you suggest? The xda page related to partitions was related to another issue....
Stefano Barbotto said:
No I didn't, I know I should have done this, though
Edit: So, should I try with the partitions or directly flash stock rom? What do you suggest? The xda page related to partitions was related to another issue....
Click to expand...
Click to collapse
Okay, the partitions page was an idea to get you out of the TWRP boot issues you had.
For now though, the priority is to get your device running, you could try reflashing omnirom after erasing /system, /data, /dalvik and /cache ( so removing your stock system and data, I hope you backed up). Try booting with the custom ROM. Since you've got TWRP access, this would be easiest, you can always copy files to your device whilst in TWRP and connected via USB.
If that doesn't get your device running or you want to revert back to stock, them flash the stock ROM in fastboot.
echo92 said:
Okay, the partitions page was an idea to get you out of the TWRP boot issues you had.
For now though, the priority is to get your device running, you could try reflashing omnirom after erasing /system, /data, /dalvik and /cache ( so removing your stock system and data, I hope you backed up). Try booting with the custom ROM. Since you've got TWRP access, this would be easiest, you can always copy files to your device whilst in TWRP and connected via USB.
If that doesn't get your device running or you want to revert back to stock, them flash the stock ROM in fastboot.
Click to expand...
Click to collapse
I didn't even back up the rom from twrp, I totally forgot. I only have information backed up from the motorola account(which is not the back up of the rom, of course). Anyway, I'll try flashing and tell you, thanks for the help
echo92 said:
Okay, the partitions page was an idea to get you out of the TWRP boot issues you had.
For now though, the priority is to get your device running, you could try reflashing omnirom after erasing /system, /data, /dalvik and /cache ( so removing your stock system and data, I hope you backed up). Try booting with the custom ROM. Since you've got TWRP access, this would be easiest, you can always copy files to your device whilst in TWRP and connected via USB.
If that doesn't get your device running or you want to revert back to stock, them flash the stock ROM in fastboot.
Click to expand...
Click to collapse
Tried to flash the stock rom you seggested in fastboot mode (followed the instructions in the link you provided), everything worked fine but the phone dosn't boot and remains connected and blinks....I don't know what else to do.
Stefano Barbotto said:
Tried to flash the stock rom you seggested in fastboot mode (followed the instructions in the link you provided), everything worked fine but the phone dosn't boot and remains connected and blinks....I don't know what else to do.
Click to expand...
Click to collapse
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
echo92 said:
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
Click to expand...
Click to collapse
Here is the output from the command "fastboot getvar all":
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2239WC6B
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A40BEC0000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354123071313730
(bootloader) meid:
(bootloader) date: 06-02-2016
(bootloader) sku: XT1622
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 5:47:54 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:7.0/NPJS25.
(bootloader) ro.build.fingerprint[1]: 93-14-10/10:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.221.10.athene.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.01R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g9b51918 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Mon Aug 28 09:30:48 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.06-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.422s
echo92 said:
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
Click to expand...
Click to collapse
As for the outputs of the flashing commands, I couldn't copy them, as I used the OEM flash provided by the author of the post(the window opened and closed automatically) rather than manually inputing the commands in the prompt. I'll try manually and tell you
echo92 said:
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
Click to expand...
Click to collapse
As for the outputs from the flashing commands, I wasn't able to copy them, as I used the "OEM flash" file (from the author of this link :https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138) which automatically opened and closed the prompt
Stefano Barbotto said:
As for the outputs from the flashing commands, I wasn't able to copy them, as I used the "OEM flash" file (from the author of this link : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138) which automatically opened and closed the prompt
Click to expand...
Click to collapse
Okay, that script should work and looking at the getvar log, it looks like the firmware flashed okay (your bootloader, baseband and system all match), so I'm confused as to why your device is failing to boot...
Can you try manually flashing and reporting back if you get all [OKAY] responses? By manually flashing, I mean copying each command into the ADB terminal in sequence, then executing each command, seeing the [OKAY] before proceeding. That way, we can be sure we have stock fully and no trace of root which might be tripping the checks. I'd like to see the output if possible
echo92 said:
Okay, that script should work and looking at the getvar log, it looks like the firmware flashed okay (your bootloader, baseband and system all match), so I'm confused as to why your device is failing to boot...
Can you try manually flashing and reporting back if you get all [OKAY] responses? By manually flashing, I mean copying each command into the ADB terminal in sequence, then executing each command, seeing the [OKAY] before proceeding. That way, we can be sure we have stock fully and no trace of root which might be tripping the checks. I'd like to see the output if possible
Click to expand...
Click to collapse
I really, extremely apologize for being so dumb : I forgot to unzip the stock rom file, so the files weren't recognised while I was entering the commands. The phone is now perfectly working, thanks again for the great help!
By the way, If I wanted to to root the device, how should I install another kernel?
Stefano Barbotto said:
I really, extremely apologize for being so dumb : I forgot to unzip the stock rom file, so the files weren't recognised while I was entering the commands. The phone is now perfectly working, thanks again for the great help!
By the way, If I wanted to to root the device, how should I install another kernel?
Click to expand...
Click to collapse
If you flashed TWRP you can install the kernel with twrp.
Stefano Barbotto said:
I really, extremely apologize for being so dumb : I forgot to unzip the stock rom file, so the files weren't recognised while I was entering the commands. The phone is now perfectly working, thanks again for the great help!
By the way, If I wanted to to root the device, how should I install another kernel?
Click to expand...
Click to collapse
Woo, we got your device working
If you're still interested in rooting on stock Nougat and flashing a custom kernel (I use ElementalX here for reference, but other custom kernels suitable for Nougat 7.0 stock Motorola athene ROMs should work, like vegito), assuming your bootloader is unlocked:
1)Download ElementalX and your choice of root manager onto your device. ElementalX v1.04 is designed for stock Motorola 7.0 ROMs : https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
2)Flash or boot TWRP. Up to you which TWRP build you use, I prefer shreps' TWRP 3.1.1 athene (https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 ) but the official builds should suffice.
Boot your device to the bootloader and connect your device to your computer. In the ADB terminal, flash TWRP to your recovery partition if you see yourself using TWRP a lot, remember to boot into recovery after flashing to ensure TWRP is not overwritten by the stock recovery (assuming your device is still in the bootloader mode following the flash, use the volume keys on your device after flashing TWRP to select Recovery on your device, then press Power to boot into recovery). You may boot as normal afterwards.
Alternatively, you can temporarily boot in TWRP, which should keep your recovery partition stock but mean you'll have to require a computer to use TWRP.
To boot into TWRP, boot your device to the bootloader and connect to your computer. Copy the TWRP image to your ADB folder. In the ADB terminal type:
Code:
fastboot boot <name of TWRP image>
The <name of TWRP image> should be the full file name (without the greater than/less than signs), you can start typing the first letters of the image name and press Tab on your keyboard to auto-complete if the file is present in the same folder (which it should be if copied to your ADB folder). Ensure that the file name has the correct file name extensions, you may wish to enable file extensions in Windows File Explorer to check, tab auto-complete will do this for you.
3)In TWRP, back up your device using the Backup option (usually everything except cache which should be the default selection).
3a)Also, make a separate backup of the boot partition - this 16 MB partition contains your clean, stock kernel (if you fully flashed the stock firmware).
4)Tap Install in TWRP, and navigate to your Download folder or wherever your ElementalX zip is stored. Flash ElementalX as directed by the installer. After flashing, wipe cache/Dalvik (should appear as an option on screen).
5)After flashing ElementalX, you can choose to flash your choice of root manager or reboot first to check your device is still running. If it's still working, then you can reboot to TWRP (either by rebooting to recovery or using a PC to temporarily boot). Flash your root manager in TWRP (same way as you flashed ElementalX) and then reboot, you should have a stock ROM rooted and booting
A few things to note:
As you'd have TWRP and root, OTA stock updates won't work, and taking an OTA update would soft bootloop your device in TWRP. There are ways to get around this, but you may wish to disable the Motorola updater to stop you being nagged/accidentally downloading the OTA update https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
If you want OTA updates, you'd have to revert to stock fully, but we'll get to that when the time comes.
Rooting with SuperSU may mean that SafetyNet fails - this is Google's anti-tamper/anti-rooting detection, and thus some apps may fail to work. You may use SuperSU hide https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855 or magisk's built-in magiskhide to hide the root manager from detection.
If you have any issues whilst rooting, you may choose to use the backups you made in 3)
If you want to switch custom kernels or change root manager, then I recommend:
a)Uninstall root via your root manager's uninstall procedure. For example, SuperSU has an uninstall function in the SuperSU app, magisk requires a TWRP flashable uninstaller.
b)Reboot into TWRP (if not already in TWRP)
c)Restore the stock kernel backup you made above in 3a). This should remove traces of root from your kernel that may conflict with your new kernel and cause chaos.
d)Flash your new custom kernel of choice followed by your root manager.
e)Wipe cache/Dalvik and reboot.
Good luck
echo92 said:
Woo, we got your device working
If you're still interested in rooting on stock Nougat and flashing a custom kernel (I use ElementalX here for reference, but other custom kernels suitable for Nougat 7.0 stock Motorola athene ROMs should work, like vegito), assuming your bootloader is unlocked:
1)Download ElementalX and your choice of root manager onto your device. ElementalX v1.04 is designed for stock Motorola 7.0 ROMs : https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
2)Flash or boot TWRP. Up to you which TWRP build you use, I prefer shreps' TWRP 3.1.1 athene (https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 ) but the official builds should suffice. Flash TWRP to your recovery partition if you see yourself using TWRP a lot, remember to boot into recovery after flashing to ensure TWRP is not overwritten by the stock recovery (use the volume keys your device after flashing TWRP to select Recovery on your device, then press Power to boot into recovery). You may boot as normal afterwards.
Alternatively, you can temporarily boot in TWRP, which should keep your recovery partition stock but mean you'll have to require a computer to use TWRP.
To boot into TWRP, boot your device to the bootloader and connect to your computer. Copy the TWRP image to your ADB folder. In the ADB terminal type:
Code:
fastboot boot <name of TWRP image>
The <name of TWRP image> should be the full file name (without the greater than/less than signs), you can start typing the first letters of the image name and press Tab on your keyboard to auto-complete if the file is present in the same folder (which it should be if copied to your ADB folder). Ensure that the file name has the correct file name extensions, you may wish to enable file extensions in Windows File Explorer to check, tab auto-complete will do this for you.
3)In TWRP, back up your device using the Backup option (usually everything except cache which should be the default selection).
3a)Also, make a separate backup of the boot partition - this 16 MB partition contains your clean, stock kernel (if you fully flashed the stock firmware).
4)Tap Install in TWRP, and navigate to your Download folder or wherever your ElementalX zip is stored. Flash ElementalX as directed by the installer. After flashing, wipe cache/Dalvik (should appear as an option on screen).
5)After flashing ElementalX, you can choose to flash your choice of root manager or reboot first to check your device is still running. If it's still working, then you can reboot to TWRP (either by rebooting to recovery or using a PC to temporarily boot). Flash your root manager in TWRP (same way as you flashed ElementalX) and then reboot, you should have a stock ROM rooted and booting
A few things to note:
As you'd have TWRP and root, OTA stock updates won't work, and taking an OTA update would soft bootloop your device in TWRP. There are ways to get around this, but you may wish to disable the Motorola updater to stop you being nagged/accidentally downloading the OTA update https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
If you want OTA updates, you'd have to revert to stock fully, but we'll get to that when the time comes.
Rooting with SuperSU may mean that SafetyNet fails - this is Google's anti-tamper/anti-rooting detection, and thus some apps may fail to work. You may use SuperSU hide https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855 or magisk's built-in magiskhide to hide the root manager from detection.
If you have any issues whilst rooting, you may choose to use the backups you made in 3)
If you want to switch custom kernels or change root manager, then I recommend:
a)Uninstall root via your root manager's uninstall procedure. For example, SuperSU has an uninstall function in the SuperSU app, magisk requires a TWRP flashable uninstaller.
b)Reboot into TWRP (if not already in TWRP)
c)Restore the stock kernel backup you made above in 3a). This should remove traces of root from your kernel that may conflict with your new kernel and cause chaos.
d)Flash your new custom kernel of choice followed by your root manager.
e)Wipe cache/Dalvik and reboot.
Good luck
Click to expand...
Click to collapse
Just a question: I already have twrp on my device(I normally access by powering off phone, then power+volume down keys, then I select recovery from the menu and I am in twrp), how do I know if it is already flashed to my recovery partition? Should I flash twrp from pc in fastboot mode again and then boot into recovery after flashing, as you wrote? Thanks in advance for the reply
Stefano Barbotto said:
Just a question: I already have twrp on my device(I normally access by powering off phone, then power+volume down keys, then I select recovery from the menu and I am in twrp), how do I know if it is already flashed to my recovery partition? Should I flash twrp from pc in fastboot mode again and then boot into recovery after flashing, as you wrote? Thanks in advance for the reply
Click to expand...
Click to collapse
If you've already got TWRP on your device and can not into it, then it's already flashed to your recovery partition. No need to flash it again.
Just boot into TWRP and follow from step 3 (backing up your device)
echo92 said:
If you've already got TWRP on your device and can not into it, then it's already flashed to your recovery partition. No need to flash it again.
Just boot into TWRP and follow from step 3 (backing up your device)
Click to expand...
Click to collapse
I can into it via the fastboot menu but not directly with the combination of power + volume down buttons(this sends me in fastboot mode). If I haven't misunderstood, this means it's already flashed to my recovery partition, is it right?
Stefano Barbotto said:
I can into it via the fastboot menu but not directly with the combination of power + volume down buttons(this sends me in fastboot mode). If I haven't misunderstood, this means it's already flashed to my recovery partition, is it right?
Click to expand...
Click to collapse
Volume down and power button combinations should always send you to the bootloader/fastboot mode (won't let you boot directly to recovery), then you can select recovery from the fastboot menu. If it's as you described, then yes, you already have TWRP flashed to your recovery partition and you're doing things correctly.
What I wrote in step 2) assumed your device was already booted into the bootloader mode to flash/boot TWRP. Hence, you can use the volume and power keys as you described to boot into TWRP recovery. I'll add that to make the procedure clearer
For clarity's sake:
Powered off device > Pressing the power and volume down keys > Bootloader/fastboot mode.
In bootloader/fastboot mode, select recovery from the fastboot menu with the volume keys. Press Power key to select
If you see:
TWRP logo - you have TWRP flashed to your recovery partition
OR a green Android on its back with No Command - that's stock recovery.

moto g4 wont boot

hi now I no you prob see this title and think oh another 1 but hear me out as I cant find any thing the same as the issue I'm having.
so I followed a rooting guide unlocked bootloader installed twrp all good installed supersu phone wont boot reinstalled twrp systemless installed supersu still nothing I have followed every guide I can find phone will only boot into twrp or bootloader I have flashed custom and stock roms however I do keep getting
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.071s
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
I have tried every way I can find still nothing when I try to boot it freezes on the screen saying my phone is unlocked and cant be trusted I'm now lost don't no were to go from here I did not back any thing up as the first thread I read don't say bout it and iv neva had any problems with any of my other phones or games consoles I no games consoles are different any help would be amazing
Most likely the flashing wasn’t complete or corrupted or the stock ROM wasn’t the correct one (Remember to be safe you’d have to flash the original ROM when you bought the phone) that being said. My suggestion you should try flashing TWRP again and boot into TWRP. Then flash stock ROM which will overwrite the current config. Not guaranteed, but it’s worth a shot.
Good luck.
Sent from my iPhone 7 Plus from Tapatalk
Sorry to sound dumb flash it through twrps? I can get twrps to boot but thats it iv flashed through bootloader putting all commands in separate but when i tried to boot it came up with no command with the andriod dude with a red triangle above him but i can flash and boot twrps after this
1) If you're rooting on stock Motorola Nougat ROMs, you need a custom kernel - attempting to root on the stock Motorola hudsoncm kernel usually results in a boot failure or bootloop as you've found. https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 for a useful guide, you can root with either magisk or SuperSU.
2)That security downgrade error suggests you're attempting to flash stock firmware older than the firmware matching your device's bootloader. If you need newer firmware, you could look into this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You'll need to flash this firmware via fastboot/the bootloader.
3) Try first of all booting into TWRP, copy a custom kernel to your device via a computer and USB cable, and then flash the custom kernel. See if that gets your device booting. If not, you may have to re-flash the stock firmware to get your device booting again (or use a backup, if you had one).
echo92 said:
1) If you're rooting on stock Motorola Nougat ROMs, you need a custom kernel - attempting to root on the stock Motorola hudsoncm kernel usually results in a boot failure or bootloop as you've found. https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 for a useful guide, you can root with either magisk or SuperSU.
2)That security downgrade error suggests you're attempting to flash stock firmware older than the firmware matching your device's bootloader. If you need newer firmware, you could look into this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You'll need to flash this firmware via fastboot/the bootloader.
3) Try first of all booting into TWRP, copy a custom kernel to your device via a computer and USB cable, and then flash the custom kernel. See if that gets your device booting. If not, you may have to re-flash the stock firmware to get your device booting again (or use a backup, if you had one).
Click to expand...
Click to collapse
If xt1625 amazon not having understood flash RSD firmware ATHENE_NPJS25.93-14-13 (instead ATHENE_AMZ_NPJ25.93-14.7) is there any way to restore the phone's load ?
bootloder lock, oem lock, "we have detected an attempt to flash unauthorized sw on your device"
hlpain said:
If xt1625 amazon not having understood flash RSD firmware ATHENE_NPJS25.93-14-13 (instead ATHENE_AMZ_NPJ25.93-14.7) is there any way to restore the phone's load ?
bootloder lock, oem lock, "we have detected an attempt to flash unauthorized sw on your device"
Click to expand...
Click to collapse
Have you tried to flash this firmware: https://androidfilehost.com/?fid=817906626617956922 That should be the AMZ NPJ25.93-14.7 US firmware (for XT1625 and XT1644)
tried, error gpt bootloader, all firmware below 14-13 not installed, AMZ NPJ25.93-14-13 I did not find it or it does not exist.
hlpain said:
tried, error gpt bootloader, all firmware below 14-13 not installed, AMZ NPJ25.93-14-13 I did not find it or it does not exist.
Click to expand...
Click to collapse
Unfortunately you'd have to wait for a newer firmware, the NPJS25.93-14-13, NPJS25.93-14-15 and NPJS25.93-14-18 firmwares are for retail devices. Amazon devices are on a different firmware and as you've partially flashed the Dec 2017 firmware, you'd likely need AMZ NPJ25.93-14.7-3 or NPJ25.93-14.7-5 (Feb 2018 update), however neither AMZ build appears to be available at the moment.
If you're desperate for a working device, your best bet may be to talk to Amazon or Motorola support, or if your bootloader was previously unlocked, you could try to unlock your bootloader and flash a custom ROM.
I will wait for a new firmware amz

Categories

Resources