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
Related
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.
ok, just got the ZE600KL, installed the latest OTA update of Android M, setup the phone and everything. Then only I realised that I cannot root the phone without unlocking the bootloader. Tried the official bootloader unlocker from Asus but it didnt work.
Had been looking low and high, Question:
1. Is there a way to unlock the bootloader since the official tool from Asus wont work? (and I understand that you must unlock the bootloader 1st by any means before rooting the phone)
2. I saw from some thread that there are pre-rooted image (I assumed that is the whole Android OTA update for the latest Android M but rooted), can I apply that onto a locked bootloader, and doing so will I be able to retain all my users files? How I do that?
I tried my best not to re-setup the whole phone but I really need to root the device so I can do more with my backup app and stuffs. Pls help.
learnyee said:
ok, just got the ZE600KL, installed the latest OTA update of Android M, setup the phone and everything. Then only I realised that I cannot root the phone without unlocking the bootloader. Tried the official bootloader unlocker from Asus but it didnt work.
Had been looking low and high, Question:
1. Is there a way to unlock the bootloader since the official tool from Asus wont work? (and I understand that you must unlock the bootloader 1st by any means befMore rooting the phone)
2. I saw from some thread that there are pre-rooted image (I assumed that is the whole Android OTA update for the latest Android M but rooted), can I apply that onto a locked bootloader, and doing so will I be able to retain all my users files? How I do that?
I tried my best not to re-setup the whole phone but I really need to root the device so I can do more with my backup app and stuffs. Pls help.
Click to expand...
Click to collapse
Why don't you try this?
Its been confirmed to work on Z00L device
sziraqui said:
Why don't you try this?
Its been confirmed to work on Z00L device
Click to expand...
Click to collapse
no working...the bootloader is locked. Shakalaca's pre-rooted patched system img doesnt have the version currently my phone is installed. The version on my phone is WW-21.40.1220.1698, but the image on the cloud is much higher version. Can I use the newer version and update my phone?
learnyee said:
no working...the bootloader is locked. Shakalaca's pre-rooted patched system img doesnt have the version currently my phone is installed. The version on my phone is WW-21.40.1220.1698, but the image on the cloud is much higher version. Can I use the newer version and update my phone?
Click to expand...
Click to collapse
Did you tried the unofficial method? Unlocking and then rooting is the best way to gain root access permanently. But if you still want to flash pre-rooted system.img, you can use ZE550KL's system.img (from shakalaca) irrespective of what version it is (Unless it is for the same android version i.e MM)
Warning: Don't flash anything other than system.img and/or boot.img. Flashing other parts may HARD BRICK your phone
sziraqui said:
Did you tried the unofficial method? Unlocking and then rooting is the best way to gain root access permanently. But if you still want to flash pre-rooted system.img, you can use ZE550KL's system.img (from shakalaca) irrespective of what version it is (Unless it is for the same android version i.e MM)
Warning: Don't flash anything other than system.img and/or boot.img. Flashing other parts may HARD BRICK your phone
Click to expand...
Click to collapse
Not working, stuck at SU.
C:\adb>fastboot oem device-info
< waiting for device >
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.008s]
finished. total time: 0.009s
C:\adb>adb shell
[email protected]_Z00M:/ $ su
/system/bin/sh: su: not found
127|[email protected]_Z00M:/ $ exit
C:\adb>
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.
Currently I have installed latest official nightly LineageOS 14.1 on my device. I want to return to stock ROM and lock bootloader. Previously, before bootloader unlocking, I had 6.0.1 stock, version with january security updates (probably).
I have downloaded latest stock 6.0.1 MPD24.107-52 ( https://github.com/motoxplay/stock ).
Unfortunately, I got an error when tried to flash it:
HTML:
$ fastboot flash partition gpt.bin
it returns:
HTML:
(bootloader) Preflash validation failed
same with recovery.img
To lock bootloader I have to flash all stock files.
Any ideas? Thanks
skip it. You cant flash same bootloader and same gpt.bin again.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
NOTE: You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin). At this point you can either continue the flash and NOT lock the bootloader at the end, or stop until you can find the most current image. Moto used to be quite willing to hand these out when they were requested, so if you have a very new firmware installed you may not find one that you can use to relock with on the Internet. Part of the requirements to lock the bootloader is you must successfully flash the partition table (gpt.bin) in order to complete the lock process, if you can't then the bootloader lock process cannot be finished.
Click to expand...
Click to collapse
so i have to wait for the official nougat flashable file.
bump
any workaround?
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory: