Related
Let me start off by saying that I have tried everything I can find. I have tried the ADB sideload method. I have tried to go to the firmware it's trying to upgrade from. I've tried both stock recovery and CWM. I'm not a n00b when it comes to unlocking, rooting, flashing etc. Anyway, here's the story. My dad bought a Nexus 7 32GB and it kept asking him to update to 4.1.1 for the landscape rotation. The first time he tried it, it failed because it was trying to update from a specific firmware that he didn't have. He has JRO03S. It was trying to update from JRO03D to the new 4.1.1 update. It fails every time no matter what. Like I stated earlier, I've tried both stock recovery and CWM, but they both error out. I've included some pictures of the error in CWM and the about device screen, but nothing from stock recovery. I was too lazy to put the stock recovery back on there to take a picture, but if it's necessary for a solution then I will. Yes, I have searched here and google. Every solution that I have found has not worked. If anyone can help me then you would be a lifesaver. Thanks for taking the time to read through all this. If I'm not being specific enough then please let me know what else you need to know.
The assert() failure you see in the custom recovery is to be expected - it is the installer script checking to make sure that someone is attempting to apply the update to an exact version of the factory software. In this case, exact also means the version of the recovery boot in use which is trying to process the update.
In general, you can not use a custom recovery with an unmodified OTA installer file because of that first assert.
The OTA updates are NOT complete re-installs; they use a patching tool to fix up existing files on the device. That allows their size to be quite a bit smaller than a full new install. Read that again - existing files!.
It is my impression (someone correct me if I am wrong) that the installer scripts also do checksums on each individual target files that are intended to be patched, and if a single one of them fails, the install will spontaneously abort - part way through the process.
That has serious consequences, as now a failed partial install will block a subsequent attempt - if any of the target files get successfully patched, they will no longer have the checksum expected by the update script - they will no longer have the (old file) checksum. [ note I might be fuzzy on whether the individual file checks cause a wholesale abort of the installation session, or they cause a per-file abort ]
In general, you can only use an OTA patch kit on a modified phone if you have not altered any of the files involved in the patching process, and you are using the stock recovery. If you want to use a custom recovery, for certain you need to diddle the update .zip file at a minimum to remove that initial assert(), and also verify that you have not removed or fooled with any of the files from the original distro that are involved in the patching process.
Given where you are, I suggest you make backups (possibly including using Titanium Backup), and start over with the phone (flash a stock 4.1.x or 4.2.x installation or a custom ROM). OR, if you happen to have a near bone-stock backup (meaning the only thing you have done is install the Superuser.apk and su binary), you could restore that, restore the stock recovery, and then proceed with the update from there.
good luck
bftb0 said:
The assert() failure you see in the custom recovery is to be expected - it is the installer script checking to make sure that someone is attempting to apply the update to an exact version of the factory software. In this case, exact also means the version of the recovery boot in use which is trying to process the update.
In general, you can not use a custom recovery with an unmodified OTA installer file because of that first assert.
The OTA updates are NOT complete re-installs; they use a patching tool to fix up existing files on the device. That allows their size to be quite a bit smaller than a full new install. Read that again - existing files!.
It is my impression (someone correct me if I am wrong) that the installer scripts also do checksums on each individual target files that are intended to be patched, and if a single one of them fails, the install will spontaneously abort - part way through the process.
That has serious consequences, as now a failed partial install will block a subsequent attempt - if any of the target files get successfully patched, they will no longer have the checksum expected by the update script - they will no longer have the (old file) checksum. [ note I might be fuzzy on whether the individual file checks cause a wholesale abort of the installation session, or they cause a per-file abort ]
In general, you can only use an OTA patch kit on a modified phone if you have not altered any of the files involved in the patching process, and you are using the stock recovery. If you want to use a custom recovery, for certain you need to diddle the update .zip file at a minimum to remove that initial assert(), and also verify that you have not removed or fooled with any of the files from the original distro that are involved in the patching process.
Given where you are, I suggest you make backups (possibly including using Titanium Backup), and start over with the phone (flash a stock 4.1.x or 4.2.x installation or a custom ROM). OR, if you happen to have a near bone-stock backup (meaning the only thing you have done is install the Superuser.apk and su binary), you could restore that, restore the stock recovery, and then proceed with the update from there.
good luck
Click to expand...
Click to collapse
I appreciate your response. I think I may have left some things out. I am not rooted. I have only flashed the custom recovery and unlocked the bootloader. That's it. If I have to start completely over then I will. I have already tried that though. I'm willing to try any solutions that anyone has. Thanks again for your response.
Evo4eva said:
I appreciate your response. I think I may have left some things out. I am not rooted. I have only flashed the custom recovery and unlocked the bootloader. That's it. If I have to start completely over then I will. I have already tried that though. I'm willing to try any solutions that anyone has. Thanks again for your response.
Click to expand...
Click to collapse
OK. I saw the "ClockworkMod Recovery v6.0.1.0" banner and assumed rooting.
Well, let's look at the assert that you show failing (first image)
assert failed: apply_patch_check("EMMC: /dev/block/platform/sdhci-tegra.3/by-name/LNX:5007....)
Click to expand...
Click to collapse
The "LNX" partition is the "boot.img" area of the device - the kernel and ramdisk for your regular OS boot.
The fact that the assert fails means one of two things:
- that your boot partition has been modified from "stock", or
- the update .zip file is intended for some other version of a factory rom.
One of those two things. Would be sort of surprising if the OTA process mis-judged which factory release was currently on the phone. From the first image, it sure looks like the update package is intended for a from/to migration of:
JRO03S -> JZ054K
and your status screen does show JRO03S. Are you sure don't have a slightly modified boot partition?
I'm not sure what the four parameters in the assert statement are - I would think that at least one of them has to be a checksum. As the LNX (boot) partition is just a binary blob there is no filesystem present; perhaps the shorter numbers are byte lengths within the partition.
If you want to download the same OTA and fool with it (for instance to omit that first assert in META-INF/com/google/android/updater-script, re-zip it & try with TWRP), this link seems to be working:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03S.d41da8f6.zip
That's the same place the OTA process gets it from (and stuffs it into /cache along with a recovery-command file).
good luck
---------- Post added at 02:22 PM ---------- Previous post was at 02:04 PM ----------
Update -
On a lark I downloaded the OTA (referenced in the URL above) and took a look at
META-INF/com/google/android/updater-script
the assert that you see failing is the very last check before it actually begins the patching process!
That means that all the other checks (things in the /system partition) passed before that last check failed.
That certainly seems to imply a boot image that has been diddled with. Since you still show JRO03S (I'm not sure about the kernel string - I don't know what it is supposed to be), most likely this would have been a flashable zip that modified something only in the ramdisk. Does that sound familiar?
bftb0 said:
OK. I saw the "ClockworkMod Recovery v6.0.1.0" banner and assumed rooting.
Well, let's look at the assert that you show failing (first image)
The "LNX" partition is the "boot.img" area of the device - the kernel and ramdisk for your regular OS boot.
The fact that the assert fails means one of two things:
- that your boot partition has been modified from "stock", or
- the update .zip file is intended for some other version of a factory rom.
One of those two things. Would be sort of surprising if the OTA process mis-judged which factory release was currently on the phone. From the first image, it sure looks like the update package is intended for a from/to migration of:
JRO03S -> JZ054K
and your status screen does show JRO03S. Are you sure don't have a slightly modified boot partition?
I'm not sure what the four parameters in the assert statement are - I would think that at least one of them has to be a checksum. As the LNX (boot) partition is just a binary blob there is no filesystem present; perhaps the shorter numbers are byte lengths within the partition.
If you want to download the same OTA and fool with it (for instance to omit that first assert in META-INF/com/google/android/updater-script, re-zip it & try with TWRP), this link seems to be working:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03S.d41da8f6.zip
That's the same place the OTA process gets it from (and stuffs it into /cache along with a recovery-command file).
good luck
---------- Post added at 02:22 PM ---------- Previous post was at 02:04 PM ----------
Update -
On a lark I downloaded the OTA (referenced in the URL above) and took a look at
META-INF/com/google/android/updater-script
the assert that you see failing is the very last check before it actually begins the patching process!
That means that all the other checks (things in the /system partition) passed before that last check failed.
That certainly seems to imply a boot image that has been diddled with. Since you still show JRO03S (I'm not sure about the kernel string - I don't know what it is supposed to be), most likely this would have been a flashable zip that modified something only in the ramdisk. Does that sound familiar?
Click to expand...
Click to collapse
All I did was use the nexus 7 toolkit to unlock the bootloader and flash CWM touch. Yes, I do think CWM was a zip file. I'm not sure though. It's been a while since I did all that. I didn't flash anything else though.
Evo4eva said:
All I did was use the nexus 7 toolkit to unlock the bootloader and flash CWM touch. Yes, I do think CWM was a zip file. I'm not sure though. It's been a while since I did all that. I didn't flash anything else though.
Click to expand...
Click to collapse
Well, I don't know what to tell you then. Everything looks kosher except for the fact the installer is complaining about the existing boot partition not matching what it is looking for. If you took that check out, and let the patcher-thingy do its work, it could easily bork your boot image and render your tablet OS unbootable.
At this point, if you are intent on staying on 4.1.x, I suggest you install Titanium Backup, back up all your User apps & data (not the system apps), and install the full factory image for JZO54K from here
To be on the safe side, make a backup of everything on your "SD card" - after you have done the Titanium Backup.
bftb0 said:
Well, I don't know what to tell you then. Everything looks kosher except for the fact the installer is complaining about the existing boot partition not matching what it is looking for. If you took that check out, and let the patcher-thingy do its work, it could easily bork your boot image and render your tablet OS unbootable.
At this point, if you are intent on staying on 4.1.x, I suggest you install Titanium Backup, back up all your User apps & data (not the system apps), and install the full factory image for JZO54K from here
To be on the safe side, make a backup of everything on your "SD card" - after you have done the Titanium Backup.
Click to expand...
Click to collapse
Well, unfortunately I have already tried that factory image on stock recovery and through ADB. It failed also. I appreciate all the help so far, but it looks like my dad has a bunk tablet. I'll just flash the stock recovery and have him get an exchange. I don't see another option. Thanks again!
Evo4eva said:
Well, unfortunately I have already tried that factory image on stock recovery and through ADB. It failed also. I appreciate all the help so far, but it looks like my dad has a bunk tablet. I'll just flash the stock recovery and have him get an exchange. I don't see another option. Thanks again!
Click to expand...
Click to collapse
Well I would think that is a failure with a different root cause as the factory installs don't really care about what is on the tablet - well, except maybe for a version check of the bootloader, and I do see that JZO54K did have the older v3.41 bootloader. That's a possibility.
What error occurs when you try to flash that factory image?
FWIW, oldblue910 mantains an archive of Nexus 7 factory images. You didn't mention whether or not you were on the WiFi only version (nakasi) or 3G version (nakasig), but he has both on his site.
good luck
PS I note that I never checked if there was a different OTA depending on whether or not the unit in question was 3G vs. WiFi-only, although TBH it would be weird if the wrong one got delivered over the air to the tablet. It does seem quite odd though, that the only thing which doesn't pass the initial OTA assert checks (checksums) is the boot image.
bftb0 said:
Well I would think that is a failure with a different root cause as the factory installs don't really care about what is on the tablet - well, except maybe for a version check of the bootloader, and I do see that JZO54K did have the older v3.41 bootloader. That's a possibility.
What error occurs when you try to flash that factory image?
FWIW, oldblue910 mantains an archive of Nexus 7 factory images. You didn't mention whether or not you were on the WiFi only version (nakasi) or 3G version (nakasig), but he has both on his site.
good luck
PS I note that I never checked if there was a different OTA depending on whether or not the unit in question was 3G vs. WiFi-only, although TBH it would be weird if the wrong one got delivered over the air to the tablet. It does seem quite odd though, that the only thing which doesn't pass the initial OTA assert checks (checksums) is the boot image.
Click to expand...
Click to collapse
It's the WiFi only version. I know this whole situation is weird. I've been rooting and flashing since the G1 and have never encountered anything like this. I did make sure I tried the one that was for the WiFi version and it still didn't work though. Thanks again for all your help.
Alright, this is a convoluted and awful process, but it works, and it is the only one we have right now.
If you already got 4.4.2 from the OTA or SBF, without using the method below. STOP none of this will work on your phone.
It is a 7 step process. Outline is as follows:
1. Download the 4.2.2 zip for your Moto X.
A. Go to Here. http://sbf.droid-developers.org/phone.php?device=0B. Download Android 4.2.2 Blur_Version.139.4.17.ghost_row.RepublicWireless.en.USC. Extract it.D. Flash the files with fastboot. Flash them all. Including bootloader and recovery.E. This will restore your phone to STOCK 4.2.2, hope you had backups.2. Root using RockMyMoto
A. http://forum.xda-developers.com/moto-x/orig-development/root-rockmymoto-yes-ota-t25095903. Install the Tmobile XT1053 Safestrap
A. http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/4. [kill write protection] MotoWpNoMo
A. This is permanent. (Well... Mostly, someone more important than me can answer how/why) Do you own research here)B. http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113C. Here is a mirror of the MotoWpNoMo, since his windows zip link is broken https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit5. Download the 4.4.2 Safestrap flashable update.zip from one of the links below.
A. Mirror A: http://www.leetnet.net/update_SafeStrap_4.4.2_RW.zipB. Mirror B: TDBC. Mirror C: TDBD. Reboot into SafeStrap TWRPE. Delete any Slots you may have. They won't work anymore after this.F. Flash the update zip into the "Stock" slot.6. Download the 4.4.2 zip for your Moto X.
A. Go to Here. http://sbf.droid-developers.org/phone.php?device=0B. Download Android 4.4.2 Blur_Version.165.44.12.ghost_row.RepublicWireless.en.USC. Extract it.D. STOP EVERYTHING AND READ THE NEXT PART CAREFULLY. YOU DON'T WANT TO SCREW THIS PART UP.E. LIKE SERIOUSLY, YOU WILL BRICK IT.F.
Code:
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
G. NOTHING ELSE. DO NOT TOUCH THE OTHER FILES. ESPECIALLY LEAVE RECOVERY UNTOUCHED. The reason for this is that you won't be able to flash the 4.2.2 ever again without the 4.2.2
recovery, which means you would lose the ability to root, disable WP, or install safestrap.7. Download the SuperSU zip (or if you are Rashed97 and then you can do some CM crap )
A. http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zipB. Flash this from TWRP, and it will "re-root" your 4.4.2
Thanks: jbrukardt, jcase, iKrYpToNiTe, glarepate, Rashed97, and my wife's phone for being a "test platform"
No Warranty. No Hating. No Killing my Dog.
RESERVED.
I can't thank you! Literally!
Bcuz: Sorry, you are limited to 8 thanks per day
So maybe I will thank you tomorrow. (X-D
---------- Post added at 04:11 PM ---------- Previous post was at 04:11 PM ----------
I can't thank you! Literally!
Bcuz: Sorry, you are limited to 8 thanks per day
So maybe I will thank you tomorrow. (X-D
glarepate said:
I can't thank you! Literally!
Bcuz: Sorry, you are limited to 8 thanks per day
So maybe I will thank you tomorrow.
Click to expand...
Click to collapse
Thank me by reading through it and making sure everything is sane and works. This is my first "Guide"
malcolmputer said:
Thank me by reading through it and making sure everything is sane and works. This is my first "Guide"
Click to expand...
Click to collapse
Ok. You have a typo in the section about downloading the KK SBF. It says:
6. Download the 4.4.2 zip for your Moto X.
A. Go to Here. http://sbf.droid-developers.org/phone.php?device=0
B. Download Android 4.2.2 Blur_Version.139.4.17.ghost_row.RepublicWireless.e n.US
It should say -- Blur_Version.165.44.12.ghost_row.RepublicWireless.en.US
So, thank you twice!!
Great new guide. ?
The only thing I think should be added, directly at the top of the OP...and in bold capital letters... ..is if you're already on 4.4.2.....stop reading.....and don't do any of this.. Lol
Unless something has changed, if they are already running 4 4.2.....and do step one, they could be on the road to trouble.
Please tho.....correct me if I'm wrong.
Great job tho!!!! I don't think many know of this relatively new method.
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
BTW....if this method leaves you with root AND write protection disabled on 4.4.2....shouldn't the person that figured this out be receiving the healthy bounty?????
Adding to this. MotoWpNoMo is dead link in the op of the original thread.
Here's a live link
https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit
---------- Post added at 11:58 PM ---------- Previous post was at 11:48 PM ----------
kj2112 said:
Great new guide. ?
The only thing I think should be added, directly at the top of the OP...and in bold capital letters... ..is if you're already on 4.4.2.....stop reading.....and don't do any of this.. Lol
Unless something has changed, if they are already running 4 4.2.....and do step one, they could be on the road to trouble.
Please tho.....correct me if I'm wrong.
Great job tho!!!! I don't think many know of this relatively new method.
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
BTW....if this method leaves you with root AND write protection disabled on 4.4.2....shouldn't the person that figured this out be receiving the healthy bounty?????
Click to expand...
Click to collapse
correct, if you've already taken the ota, you're right and proper borked.
Well, I couldn't wait for reports of success, requests for clarification, etc. So I just kind of bulled my way through and now I am up and running165.44.12.ghost_row.RepublicWireless.en.US and my phone is downloading stuff wildly as it syncs with Google's servers and restores all my old apps and settings and such-like.
Haven't switched to ART yet. But it's early days yet. Certainly too early to start whining when I have this lovely new OS to play with.
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
Well, I couldn't wait for reports of success, requests for clarification, etc. So I just kind of bulled my way through and now I am up and running165.44.12.ghost_row.RepublicWireless.en.US and my phone is downloading stuff wildly as it syncs with Google's servers and restores all my old apps and settings and such-like.
Haven't switched to ART yet. But it's early days yet. Certainly too early to start whining when I have this lovely new OS to play with.
OK, so I used the update.zip to update to 4.4.2. If I use RSD Lite to go back to 4.2.2, why wouldn't this guide work?
ScipioWarrior said:
OK, so I used the update.zip to update to 4.4.2. If I use RSD Lite to go back to 4.2.2, why wouldn't this guide work?
Click to expand...
Click to collapse
Cause once you're on the 4.4.2 boot loader....trying or successfully downgrading it can lead to a bricked device. Just something about that 4.4.2 boot loader.
kj2112 said:
Cause once you're on the 4.4.2 boot loader....trying or successfully downgrading it can lead to a bricked device. Just something about that 4.4.2 boot loader.
Click to expand...
Click to collapse
OK, so what step can't you do on the 4.4.2 bootloader?
Yep. If you use any other method to update than mine, you lose the ability to downgrade back to 4.2.2, which means no more disable WP, and in RW's case, without 4.4, no more root.
ScipioWarrior said:
OK, so what step can't you do on the 4.4.2 bootloader?
Click to expand...
Click to collapse
You can't downgrade it, period. And if your on a locked boot loader, you can't root it.
All you can do is sell it, and put the money towards one that can be unlocked and works on your provider.
Sorry.
kj2112 said:
Cause once you're on the 4.4.2 boot loader....trying or successfully downgrading it can lead to a bricked device. Just something about that 4.4.2 boot loader.
Click to expand...
Click to collapse
that something specifically is the recovery. the 4.4.2 recovery patches the bug that allows us to exploit and run MotoWpNoMo
So let's say that I somehow screwed up Step 1. I downloaded 4.2.2, verified md5, extracted, and ran the included .bat to flash everything. I've now booted up into a sick android logo with an exclamation point. How exactly have I screwed up and can it be fixed?
edit: Weird. After that happened, it rebooted on its own and now its fine.
teh_lorax said:
So let's say that I somehow screwed up Step 1. I downloaded 4.2.2, verified md5, extracted, and ran the included .bat to flash everything. I've now booted up into a sick android logo with an exclamation point. How exactly have I screwed up and can it be fixed?
edit: Weird. After that happened, it rebooted on its own and now its fine.
Click to expand...
Click to collapse
this wording looks awfully similiar.
A little bit more feedback on the process.
NOTE: I was 97% in Debian Wheezy but WPNoMo requires 32 bit Linux so for that I had to boot into Slackware. Also watch your phone's screen and grant permission when Su asks for it. I spaced that part out and had to -- shudder -- run the 'wpbegone' script a second time for it to succeed.
I was able to use the Android version of fastboot to set oem mode but for most everything else only the motofastboot program worked. My advice is just use the Motorola version for everything since there doesn't seem to be anything that it _can't_ do, it just has some things that it __can__ do that are needed. If you see the "variable not supported" diagnostic message then go back and re-do that step over again with motofastboot. When the step to configure the carrier for Sprint failed my heart dropped into the apartment down on the first floor. But re-doing the erasing and flashing steps, with no reboot, no re-running the 'fastboot oem set_fb_mode' command line or anything else, and it succeeded ; bullet dodged. Whew!
It would be nice if there were excruciating detail on things like every little step of wiping/factory setting the Stock slot in SafeStrap. Maybe it's just because I am out of practice that it seemed a little bit lacking in specificity and left me wondering a bit about what I was going to do next in light of what the instructions conveyed to me. Or maybe it's just my anxiety, after all I did get through it successfully.
glarepate said:
A little bit more feedback on the process.
NOTE: I was 97% in Debian Wheezy but WPNoMo requires 32 bit Linux so for that I had to boot into Slackware. Also watch your phone's screen and grant permission when Su asks for it. I spaced that part out and had to -- shudder -- run the 'wpbegone' script a second time for it to succeed.
I was able to use the Android version of fastboot to set oem mode but for most everything else only the motofastboot program worked. My advice is just use the Motorola version for everything since there doesn't seem to be anything that it _can't_ do, it just has some things that it __can__ do that are needed. If you see the "variable not supported" diagnostic message then go back and re-do that step over again with motofastboot. When the step to configure the carrier for Sprint failed my heart dropped into the apartment down on the first floor. But re-doing the erasing and flashing steps, with no reboot, no re-running the 'fastboot oem set_fb_mode' command line or anything else, and it succeeded ; bullet dodged. Whew!
It would be nice if there were excruciating detail on things like every little step of wiping/factory setting the Stock slot in SafeStrap. Maybe it's just because I am out of practice that it seemed a little bit lacking in specificity and left me wondering a bit about what I was going to do next in light of what the instructions conveyed to me. Or maybe it's just my anxiety, after all I did get through it successfully.
Click to expand...
Click to collapse
Flesh it out into a "noob guide" then that includes every detail
Fastboot Flash Errors
First of all, thanks so much!
So, when I try to flash the .img files through fastboot, boot.img always goes through successfully, but if i try to flash in motoboot.img, recovery.img, or system.img, I get this:
"Variable not supported!
target reported max download size of (whatever size it was) bytes
sending 'boot' <whatever size the file was kb>...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: however long it took s"
I have no idea what's going wrong, could you please help? I am able to restore my phone by selecting recovery in fastboot so there's no permanent damage done, but I want to get out of 4.2.2.
Will try to work on some noob-friendly verbiage this weekend. (-
---------- Post added at 12:25 AM ---------- Previous post was at 12:15 AM ----------
Victor Czar said:
First of all, thanks so much!
So, when I try to flash the .img files through fastboot, boot.img always goes through successfully, but if i try to flash in motoboot.img, recovery.img, or system.img, I get this:
"Variable not supported!
target reported max download size of (whatever size it was) bytes
sending 'boot' <whatever size the file was kb>...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: however long it took s"
I have no idea what's going wrong, could you please help? I am able to restore my phone by selecting recovery in fastboot so there's no permanent damage done, but I want to get out of 4.2.2.
Click to expand...
Click to collapse
For every step where you see "Variable not supported!" you will need to use the Motorola version of fastboot because the Android SDK version isn't capable of performing the task.
The Moto version is contained in this Zip archive:
http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280
So, I just downloaded the OTA 3.0 update and it said to reboot to continue? So, I let it reboot but after rebooting, it loaded up the TWRP screen?
What should I do?
Neo3D said:
So, I just downloaded the OTA 3.0 update and it said to reboot to continue? So, I let it reboot but after rebooting, it loaded up the TWRP screen?
What should I do?
Click to expand...
Click to collapse
Navigate to /data/user/0/com.nvidia.ota/app_download
There should be your downloaded ota zip and install manually through twrp. If that would be native stock recovery the process of installation would be automatic
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
Navigate to /data/user/0/com.nvidia.ota/app_download
There should be your downloaded ota zip and install manually through twrp. If that would be native stock recovery the process of installation would be automatic
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
Thank you! But, my machine doesn't have a subfolder called, "0" after /data/user/?
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
unvaluablespace said:
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
Click to expand...
Click to collapse
Thanks!
I just started looking in all the folders and found the ota.zip file. Mine was located in:
Code:
/data/data/com.nvidia.ota/cache/
However, I have a new problem now. I keep getting this error:
Code:
This package is for "foster" devices; this is a "shieldtablet"
E:Error executing updater library in zip '@/cache/recovery/block.map'
E:Error installing zip file '@/cache/recovery/block.map'
I don't want to do a stock reset because that means I'll have to reinstall Kodi again. I don't want to lose all my preferences and settings in Kodi.
unvaluablespace said:
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
Click to expand...
Click to collapse
(little bit browsing for appropriate folder then walk through factory reset procedure for automatic upgrade ??? !!!!) yes u can do that if you already on 2.1, but if you on 3.0 vulkan without stock recovery? and my way bit faster is (just navigate to appropriate folder for ota) ---- after upgrading 3.0 you can do factory reset through twrp or through system it self.
---------- Post added at 06:26 PM ---------- Previous post was at 06:09 PM ----------
Neo3D said:
Thanks!
I just started looking in all the folders and found the ota.zip file. Mine was located in:
Code:
/data/data/com.nvidia.ota/cache/
However, I have a new problem now. I keep getting this error:
Code:
This package is for "foster" devices; this is a "shieldtablet"
E:Error executing updater library in zip '@/cache/recovery/block.map'
E:Error installing zip file '@/cache/recovery/block.map'
I don't want to do a stock reset because that means I'll have to reinstall Kodi again. I don't want to lose all my preferences and settings in Kodi.
Click to expand...
Click to collapse
start downloading ota....when its over dont restart just press home button on remote and go to es file explore (first enable root exlorer) ---- navigate device/data/data/com.nvida.ota/app_download/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.zip
copy that long name file with ending with .zip to somewhere like download folder ------------reboot to recovery and reflash
p.s. ota location path is from 16gb i have 500gb i have same path, should be on yours tooo. try
p.s. sorry for gave you wrong path first, didnt check personally my self
Thanks, I just had to flash the recovery image again for the update to work.
Nice. glad to hear thats all you needed to do. I had a feeling that might be the case, but i didn't want to suggest that in case it was wrong. lol
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Install supersu or dm-verity to bypass the security checks.
tupurl said:
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Click to expand...
Click to collapse
I think this is B29 stock image DrakenFX has uploaded it on sharing website, give it a try.
https://www.androidfilehost.com/?fid=312968873555009511
romeoh said:
I think this is B29 stock image DrakenFX has uploaded it on sharing website, give it a try.
https://www.androidfilehost.com/?fid=312968873555009511
Click to expand...
Click to collapse
Thanks for the link!
Will this work via the update from sd card option on the stock recovery? Or would you recommend flashing from TWRP? Or via MiFlash in EDL mode?
gpz1100 said:
Install supersu or dm-verity to bypass the security checks.
Click to expand...
Click to collapse
Doesn't that require unlocked bootloader? I want to avoid voiding the warranty.
tupurl said:
Thanks for the link!
Will this work via the update from sd card option on the stock recovery? Or would you recommend flashing from TWRP? Or via MiFlash in EDL mode?
Click to expand...
Click to collapse
This is the zte official B29 package and the only way to used it from the stock recovery from the SD card. It won't work with twrp because it requires the stock recovery. You can also use this method and you don't have to have unlcked bootloader http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page26
romeoh said:
This is the zte official B29 package and the only way to used it from the stock recovery from the SD card. It won't work with twrp because it requires the stock recovery. You can also use this method and you don't have to have unlcked bootloader http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page26
Click to expand...
Click to collapse
So, I just now tried to apply the package you linked to (Draken FX stock Marshmallow) and it gave me the same errors :/
E: footer is wrong and E: signature verification failed. Should I try something else?
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
lafester said:
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
Click to expand...
Click to collapse
I can't boot into system. Is there a way to enable OEM unlock from recovery, EDL, or factory test mode?
Did you check the zip? You could always use miflash b15 full.
lafester said:
Did you check the zip? You could always use miflash b15 full.
Click to expand...
Click to collapse
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
tupurl said:
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
Click to expand...
Click to collapse
axon7tool uses different drivers. install the correct drivers for miflash.
tupurl said:
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
Click to expand...
Click to collapse
Ok, I think there was a little misunderstanding about the B29 link that I sent to you bro. That file can only be flashed in Stock recovery you can't flash it with MiFlash. If you want to use MiFlash the only version that's available to flash in EDL mode is Nougat B15. Just reread the OP of the the link I've sent to you before and If you didn't understand anything let us know there is always someone here will help you.
romeoh said:
Ok, I think there was a little misunderstanding about the B29 link that I sent to you bro. That file can only be flashed in Stock recovery you can't flash it with MiFlash. If you want to use MiFlash the only version that's available to flash in EDL mode is Nougat B15. Just reread the OP of the the link I've sent to you before and If you didn't understand anything let us know there is always someone here will help you.
Click to expand...
Click to collapse
I'm having sort of the same problem except I'm stuck on the bootloader unlocked screen and any rom I flash gets stuck on "patching system image unconditionally"
Fazedyrus said:
I'm having sort of the same problem except I'm stuck on the bootloader unlocked screen and any rom I flash gets stuck on "patching system image unconditionally"
Click to expand...
Click to collapse
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
romeoh said:
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
Click to expand...
Click to collapse
Did that, the flash is successful but I still have the same problem in that the system won't boot. Should I just relock and rma at this point?
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
romeoh said:
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
Click to expand...
Click to collapse
Flashing supersu and dmverity zip doesn't work either
Fazedyrus said:
Did that, the flash is successful but I still have the same problem in that the system won't boot. Should I just relock and rma at this point?
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
Flashing supersu and dmverity zip doesn't work either
Click to expand...
Click to collapse
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
---------- Post added at 04:45 PM ---------- Previous post was at 04:21 PM ----------
Fazedyrus said:
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
Click to expand...
Click to collapse
also, not being able to flash any rom with a working twrp makes it look like only I have this problem
---------- Post added at 05:32 PM ---------- Previous post was at 04:45 PM ----------
Fazedyrus said:
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
---------- Post added at 04:45 PM ---------- Previous post was at 04:21 PM ----------
also, not being able to flash any rom with a working twrp makes it look like only I have this problem
Click to expand...
Click to collapse
yep, everything is stock yet I am still not able to boot into system
lafester said:
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
Click to expand...
Click to collapse
tupurl said:
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Click to expand...
Click to collapse
lafester is correct, the B15 file from downloaded from ZTE is zipped twice. There is an actual update.zip inside a folder inside the "America A2017U SD card software package(A2017UV1.1.0B15)SD_W" zip. When I bricked my phone, I extracted the update.zip and I was able to flash it from the SD with the stock recovery. Hope that helps.
Howie Dub said:
lafester is correct, the B15 file from downloaded from ZTE is zipped twice. There is an actual update.zip inside a folder inside the "America A2017U SD card software package(A2017UV1.1.0B15)SD_W" zip. When I bricked my phone, I extracted the update.zip and I was able to flash it from the SD with the stock recovery. Hope that helps.
Click to expand...
Click to collapse
where can I find this zip
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck
superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.
superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.