Hi Guys,
So Tuesday morning woke up to my phone cycling through the "M - powered by android" screen. Have absolutely no idea why, though previous to placing it on the charger it had gotten down to 4% battery and I switched it off.
Anyway I have tried during the week to resuscitate the phone with many different methods posted here but still can not get it past the M logo loop
History of phone is:
March: 64GB model arrives with 6.0 reinstalled
Unlocked and Rooted the phone in March and installed TWRP
Made own recovery/backup in July - can't rember why but it seemed like a great idea at the time
At end of September Flashed phone to 7.0 - no problems there
Running fine until
Tuesday morning 1/11 from nowhere bootloop from hell hits
So in past 4 days I've tried in order (and some repeatedly):
Turning off, switching back on
Turning off, leave phone for an hour, switching back on
Turning off overnight > switching on
wiping caches
Wiping caches from cold start
draining completely flat > complete charge > wipe data from cold start > boot Still boot loop
Quickboot menu booting into recovery > TWRP > tried recovery (went fine but still bootloop)
Quickboot menu booting into recovery > TWRP > tried flashing 7.0 again (also went fine still bootloop)
Quickboot menu booting into recovery > TWRP > tried flashing 6.0 stock (also went fine still bootloop)
From quickboot menu tried RSD Lite stock flash - (failed at 3/29 gpt.bin)
From quickboot menu manually tried flashing 6.0 stock EU rom (as per instructions here using mfastboot and cmd window in windows 8 64 bit - flashed ok but still boot loop)
From quickboot menu manually tried flashing 6.0 stock MX rom
From Quickboot menu Manually tried flashing EU and MX 6.0 stock roms including the recovery command line (so now I don't have TWRP on the phone, though I am sure it will flash back easy enough).
After reading countless threads, I really thought by the time a manual flashing stock the phone would be working by now. Have I missed something obvious? Is there something else I should do? It seems stuck somewhere just before it boots - like if the boot partition in windows looses its boot flag.
Any ideas as to what to do next appreciated
In case it helps any the retvar details are:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8994-A8.56
(bootloader) product: kinzie
(bootloader) board: kinzie
(bootloader) secure: yes
(bootloader) hwrev: 0x8301
(bootloader) radio: 0x2
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S16 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x4
(bootloader) cpu: MSM8994
(bootloader) serialno: ZY223#####
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: A531EC011B000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358962########
(bootloader) meid:
(bootloader) date: 01-23-2017
(bootloader) sku: XT1580
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Oct 19 23:21:52 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/kinzie_reteu/kinzie_uds:7
(bootloader) ro.build.fingerprint[1]: .0/NPKS25.200-12-4/4:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.kinzie_rete
(bootloader) ro.build.version.full[1]: u.reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8994_1255341.44.01.95.01R KINZIE_ROW_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga0e0551 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT M
(bootloader) kernel.version[3]: on Jul 10 09:14:29 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VA8.56-0-g7c62395
(bootloader) rpm.git: git=fa49dab
(bootloader) tz.git: git=MBM-NG-VA8.56-1-gf12946f
(bootloader) hyp.git: git=MBM-NG-VA8.56-1-gf12946f
(bootloader) sdi.git: git=298d574-dirty
(bootloader) pmic.git: git=MBM-NG-VA8.56-0-g7c62395
(bootloader) aboot.git: git=MBM-NG-VA8.56-0-g09a6e4e
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retapac
Ok so I've been doing some more flashing - the flash process works fine no errors. I've put TWRP back on and it works fine when accessed via fastmoot menu then into recovery.
Frustratingly despite all recoveries flashing fine (logo's updating correctly as per version etc) it will not get past boot. Makes me think this phone is headed for the bin.
Is there a way to test the pre-boot memory or a tool to see what is going on at that stage of the boot process? perhaps a tool to check the hardware is working properly?
Cheers again
Val
Check my last 20-30 post, in one of them you'll find possible solution.
I've had similar problem - it's faulty file system on one of the partitions, exactly few first bytes which for some reason can't get formated, factory flash doesn't fix it either.
All you need to do is fill up partition which zeroes.
Hi TeddyBeers,
Thank you for your response.
been through the last 20-30 odd posts. Is this the instructions in the post you are referring to?
" In most cases it's MISC partition.
To fix it need to run this command from adb
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
or just through TWRP ->Advanced -> Terminal Emulator
Code:
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
If this doesn't help (like in my case) than overwrite system and data partition - THIS WILL DELETE ROM AND ALL DATA
For system partition
ADB
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/system
TWRP ->Advanced -> Terminal Emulator
Code:
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/system
For data partition
ADB
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/data
TWRP ->Advanced -> Terminal Emulator
Code:
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/data"
After zeroing all these partitions, which instruction do you recommend flashing with - ie mfastboot, Sideload, reflash TWRP and then install?
Cheers
Val
So a brief update - Tried the flashing zeros as per Teddybeers suggestion using terminal in TWRP. Still same result, phone is responsive to flashing from fastboot (and twrp after reinstalling TWRP) but phone will not get past the boot logo before re-starting and repeating
My thoughts (and googling) is leading me to think blank-flashing the phone is the only way to go.
The only guide I have been able to find suggests RSDlite. As I can't see the phone using RSDlite, is there a way to blank flash from fastboot mode? Or TWRP?
Cheers as always
Related
I was trying to root my Moto G4 Plus (XT1641) (Dual SIM bought in Wallmart, Mexico), installed the superuser-zip file, but it never loaded. Heres the deatiled info:
(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.03
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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: (**********)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x22
(bootloader) uid: B129A00000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354116070814435
(bootloader) meid:
(bootloader) date: 05-21-2016
(bootloader) sku: XT1641
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 14 10:46:36 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_LATAM_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retmx
all: listed above
finished. total time: 0.102s
-First, i had to get the unlock bootloader code from Motorola following the steps on the website
(1) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
(2) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
(3) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
And it was the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock (******************)
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.006s]
finished. total time: 0.007s
but, as it said in the las section, my device appears to succesfuly unlocked bootloader:
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
- Following the next post https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 i installled Minimal ADB and Fastboot on my pc, and flashed twrp-3.1.0-0-athene.img. BUT, I DIDN´T NOTICE THE WARNING ON TOP OF THE POST: "If you are on NPJ25.93-11/12/14 (non-soak test Nougat), you MUST flash the ElementalX kernel (link) after step 4. Make sure to backup the stock kernel before proceeding". (and honestly i have no f****** idea if i was on NPJ25.93-11/12/14). I finished installing that post's phh's SuperUser, and Voila!, it didn't worked
-After loking for any solutions to this issue, i've found this post: https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592 and tried rooting and tried typing echo SYSTEMLESS=true>>/data/.supersu on the TWRP's terminal and using it's SuperSU file.
-Also: I forgot to make an Backup on TWRP :crying: before installing my first superuser file
I can acces bootloader on my cellphone and TWRP witouth problem, so it's softbricked.
1: How can i finish rooting my device and make ti work? or
2: Is there any way i could reinstall the OS (nougat or Lollipop) using any recovery file, re-stock, re-lock or something?
Okay, a few things from what I see from your post:
You're on NPJ25.93-14/16 (from your getvar infor fingerprint), so that build requires ElementalX or another custom kernel. I think that requirement stands for any Nougat build on Moto G4 devices anyway, since Google appears to have enforced kernel security under Nougat.
Regardless, you'll need to flash a custom kernel to get any root solution (or somehow bypass dm-verity), else you won't be able to boot. You may be able to copy ElementalX (https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836) to a SD card, or use the 'adb push' commands from your adb terminal to push the file onto your device.
Then, you may be able to boot into TWRP, flash the ElementalX kernel, wipe your cache/Dalvik then reboot.
If your device boots, then you may wish to check if phh Superuser is still active.
If no root is present, reboot into TWRP and then flash phh Superuser.
If you still get bootloops or are unable to get ElementalX onto your device, you may wish to flash the stock Nougat ROM (same build as what you have currently) from here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 This will wipe TWRP and any root present (as your kernel and recovery will be stock again), you do not have to re-lock your bootloader if you choose not to, and if you do not use 'fastboot erase userdata' and the OEM lock commands, you may be able to retain your data (though hopefully someone else can chime in on this point). However, for a stable system, I'd recommend using all the erase commands as listed (which potentially means losing your data)
EDIT - from toppits' post here (https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64), you may be able to use these commands for the fastboot ROM (may save your data if you choose to re-flash the fastboot stock ROM):
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
As always, you may have to erase your data if your system becomes unstable, but hopefully you may be able to boot and recover your data. You may then wish to continue on with your system as is or, after backing up your data, fully wipe and re-flash to get a stable system.
I do not have a custom recovery. Can however boot to regular recovery. Tried to use ADB but computer just won't recognize the device. Tried multiple different cables.
vu45 said:
I do not have a custom recovery. Can however boot to regular recovery. Tried to use ADB but computer just won't recognize the device. Tried multiple different cables.
Click to expand...
Click to collapse
Can you tell us more about what's going and how you got to that point? And what device specifically?
What are you trying to do with ADB? It is really of no use at this point, can you access fastboot in the bootloader?
Tried to return to stock for update. Afterwards it just doesn't boot. X Pure 1575.
Trying to ADB into some sort of usable rom. It goes into ADB but computer won't recognize. Phone doesn't even boot into an OS.
vu45 said:
Tried to return to stock for update. Afterwards it just doesn't boot. X Pure 1575.
Trying to ADB into some sort of usable rom. It goes into ADB but computer won't recognize. Phone doesn't even boot into an OS.
Click to expand...
Click to collapse
ADB only works after the OS is booted... Do you have a terminal capture of your flash attempt? And how long are you waiting on first boot, it can take 30 minutes for first boot sometimes.
I do not unfortunately but it doesn't even boot into OS. It boots immediately into bootloader.
vu45 said:
I do not unfortunately but it doesn't even boot into OS. It boots immediately into bootloader.
Click to expand...
Click to collapse
Connect into bootloader mode to pc.
In cmd type+enter:
fastboot devices
/If you will see SN continue/
fastboot getvar all
/Copy and paste here the answer from pc/
If no devices:
Reinstall drivers + minimal adb & fastboot & repeat steps.
/Uninstall all drivers and programs for android, reboot pc, install/
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57 PNM=016G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA08403TSL
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 9362E5001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 358986064519224
(bootloader) meid:
(bootloader) date: 03-22-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5: EDFE69452203DA0709C2C09BF656C85D
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 8 16:59:17 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.062s
Continue in this state flashing stock rom. Here is how to:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Download xt1575.retus.24...18-8 from:
https://mirrors.lolinet.com/firmware/moto/clark/official/RETUS/ @vu45
Got it to boot! Thank you so much sir. If you don't mind me asking what does this mean:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Still got it to boot however
Also what is the latest security patch?
vu45 said:
Got it to boot! Thank you so much sir. If you don't mind me asking what does this mean:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Still got it to boot however
Also what is the latest security patch?
Click to expand...
Click to collapse
Those are related to devices that ship with Nougat, they have 2 software slots, basically fastboot is just telling you that there are not multiple slots found, which is true for this device, they are informational only.
acejavelin said:
Those are related to devices that ship with Nougat, they have 2 software slots, basically fastboot is just telling you that there are not multiple slots found, which is true for this device, they are informational only.
Click to expand...
Click to collapse
Ah thank you. I was wondering why it kept popping up.
vu45 said:
Ah thank you. I was wondering why it kept popping up.
Click to expand...
Click to collapse
Yeah, it seems pretty handy... my understanding is that Nougat devices and newer have 2 (or more) software slots, one is active and one is a backup, and you can even tell the device which one is active via fastboot... currently it is only used for seamless updates, although some custom ROMs may use this as well but I don't own a device that shipped with 7.0 or never so I haven't looked into it.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Alcatel 5065n ADB it won't recognize bricked phone
I have the drivers installed and it shows up Android device manager, but however when I type in command ADB devices the phone doesn't show up in the list
Morning,
I have a Motorla G4 plus UK model XTN1642 I rooted this and installed TWRP when I first bought it several months back.
Yesterday, I got the 'update is avaialble' notification and follishly I allowed it to download and then install which failed, now the phone will only boot to the TWRP screen each time it restarts.
However, If I boot into bootloader then manually click 'Start' the phone will boot normally, but this is not ideal.
The phone is running stock Android 7.0 build number NPJS25.93-14-4, i've tried reading the forum but there is quite a lot that I don't understand and I don't want to make it worse by killing it completely and then not having a phone to use.
Can anyone give me a straight forward way to get the phone to boot up normally without having to go through bootloader and then manually click start?
I'm hoping that it is something simple, I don't have any backups of the device either!
Look, with twrp installed there's no way to update via ota. That's why I reflashed stock rom for getting the ota update. Although I planned to flash 6.0 M stock initially, I managed to flash 7.0 N stock ROM since it was available on this forum.
The version I have at the moment is 25.93.14.10 which is the September 2017 security patch. My another G4 absolutely untouched received ota today from 14.4 March patch to 14.13 December patch. I am not quite sure what happened to my 14.10 September patch. Why there is no ota? Maybe because this ROM was found on the G4+ forum?
Back to your question, find a stock ROM to flash, don't install twrp as it will modify the recovery. For install ota you will need to keep the ROM completely untouched.
Hi,
Yes, I am aware of that now but at the time I wasn't or else I wouldn't have done it.
But, after reading through teh forum, I followed this https://forum.xda-developers.com/moto-g4/help/ota-upgrade-7-0-twrp-installed-t3727807 after which the device booted normally again.
I should have left it at that, but again, I was notified of the update, so having read the thread above, let it go ahead, it download the update and rebooted., I then tried to root again and install twrp and elementalx and now it doesn't boot just get a black screen, I can still get into twrp and bootloader though.
Here is what I get from fastboot getvar all
C:\Program Files\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.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(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: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: E492B10000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ****************
(bootloader) meid:
(bootloader) date: 05-30-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:53:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.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-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-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.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.562s
I've blanked out the IMEI and Serial number in the above
I guess I should have left it ater getting it back and booting, but it sort of made sense to do the update then I needed to root it again.
What now?
right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !
ffrlr said:
right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !
Click to expand...
Click to collapse
How are you rooting, and what software are you using?
The general order for rooting is to:
1)Flash/boot TWRP. Either the official TWRP (3.2.1 - https://dl.twrp.me/athene/ ) or shreps' TWRP should suffice: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
2)In TWRP, backup your stock ROM and make a separate copy of your kernel (boot) partition.
3)Flash ElementalX or another custom kernel. Ensure this happens before you root else you'll bootloop. ElementalX v1.04 or v2.0 is here: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
3a)Wipe cache and Dalvik. At this point, you may wish to boot and check your device is working. If so, proceed to 4)
4)In TWRP (or boot back to TWRP), flash the root manager of your choice, either SuperSU v2.8.2 SR5 https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 or magisk 14/15. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Do not mix and match root managers without fully uninstalling and flashing the stock kernel again (hence the separate backup you made in 2)).
5)Wipe cache and Dalvik if not done in 3a) and reboot.
6)Any issues, revert to your backup made in 2).
This should give you a device booting with the latest stock ROM and rooted. This procedure is working on a XT1642 with NPJS25.93-14-13 (same firmware as you have now) and ElementalX v2.0 and magisk 15.3. As I linked in the other thread you've seen, you may wish to disable the Motorola updater to stop you from getting into another TWRP bootloop.
Hope that helps.
EDIT - have a look at this thread too: https://forum.xda-developers.com/moto-g4/how-to/guide-how-to-root-moto-g4-magisk-stock-t3725712/
Hi
thank you for the reply, very much appreciated, I'm keen to get my phone rooted again as I use 'timed toggles' to switch the phone into aeroplane mode when i'm asleep etc.
When I last rooted it after I bought it, I used magisk from what I recall, but I amnot really fussy to be honest.
Yesterday, I bravely attempted several times to install twrp in fact it was the shreps version which I found a link to, but for some reason I cannot get it to install.
I boot the phone using volume down button and power, then connect to the pc, then type fastboot flash recovery twrp-3.1.1-athene_shreps.img.
during the flash, I get the following
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
I then immediately boot to recovery using the volume keys and power button, after the device reboots, I don't get TWRP, justa dead android lying on it's back with a red exclamation mark above it, beneath is written no command.
I've had about four goes, but each time I get the same, am I missing something?, i've followed various threads and tutorialsd to no avail.
Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.
ffrlr said:
Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.
Click to expand...
Click to collapse
Good to hear it worked I'm glad that it worked on your other computer - Windows 10 appears to cause some headaches on flashing - I don't know if it's to do with the driver signature enforcement, that I don't think Windows 7 has. I've not had issues with Windows 10 flashing for the most part, though I do have a computer with a BIOS and not UEFI - though that being said, last time I flashed TWRP (shrep's TWRP), it didn't stick and required another re-flash, so maybe it's to do with the updated B1:07 bootloaders in both cases?
By the way, that 'image not signed or corrupt' message when flashing TWRP is normal and expected. TWRP is not cryptographically signed with the keys that the system/fastboot is expecting, so it's simply a message to alert you.
Have fun with your new root powers (please use responsibly )
Hi all,
My XT1644 is currently on build NPJS25.93-14-4, I just flashed it. It is on the March 2017 Security patch, retus Software channel. Bootloader is unlocked and phone is unrooted.
I don't understand why I can't update the phone further through OTA. According to the system update check: "Your system is up to date", which is quite clearly not true.
I went back to stock in order to update my phone before re-rooting it, but it doesn't work. What can I do? Should I look for every OTA since March 2017 and flash it manually or is there an other option?
Thanks a lot for any guidance you could provide, I don't know how to proceed any further.
Hmm, do you have a SIM card installed in your device? Sometimes, the OTA servers only serve updates if they know what network you're on. Is this a clean flash of the firmware that you performed ( full data wipe)?
If I recall, the next update you should be getting is the June 2017 NPJ25.93-14.5 update. If you want to flash the firmware, have a look here: https://androidfilehost.com/?fid=673368273298984458
echo92 said:
Hmm, do you have a SIM card installed in your device? Sometimes, the OTA servers only serve updates if they know what network you're on. Is this a clean flash of the firmware that you performed ( full data wipe)?
If I recall, the next update you should be getting is the June 2017 NPJ25.93-14.5 update. If you want to flash the firmware, have a look here:
Click to expand...
Click to collapse
Thanks for answer.
I have indeed a SIM card installed. However, the flash was not 100% clean, I have not run
Code:
fastboot erase userdata
Could this cause the issue?
Artanaol said:
Thanks for answer.
I have indeed a SIM card installed. However, the flash was not 100% clean, I have not run
Code:
fastboot erase userdata
Could this cause the issue?
Click to expand...
Click to collapse
I'm not sure - it could be a factor. Is it possible for you to do a full data wipe? When you were rooted, was your Motorola updater disabled?
If possible, can you post your getvar all info too?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal on your computer. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Please post the info here, omitting your IMEI. I'd like to see what state your device is in at the moment, which is what this info should show.
echo92 said:
I'm not sure - it could be a factor. Is it possible for you to do a full data wipe? When you were rooted, was your Motorola updater disabled?
If possible, can you post your getvar all info too?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal on your computer. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Please post the info here, omitting your IMEI. I'd like to see what state your device is in at the moment, which is what this info should show.
Click to expand...
Click to collapse
Ideally I would rather avoid it, so I'm trying to keep the userdata reset as a last resort. When rooted, I had indeed disabled the Moto Update Services with Servicely, but I have disabled servicely after the new flash (I've done it unrooted, so I'm not sure it 100% reversed the process though).
Regarding the getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.05
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8952
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 05E16B0100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) reason: UTAG "bootmode" configured as fastboot
Thanks!
Here is the rest of the getvar, as I couldn't post it in one message (I have removed a few info, since the forum seemed to be blocking some?)
Code:
(bootloader) date: 09-13-2016
(bootloader) sku: XT1644
(bootloader) cust_md5:
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.05-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.05-0-g8a1de8c
(bootloader) qe: qe 0/1
(bootloader) frp-state: no protection (277)
(bootloader) ro.carrier: retus
Artanaol said:
Ideally I would rather avoid it, so I'm trying to keep the userdata reset as a last resort. When rooted, I had indeed disabled the Moto Update Services with Servicely, but I have disabled servicely after the new flash (I've done it unrooted, so I'm not sure it 100% reversed the process though).
Regarding the getvar:
<snip>
Thanks!
Click to expand...
Click to collapse
Thanks for the info - looks like your device should be ready for another update - you've still got the B1:05 bootloader from the March 2017 security patch and the right firmware.
From what you've mentioned, I'm not sure if uninstalling Servicely would have restored the Motorola updater to its normal status (or whether it's still disabled).
You may either have to re-root, then activate the updater then revert back to full stock, or try to flash the NPJ25.93-14.5 firmware without wiping your data, if you really don't wish to wipe your data. You could also try to flash the NPJ25.93-14.7 Sept 2017 security patch firmware as an alternative: https://androidfilehost.com/?fid=817906626617945295
EDIT - is this your post on the Moto G subreddit? https://www.reddit.com/r/MotoG/comments/916to5/no_available_update_on_g4_best_way_forward/
Thanks, I will give a shot at the various options you suggested!
(It is indeed my post, good catch! I wasn't sure where I would get an answer).
Hi There , Idont Know How To Say This In Normal Way But Idont know How , So I Will Go Right Through The Problem
I Got This Moto X Pure Edition (style) X1572 | Retasia
And It Was On Android 5 On Locked
I Didn't Know I Have To unlock It Before Flashing So It's Lock
so I Tried To Update The Phone With Frimware That I Grabbed For Frimeware Center But It Was The Wrong Region( La )So I Tried Another (Eu)
Then I Found The Right Region By This Code : fastboot Getvar All and I Found That My Phone Is For Asia but I Can't Flash it because Of Gpt Partiton or bootloader Or Boot ، every Time I get the same errors
To sum up i want These Questions Answered
1 - is There any File For Region Asia With Android 7
2 - does my Phone Supports Deep Flash Cable Or Can I Flash it with Deep Flash Cable and How I Make Deep Flash Cable For Moto
3 - If I Couldn't Flash it Can It be flashed With a Box (like z3x for Samsung)
Please Help as Fast As You Can Im In deep Pain By This Phone and the Phone isn't mine I have to Return it By Tomorrow (1/8/2018) so Please Help To Solve This Problem Thanks
Normally, we should unlock bootloader before flashing firmware.
With unlocked bootloader, you can flash firmware from other regions, low android version (5) to higher one (6 or 7).
When flashing a different region firmware, you should make a factory reset via Recovery.
You should give more infomation about the state of the phone: can enter bootloader, recovery mode or not; can turn on screen or not; how the PC shows when the phone is connected to PC.....
mr_5kool said:
Normally, we should unlock bootloader before flashing firmware.
With unlocked bootloader, you can flash firmware from other regions, low android version (5) to higher one (6 or 7).
When flashing a different region firmware, you should make a factory reset via Recovery.
You should give more infomation about the state of the phone: can enter bootloader, recovery mode or not; can turn on screen or not; how the PC shows when the phone is connected to PC.....
Click to expand...
Click to collapse
Hi My Phone Is On And Its Locked On Bootloader (State Is Locked) I Couldn't Flash Any Frimware My Phone Region Is Asia I Cant Enter Recovery Mode PC And PC Shows It In Fastboot Mode
By The Way Is There Any Way To Put This Phone On Test Point Or EDL?
When you connect the phone to PC, if it turns on and enters fastboot mode (the screen turns on, and you can see the android and phone information), it is reflashable. But the bootloader is needed to unlock (you can google this problem, it's easy to perform). Then you go to firmware.center, find rom Asia with android 7 and flash it to the phone.
If the lcd is not on when you connect to PC, here is the method: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
mr_5kool said:
When you connect the phone to PC, if it turns on and enters fastboot mode (the screen turns on, and you can see the android and phone information), it is reflashable. But the bootloader is needed to unlock (you can google this problem, it's easy to perform). Then you go to firmware.center, find rom Asia with android 7 and flash it to the phone.
If the lcd is not on when you connect to PC, here is the method: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
It turns on and boots to bootloader but I tried to unlock the bootloader but it says you should allow bootloader oem unlock in developer options , and I can't access that obviously
So you can try to flash the firmware without flashing gpt.bin; bootloader.img; boot.img; recovery.img
Or you can try to make an sdcard like the link I mentioned before. Insert it to the phone and try to flash the firmware then.
mr_5kool said:
So you can try to flash the firmware without flashing gpt.bin; bootloader.img; boot.img; recovery.img
Or you can try to make an sdcard like the link I mentioned before. Insert it to the phone and try to flash the firmware then.
Click to expand...
Click to collapse
This the problem I tried every rom I cloud but none of it worked
If the phone can enter bootloader, the easiest way is to flash the newest firmware to the phone for both situations: locked or unlocked bootloader. My Verizon Droid Turbo had been soft-bricked when it was on Android 5. When android 6 came, it resurrected.
If a firmware is successfully flashed to the phone, it can start up normally or be stuck at logo. If it is stuck, enter recovery mode and factory reset.
There is one last method with super high risk: break the bootloader then resurrected by sdcard. One of my phone has died before, so never use this method if you don't have experience.
I mentioned everything I know. If your phone does not start, you may need another one.
I'm sorry that it does not help
Can Any Buddy Find The Right Frimware Based On This Info For Me I Need It ASAP Thanks
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA08305BXS
(bootloader) cid: 0x0007
(bootloader) channelid: 0x52
(bootloader) uid: B02FEA001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 352342070733563
(bootloader) meid:
(bootloader) date: 12-24-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 28 3:15:52 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :5.1.1/LPH23.116-18/22:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.18.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255309.10.01.68R FSG-8994-01.71
(bootloader) version-baseband[1]: _CLARK_EMEA_DSDS_CUST+SW_DFLT
(bootloader) kernel.version[0]: Linux version 3.10.49-perf-ge36128e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Jul 30 14:36:15 CDT 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=2d08904-dirty
(bootloader) hyp.git: git=2d08904-dirty
(bootloader) sdi.git: git=d9f358f
(bootloader) pmic.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) aboot.git: git=MBM-NG-VA0.52-0-g69ca042
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retmea
all: listed above
finished. total time: 0.116s