Hi, I'm trying to get my phone back to normal state. It was on Nougat 7.0 I would like to get it on 6.0.1. but I'm so new know where to begin. It's also a Republic Wireless (not a major carrier) so I'm not sure how to start messing with this thing. I ran in to a problem last night trying to put on Magisk because I wanted the option of hiding root and it got stuck in a bootloop. I wasn't sure i could get it back but i did with Lineage OS now I'm trying to get it back to some degree of what I had it. I would like tips putting on Android 7.0 if I choose to upgrade to it again but mostly I want to know a way to put it on A Marshmallow.
1)Rooting on stock Motorola Nougat ROMs is different to rooting on 6.0.1. Due to the stricter anti-rooting measures on stock 7.0 kernels, you need a custom kernel (e.g. ElementalX), else you'll bootloop as you've discovered. If you wish to root in future on stock 7.0, this guide might be useful: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You can use magisk instead of SuperSU.
2)If you want to go back to stock Nougat, are you on the retus software channel (might be under Settings, but I'm not sure if it'll show up on Lineage OS)? If you are, then this NPJ25.93-14.7 firmware might be for your device https://androidfilehost.com/?fid=817906626617945295 Please doublecheck that this is the correct firmware for your device before flashing. Also, be aware that flashing stock ROMs will wipe TWRP, your data and may wipe your internal storage, so back up before flashing. Nougat stock ROM firmware may also offer better compatibility for the custom Nougat/Oreo ROMs out there.
3)If you previously were on stock Nougat, can I ask why you wish to downgrade to Marshmallow (MM)? There's MM (6.0.1) stock ROMs out there (MPJ24.139-64, which should be the latest US build for MM: https://androidfilehost.com/?fid=312978532265364350 ). However, if you were on stock Motorola Nougat previously, especially on the June/September 2017 stock Motorola ROMs, I personally would advise against downgrading, or if you do choose to flash stock Marshmallow, do not accept OTA updates to update (e.g. to Nougat). If you downgraded, then in this case you'll have a Marshmallow system, but a Nougat bootloader - bootloaders typically won't downgrade. By taking a MM to Nougat OTA, you may corrupt your bootloader and hard brick your device (i.e. won't turn on, blinking LED, not recognised by your computer etc, device not usable and data not accessible.). We do have a way to recover a device hardbricked, but it's a last resort really. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Custom MM and Nougat ROMs don't mess with the bootloader, so should be safer.
I leave it up to you about what you wish to do with your device. Good luck whatever you choose.
How do I install the firmware? I tried flashing it in twrp, and it said invalid zip
endleesss said:
How do I install the firmware? I tried flashing it in twrp, and it said invalid zip
Click to expand...
Click to collapse
Stock ROM firmware zips are not flashable in TWRP. You need fastboot to flash stock ROMs (following a procedure like https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ), bear in mind that flashing these stock ROMs will usually replace TWRP with the stock recovery. Also they will revert your device to full stock.
Erasing your data will also happen unless you omit the erase userdata command, but if you're switching from a custom ROM back to stock, you may have to erase data anyways for stability.
Thank you!
Hoping this will help someone, this is what happened to me:
My phone is XT1625 Build # NPJ25.93-14.7
I flashed TWRP, then backed up, then flashed supersu. resulting in bootloop, i restored using the twrp back up, still bootloop.
To fix, download stock firmware: download https://androidfilehost.com/?fid=817906626617945295
Unzip the file, then in In adb run these commands one at a time.:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Phone is back to stock
Related
hi everyone i am running on nougat stock rom successfully unlock my bootloader and follow this step to root my phone but after installing twrp and flash supersu and i restart my phone it again boots into twrpi am not able to boot into system.
It only boot into fastboot and recovery
plz help me here i have indian moto g4 plus.
this the link which i follow
https://www.youtube.com/watch?v=dK2uacpjGwc&t=64s
Yeah, that Youtube guide is for rooting under Marshmallow - Nougat is more stringent and rooting with the stock kernel, as you've found out, will cause boot issues. A reliable way to root on Nougat is to flash a custom kernel onto your device.
Do you have a backup in TWRP to fall back to?
If so, and you've restored it, or if you don't have a backup of your system, then try rebooting back to TWRP and flash ElementalX v1.04 onto your device (either from a SD card or by plugging your device into your computer and try using 'adb push' to transfer ElementalX v1.04 to your device's internal storage). https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX. Hopefully then, you'll be able to boot.
For rooting under Nougat with SuperSU, have a look at this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
I faced the same problem when I unlocked my bootloader because for some reason on some models the phone will wipe the whole system partition instead of just the data. If you want to use a custom rom then you are able to flash that with twrp no problems but if you want the stock rom back you will hava to flash it either with fasboot (will flash stock recovery) or use a twrp backup someone made of the stock rom (nougat) I just did a google search for *moto g4 plus stock rom twrp backup* and clicked on the first link which contains guides for both methods (I cannot post links sorry)
Hope I could help
echo92 said:
Yeah, that Youtube guide is for rooting under Marshmallow - Nougat is more stringent and rooting with the stock kernel, as you've found out, will cause boot issues. A reliable way to root on Nougat is to flash a custom kernel onto your device.
Do you have a backup in TWRP to fall back to?
If so, and you've restored it, or if you don't have a backup of your system, then try rebooting back to TWRP and flash ElementalX v1.04 onto your device (either from a SD card or by plugging your device into your computer and try using 'adb push' to transfer ElementalX v1.04 to your device's internal storage). https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX. Hopefully then, you'll be able to boot.
For rooting under Nougat with SuperSU, have a look at this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
Tried element kernel but the results will be same boot into twrp
Can anyone have stock rom for indian dual sim variant of moto g4 plus firmwares?
rakesh595160 said:
Tried element kernel but the results will be same boot into twrp
Can anyone have stock rom for indian dual sim variant of moto g4 plus firmwares?
Click to expand...
Click to collapse
If you're after Nougat v7.0 Dec 2016, NPJ25.93-14 https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Nougat v7.0 March 2017, NPJS25.93-14.4 https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Bear in mind flashing either may wipe your device (and thus your data and internal storage), if you can, try to back up your key files via TWRP to your computer.
If you're downloading the same firmware as the build you have at the moment, you may be able to save your data and restore your system by using these commands, however be prepared to use all the flash commands (including wipes) if it doesn't work:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
echo92 said:
If you're after Nougat v7.0 Dec 2016, NPJ25.93-14 https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Nougat v7.0 March 2017, NPJS25.93-14.4 https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Bear in mind flashing either may wipe your device (and thus your data and internal storage), if you can, try to back up your key files via TWRP to your computer.
If you're downloading the same firmware as the build you have at the moment, you may be able to save your data and restore your system by using these commands, however be prepared to use all the flash commands (including wipes) if it doesn't work:
Click to expand...
Click to collapse
I just flash revivour os ut boots my phone well nkw how do i root my devices?
rakesh595160 said:
I just flash revivour os ut boots my phone well nkw how do i root my devices?
Click to expand...
Click to collapse
If you've flashed revivorOS, the rooting instructions are on the opening post of that ROM... https://forum.xda-developers.com/mo...om-npjs25-93-14-4-deodexed-debloated-t3587180
I have a Moto G4 (XT1625) Unlocked with 32GB of storage. Bootloader Unlocked and TWRP Bootloader or Recovery, IDK how to word it, but I attempt to update from Android 6.0.1 to Android 7 and the update fails. When the device reboots it reboots into the TWRP Recovery Menu. How do I proceed. Please help.
Haven't used adb, drivers, or anything and cannot seem to remember the process. Any pointers in the right direction are appreciated. Thank you.
Update 1: I am able to boot into TWRP 3.0.2-0 and see files on my MicroSD. However I downloaded a .ZIP file that was suppose to be the Nougat factory image and when I went to flash it, it says "Installing zip file.... could not find 'META-INF/COM/GOOGLE/ANDROID/UPDATE-BINARY' in the zip file. Error installing zip file."
Update 2: Can someone confirm that I would need to first somehow remove TWRP in order to update? How do I remove TWRP and get phone back to FULL STOCK.
Okay, accepting OTA updates requires a stock recovery (as you've discovered), stock kernel and unmodified system. Furthermore, the stock Nougat zip that you've downloaded needs to be extracted on your computer and flashed via fastboot, it's not flashable in TWRP.
If you're wanting to update and update to the latest Nougat build (which for US devices - XT1625 and XT1644 - appears to be NPJ25.93-14.5, June 2017), the easiest way is to download the stock Nougat ROM from here: https://www.androidfilehost.com/?fid=673368273298984458 . Download to your computer and extract the files. This build is for retail US (non-Amazon devices), with a retus software channel as listed in Settings>About Phone.
Then follow the instructions here, but using the above NPJ25.93-14.5 stock ROM instead. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Beware that this process may erase your data in the process, so back up as necessary. If you do not wish to erase your data, then you can use the following fastboot commands instead of the commands in the guide. Back up anyway and you may have to factory reset (thus losing your data) if your device is not stable. Also, either process will remove TWRP, root and any other modifications. Xposed is still not officially released for Nougat. It is up to you if you choose to re-lock your bootloader or not (of course, re-locking the bootloader will prevent you from flashing TWRP/root/any other modifications).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
pause
One word of warning, once you have formally updated to June 2017 (B1:06 bootloader), do not attempt to downgrade and accept OTA updates. You may wish to downgrade, but I don't recommend it - if you forget to not accept OTA updates, you may hard brick your device. If you think you'll forget, do not downgrade.
Hello,
So I've been trying to update my XT1265 which is currently on build number NPJS25.93-14-4. I my phone is rooted with TWRP installed. The phone was unlocked through the motorolla site. There's an OTA update that keeps annoying me so I'm trying to update it. If I try the update it updates, then when it reboots it stops in TWRP. (My phone actually always boots into TWRP when it reboots/boots but I'm able to reboot bootloader and get it booted.) I've read that I need to get back to stock recovery to get it to update. I've yet to be able to find a stock recovery that I can fastboot to reinstall.
What do I need to do to get this to update?
Generally, OTA updates require stock recovery, stock system and stock kernel - any modifications to these and the OTA update fails, as you've found (e.g. the TWRP boot issue). By modifications, I mean TWRP, root, even letting TWRP modify the system read/write status.
If you really want to flash OTA updates, then you'd be best served by re-flashing the stock ROM. The following commands in fastboot should preserve your data and roll back your device to an OTA friendly state. However, back up and be aware that this will remove TWRP, any modifications (including custom logos) and restore your system partition to a read-only status.
Link for NPJS25.93-14-4 (non Amazon): https://androidfilehost.com/?fid=673368273298955218
Amazon: https://androidfilehost.com/?fid=889764386195899718
Extract the correct stock ROM zip to your ADB directory (it's about 2 GB expanded) and flash with the following commands in your ADB terminal:
Code:
[B]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/B]
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
[B]fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn[/B]
fastboot erase cache
fastboot reboot
Up to you if you choose to flash the steps in bold, as you should be flashing the same firmware onto your device as what you currently have.
Upon rebooting, your device should be back to where it was (though the initial boot might be longer as the cache is re-built) and then you should be okay to take OTA updates.
If you simply want to silence the updater, have a look at this thread (requires root) : https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
As for the TWRP boot issue, you may wish to look at this thread too (though I've not tried this, so be careful) : https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
tried to pass the last stock if I am not mistaken version that is or updated passes without being with bootloader unlocked.
Pranav_dp said:
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
echo92 said:
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
Click to expand...
Click to collapse
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Pranav_dp said:
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Click to expand...
Click to collapse
If you flashed the April 2018 security patch stock firmware, there are currently no OTA updates, the April 2018 security patch is the latest available.
If you fully flashed the latest firmware as I mentioned, you should be okay to use OTA updates. Just in future please remember to not use OTA updates if you downgraded your device by flashing old stock firmware.
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Daroas said:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Click to expand...
Click to collapse
Without a blankflash new enough to flash to the device, I don't think so. You'd have to consider a JTAG repair, a motherboard replacement or buy a new device.
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory: