Hi to everyone
i have htc one m8 eye(MELS_TUHL)
i need a stock firmware or (recovery custom with Custom firmware) to find a way to bootup the phone (now phone on the htc logo and did not wipe with original recovery...)
please give me a link to download the firmware that similar os version as below
C:\adb-fastboot>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.29.213311711.15G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.35.401.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA54PY900289
INFOimei: 358703060038798
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: mels_tuhl
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B81000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 719237f7
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Thank You in Advance
is there anyone to help me?
Sent from my iPhone using Tapatalk
Not many people have your device version on XDA.
Is the bootloader unlocked ? If yes, I can suggest something
Need HTC One m8 eye(MELS_TUHL) Stock firmware or (Custom recovery with Custom...
yes
bootloader is unlocked
Sent from my iPhone using Tapatalk
I assume you still have TWRP recovery that meant for your device version.
What you can do is restore an older version then do OTA to the latest
Install TWRP
Restore 1.82.401.7 backup
Install 1.82.401.7 stock recovery
Reboot then do OTA up to 4.35.401.3
You can get 1.82.401.7 backup & recovery in my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
tanx bro
Sent from my iPhone using Tapatalk
Need HTC One m8 eye(MELS_TUHL) Stock firmware or (Custom recovery with Custom...
tanx for your help
but i have a problem with entering to the twrp
after flashing twrp with any version when i want to enter the recovery mode it takes me to the fastboot mode and doesn't go the recovery mode
thay may not belong to this htc one m8 eye
please kindly give me the right link for this model
thank you in advance
Sent from my iPhone using Tapatalk
Try this : http://forum.xda-developers.com/showpost.php?p=62973038&postcount=211
In his link there is TWRP recovery named as recovery m8eye.img
You need to rename that to only twrp.img or recovery.img
download twrp from https://drive.google.com/file/d/0B3w...ew?usp=sharing
install it via fastboot [fastboot flash recovery twrp-m8eye-2.8.0.3 (1).img] use the command inside the bracket, download this backup from http://1drv.ms/1WkbudN now for the back to work well i suggest that you create a backup of your cache on your sd card so that you can have the correct directories to copy the backup to, usually its TWRP/BACKUPS/YOUR SERIAL NUMBER/BACKUP FILES, if you wish to root flash supersu zip from chainfire,
MuminMohamed said:
download twrp from https://drive.google.com/file/d/0B3w...ew?usp=sharing
install it via fastboot [fastboot flash recovery twrp-m8eye-2.8.0.3 (1).img] use the command inside the bracket, download this backup from http://1drv.ms/1WkbudN now for the back to work well i suggest that you create a backup of your cache on your sd card so that you can have the correct directories to copy the backup to, usually its TWRP/BACKUPS/YOUR SERIAL NUMBER/BACKUP FILES, if you wish to root flash supersu zip from chainfire,
Click to expand...
Click to collapse
That backup that you linked is for India version - 1.80.720.1 I guess.
This won't work for him
ckpv5 said:
That backup that you linked is for India version - 1.80.720.1 I guess.
This won't work for him
Click to expand...
Click to collapse
but he can change his mid and cid
MuminMohamed said:
but he can change his mid and cid
Click to expand...
Click to collapse
How to do that on S-On device ?
Are you going to give him USD25 to s-off the device ?
Why do you want to spend USD25 when you can fix it for free with the correct files ?
Stock ROM for M8 Eye
https://drive{dot}google.com/file/d/0B-JhHhqeg46jZm9DYU5rMGVnRTg/view?usp=sharing
CrazyRyanCooper said:
https://drive{dot}google.com/file/d/0B-JhHhqeg46jZm9DYU5rMGVnRTg/view?usp=sharing
Click to expand...
Click to collapse
can u tell us which version is this
and always write full info
A_1st said:
can u tell us which version is this
and always write full info
Click to expand...
Click to collapse
Its' Lollypop...
internal storage problem
ckpv5 said:
How to do that on S-On device ?
Are you going to give him USD25 to s-off the device ?
Why do you want to spend USD25 when you can fix it for free with the correct files ?
Click to expand...
Click to collapse
hello, help plzz
After restoring from marshmallow backup , my internal storage is not showing files & folders, I can`t copy files in my internal storage just can install app , how to fix it ??????
mrd44 said:
hello, help plzz
After restoring from marshmallow backup , my internal storage is not showing files & folders, I can`t copy files in my internal storage just can install app , how to fix it ??????
Click to expand...
Click to collapse
I am also facing same problem in my htc one m8 eye, can any one help us on this ? : (
Saved my Life!!
Thanks a lot
CrazyRyanCooper said:
https://drive{dot}google.com/file/d/0B-JhHhqeg46jZm9DYU5rMGVnRTg/view?usp=sharing
Click to expand...
Click to collapse
Hi there,
How can i get htc m8 eye marshmallow stock rom or lineage OS 14 for htc m8 eye. I have tried to install htc m8 lineage rom via TWRP but its not working in m8 eye as both are different phone.
Plzz assist.
Htc One M8 Eye firmware
Htc One M8 Eye firmware
Model : MELS_TUHL
IMEI : 355991060321032
Build : 5.07.720.1
CID : HTC__038
HBoot : 3.19.0.0000
MID : 0P6B90000
Security : ON
Region : ASIA_INDIA
Plxxxx Provide me This flash File
My HTC One M8 got stuck on bootload shortly after I asked O2 to unlock it. The bootload said ***software status: modified***
After a lot of research, I came accross a tutorial to fix a soft bricked device via TWRP and managed to flash a new ROM on it. I choose Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9)/ stock HTC system dump that I found on android-revolution HD website and everything went very smoothly.
So my M8 is now starting and working fine, BUT doesn't read sim cards. It doesn't tell me whether a sim card is inserted, and if I put my Vodafone Malta sim card in, nothing happens, no error of reading, nothing. (if was working fine after the unlock code was put in).
I also noticed that HTC SDK API level now says unknown. And under mobile data>Network mode where I don't see 4G anymore.
I've received OTA update but can't install them. I get the "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www . htc . com".
I thought that maybe installing a new ROM would be the solution and tried various RUU to no avail (159 error). I also tried using fastboot to flash 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
But it failed with 42 Wrong Customer ID (wrong CID).
I tried to amend android-info.txt but 1/windows won't open the zip (I am on Windows 7) - 2/ 7zip will but won't let me copy or edit the file (unsupported compression method error).
I am very much a newbie and I am not very keen on going S-Off as yet and would like to have opinions on what my next move could be, staying S-On.
My main concern isn't the updates but the non reading of my sim card. That's the main thing I'd like to resolve (and I thought that flashing a new ROM could be the solution - correct me if I am wrong!)
here is a reading of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any advice!
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
ckpv5 said:
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
Click to expand...
Click to collapse
Hi ckpv5,
Thanks for your advice, really appreciate it.
Definitely sure about the phone being SIM unlocked as the Vodafone Malta SIM card worked for a while until everything went pear shaped and the phone stopped booting.
I'll try both and will let you know how it went.
ckpv5 said:
Remove serial & imei no. on your post.
Restore 6.13.206.5 nandroid backup, the correct version for your firmware (get it from my backup thread linked in my signature)
Or install any Marshmallow custom ROM available in Development section.
See whether any of these suggestions will fix your problem.
You're very sure your branded device is now SIM unlocked, right ?
Click to expand...
Click to collapse
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
No imei no baseband
JenovaXIII said:
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
Click to expand...
Click to collapse
I have got the same problem. On my One M8 it reads unknown imei unknown baseband. But when I type "fastboot getvar all" everything seems OK. This might be due to corrupted EFS or other partitions I think. I've found an article written by mike1986. (Android Revolution HD developer) about how to fix a corrupted DATA partition on the HTC One[/URL] but couldn't still find chance to restore/recreate/fix partitions. I send the device to a private service in Istanbul and they called me and told me that my phone requires a new motherboard. The device is running well but it can't detect the simcards. Actually it was, but in Turkey our network operators managed to give 4.5G service or (LTE?) and when I changed my simcard to 4.5G simcard itwas unable to detect it. I thought it was due to radio/cid/mid problem and I changed them all. Afterwards It couldn't detect any simcards. No imei no baseband.
Anybody willing to help these poor are appriciated. Thanks.
JenovaXIII said:
Hello,
I eventually came across flashing a new Marshmallow ROM on my device, but unfortunately it's the same as before. The phone doesn't read or acknowledges sim cards.
Any more ideas ?
Click to expand...
Click to collapse
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
ckpv5 said:
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
Click to expand...
Click to collapse
I am going through your tutorial on how to restore nandroid backup and am a bit confused:
once restored, I need to proceed to steps 11 - 12 - 13 (flash the recovery img) ?
Then relock bootloader, then flash 6.13.206.5 signed firmware.zip using adb and fastboot ?
Sorry I just want to make sure I'm not doing something stupid!
ckpv5 said:
After restore 6.13.206.5 nandroid backup, relock bootloader then flash 6.13.206.5 signed firmware.zip
I read many posts that mentioned flashing firmware.zip fixed this kind of problem.
Click to expand...
Click to collapse
And it did! After following your tutorial, I re-locked the bootloader, and flashed the signed firmware.zip.
My M8 is now recognising sim cards and my vodafone Malta one is read no problem. So glad to have my phone back.
Thank you ckpv5!
Hi,
My personal phone is a Moto G5s Plus, European dual sim version (model "sanders XT1805", retail, unbranded, not from a network) with the latest version of Android available (I think it's 8.0 or 8.1, but not sure). It has rebooted today on its own while being used, and is now stuck in a boot loop. I am trying to either fix the boot loop, or recover personal data from the device (possibly destructively, but I would like to prevent that).
Here are things I have tried:
- I have checked that it's not the contact on the power button stuck in the on position that creates the boot loop. I have experienced this with a previous phone. Cleaning the contact with IPA and engaging it a few times helped this issue.
- I have tried entering recovery mode and formatting the cache partition. This hasn't helped.
I am a developer, but I don't know that much about Android devices. This phone has the stock boot loader and OS image. Is it possible to hook it up via adb, and possibly browse the file system or do something else to debug and fix the boot loop?
The device does boot into recovery mode. Recovery mode contains options for applying an update from an SD card, and via ADB via sideloading. Could this be used to fix this situation somehow?
The battery in this device is somewhat bad. Sometimes it would turn off when on battery power, and not hooked up to a charger, if the battery was on 30%, and recently it did once when it was on 60%. The battery is a 3.8V Motorola HG30. Could it be that the battery is shot, and when the device boots up, after a few seconds of boot time the SoC requests higher current, and then the battery cannot deliver the required voltage, and the device browns out and resets? I tried booting with a charger hooked up (which also supports QC 3.0) but that didn't help.
The boot loader also has the following two options: "BP Tools" and "QCom" but I don't know what they do. Both of them reboot the device, it sits in the boot screen for a longer time and then enters the boot loop again. There is also an option in the boot loader for turning on "tool mode" which sounds like it might be a way of enabling some form of debug tools.
The device contains important personal information that I need to recover. I am very good with micro-soldering (I can solder 01005 without magnification), and I have the right fluxes and ball kits, although at the moment I don't have a hot air station but could possibly get one. In case such physical access could help in rooting this device, how would I do this?
Finally, I am aware that the emmc chip can be read by a Beaglebone Black, but I'm hoping it will not come to that. If I do that, will the file system be encrypted in some way?
I would appreciate any suggestions.
Thanks
One thing... this is my first post here, so if I posted this in the wrong forum, or did something wrong, please let me know! I would like to do things adhering to the rules of this forum. Thank you!
One thing I have tried since is to try to hook up the device via adb, but it only allows sideloading, and it doesn't open a tcp port, so debugging isn't possible.
Researching the issue - Moto G5S Plus boot loop
I thought I'd post what I learn from the forum here and from other places... information that might be relevant to figuring out this issue, plus questions I have regarding those options:
I have tried to let the device discharge completely (I left it running in the boot loop), then I charged it up to 100%, but that did not help.
If your Moto will not boot, and your PC shows it as Qualcomm HS-USB QDLoader 9008 or Qualcomm QHSUSB_Bulk - but if I go into FastBoot mode (by holding power and volume down), and connect via USB, then the device does not show up in Windows 10 at all. If I tell FastBoot to go to Recovery Mode and in there select to download update via ADB, Windows 10 finds the phone and it shows up in the Device Manager under "Universal Serial Bus devices" as "Moto G (5S) Plus". Inside Properties for that item, the "Device description" field says "ADB Device". However, my PC doesn't have fastboot installed, or the Motorola drivers.
Motorola Drivers
How to back up mmcblk0 using terminal - I would like to do that, however I cannot boot the device at all into something that shows a terminal. Also the device is not rooted. Is it possible to boot from SD Card to be able to do this?
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD Card - ArykSTORE - this allows to boot the device from SD card. I am not sure if it will let me boot my device without first unlocking the bootloader. However, the SD card created in this image puts the phone into download mode and I wouldn't like to do that. If the SD Card image boots up, and is able to enter download mode, then I assume it can access mmcblk0. Can I create an image that I can use to run dd in order to image mmcblk0 onto the file system of the SD card? (phone is 32 GB, SD card is 64 GB, so there should be space).
Use Lenovo Motorola Smart Assistant and Skip Data Wipe - this is said to not always work. I am scared to flash the device (even if it says it won't wipe) before I back up mmcblk0. From the post: "Note: This is not guaranteed to work"
[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot - describes how to clear the misc partition using TRWP - is the misc partition different from the cache partition? Could this help with the boot loop? Note that my recovery mode has no option to "boot normally". Fastboot has an option called "START", but using that just enters the boot loop again.
Hacking Hardware With A $10 SD Card Reader (pdf) - worst case scenario, I could try and modify the hardware to use this method of recovering data from eMMC. It uses an SD Card Reader or a BeagleBone Black (use BBB if you also want to read the mmcblkXbootY partitions. Not sure if that's necessary). One of the things I'd like to recover is URLs of tabs open in Google Chrome. Will they be on a boot partition, or the "normal" partitions available via SD Card interface?
Laptop eMMC Data Recovery on a Budget - Andy's Boring Job - shows how to recover data off an eMMC chip. It recommends using a board view (.brd) file to search for signal hook up points. Does anyone have a board view file for the Moto G5S Plus model XT1805?
Stuff I've read that didn't give me any new ideas on how to fix my issue:
Guide: Flashing Motorola Firmware
Using Mfastboot.exe to Flash a Motorola device
[GUIDE][FAQ][KK] How to Root, Boot Unlock & More
RSD Lite
How to use RSD Lite
[Guide]Un/locking Motorola Bootloader - this describes how to get a bootloader unlock code from Motorola via the Official Motorola Bootloader Unlocker Site
Btw if you read this sd_shadow thanks a lot for all the guides. You're a real hero :good::good::good:
@sd_shadow in one of your threads you mentioned one could ping you with issues with debricking Moto devices, so I was wondering if you'd be kind enough to chime in? I'm trying to recover data from this (stock) G5S Plus, and then debrick it. Thanks.
cheater00 said:
@sd_shadow in one of your threads you mentioned one could ping you with issues with debricking Moto devices, so I was wondering if you'd be kind enough to chime in? I'm trying to recover data from this (stock) G5S Plus, and then debrick it. Thanks.
Click to expand...
Click to collapse
Trying to backup data from a locked bootloader device with out usb debugging enabled, is next to impossible, if device will not boot.
Very possible that the battery has failed.
Have you tried a different charger and usb cable?
While it's in fastboot/bootloader mode, connect wall charger and select power off in fastboot options
Does it show charging screen?
sd_shadow said:
Trying to backup data from a locked bootloader device with out usb debugging enabled, is next to impossible, if device will not boot.
Very possible that the battery has failed.
Have you tried a different charger and usb cable?
While it's in fastboot/bootloader mode, connect wall charger and select power off in fastboot options
Does it show charging screen?
Click to expand...
Click to collapse
Thanks for your quick reply. Yes, charging screen is visible. I have been able to charge up to 100%. I have bought a new usb cable from a very good brand and tried several chargers, but all of them do charge the phone, and the phone does recognize QuickCharge 3.0.
cheater00 said:
Hi,
My personal phone is a Moto G5s Plus, European dual sim version (model "sanders XT1805", retail, unbranded, not from a network) with the latest version of Android available (I think it's 8.0 or 8.1, but not sure). It has rebooted today on its own while being used, and is now stuck in a boot loop. I am trying to either fix the boot loop, or recover personal data from the device (possibly destructively, but I would like to prevent that).
Here are things I have tried:
- I have checked that it's not the contact on the power button stuck in the on position that creates the boot loop. I have experienced this with a previous phone. Cleaning the contact with IPA and engaging it a few times helped this issue.
- I have tried entering recovery mode and formatting the cache partition. This hasn't helped.
I am a developer, but I don't know that much about Android devices. This phone has the stock boot loader and OS image. Is it possible to hook it up via adb, and possibly browse the file system or do something else to debug and fix the boot loop?
The device does boot into recovery mode. Recovery mode contains options for applying an update from an SD card, and via ADB via sideloading. Could this be used to fix this situation somehow?
Click to expand...
Click to collapse
I don't think so, Moto updates only update, they don't work for same version they would install.
There would have to be an update for your current version, then you need a copy of it.
Same Model and software channel.
The battery in this device is somewhat bad. Sometimes it would turn off when on battery power, and not hooked up to a charger, if the battery was on 30%, and recently it did once when it was on 60%. The battery is a 3.8V Motorola HG30. Could it be that the battery is shot, and when the device boots up, after a few seconds of boot time the SoC requests higher current, and then the battery cannot deliver the required voltage, and the device browns out and resets? I tried booting with a charger hooked up (which also supports QC 3.0) but that didn't help.
The boot loader also has the following two options: "BP Tools" and "QCom" but I don't know what they do. Both of them reboot the device, it sits in the boot screen for a longer time and then enters the boot loop again. There is also an option in the boot loader for turning on "tool mode" which sounds like it might be a way of enabling some form of debug tools.
Click to expand...
Click to collapse
There is no way to use those modes that I know of.
The device contains important personal information that I need to recover. I am very good with micro-soldering (I can solder 01005 without magnification), and I have the right fluxes and ball kits, although at the moment I don't have a hot air station but could possibly get one. In case such physical access could help in rooting this device, how would I do this?
Click to expand...
Click to collapse
I haven't heard of any modern Motorola devices being rooted with a Locked Bootloader.
Finally, I am aware that the emmc chip can be read by a Beaglebone Black, but I'm hoping it will not come to that. If I do that, will the file system be encrypted in some way?
Click to expand...
Click to collapse
I have no idea.
---------- Post added at 07:04 PM ---------- Previous post was at 06:23 PM ----------
cheater00 said:
I thought I'd post what I learn from the forum here and from other places... information that might be relevant to figuring out this issue, plus questions I have regarding those options:
I have tried to let the device discharge completely (I left it running in the boot loop), then I charged it up to 100%, but that did not help.
If your Moto will not boot, and your PC shows it as Qualcomm HS-USB QDLoader 9008 or Qualcomm QHSUSB_Bulk - but if I go into FastBoot mode (by holding power and volume down), and connect via USB, then the device does not show up in Windows 10 at all. If I tell FastBoot to go to Recovery Mode and in there select to download update via ADB, Windows 10 finds the phone and it shows up in the Device Manager under "Universal Serial Bus devices" as "Moto G (5S) Plus". Inside Properties for that item, the "Device description" field says "ADB Device". However, my PC doesn't have fastboot installed, or the Motorola drivers.
Click to expand...
Click to collapse
If it boots to fastboot mode it is not in EDL mode.
Motorola Drivers
How to back up mmcblk0 using terminal - I would like to do that, however I cannot boot the device at all into something that shows a terminal. Also the device is not rooted. Is it possible to boot from SD Card to be able to do this?
Click to expand...
Click to collapse
Terminal is an app you would install, the whole backup process requires the device can boot normally.
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD Card - ArykSTORE - this allows to boot the device from SD card. I am not sure if it will let me boot my device without first unlocking the bootloader. However, the SD card created in this image puts the phone into download mode and I wouldn't like to do that. If the SD Card image boots up, and is able to enter download mode, then I assume it can access mmcblk0. Can I create an image that I can use to run dd in order to image mmcblk0 onto the file system of the SD card? (phone is 32 GB, SD card is 64 GB, so there should be space).
Click to expand...
Click to collapse
As the device cannot boot normally, someone else with same model would have to create an loader.img
Flashing a full mmcblk0.img would likely overwrite userdata.
Normally after flashing a loader.img, flashing stock firmware is necessary before the device will boot normally.
Use Lenovo Motorola Smart Assistant and Skip Data Wipe - this is said to not always work. I am scared to flash the device (even if it says it won't wipe) before I back up mmcblk0. From the post: "Note: This is not guaranteed to work"
Click to expand...
Click to collapse
I believe this method only works with an unlocked bootloader, I haven't had time to thoroughly tests method.
[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot - describes how to clear the misc partition using TRWP - is the misc partition different from the cache partition? Could this help with the boot loop? Note that my recovery mode has no option to "boot normally". Fastboot has an option called "START", but using that just enters the boot loop again.
Click to expand...
Click to collapse
Most moto devices no longer have a real cache, to was removed with the a/b system partition change from a single system partition.
Misc is used by recovery.
Hacking Hardware With A $10 SD Card Reader (pdf) - worst case scenario, I could try and modify the hardware to use this method of recovering data from eMMC. It uses an SD Card Reader or a BeagleBone Black (use BBB if you also want to read the mmcblkXbootY partitions. Not sure if that's necessary). One of the things I'd like to recover is URLs of tabs open in Google Chrome. Will they be on a boot partition, or the "normal" partitions available via SD Card interface?
Click to expand...
Click to collapse
If you were signed in to a google account, browser history maybe synced. Depending on which browser was being used.
Laptop eMMC Data Recovery on a Budget - Andy's Boring Job - shows how to recover data off an eMMC chip. It recommends using a board view (.brd) file to search for signal hook up points. Does anyone have a board view file for the Moto G5S Plus model XT1805?
Stuff I've read that didn't give me any new ideas on how to fix my issue:
Guide: Flashing Motorola Firmware
Using Mfastboot.exe to Flash a Motorola device
[GUIDE][FAQ][KK] How to Root, Boot Unlock & More
RSD Lite
How to use RSD Lite
Click to expand...
Click to collapse
If you have a Windows pc that originally did not have 10 (7 or XP). You can flash firmware without wiping data.
RSD Lite is your best option.
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
Thanks a lot for the reply. I have fastboot.exe from the Android SDK.
Do I need to have the Motorola Drivers installed for this? I can't install them. I got the file from XDA from your link here.
I opened the downloaded file in 7zip and double clicked on Motorola_End_User_Driver_Installation_6.4.0_64bit.msi, clicked "Next", "I agree", and "Next", and I was presented with the image "motorola drivers error 1" in the attachment. Clicking through on those continued what you can see in file 2 and 3.
Or should I just run the device in Fastboot mode, connect it via USB, and then run fastboot.exe like you say above? (when I connect the device via USB in fastboot mode, it doesn't get recognized in the Device Manager on Windows. I guess due to missing drivers, but not sure, so I'm just giving you all the information I know)
If you have a Windows pc that originally did not have 10 (7 or XP). You can flash firmware without wiping data.
RSD Lite is your best option.
Click to expand...
Click to collapse
The PC I am on has Windows 10, but it didn't come with it - I installed it manually. Will that be fine?
I also have an older PC which never had Windows 10 on it (only Linux and maybe XP, not sure). I would run RSD on that too, but it would take a bunch of time to set up.
How would I use RSD Lite for that purpose? Will "without wiping data" also mean photos, as well as Chrome tabs and settings of other apps? (Google Authenticator, Steam Authenticator, Google Keep (notes), WhatsApp, etc)
Chrome on that device is not logged in so the tabs are not in the cloud.
Thanks again for being so nice to help out - that means a lot to me!
cheater00 said:
Thanks a lot for the reply. I have fastboot.exe from the Android SDK.
Do I need to have the Motorola Drivers installed for this? I can't install them. I got the file from XDA from your link here.
I opened the downloaded file in 7zip and double clicked on Motorola_End_User_Driver_Installation_6.4.0_64bit.msi, clicked "Next", "I agree", and "Next", and I was presented with the image "motorola drivers error 1" in the attachment. Clicking through on those continued what you can see in file 2 and 3.
Click to expand...
Click to collapse
Use the newer link
https://mobilesupport.lenovo.com/us/en/solution/MS88481
The PC I am on has Windows 10, but it didn't come with it - I installed it manually. Will that be fine?
I also have an older PC which never had Windows 10 on it (only Linux and maybe XP, not sure). I would run RSD on that too, but it would take a bunch of time to set up.
Click to expand...
Click to collapse
RSD Lite doesn't work with PCs built for windows 10, not sure why exactly.
I know RSD Lite doesn't like usb 3.0.
I have used RSD Lite on a few PCs that have been updated to 10 that worked fine.
How would I use RSD Lite for that purpose? Will "without wiping data" also mean photos, as well as Chrome tabs and settings of other apps? (Google Authenticator, Steam Authenticator, Google Keep (notes), WhatsApp, etc)
Chrome on that device is not logged in so the tabs are not in the cloud.
Thanks again for being so nice to help out - that means a lot to me!
Click to expand...
Click to collapse
see My flashing guide https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
use getvar all to find codename, software channel, and moto blur software version.
You must not downgrade software version.
Downgrade the correct firmware from
https://mirrors.lolinet.com/firmware/moto/
or use LMSA Flash rescue to download firmware
This is the safer option
LMSA will ask to download firmware, after downloading, it will ask to continue with flashing.
Just don't flash with LMSA.
Firmware will be in something like c/program data/lmsa/downloads/romfiles
If you download from Lolinet unzip the file, LMSA shouldn't be zipped.
There should be 2 .xml files in the folder, these contain the flashing commands.
The servicefile.xml does not wipe user data, the flashfile.xml does wipe data.
If you want you can use notepad++ to view the xml file commands.
select the servicefile.xml with RSD Lite and flash.
After flashing with RSD Lite the device should boot, provided there is not a hardware issue.
No guarantees though.
Thanks again. Highly appreciated.
sd_shadow said:
Use the newer link
https://mobilesupport.lenovo.com/us/en/solution/MS88481
Click to expand...
Click to collapse
Unfortunately this results in the same error. I guess RSD Lite and the other software will not work without those drivers. So I might have to build a new windows system for this purpose. I will try to do that asap.
There should be 2 .xml files in the folder, these contain the flashing commands.
The servicefile.xml does not wipe user data, the flashfile.xml does wipe data.
If you want you can use notepad++ to view the xml file commands.
select the servicefile.xml with RSD Lite and flash.
After flashing with RSD Lite the device should boot, provided there is not a hardware issue.
No guarantees though.
Click to expand...
Click to collapse
Thank you. Just to be sure. Using servicefile.xml with RSD Lite will not erase phone logs? Can you tell me about that specifically? The reason is, and I'm not sure if I should be talking about this here, the following. (please let me know and I'll delete this or feel free to edit the post on your own). I'm pretty ill with, well, you can guess what, and I'm quarantined. Since March none the less. So every now and then the police will come checking if I'm home. Apparently last month they couldn't find me on one day. But I did call them back after I woke up. So to prove this I need the phone logs. Otherwise I might go to jail for a month, just because I was sleeping (because after all I'm ill!). So as you can tell this is pretty important... it's not just kitten pictures. I would appreciate if you could let me know.
cheater00 said:
Thanks again. Highly appreciated.
Unfortunately this results in the same error. I guess RSD Lite and the other software will not work without those drivers. So I might have to build a new windows system for this purpose. I will try to do that asap.
Click to expand...
Click to collapse
You could try the google android drivers
https://developer.android.com/studio/run/win-usb
or manually install the old moto drivers.
https://forum.xda-developers.com/showpost.php?p=59139887&postcount=4
Thank you. Just to be sure. Using servicefile.xml with RSD Lite will not erase phone logs? Can you tell me about that specifically? The reason is, and I'm not sure if I should be talking about this here, the following. (please let me know and I'll delete this or feel free to edit the post on your own). I'm pretty ill with, well, you can guess what, and I'm quarantined. Since March none the less. So every now and then the police will come checking if I'm home. Apparently last month they couldn't find me on one day. But I did call them back after I woke up. So to prove this I need the phone logs. Otherwise I might go to jail for a month, just because I was sleeping (because after all I'm ill!). So as you can tell this is pretty important... it's not just kitten pictures. I would appreciate if you could let me know.
Click to expand...
Click to collapse
As long as the .xml doesn't contain the line
Code:
fastboot erase userdata
Call logs, browser history, texts... will still be there.
To be extra safe I would remove the flashfile.xml
Have you tried any fastboot commands?
like fastboot devices, fastboot getvar all ?
sd_shadow said:
You could try the google android drivers
https://developer.android.com/studio/run/win-usb
or manually install the old moto drivers.
https://forum.xda-developers.com/showpost.php?p=59139887&postcount=4
Click to expand...
Click to collapse
Actually I didn't need to install old drivers. I took the latest msi file and extracted it the following way:
Code:
msiexec /a c:\testfile.msi /qb TARGETDIR=c:\temp\test
Note that if the .msi file's file name is too long, msiexec will have issues extracting it. Also, you have to use full path names. If you use relative path names, msiexec will be stupid and think you are using a network file name or something like that. So always start with a drive letter.
The extracted directory structure had a subdir several levels deep called Drivers. I went to the Windows 10 Device Manager, and under "Other devices" (which is stuff that Windows didn't recognize and doesn't have drivers for) there was "fastboot sanders S". I selected "Update Driver" on that item, and pointed the dialog to the Drivers directory, and now the phone is being recognized. It is located under "Android Device" and it's now called "Motorola ADB Interface". The device called "fastboot sanders S" is gone.
sd_shadow said:
As long as the .xml doesn't contain the line
Code:
fastboot erase userdata
Call logs, browser history, texts... will still be there.
To be extra safe I would remove the flashfile.xml
Click to expand...
Click to collapse
Thank you very much for confirming!
Have you tried any fastboot commands?
like fastboot devices, fastboot getvar all ?
Click to expand...
Click to collapse
Thank you, it works now! Here's the output.
Code:
> .\fastboot.exe devices
ZY32283ZDS fastboot
Code:
> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: (removed) (let me know if you need it)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: (removed) (let me know if you need it)
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed) (let me know if you need it)
(bootloader) meid:
(bootloader) date: 08-10-2017
(bootloader) sku: XT1805
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 0:44:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: protected (1003)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.110s
Please let me know if you see anything interesting here - or what you're looking for - I'd love to learn more about the topic. Thanks.
cheater00 said:
Thank you very much for confirming!
Thank you, it works now! Here's the output.
Code:
> .\fastboot.exe devices
ZY32283ZDS fastboot
Code:
> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: (removed) (let me know if you need it)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: (removed) (let me know if you need it)
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed) (let me know if you need it)
(bootloader) meid:
(bootloader) date: 08-10-2017
(bootloader) sku: XT1805
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 0:44:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: protected (1003)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.110s
Please let me know if you see anything interesting here - or what you're looking for - I'd love to learn more about the topic. Thanks.
Click to expand...
Click to collapse
codename is sanders
Model is XT1805
Software Channel is reteu
Software Version is 28.65-36-14
so this version should be good.
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/
XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but I would also see which version LMSA selects.
sd_shadow said:
codename is sanders
Model is XT1805
Software Channel is reteu
Software Version is 28.65-36-14
so this version should be good.
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/
XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but I would also see which version LMSA selects.
Click to expand...
Click to collapse
Thank you, I'll check LMSA.
What is the difference between SS/DS and OPS/OPSS?
cheater00 said:
Thank you, I'll check LMSA.
What is the difference between SS/DS and OPS/OPSS?
Click to expand...
Click to collapse
ss should be Single Sim
ds should be Dual Sim
O is android 8 (oreo)
Not sure about the difference between PS and PSS.
But don't think it's anything big.
sd_shadow said:
codename is sanders
Model is XT1805
Software Channel is reteu
Software Version is 28.65-36-14
so this version should be good.
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/
XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but I would also see which version LMSA selects.
Click to expand...
Click to collapse
I tried LMSA and it says the phone is not supported. If I select the model number manually
Model Name: "Moto G Plus (5th Gen S)"
SKU: "XT1805"
then it says it doesn't match.
If I instead click on "Read current device" then it says it was not recognized.
Pictures are attached.
What do you suggest?
Edit: should I just go ahead with XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?
cheater00 said:
I tried LMSA and it says the phone is not supported.
Click to expand...
Click to collapse
After installing LMSA, it directed me to the Lenovo forums, which I didn't know even existed.
It turns out there are two instances of people's G5S Plus spontaneously developing a boot loop: Thread 1, Thread 2.
In addition to that, the issue with LMSA is known on the Lenovo forums: LMSA not Working for Moto G5s Plus - Motorola Community
Following the advice in that thread, I looked at my LMSA logs. I uploaded them here: LMSA.log.
There are two things that come to mind. Here I quote from the log link above:
Code:
It's clear to me that the error is on these lines:
2020-06-29 09:48:52 [26] [INFO] Current_SoftStatusChanged - match rescue resource params: {"blurVersion":"Blur_Version.28.271.12.sanders.retail.en.US","fingerPrint":"motorola/sanders_n/sanders_n:8.1.0/OPS28.65-36-14/63857:user/release-keys","fsgVersion.qcom":null,"roCarrier":"reteu"}
2020-06-29 09:48:52 [26] [INFO] Match - missing parameter when match rescue resource
I do not have US english selected. I have bought the phone in Europe, in Austria (so the code
would be de_AT or de.AT) and I kept using the phone in British English (code en_GB or en.GB
or en_UK or en.UK). So this could be related. Or maybe fastboot not being able to find the
baseband version is an issue.
2020-06-29 09:49:40 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Failed to read [version-baseband] in fastboot, will try again
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband]: <not found>
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband] finally value:
Note that LMSA also detected OPS28.65-36-14, which is the same version as you suggested. However, the fact that LMSA says the phone is not supported, makes me worried.
If fastboot.exe is not able to detect the baseband, what does that mean? Is that normal, or should I be worried?
Thank you for your help thus far.
cheater00 said:
After installing LMSA, it directed me to the Lenovo forums, which I didn't know even existed.
It turns out there are two instances of people's G5S Plus spontaneously developing a boot loop: Thread 1, Thread 2.
In addition to that, the issue with LMSA is known on the Lenovo forums: LMSA not Working for Moto G5s Plus - Motorola Community
Following the advice in that thread, I looked at my LMSA logs. I uploaded them here: LMSA.log.
There are two things that come to mind. Here I quote from the log link above:
Code:
It's clear to me that the error is on these lines:
2020-06-29 09:48:52 [26] [INFO] Current_SoftStatusChanged - match rescue resource params: {"blurVersion":"Blur_Version.28.271.12.sanders.retail.en.US","fingerPrint":"motorola/sanders_n/sanders_n:8.1.0/OPS28.65-36-14/63857:user/release-keys","fsgVersion.qcom":null,"roCarrier":"reteu"}
2020-06-29 09:48:52 [26] [INFO] Match - missing parameter when match rescue resource
I do not have US english selected. I have bought the phone in Europe, in Austria (so the code
would be de_AT or de.AT) and I kept using the phone in British English (code en_GB or en.GB
or en_UK or en.UK). So this could be related. Or maybe fastboot not being able to find the
baseband version is an issue.
2020-06-29 09:49:40 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Failed to read [version-baseband] in fastboot, will try again
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband]: <not found>
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband] finally value:
Note that LMSA also detected OPS28.65-36-14, which is the same version as you suggested. However, the fact that LMSA says the phone is not supported, makes me worried.
If fastboot.exe is not able to detect the baseband, what does that mean? Is that normal, or should I be worried?
Thank you for your help thus far.
Click to expand...
Click to collapse
@sd_shadow just wanted to update, I have tried contacting Lenovo on multiple fronts (someone even put me in touch of the president of Lenovo for north america!) but silence so far.