Related
Hi!
Does anyone know about a tool to check (and maybe also fix) a bad NAND/EMMC? This is my story:
This Friday I was sitting in my couch and browsing the web on my M9 (HTC__Y13, Europe version) and suddenly it just reboots itself.
This is normal behavior (at least with my phone, happens now and then), but this time it just kept rebooting itself.
I can boot to FASTBOOT but not to "Download Mode" or "Recovery Mode". If I choose Download/Recovery-Mode, it starts to load but just to reboot itself
again.
Pressing VolUp+VolDwn+Pwr takes me to the FASTBOOT menu.
Choosing "Download Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Choosing "Recovery Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds it reboots itself.
Pressing VolDwn+Pwr takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Trying to boot to RUU-mode (fastboot oem rebootRUU) gives me the same behavior.
S-ON: YES
Relocked: YES
Thanks in advance!
From getvar-command (looks pretty strange to me)
Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT**********
I modified the value on row "(bootloader) serialno:" for this post, value is proper.
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like it may have been slowly dying over time.
If you live in the USA or taiwan, or have a warranty you can get a replacement from HTC free of charge.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you so much for your response!
As I suspected
Unfortunately I'm live (and has bought the phone) in Sweden, so I think an unlocked/relocked bootloader = f*cked. But I will contact HTC support anyway.
shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
Click to expand...
Click to collapse
I agree with you that the EMMC is probably broken. However, the "HT" has nothing to do with the model of the device. (How to read Serialnumbers)
Very creepy. I'm having the same exact bootloop issue as the OP. Friday evening, got stuck on the bootloop. Earlier in the week, I thought I was stuck but hooked it up to my pc and was able to reboot fine. Now I'm most certainly screwed.
I'm ***software status: Official*** ***UNLOCKED*** ***S-OFF***.
Now I'm not sure my phone is even showing up when connected to my PC. When I'd run "adb devices" no devices would show up, but if I did "htc_fastboot getvar all" I had an output similar or same as the OP. I tried to uninstall/re-install HTC Sync Manager, and install the latest Minimal ADB, and now I can't even get that output as seen above.
Where do I go from here? I had the hardest time putting ViperOne on my phone a year ago. I spent three or four weekends studying the forums here. I need detailed instructions or I'll get lost. Thank you all for your work so far here in the forums. If you want to experiment on my phone to get it functional again please feel free to point me in the right direction. I had hoped this post would help, but like I said, I can't see my phone in task manager. (Also, I'm not sure about step 4., I don't see an MAF32 file in what I extracted from the latest minimal adb files.). Please help!
Download mode and then htc_fastboot getvar all.
Qualcomm makes publicly available software that controls the raw hardware so that the manufacturer can upload their firmware. I can't remember where I saw it but it was only a short google search to find it.
It may help. It may not help.
Beamed in by telepathy.
I left the phone on the bootloader screen, plugged in to the PC. I think it got a solid charge overnight, and I am now able to boot normally. In the interest of making my phone more stable, I've tried the No wipe.zip method as seen here to go from 3.35.401.12 to the M9_4.14.401.7_NoWipe_TWRP3030.zip, followed by a TWRP wipe. My Venom ROM would still be based on the older firmware. Also, download mode screen shows the older firmware OS version. Will this cause problems? What can I do to make my phone stable again?
Joining the flock
Hello all. My first post here. I have the same issue on my m9
Status modified, s-on, locked, security warning.
Can't access download mode or recovery. It gives me the green logo on white background with red warning text ('failed to load... This build is for...').
Adb can't see device.
Issue appeared after cracked display started ghost touching all over. Changed system language and such before I turned it off. I went to unofficial service to replace display/frame set and they said it's locked on bootloader.
From what I see here, others with screwed up NAND experience bootloop and can't access download mode..
I just want to be 100% shure it's bricked forever before selling it for parts. I want to fight for my 'baby' to the very end.
So how can I test this or are there any there any tricks I can use to make it boot/get to download mode?
Thank you!
Later edit: don't know if this means anything, but if I select Reboot to Bootloader, the security warning is missing. It just appears if I user the other options.
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
groxack said:
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
Click to expand...
Click to collapse
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
ludemon said:
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
Click to expand...
Click to collapse
Further to the above, whilst in TWRP I used the command adb shell getprop and in the result noticed that there are references to OmniROM. The main one being [ro.modversion]: [OmniROM-6.0.1-20171209-hima-HOMEMADE]. I assume that someone has previously flashed OmniROM and this has caused the brick.
As far as I know HTC devices are not supported by OmniROM.
Does anyone know if the phone is recoverable from this condition?
Hi,
I have just discovered that I can hear no sound when I use my HTC M8 dual sim phone for phone calls (I don't use it for calls very often so it could have been like this for a while?).
It seems this is a common problem but I have not managed to find what the solution is so any advice would be very welcome.
I have resetting to factory defaults, clearing the cache, plugging headphones in and out, turned blue-tooth on then off but still the same.
I have LineageOS v15.1 on it with no Google apps but I have tried going back to v15.0 (it definitely used to work ok with this version) but no change.
btw - sound works ok with through the headphones or on speaker but nothing from the inbuilt ear piece speaker.
Adnl info:
I have installed some software which records phone conversations but this records silence which I think confirms my suspicion it is a software problem (if it were a faulty speaker this would still record the audio being sent to it)
I have also tried an app which sends all audio to the earpiece but still no sounds comes from it
Anyone got a solution to this?
It seems a very common problem so I am guessing there is a fix
I have ordered a replacement speaker but I am reluctant to fit it as it is a difficult task and I am pretty convinced it is a software problem but at the moment this is the only option I can think of before consigning this phone to land fill.......
Did you try going back to stock Sense to see if the issue persists? Did it work correctly (sound when on calls) when on stock ROM?
redpoint73 said:
Did you try going back to stock Sense to see if the issue persists? Did it work correctly (sound when on calls) when on stock ROM?
Click to expand...
Click to collapse
I did consider that but wasn't confident I knew how to do it and hoped someone somewhere would know a simple fix (with it seemingly being a very common problem).
This morning I gave it a try, but I proved myself right in that I failed - lol
When I try to install the stock foirmware (with the command "fastboot flash zip xxx.zip") after a few mins it returns the error "FAILED-remote: 32 header error".
alanes said:
When I try to install the stock foirmware (with the command "fastboot flash zip xxx.zip") after a few mins it returns the error "FAILED-remote: 32 header error".
Click to expand...
Click to collapse
Not enough detail to know what you did wrong here. Always give exact file names (and where you got it from); since the term "stock firmware" can literally mean dozens of different things, and we have no idea what you flashed if you are not specific.
Also, if it is an RUU, using the "generic" fastboot is likely not going to work (need htc_fastboot). But given the header error, I don't think you even have the right file for your device.
---------- Post added at 09:28 AM ---------- Previous post was at 09:20 AM ----------
Did you put Lineage on the device, or was it already on there when you got the phone? Since you never answered my question whether calls worked correctly when on stock ROM. Always do your best to answer all questions posed to you, if you want us to try to help.
If you flashed Lineage, you should know how to go back to the stock ROM. Best practice and a basic golden rule of modding phones (whether it be flashing custom ROMs, root, etc.): never do anything you don't know how to reverse. Always have an escape plan. You should know how to go back to stock, before doing any mods. If you don't know, ask. But waiting until there is a problem, to try figure out how to return to stock.
Did you make a TWRP backup before flashing Lineage? Again, another basic golden rule of phone modding: always make a nandroid (TWRP) backup of the stock ROM before root, custom ROM, etc.
Thanks for your replies. Sorry for not giving enough info., I think I am getting too frustrated with the whole thing....I could write a novel about the stress I have had with this phone.
I decided I wanted LineageOS but it was not available for the phone I had so after much research I decided the HTC M8 was the only phone supported with most of the features I wanted (especially dual sim) so I bought one and set about putting Lineage on it. Turned out to be much more difficult than the instructions suggested and I estimate I spent something like 200hrs on it before finally getting it working (with much help from this forum) - This included having to take the phone apart as it turned out a coax cable was missing for the GPS and then had to replace a button.
I finally had it all working and pretty pleased with it then suddenly after a month or so it stops working as a phone and so is now pretty much useless
When I had it all set up and updated with the HTC stock rom I did a TWRP backup but after installing Lineage I realised I had backed it up to the wrong place and so lost the backup
I took notes when I installed the stock rom and kept all the files (or so I though) so I had a backout plan but had never tested it and knowing the problems I had had always suspected I would have trouble if I tried it.
Calls always worked correctly with all the firmwares I have had on this phone, although I can't say for sure it ever worked when I upgraded to LineageOS v15.1 from 15.0
I thought I had seen this problem before but referring to my notes this was a different problem I had hanging up calls with LineageOS 14.
The RUU I used is the one I used when I first set up the phone:
0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F_release_428493_signed.zip
from https://easy-firmware.com/home/browse/category/id/7825/
I did not use the HTC Fastboot so this may well be the problem. I will give it a try and let you know...........
I don't think I used it originally but could be wrong.
Can you please do fastboot getvar all, and post the result (delete IMEI and serial number before posting)? I'd like to see more info about the phone.
To be clear, I don't have the dual SIM M8 (just the single SIM one). So my assistance may be limited. But some things are same/similar, so I'll try to help as much as I can.
Some comments below in red font:
alanes said:
This included having to take the phone apart as it turned out a coax cable was missing for the GPS and then had to replace a button.
I finally had it all working and pretty pleased with it then suddenly after a month or so it stops working as a phone and so is now pretty much useless
So the phone (earpiece sound) worked after you did the hardware repairs? But then stopped working about a month later? I'm suspicious of a hardware issue related to the repair. But flashing the stock RUU (if we can do it) will help determine whether it's a hardware or software problem.
When I had it all set up and updated with the HTC stock rom I did a TWRP backup but after installing Lineage I realised I had backed it up to the wrong place and so lost the backup
What does that mean "wrong place"? You backed up to internal storage, then wiped internal storage, thinking the backup was on SD card?
I did not use the HTC Fastboot so this may well be the problem. I will give it a try and let you know...........
I don't think I used it originally but could be wrong.
You definitely need to use htc_fastboot. The "generic" Google fastboot can't handle the large file size of an RUU. But in that case, it will usually give you an error message to that effect (file size too large); and not "header error". I have a feeling the error may have to do with the version number, but the getvar data will tell me more
Click to expand...
Click to collapse
redpoint73 said:
Can you please do fastboot getvar all, and post the result (delete IMEI and serial number before posting)? I'd like to see more info about the phone.
:
Click to expand...
Click to collapse
Yes, I thought I had backed up to SD card but was wrong
I have just discovered the microphone doesn't work either. I have software which records phone conversations but this now just records nothing, if it were a wire off the speaker or something I think this would still work.
I spent all this morning trying again but still getting the same error. I am wondering if it is because my phone was upgraded(via the HTC automatic updates) to version 6.16.401.101 and so now doesn't like going back to the older version?
Would it be a bad idea to try the file "0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.101_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465002_signed.zip"?
- although if this worked I guess it wont install the updates which is what I am hoping will get the phone working again as I keep reading that HTC released an update for what sounds like the problem I have.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.401.101
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxx
(bootloader) imei2: xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I spent all this morning trying again but still getting the same error. I am wondering if it is because my phone was upgraded(via the HTC automatic updates) to version 6.16.401.101 and so now doesn't like going back to the older version?
Click to expand...
Click to collapse
Since you have s-off, it should be okay to flash an older version; as long as it is the proper RUU for your CID and MID, which it appears to be. Unless HTC imposed some limitation on the M8s, that isn't present on M8 (meaning, at least on the M8, flashing older RUU is okay as long as you are s-off).
alanes said:
Would it be a bad idea to try the file "0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.101_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465002_signed.zip"?
- although if this worked I guess it wont install the updates which is what I am hoping will get the phone working again as I keep reading that HTC released an update for what sounds like the problem I have.
Click to expand...
Click to collapse
That should be the perfect RUU for you to flash, given the current main version you show in getvar. Verify it is a full RUU (>1 GB).
The RUU will include all partitions updated to version 6.16.401.101, including whatever was updated. And you should get any updates after that, if there are any. So I'm not sure what you are saying, that you don't think you will get updates.
Thanks, I will give it a try tomorrow (It won't let me download it as it says I have hit my daily limit for the site)
I was told when I first set up the phone that there are lots of partitions which I am not aware of which HTC updates will modify etc., which is why I had to do the official HTC updates to the latest version before I was able to install LineageOS (but I may well have misunderstood).
Gave it a try this morning but same error message as before
I even tried it on a different computer but no change
Just in case I am doing something wrong, what I do is:
First wipe all the partitions using TWRP (apart from sd card) then use htc-fastboot to try and send the RUU zip file
I have not removed TWRP although I did once try first uploading the HTC recovery file corresponding to the RUU version I was about to upload.
I have seen some instructions which say you have to re-lock the phone first but I don't think this is the case (I don't want to do this unless I have to as it is a pain to unlock again).
i.e. fastboot oem lock
Been experimenting with the phone and it turns out the other person can hear me but I can't hear them, but if I switch it to speaker phone then I can hear them but they can't hear me - lol
I guess this proves it is software related though.
--------------
Latest news: I have downloaded TWRP backups instead of using the RUU, this seems to be installing and I will let you know how it goes........
alanes said:
Gave it a try this morning but same error message as before
Just in case I am doing something wrong, what I do is:
First wipe all the partitions using TWRP (apart from sd card) then use htc-fastboot to try and send the RUU zip file
I have not removed TWRP although I did once try first uploading the HTC recovery file corresponding to the RUU version I was about to upload.
I have seen some instructions which say you have to re-lock the phone first but I don't think this is the case (I don't want to do this unless I have to as it is a pain to unlock again).
i.e. fastboot oem lock
Click to expand...
Click to collapse
Strange, I don't know what you are getting header error. Really, from what I can tell, either RUUs you tried should work.
No need to wipe anything in TWRP, nor install stock recovery, in order to RUU. But doing those things won't hurt anything, either (such as the header error).
Also, no need to relock the bootloader since you are s-off. Again, unless the dual SIM M8 has some difference from the "regular" single SIM M8. At least on the single SIM, I'm absolutely positive the RUU will flash with either bootloader locked/relocked or unlocked, as long as you are s-off.
Hi,
I spent much of today on it and managed using TWRP to install the stock HTC rom (6.16.401.101) and do the updates but still the same so tried 4.30.401.15 but still no joy.
Guess my only hope now is to try replacing the earpiece speaker but I still think it is software rather than hardware related.
I finally decided it is not a hardware problem so will consign this phone to the trash and I will give a Willeyfox phone a try, see if this works out any better (can't be much worse - lol)
I'm on the June security patch and I haven't been able to update anything OTA even though I have an AT&T SIM. Is there someway to force the Software Update check to work properly by using a pm command in the shell? Do I need to sideload the firmware to get it update to OREO and if so, what is the command and where can I find the full file. Any help would be useful.
please go here: https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/XT1789-04/
download the at&t rom for your device.
unzip into platformtools.
and run these commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
let me know if this helps you get back on track with being able to update from AT&T
i have used this in a bat script to install the AT&T rom on the tmobile hardware, then i was able to go back to stock once more and install updates.
Do these commands work on a locked bootloader which AT&T has? Does someone have a good understanding of how the following packages work regarding ota updates?
com.motorola.ccc.devicemanagement
com.motorola.ccc.checkin
com.motorola.ccc.mainplm
com.motorola.ccc.ota
com.motorola.ccc.notification
I was wondering if i could clear out the cache of one of them or disable then re-eanable one or more of them would that possibly fix my ota problems?
I am having the same issue, the phone is stuck on the June patch and no matter what I do I can't get any updates, nor will adb sideload or install update from zip in recovery work.
edit:
got it working, if you are still stuck on June security patch just download the AT&T update from the 2nd post above, put the phone into bootloader mode, and unzip the attached bat file in the folder then run it (ensure you have the Motorola drivers installed). as soon as I rebooted and set up I checked for updates and it started downloading the new 8.0.
DISCLAIMER: for AT&T Z2 Force models.... will wipe data.... this worked for me may not work for you... use at your own risk.... it's you not me.... this is your choice.
i did the same, now i have november update but i didnt get the oreo update afterwards.
Install the stock rom
Is there any way to flash the downloaded stock rom from post 2? No further OTA update
What do you mean will wipe data
Mrgabi said:
What do you mean will wipe data
Click to expand...
Click to collapse
It will wipe everything from your phone like a factory reset so make sure you have a backup of whatever you need to reinstall.
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next.
Thanks,
Click to expand...
Click to collapse
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
kingstu said:
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
Click to expand...
Click to collapse
OK well, I bought it on Swappa it was new (resale) so the box was opened but everything else wasn't and still had the plastic on it. So I contacted Motorola on their support forums and they said to just wait a little while and see if it'll update but too they also said they'd have someone take a look into it as they have my IMEI number so I guess will see what they say.
Thanks for the reply
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hello, Just checked and it says my warranty expires Sep 2018. So hopefully it shouldn't cost. Now though if I do return it I am assuming they'll just want the device nothing else and will they send me back a new device as this device is new no scratches or nothing and don't want to get back a device that has any marks or scuffs etc. Also, the first thing I did before even turning the device on was put on a tempered glass screen protector so I am assuming I'd take that off before I sent the device back to them. Either way, I hope I can get the issue fixed without having to return it but at least I know it's under warranty, Assuming that when it says Sep 2018 that once Sep 1st hits that the warranty will be expired?
Thanks again
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hey, I dropped my device off with FedEx on Sunday and Motorola said they received it yesterday, anyways just wondering how long your turnaround time. I have my Moto E4 that I can use so it's not the worst if I have to wait. Hopefully, it won't be too long especially if they're just going to send me a new device that should have Android oreo and updated security patches on it.
Thanks again for your advice.
Seems like it runs through script fine until the end
Script seems to run fine until the end. Phone wont boot and flashes at logo screen and then goes to bootloader logs saying your device didn't start up successfully. Need help. Can anyone help with this? I think the problem might be with the userdata not automatically formatting at the end. Nevermind, Everything all good after 3 or 4 tries. I still can't update to the latest build after flashing, which is OCXS27.109-47-11 according to what I looked @ att website. It says I have the latest version which is OCXS27.109-47-7. Anyone have the latest build to flash?
i had the same issue
I've used Lenovo Smart Moto Assistant and managed to get the last update
I have the same issue with T mobile. the phone says there is a new update, it downloads and tries to install but fails. I am on the May 2018 security patch, OCXS27.1.3. Android File Host and other sites don't list any new firmware. I have tried the Lenovo Smart Moto Assistant and it also doesn't recognize the new update. Any suggestions?
Oreo Update
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
Click to expand...
Click to collapse
westec2 said:
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
Click to expand...
Click to collapse
Hello.
I don't know if i did not understand correctly, but when I have the phone recognized to do the update, i turn it off, and since the PC stops recognizing it is connected, the lenovo smart assistant goes back to the sync page.
How could you achieve that? Do you have another setting on your PC or lenovo assistant software?
Do you turn it off before clicking proceed?
Do you turn it off while the "all information could be wiped" is on screen?
Do you turn it off when the "loading bar" starts?
Could you be more specific? I would like to update my phone.
Thank you.
While I saw this problem on several other devices (this thread, for example), I haven't seen a post about this problem on this device on XDA, hence starting a new thread. My problem is that I stop receiving notifications from apps that rely on Internet connection. Below are the details:
After 10 minutes of turning off the the phone screen (my device is set to immediately lock after screen turning off), I stop receiving notifications from Messenger, WhatsApp, Gmail and so on. This happens only when the phone is connected to WiFi and NOT charging. On cellular data, notifications arrive timely, as is the case with WiFi when the phone is charging. I discovered this "solution" after months of missing important calls and messages.
The phone came with Android 4.4 Sense, which I didn't use for more than a few days, hence can't really confirm if the problem was present there (it most likely wasn't; those few days I did get timely notifications, as far as I remember). I switched to LineageOS 14.1, Android 7.1.2, and noticed this problem for the first time. After quite some time of thinking it's a bug in LineageOS, I converted the device to GPE, installed stock Android 6.0 (the last version of Android shipped by Google for this device), only to see the problem was worse there. At least in LineageOS 14.1 notifications would stop after 10 minutes. In GPE Marshmallow, it would stop after 2-4 minutes, and the problem persisted even while charging. Now I'm using LineageOS 15.1 from this thread. Notifications STILL stop arriving timely when not charging and connected to WiFi.
To make it clear, I tried pretty much everything suggested by people for similar problems in other devices. I have battery optimization turned off for EVERY app on the list (this DOES seem to be a power management issue, since while charging, notifications work fine). WiFi was set to be active "Always" in Android 6.0 and 7.1.2 (didn't find that option on LineageOS 15.1/Android 8.1). Made unrestricted data access available for all apps. Battery is set to "Performance". All apps allowed to notify. Installed "WiFi Keep Alive" kind of apps. No use!
Yes, every ROM installation was "clean". Yes, the device firmware is the latest one shipped by Google (from here). The device is S-OFF. I only have Google Apps installed, never rooted it. This making me go nuts. If anyone can provide me with a solution, I'll be grateful beyond words.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
You sure youconverted to GPE using the RUU, and not just flashing the ROM in TWRP?
redpoint73 said:
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
You sure youconverted to GPE using the RUU, and not just flashing the ROM in TWRP?
Click to expand...
Click to collapse
Thank you for your reply. Here's the output of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
And yes, I am sure. First I flashed the firmware, then the RUU. It wiped everything on my phone, and the date on the bootloader changed to Jul 20 2016.
i have exactly the same problem but its only with 7.x.x ROMs, in 6 it works fine, i test using WhatsApp web and as soon as the screen goes off it will work for a minute or 2 then say phone not connected, its like it kills all data connection once the screen goes off, i will add it ONLY does it when on wifi and not charging if i turn wifi off it works fine with screen off, i think i did cure it for a while by messing with the WCNSS_qcom_cfg.ini file in the data folder but it caused a huge battery drain.
JaffaTB said:
i have exactly the same problem but its only with 7.x.x ROMs, in 6 it works fine, i test using WhatsApp web and as soon as the screen goes off it will work for a minute or 2 then say phone not connected, its like it kills all data connection once the screen goes off, i will add it ONLY does it when on wifi and not charging if i turn wifi off it works fine with screen off, i think i did cure it for a while by messing with the WCNSS_qcom_cfg.ini file in the data folder but it caused a huge battery drain.
Click to expand...
Click to collapse
That's exactly the kind of thing I was looking for--if the settings can be applied in a config file to keep the WiFi always active. Can you please tell me which options need to be tweaked to achieve this?
zurjskj said:
That's exactly the kind of thing I was looking for--if the settings can be applied in a config file to keep the WiFi always active. Can you please tell me which options need to be tweaked to achieve this?
Click to expand...
Click to collapse
Im not sure if it did cure it 100% but this was what i did:
1. Open the file WCNSS_qcom_cfg.ini in text editor.
2. Change the line gEnableBmps = 1 to gEnableBmps = 0
3. Save and reboot
dont know what this setting does but i found it on another forum that fixed it on a different phone.
Edit: also found this which may also work, i would try this if the top one doesnt, then try both together if neither work alone
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=0"
Save the file and double check file permissions (-rw-r--r-- root root)
Reboot the phone
your config file might be in a different location, i'm on Oreo and mine was in /data/misc/wifi
"McastBcastFilter=0" setting seems to have worked for me, i havent messed with the "gEnableBmps=" setting this time as last time it drained my battery, only a day or so with this new setting changed will tell if this is the same or not, but whatsapp web still connected after 30~ mins
JaffaTB said:
Im not sure if it did cure it 100% but this was what i did:
1. Open the file WCNSS_qcom_cfg.ini in text editor.
2. Change the line gEnableBmps = 1 to gEnableBmps = 0
3. Save and reboot
dont know what this setting does but i found it on another forum that fixed it on a different phone.
Edit: also found this which may also work, i would try this if the top one doesnt, then try both together if neither work alone
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=0"
Save the file and double check file permissions (-rw-r--r-- root root)
Reboot the phone
your config file might be in a different location, i'm on Oreo and mine was in /data/misc/wifi
Click to expand...
Click to collapse
JaffaTB said:
"McastBcastFilter=0" setting seems to have worked for me, i havent messed with the "gEnableBmps=" setting this time as last time it drained my battery, only a day or so with this new setting changed will tell if this is the same or not, but whatsapp web still connected after 30~ mins
Click to expand...
Click to collapse
That, sir, is pure gold. Also, I couldn't have done it without your elaborate instructions. This problem has bugged me SO much that I couldn't at first believe it was working. But tested with WhatsApp Web for about 40 minutes. It was connected! I changed McastBcastFilter value to 0, and didn't touch gEnableBmps, like you suggested. However, I did make one additional change. I saw here that the option "isAndroidPsEn" is set to 0, i.e. it was disabled. It was said when this option is disabled, the driver controls power saving mechanism on its own, separate from Android's power saving. This, however, was set to 1 (enabled) on my file. It seemed reasonable to change it. I know, like you said, it takes a day or two to realise if the solution really worked, but I am going to mark this post solved nonetheless.
Thank you SO much!
Glad I could help, it too has bugged me ever since ive used a 7.x.x ROM, I had given up trying to fix it but your post gave me renewed spirit to try and fix it, also the second option you mentioned was also enabled on mine but I left it as it and battery usage seems normal up to now.
JaffaTB said:
Glad I could help, it too has bugged me ever since ive used a 7.x.x ROM, I had given up trying to fix it but your post gave me renewed spirit to try and fix it, also the second option you mentioned was also enabled on mine but I left it as it and battery usage seems normal up to now.
Click to expand...
Click to collapse
So far, battery usage is quite normal on my end. By the way, I really feel these things should be better documented by AOSP/Google. Quite a lot of people seem to suffer from this issue. People blame battery optimization, bugs in push notification... whatnot.
Same here too, it looks like we have finally cured it I know what you mean about it affecting loads of other I tried all sorts to cure it but to no avail.
JaffaTB said:
Same here too, it looks like we have finally cured it I know what you mean about it affecting loads of other I tried all sorts to cure it but to no avail.
Click to expand...
Click to collapse
Yes! Again, thank you! By the way, I have one question. Will the WCNSS_qcom_cfg.ini file be overwritten with LineageOS OTA upgrades? I'm currently using the official 14.1 branch.
Unsure but i wouldnt think so as i doubt that would have to be updated? if it does you can always change back the options (or make the file read only but i dont know if that would mess anything up?)
JaffaTB said:
Unsure but i wouldnt think so as i doubt that would have to be updated? if it does you can always change back the options (or make the file read only but i dont know if that would mess anything up?)
Click to expand...
Click to collapse
Yeah, I thought updates shouldn't affect it, but just wanted to be sure. I'll check after next week's update and post here. Also, I submitted a bug report on LineageOS, now only hoping they'd permanently fix it. After Google stopped supporting this device, LineageOS is the only thing that I can rely on for updates. Besides, this OS runs just too smooth.
well i ended up flashing a different ROM last night as i always get bored and like a change and the first thing i did was change the "McastBcastFilter=0" and nothing else, it 100% fixes it
JaffaTB said:
well i ended up flashing a different ROM last night as i always get bored and like a change and the first thing i did was change the "McastBcastFilter=0" and nothing else, it 100% fixes it
Click to expand...
Click to collapse
Hope you're enjoying your new ROM! I myself will shift to Android 8.1. And that McastBcastFilter really is the trick By the way, OTA updates DO overwrite the file. Also, my bug report in LineageOS has been rejected, on the basis of not being able to be reproduced. The developer also said that they won't disable multicast and broadcast filtering. This is overall a VERY strange issue. I don't think a lot of people with HTC One M8 other than you and I suffer from this problem. Also, at my home other devices work just fine without disabling this option, so it's not a router issue, either. I did some more digging and saw that mcast and bcast filtering CAN cause WiFi to drop. It just doesn't happen all the time. It's all very strange, really... Anyway, as long we keep using this device, we just have to keep setting "McastBcastFilter=0". Again, really thank you for your help.
Hi, i'm a user from France.
After installing the last Android version proposed by Mi on the 7th of June 2019 my phone is now stucked on the black screen with the red mention " this miui version can't be installed on this device " - I made the choice to wipe all the data - after restarting nothing changed and I'm stucked to the same black screen.
First big loss. I didn't do any thing solo, I've just being installing the official update proposed by the company like I always do when notification comes. I don't do extra stuff that I have no knowledge about, I'm a regular user.
Now I'm trying to wipe the data through my computer using XiaomiFlash, however I'm getting this error alert : Flash antirbpass error.
What does it mean ? I have read about Google protection briefly on the internet but now it's getting really complicated for me to swim in these waters,
none of the solution worked for me, from the ADB thing to the CMD thing - I also downloaded a "dummy" file which I don't know how to use. After installing ADB I don't get any file of that name in my ":c" repertory and when typing the command "fastboot etc" in CMD it says that it's not recognized. I don't know what I'm doing and I don't know what to do, I don't have a car to get to the nearest phone repair shop and it's like i'm in an alien world with all the technical vocabulary in front of me when search the solution online.
All help would be really appreciated for an ignorant beginner like me.
1.Connect phone to PC, backup important data.
2.Reboot phone to bootloader(fastboot,Power+Volume Down).
Goto PC CMD
fastboot flash antirbpass dummy.img
fastboot flash recovery twrp-3.3.1-0-whyred.img
3.Reboot to TWRP (Power+Volume UP).
Wipe DalvikCache, Cache, Data, Internalstorage, System, Vendor.
Install miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0.zip.
Wipe Cache, Data and do Factory reset.
4.Reboot to system.
Just try abovementioned steps, good luck!
Thanks garyemail for your help.
I'm halfway done with this problem, but another thing came on the way which is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-0-whyred.img
target reported max download size of 536870912 bytes
sending 'recovery' (38924 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.942s
Apparently my phone is locked after being checked :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.014s
I know there is no way for unlocking it through "official" method by using whatever Xiaomi is throwing away, do you have a particular way to get that unlocked ?
I know Xiaomi and Google would scream out of hysteria by reading this post but I'm not trying to unlock my phone for the pure sake of adrenaline.
They putted out that Android Update, not me. It didn't work. Rather it blocked my phone.
Now that the only way to solve the problem is to unlock the phone, what do you know, they decide to put a lock on the phone that basically doesn't allow the user to officially and directly restore the phone.
What is wrong with these people ? Are we just supposed to throw the phone away and buy a new one whenever they are making an uncorrect move resulting in a broken phone ?
I learned now what I'm paying when adding a high price difference for an iPhone, I'm paying for avoiding all that torture which Google and Xiaomi together are dragging me into.
Buy a 1€ phone and spend 1000€ worth of time in searching the remedee in case of a problem. -> Android logic -> money saved at first look, whatever happen you are entirely on your own. A small rock hiding a mountain.
Buy a 1000€ phone and spend 1€ worth of time in searching for the remedee to the sickness. -> Apple logic -> expensive at first look, but client satisfaction guaranteed - time and energy saved.
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Wiguna77 said:
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Click to expand...
Click to collapse
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
RebornSAGA said:
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
Click to expand...
Click to collapse
There is no "non-xiaomi way" you have to flash the chinese official rom with miflash and then unlock your phone, thats the only way.
btw you can try the "EDL-Method".
Thanks Gerr1 and thanks anyone else who helped. Really appreciated.
[How To] Unlock Bootloader on Your Redmi Note 5 Pro
Try abovementioned link!...
First unlock your phone bootloader, then do the #2 setps again!...
Hi
Whenever, Irey to turn on the device, it freezes in the mi logo and can only access the FASTBOOOT. I tried to flash the device but ut says "Flashing is not allowed in Locking State" Also, I treid unnlocking the phone through the mi Unlock software but once it says "You've exceeded the number of verification attempts allowed within 24 hours" and I can login twice in a day to that aoftware it seems. Also, I tried to unblock the device through CMD but it says failed. Please Help. Its hard to work without a phone
Please help