Database Users

loaded wrong rom, stuck on boot screen

Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.

you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.

thanks
Thanks for the quick response! I'll try that.

Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?

So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.

david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.

gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.

So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.

working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.

David, now that it is working, I would recommend updating your recovery to 1.5.2.

I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.

[Q] Clockworkmod not Recoverying/Doing anything useful

So I had Cyanogenmod 7.1.0-RC1 flashed on my phone and working fine. Then one day it was all frozen up and wouldn't boot or do anything. So I decided to use Clockworkmod (3.0.2.4) to restore to an old backup I have of Cyanogen 7.0.3. It came up with a silly error saying it could not format /cache, but everything else worked so I shrugged it off and rebooted. Cyanogen 7.0.3 loaded fine, but I could not download apps from the marketplace. (They would never "start" - I even tried installing the new marketplace update). So then I decided to restore the SAME backup again, with the same error, and after struggling I tried restoring to a backup I have of the stock rom. Which worked. Magically. No errors. So then, being stupid and unsatisfied I reflashed the Cyanogen 7.0.3 backup again. This time it said "error while formatting /system!" And now I've been stuck trying to figure out how to fix this error.
I can still boot into ClockworkMod, so I assume my phone is not bricked. I've read that updating to ClockworkMod 3.0.2.5 may actually fix my problem, but I can't seem for the life of me to find a tutorial that can tell me how to flash a new recovery image on the MT4G without Rom Manager (since I can't boot a rom, I can't open rom manager).
Thank you for your time, any help is appreciated. (I also apologize upfront if this error has been reported and solved before, I can't seem to find it though.)

Sorry, but your phone is bricked. Those errors indicate that your eMMC chip has failed. Your only hope is to flash the PD15IMG.zip file from the bootloader. That will unroot your phone and flash the stock ROM. It's unlikely to work, however. Some people will swear up and down that eMMC failure doesn't brick the phone, but I have yet to see anyone save their device once those errors appear in recovery mode.

Thanks for you quick response. I am going to try what you suggested and update what happens.
Do you know what may cause this error? So I can avoid it in the future. Granted, I may not have a phone for a while now.

crebu said:
Thanks for you quick response. I am going to try what you suggested and update what happens.
Do you know what may cause this error? So I can avoid it in the future. Granted, I may not have a phone for a while now.
Click to expand...
Click to collapse
Some MT4G's have a different brand of eMMC chip that is prone to failure after the phone has been rooted. See this thread for a little more info.
Make sure you flash the correct PD15IMG.zip file. Any file flashed in the bootloader has to be named that, so a search could easily turn up a radio. Search the dev section for the stock TMOUS RUU. It will be around ~328MB in size (roughly).

Not every "can't open /cache/recovery/log" error means your eMMC is dead. My phone gave that error after a bad ROM flash. Flashing PD15IMG.zip in hboot fixed it.

TeeJay3800 said:
Some MT4G's have a different brand of eMMC chip that is prone to failure after the phone has been rooted. See this thread for a little more info.
Make sure you flash the correct PD15IMG.zip file. Any file flashed in the bootloader has to be named that, so a search could easily turn up a radio. Search the dev section for the stock TMOUS RUU. It will be around ~328MB in size (roughly).
Click to expand...
Click to collapse
When I try to use Clockwork to update from the zip I get the error
E:Can't open /sdcard/PD15IMG.zip
(bad)
Installation aborted.
Maybe I don't understand the correct procedure for flashing a PD15IMG.zip file?
**EDIT** I'm dumb, I had to boot into the bootloader. Hehe.

crebu said:
When I try to use Clockwork to update from the zip I get the error
E:Can't open /sdcard/PD15IMG.zip
(bad)
Installation aborted.
Maybe I don't understand the correct procedure for flashing a PD15IMG.zip file?
Click to expand...
Click to collapse
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
Thank you so, so much.
What you suggested absolutely worked. I'm not back to the stock rom working seemingly perfectly. Does this mean I don't have a bad eMMC chip? Would it be safe to continue flashing custom ROMS?
Thanks again.

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
Thank you so, so much.
What you suggested absolutely worked. I'm now back to the stock rom working seemingly perfectly. Does this mean I don't have a bad eMMC chip? Would it be safe to continue flashing custom ROMS?
Thanks again.
Edit: changed "not" to "now". Quite a misleading typo.

crebu said:
Edit: changed "not" to "now". Quite a misleading typo.
Click to expand...
Click to collapse
Haha, yeah it was! I'm glad your phone is not (now) working. As far as where to go from here, find out what eMMC you have. The thread I linked to has ADB instructions in the OP, and there are instructions to run commands via a terminal emulator throughout the thread. If you have the "good" eMMC, there's no reason you can't re-root and start over. Because of the errors you got in recovery, I'm afraid you have the "bad" eMMC in which case rooting is risky. Essentially, once you've rooted a phone with the bad chip, it's only matter of time until it fails and the phone is bricked. It could be a few days, few months, or few years, but the evidence shows it likely eventually will. Good luck!

TeeJay3800 said:
In my earlier post I said to flash in the bootloader. Put the file in the root of your SD card, boot into the bootloader, and it will ask you if you want to flash the file.
Click to expand...
Click to collapse
hi, could you help me on this?
Even if I hboot my phone ( by hold power and vol down), the phone still gets to CWM. Could you help me to boot PD15img.zip in the bootloader.
Thank you so much,

[SOLVED] Error installing recent OTA update, anyone help or provide insight?

Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and when the device reboots it then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!

MarkAllen said:
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and it the device reboots then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
Click to expand...
Click to collapse
From what i recall the fingerprint is what is shown in the buildprop. You could try editing this but i would tread carefully if its just a minor update as it may justmess up your system if there are other mismatches during the update process.
Lenovo technical support is a complete joke, you get much better help here. Lol
Sent from my F5121 using Tapatalk

Nope every line of my build.prop, where listed, has the proper "Lenovo/yeti_10_row_wifi" that the update claims is wrong. I personally think it is this update itself but no confirmation from other users if the update
"YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90 F_USR_S000426_1705080316_WW06_BP_ROW"
has installed for them yet.
And I certainly knew how far I was *not* going to get with Lenovo but figured it couldn't hurt. I was really trying to get a stock ROM download from them or anywhere. I would love to just revert this to how it was out of the box and start over.

Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?

MarkAllen said:
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
Click to expand...
Click to collapse
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.

Broomfundel said:
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Click to expand...
Click to collapse
Thanks for that confirmation! I did end up getting a registered account ($15) used Paypal and all looked good. I ended up downloading two versions of firmware. Initially I thought I would start with the oldest knowing many updates awaited but really wanted to be sure in erasing all my previous steps just in case it didn't work or the same thing happened again.
Used "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" from Easy Firmware. I opted to follow the included "installer.cmd" but did not do the "unlock" or "lock" as I already was unlocked of course and did not want to lock it again. When it completed I first noted my Halo keyboard not working and things were in Chinese here and there. This post resolved both items (thanks vimalbhimani!). Pretty sure that was because I formatted all the various partitions including "country", duh. Sadly however this version was showing no further OTA updates were available at all. Maybe Lenovo has deleted some of the really old OTA downloads and they are no longer available? Not sure.
I then installed the most recent rom "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". This time I did not format and only flashed this newer roms boot, bootloader, factory, recovery, and system images. After the system was backup everything was in great shape and updates were available. I made a TWRP backup straight away. Then I let the first and second updates listed below download and install via OTA and had no issues. The final two I opted to save time and installed using the standard recovery from my SD card after I downloaded them from my PC. Here are direct links to those if anyone wants them and they are in order of install (descending) based on already having "YB1-X90F_USR_S000196_161104"
http://tabdl.ota.lenovomm.com/dls/v...S000239_1612091428_WW06_BP_ROW_WCAC703BC6.zip
http://tabdl.ota.lenovomm.com/dls/v...S000340_1702251540_WW06_BP_ROW_WC365253B3.zip
http://tabdl.ota.lenovomm.com/dls/v6/YB1-X90F_170420_WC76FD00EF.zip
http://tabdl.ota.lenovomm.com/dls/v...S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip (this is the failed update that incited this thread)
All updates went great and all is well at this point. Made another TWRP backup and I plan to root again now and see if any upcoming updates later have some issue?

I just wanted to report back here if anyone was interested that I unrooted, updated the June OTA update, and was able to root again without issue.

i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...

FreddeHamm said:
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
Click to expand...
Click to collapse
You cannot flash the ZIP file with TWRP or stock recovery. You have to unzip the file and then flash each IMG file that you need manually while in fastboot mode (there are seven of them).
**** IF YOU FOLLOW THESE DIRECTIONS IT IS NO ONES FAULT BUT YOUR OWN IF IT SCREWS UP SOMETHING!!! ****
**** WILL TRY TO HELP PROVIDE INFO IF I CAN BUT CANNOT GUARANTEE ANYTHING. ALSO THIS ERASE ALL YOUR DATA ****
First be aware as noted in the previous post above that I tried using "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" intially and it worked fine to get me back up and running but once I was done no new OTA updates were showing at all. No clue why so I ended up doing it again but used the ROM named "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". Also note I had erased my "country" partition and flashed "country.img" which requires the info posted by vimalbhimani again linked above in my previous post. It has to be used to correct for your country, no biggie at all and worked fine for myself.
1) Unzip the ROM you downloaded to a folder on your PC
2) From command prompt go to that folder
3) Make sure from the command prompt that ADB and fastboot commands are working properly
4) Put your tablet in fastboot mode ("adb reboot bootloader")
(these next commands are directly from the "install.cmd" included with the ROM from EasyFW, I just opted to run them manually one at a time in order and I omitted the unlock and lock commands)
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot continue
That's it. Minus the Intel error code 03 for being unlocked, it should be a normal out of the box setup when it boots back up into Android.
good luck!

