Related
I used the fastboot command and updated every time when I bought nexus 7 (wifi) from last year.
However, when I updated from jwr66v to jwr66y, I used wipe function in CWM. Then, I got the "archive does not contain boot.sig" and "archive does not contain recovery.sig" and "failed to allocate XXXXXXX.byte"...
Then I tried to get back version to 4.2.2, but I also got the same error message. I follow the guidehttp://forum.xda-developers.com/showthread.php?t=1907796 to manual flash each .img files, the same problem occur at flashing system.img
At now, I could not get into android system, just hang on the "Google" logo.
I have read the same problem in another threadhttp://forum.xda-developers.com/showthread.php?t=1992063, but I could not have any idea to solve it?
Anyone have idea?
Thank you very much.
PS: I used the platform-tools r22.0.5
"boot.sig и recovery.sig"
You must install the recovery.img and boot.img
Solution
Here's a solution for ya: http://shuiqingwang.blogspot.com/2013/03/solvedfastboot-wired-errors.html
Basically use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
I know this post is late, but this worked for me
vitaminan said:
I used the fastboot command and updated every time when I bought nexus 7 (wifi) from last year.
However, when I updated from jwr66v to jwr66y, I used wipe function in CWM. Then, I got the "archive does not contain boot.sig" and "archive does not contain recovery.sig" and "failed to allocate XXXXXXX.byte"...
Then I tried to get back version to 4.2.2, but I also got the same error message. I follow the guidehttp://forum.xda-developers.com/showthread.php?t=1907796 to manual flash each .img files, the same problem occur at flashing system.img
At now, I could not get into android system, just hang on the "Google" logo.
I have read the same problem in another threadhttp://forum.xda-developers.com/showthread.php?t=1992063, but I could not have any idea to solve it?
Anyone have idea?
Thank you very much.
PS: I used the platform-tools r22.0.5
Click to expand...
Click to collapse
I have a G4 Plus which i've flashed with a stock ROM. The phone is running Marshmallow 6.0.1 and the build number is: MPJ24.139-48 - the patch level is 1 May 2016. When I hit 'update' it doesn't update to July 2016 which is the latest available patch in the UK.
Does anyone have a UK marshmallow rom for the G4 Plus which I can load onto the phone and then update to the July 2016 patch??
Any help would be fantastic. Thanks in advance.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Select I agree and then moto g from the dropdown menu. The instructions are fairly straightforward. XT1625 works for your device. Bootloader probably does not need to be unlocked if not downgrading**
Then execute the following
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Edit: Use 7-Zip to extract the tarball from tgz file, and then again extract the files from the tarball.
**I'm not sure though, select allow oem unlocking in developer options just in case
mrinmaydhar - thank you very much. I will try that out now.
Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.
echo92 said:
Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.
Click to expand...
Click to collapse
Thanks i'll try that because it sounds like you've had a good success with it!
I flashed this one: ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
It worked but it was stuck on the 1st May 2016 security patch and kept saying it was up to date and wouldn't upgrade further.
Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?
motogfalcon said:
Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?
Click to expand...
Click to collapse
Nice one, from the sounds of it, everything's working
As for Nougat (whenever it arrives in the UK and Europe!), you should be receiving an OTA update, since you're up to the latest MM 139-63/64 build for our region. It also should flash onto your device provided no modifications have been made to the recovery/system (bootloader lock/unlock doesn't appear to matter).
What did you see that suggested your recovery wasn't properly installed? If it was an error such as 'not signed' or 'bad key', but reported OK after flashing, don't worry about it.
I got the 'not signed' message. Excellent! All seems to be working well. Looking forward to when Motorola release Nougat. It's a shame they haven't kept on top of the security patches because its a great device I think! Thanks again!
motogfalcon said:
Excellent! All seems to be working well.
Click to expand...
Click to collapse
What is your software channel now? Still retgb ?
Yes retgb. Apparently Lenovo are releasing Nougat soon in the UK so hopefully I'll get it on the retgb channel
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
Hello to this amazing community,
I have recently tried for the first time to root my device.
Being unaware of the XDA community, I used this guy's guide - https://theunlockr.com/2016/11/29/root-motorola-moto-g4-moto-g4-plus/ .
As I went through the steps of unlocking, booting TWRP and installing superSU, I found out that the device won't start anymore, though the bootloader was still working at that point.
Unfortunately, that guide didn't emphasized the importance of first backing-up the system with TWRP.
Panicking, I even ended up wiping the entire device.
So I started my sisyphic journey of reviving the phone.
Being clueless of OEM stock versions etc. at this point, I thought that I should look for a fresh TWRP backup someone did after purchasing my exact Moto G4 Plus model - XT1644 so I ended up recovering the version that this dear guy has uploaded:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1644-stock-unmodified-6-t3536448
Happy as I was that the machine would finally start, I found out I was running an old Marshmallow version - exactly as the title says.
Still, I assumed that new OTA versions will be available and my device will be upgraded to the most up-to-date version.
Surprisingly for a rookie as me, checking for software updates showed " Your device's software is up to date".
So I search for a more up-do-date OEM stock version, and I have found the following version - NPJS25.93-14-13 here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I ran the bash file to flash the OEM while keeping the device unlocked.
The device has loaded finally with the familiar up-to-date version, and an available OTA update appeared.
I immediately ran the update.
That's when I first became familiar with the term "Brick". The device became completely dead.
Now, thanks to siddhesh9146 inceredible thread I managed to revive the device:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
I went through his steps, installed BlankFlash, flashed the latest gpt and bootloader and flashed version NPJS25.93-14-10.
The device will finally work! I would realize then, that the latest version is actually ATHENE_NPJS25.93-14-13 ,
And again, the device won't show any updates available.
So, finally, here are my questions:
1. What could I have done wrong in first place? Was it a wrong superSU version that caused the problem? (In case my rooting aspirations will return)
2. What caused the device to turn brick? I realize it has to do with downgrading version, but after I wiped the device, I only upgraded versions.
3. In general, when OTA are available? Only the newest stock version would receive OTA? Will I have to manually upgrade versions from now on?
4. Could I upgrade now to NPJS25.93-14-13 using the version that siddhesh9146 presented without wiping my entire phone? What exactly should I flash to do so?
5. What are the precautions I have to take while doing so? Is there a risk my phone will tun brick again?
Thanks!
Good to hear your device is working again, seems like it's been through a journey.
1)When you originally rooted, were you on stock Nougat (7.0)? If so, those rooting guides will not work and are likely for Marshmallow 6.0 systems only. What they fail to mention is that attempting to root whilst still on the stock Motorola Nougat kernel likely causes your device to not boot. The Nougat 7.0 stock kernel for our devices seems to be much stricter than the Marshmallow kernel when it comes to anti-rooting protections. Thus, we generally need to flash a custom kernel onto our devices before rooting - either with SuperSU or magisk. An example of a working guide for rooting on stock Nougat Moto G4/Plus is here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
2)Do you remember what the OTA you received was? I don't think there's an OTA for a build later than NPJS25.93-14-13 out yet. That suggests that the NPJS25.93-14-13 flash didn't work - did you check if the bash script reported [OKAY] after each command? By brick, do you mean the device had a blinking LED light, and there was no screen, and you were unable to boot to the bootloader and/or recovery? If the flash didn't work, then you may have taken a Marshmallow to Nougat OTA (NPJ25.93-14) which may have corrupted your device bootloader in the process.
3)OTAs are generally available for a particular build and for a particular software channel when they are released. For NPJS25.93-14-13, that's currently the latest build for EU/UK, Brazil and India devices, and there's word that there's a February 2018 OTA coming soon (no sign of it yet).
However, for your device (XT1644), if you are on the retUS - retail US - software channel, your device is on a different update path - NPJ25.93-14.7 would be the corresponding September 2017 patch for retUS software channel devices. NPJS25.93-14-10 is not one of the builds deployed to the retUS, and as such the Motorola servers may not issue you an OTA patch, regardless of whether the firmware would work. There have been reports of NPJS25.93-14-10 and NPJS25.93-14-13 working on US devices without issue, but you may not receive OTA updates.
You could manually update to NPJS25.93-14-13 using the OTA here, provided that you fully flashed the NPJS25.93-14-10 stock ROM (including GPT and bootloader, system, modem, boot, recovery, OEM, DSP, FSG). If you did not fully flash, you may be risking another hardbrick. https://forum.xda-developers.com/showpost.php?p=74973505&postcount=7
4)If you want to flash the NPJS25.93-14-13 stock ROM to be safe, or attempt to cross flash to the Sept 2017 NPJ25.93-14.7 firmware without wiping your data, you can use the following flashing commands. Be warned that you may have to factory reset if your device becomes unstable, so backup anyway. I would recommend manually flashing these commands:
a)copy and paste the first command to the ADB terminal
b)press enter, wait for [OKAY] to appear.
c) copy the next command, individually and in order, to the terminal, repeat b) and c) until you get to the end of the list.
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 omit the fastboot erase userdata, preserving your data, and omit the OEM locking commands, which would lock your bootloader and erase your data in the process as well. Bear in mind that cross flashing can be risky, however, you may have to flash the NPJ25.93-14.7 update if you wish to receive OTA updates for the retUS software channel, if you are on that software channel. Link for the NPJ25.93-14.7 stock firmware if you wish to try: https://androidfilehost.com/?fid=817906626617945295
5)Generally, the main source of hard bricks I've noted has been users have been on stock Nougat (particularly the March 2017-latest) builds. They downgrade their device to stock Marshmallow firmware, which goes okay. However, in most - if not all - cases, their bootloaders are not downgraded, so you have a system and bootloader mismatch, with a newer Nougat bootloader but an older system than their bootloader patch level. For example, a B1:06 June 2017 patch level bootloader but a July 2016 Marshmallow system patch level.
The OTA checks that are performed are mainly on the system side i.e is your device on the July 2016 system patch? Are your system, OEM, recovery, boot etc. partitions unmodified and match the expected checksums for this OTA patch? If so, then install. However, in the updater script, there is no such check for the bootloader - the OTA updates appear to assume your bootloader is of the same patch level as your system. Normally, for a locked bootloader or for a user that has only updated their device, that assumption holds.
The issue we have here is that the system was downgraded to Marshmallow, so that assumption no longer holds. As the OTA updates are signed by Motorola, they have authorisation to write to your bootloader. That means this OTA can overwrite your bootloader, and if it's applying older code, can corrupt your newer Nougat bootloader and thus hard brick your device, which necessitates a blankflash to repair.
In other words, if you downgrade your device firmware, do not use or install OTA updates. If you do downgrade, only update with stock firmware that is as new or newer than your bootloader patch level. If your device is on the same patch level , then you should be able to use OTA updates. However as mentioned above, you need to be on the correct build for your device software channel as well to receive OTA updates from Motorola.
Does anyone have stock rom npns25.137-93-14 for xt1685 for fastboot flash ???
I am trying to get oreo OTA update to work, and i had twrp installed, tried to flash stock recovery.img "not sure i got the right version" but update to oreo failed for some reason....
Think i maybe must flash the stock rom again and lock bootloader....
There is no image leak for 137-93-14, however using this tool on your pc you can download and flash the latest system images for your device. Install it, connect, select rescue and reboot your phone to fastboot. It will format the phone so make sure you have backups of your files.