People that are looking for the YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip may want to take a look at this post.
In contrast to my experiences with devices made by other OEMs, it seems like the files can directly be used for downgrading the Yoga Book if you're currently using a newer version.

Moved...

Soft bricked HTC 10 - having issues getting back up and running

A lot of these I'm sure are general but since the HTC 10 is what I have and I'm using firmware and ROMs from within this subforum I thought this would be the most appropriate place to post. I have rooted/unlocked all of my (non-Nexus) phones over the years and like to think I have a moderate amount of experience with the process, but this is driving me up the wall and my searches for similar problems are turning up nothing but unrelated issues. My HTC 10 is unlocked and S-Off. I was running the ROM from this thread (the 6.0.1 version) for quite some time but stopped using the phone due to unrelated issues (screen is too big, can't get over the polarized screen and not being able to use the phone with sunglasses on). I'm now trying to sell it and therefore trying to get current firmware and a stock ROM onto it so potential buyers are not freaked out about modifications to the phone. I'd like to leave it unlocked and S-Off though.
I am able to successfully flash the firmware (from this thread), and have been going back and forth between the full stock ones and the ones with TWRP built in. As of right now the phone has no bootable ROM and I have been unable to load one. I can successfully get into Download, Recovery, and Fastboot modes. I see that I have three main paths to potentially flashing a stock ROM:
- Repair/Upgrade via HTC Sync with the phone in download mode
- Load the ROM onto the phone's SD card and use TWRP to flash
- Use ADB to sideload the ROM directly from Windows
My problems with these three options are thus:
- HTC Sync does recognize the device when put in Download mode. It even successfully downloads the update it perceives the phone needs. But at 20%, it claims the phone has too low of battery (it doesn't, it's locked at 100% and has been plugged in the whole time) and quits. It does this regardless of whether I select Upgrade or Repair. Tried multiple times, with both stock recovery and TWRP. I found one other case of this, and the only response was the OP saying he just sent his phone back to HTC. I don't think this is an option for me because it has sat unused basically since I bought it over six months ago.
- The phone does not read the SD card. Other devices read it just fine, but I don't have any SD card reader that can directly talk to my computer to do the file transfer through. I have not found any guides that allow me to mount the SD card without having a bootable ROM. Maybe this is where I simply don't know enough about ADB/TWRP and someone can point out a simple solution? I'm hopeful.
- I can get the phone into Recovery and then into "Sideload" mode. But trying to run "adb devices" or "adb sideload 2PS6IMG.zip" returns some variation of the following (the 31 and 39 are always there, sometimes it had more detail and sometimes it has less):
>adb server version (31) doesn't match this client (39); killing...
>error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
>This application has requested the Runtime to terminate it in an unusual way.
>Please contact the application's support team for more information.
I can't find anyone having these errors in this combination, but from what I can gather it's somehow tied to not having an up-to-date version of ADB... but I keep going and downloading the absolute most recent one (either from one of the threads here or Android Studio) and it just doesn't work. If I use one of the HTC_fastboot packages instead to try running the commands I just get "cannot read 'sideload'". I assume there is some kind of package or library missing from those directories.
Really I will take advice on troubleshooting any of these three angles, or one I have not though of. I'm sure all of the problems are stemming from one very annoying source but I just don't know what else to try. Thanks for any help you can offer.

I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.

Valdair0 said:
I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.
Click to expand...
Click to collapse
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.

Tarima said:
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.
Click to expand...
Click to collapse
Make sure it's named 2PS6IMG.zip

Thanks guys, it seems to be working okay now. It was upgrading to 7.0 when I left the house this morning. I'm going to flash stock recovery one last time tonight and hopefully it will be set.

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.