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 read a couple of other threads with similar symptoms but I do not know if I have the same problem. So I think it's better to start a new thread. In any case I hope some expert here can help me.
About 1,5 years ago I bought a secondhand HTC One M8 and it has been working fine up to last Tuesday. I use it to hike (to follow downloaded tracks and record my hike, using GPS, and when I do this I put it into flight mode to not use any more battery than necessary). I keep it in a pocket in my shorts when I hike. Last Tuesday, I was simply walking (not climbing, running or anything of that kind) and it had just started raining, but my phone was in my dry pocket, when I felt it vibrated. It had powered off by itself. I powered it on again, tried to reactivate my hiking application (Alpine Quest) but it didn't register my location nor track my moves. I didn't have any connection and it was stuck in flight mode.
At home, powering off and on, it all of a sudden asked me for a PIN code (I've never secured my phone with a code, and I've never seen this screen before) and it only lets me make emergency calls. I tried 0000 but that didn't work (using 1 of the 3 PIN code attempts... I've 2 left now). Powering it off and on a couple of times, it sometimes gives this screen, but sometimes it also allows me to access my phone without the code (the normal home screen). In doing so I was able to get rid of the flight mode (when it is powered it freezes when powering on or off flight mode, which than becomes greyed out). Sometimes it powers on and off by itself. But I have no connection, no baseband, EMEI is unknown, phone number is unknown.
If any of you has any idea as to solve this porblem, I would appreciate the help !
Thanks !
Judith
Ps Oh and by the way, I'm quite illiterated when it comes to phones... I may understand computers but because with phones the software is hidden and can only be accessed when the phone is rooted (and I already "bricked" my previous unlocked Samsung by trying to root it when it had a problem) I cannot learn and I'm scared I may do something wrong this time too . I find it ridiculous that when you BUY a (unlocked) phone you cannot access the software installed on it (and get rid of xxxxx MB of bloatware that fills up the memory, to name one thing...).
Phone: HTC One M8
Android version: 6.0
HTC Sense: 7.0
Software number: 6.12.401.4
Kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
Baseband version: unknown
IMEI: unknown
IMEI SV: unknown
Phone number: unknown
IMSI: unknown
Judiver said:
Ps Oh and by the way, I'm quite illiterated when it comes to phones... I may understand computers but because with phones the software is hidden and can only be accessed when the phone is rooted (and I already "bricked" my previous unlocked Samsung by trying to root it when it had a problem) I cannot learn and I'm scared I may do something wrong this time too
Click to expand...
Click to collapse
What do you mean "I cannot learn"? Anybody can learn! But it requires you to take the time and effort to learn the proper info and methods.
If you don't understand enough to root a phone, then you don't know enough to be messing with the phone's software. This is the main reason they don't let users easily access the operating system (more likely to cause damage then do good).
Judiver said:
Software number: 6.12.401.4
Click to expand...
Click to collapse
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number, if they appear).
It appears you obtained the info from the phone settings (within OS) which is not a reliable way of obtaining this data.
If you don't know how to do fastboot getvar, at least go to bootloader screen, and confirm OS number, and tell us whether baseband number is listed as well.
Hi Redpoint,
Thank you for your reaction. Sorry for my slow reaction. I've been doing some reading and also finding out how to make a back-up without a connection. I ended up downloading HTC Sync Manager, which didn't want to connect my phone at first, and sometimes still doesn't. I am apparently not the only one who has this problem with HTC Sync Manager but I noticed that since my phone disconnected last week, that when I plug it to my pc with a USB cable (not an original HTC as that was not delivered with my 2nd hand phone...) I get the message that the driver doesn't install. I now sometimes I can connect my phone and sometimes not. This must be related to the problem with the phone, as formerly this never happened, I could always connect my phone to my pc with USB and never got a message about drivers not correctly having been installed. Also my phone powers off and on by itself now.
Off course I can learn ! I wouldn't have asked for help here if I didn't want to learn ! What I meant is that, opposed to computers, a normal user with an unrooted phone (like me) doesn't see nor can he/she access any software on a phone. When I had a problem with my previous phone (a Samsung), I asked for help on this forum but I didn't get any reaction. So I tried to figure things out myself and downloaded a file from the internet to (easily) root the phone. But the program appeared to be crap, it bricked my phone (I think my EMEI was stolen ?). That wouldn't happen on a pc, which is much more fool proof : you can see your system files, run malware and other scans, lots of security facilities are built in, lots ways to get back to a previous state from before messing up, etc. Everything I learnt about computers is done by reading & trying and I am much less afraid of doing something wrong because it is like walking in a city where I've been wandering around many times, seeing things that are either familiar or weird. With the experience of my Samsung in mind, I am afraid of doing something wrong with my HTC now, and especially afraid of downloading from websites that have not been recommended by a trustworthy source. That's all.
I just installed the Minimal ADB and Fastboot (https://forum.xda-developers.com/showthread.php?p=42407269#post42407269) and got this result :
(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.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: *****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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
all: Done!
finished. total time: 0.080s
I bought it from Second-hand Phones in the UK in April last year.
Thanks for your help. I appreciate it.
Judith
Ps learned something already
Oh I forgot,
It says
***Software status: Official***
Judiver said:
When I had a problem with my previous phone (a Samsung), I asked for help on this forum but I didn't get any reaction. So I tried to figure things out myself and downloaded a file from the internet to (easily) root the phone. But the program appeared to be crap, it bricked my phone (I think my EMEI was stolen ?).
Click to expand...
Click to collapse
I don't know what Samsung phone (your info is too vague, maybe intentionally so) but there is plenty of info on XDA on how to root all the common Samsung phones. You may have been asking for an old device, where the forum is not very active anymore (the M8 forum itself is pretty quiet, only a few of us "helpers" left anymore. Or maybe asking a question that has already been answered too many times ("how to root" is one of those).
If you downloaded a random root program from websites outside XDA, that is a mistake. My advice would be to stick to XDA, and advice/files from reputable XDA members, and you won't go wrong.
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
Judiver said:
Off course I can learn ! I wouldn't have asked for help here if I didn't want to learn ! What I meant is that, opposed to computers, a normal user with an unrooted phone (like me) doesn't see nor can he/she access any software on a phone.
Click to expand...
Click to collapse
This is a false statement. Linux systems are both computers and PCs. And Linux has root privileges just like Android.
If you are talking Windows specifically, I can tell you having tinkered with both Windows PCs and Android Phones, that phones are far easier to manipulate and restore, than PCs. You just know your way around PCs, than phones.
There are plenty of ways to restore an Android device. You just haven't learned them yet.
---------- Post added at 09:53 AM ---------- Previous post was at 09:41 AM ----------
Judiver said:
I've been searching for fastboot getvar all, but it looks like I need to download a program for that (?) and, as I said, I am a bit afraid of downloading from the wrong websites.
Click to expand...
Click to collapse
By installing HTC Sync, you already have fastboot installed. There are also fastboot/adb installers available on XDA (reputable and used by many) if you use the XDA search function and search "easy fastboot install" or similar search phrase. Also "fastboot guide" will help you find threads on the basics.
Fastboot is mandatory not just for the info I asked for, but also the recovery option I will suggest. So you need to learn how to use fastboot, at least on a basic level. Fastboot is handled through PC's command prompt interface. So if you are experienced with PCs, it really shouldn't be a problem for you to learn.
And when I say "recovery option I will suggest" keep in mind, it is just a clean install of the stock software/firmware. It sounds like your issue may or may not be a hardware failure. But in the even it is, my forthcoming suggestion won't fix your issue. But it's worth trying, to at least see if the problem is in the software/firmware.
redpoint73 said:
I don't know what Samsung phone (your info is too vague, maybe intentionally so) but there is plenty of info on XDA on how to root all the common Samsung phones. You may have been asking for an old device
Click to expand...
Click to collapse
It was indeed a bit of an old device. I didn't mention the model because it isn't relevant for this thread, but it was Samsung Galaxy i9003 S SCL, bought in 2012 (in Spain). It got a problem last year, but, if I remember well, as the software was outdated (and apparently not updated to anything newer?) I wanted to root it to be able to put something more recent on it (hoping to fix the problem at the same time).
redpoint73 said:
If you downloaded a random root program from websites outside XDA, that is a mistake. My advice would be to stick to XDA, and advice/files from reputable XDA members, and you won't go wrong.
Click to expand...
Click to collapse
I fully agree! It was a stupid action and I should have known better. I have enough experience with pc's to know the risks of downloading executable files from shady sources...
redpoint73 said:
You just know your way around PCs, than phones.
Click to expand...
Click to collapse
Well, I'm no expert in pc's but I try and learn, and stuff becomes easier on the go. But I am a blank page when it comes to mobiles phones !
redpoint73 said:
By installing HTC Sync, you already have fastboot installed. There are also fastboot/adb installers available on XDA (reputable and used by many) if you use the XDA search function and search "easy fastboot install" or similar search phrase. Also "fastboot guide" will help you find threads on the basics.
Fastboot is mandatory not just for the info I asked for, but also the recovery option I will suggest. So you need to learn how to use fastboot, at least on a basic level. Fastboot is handled through PC's command prompt interface. So if you are experienced with PCs, it really shouldn't be a problem for you to learn.
And when I say "recovery option I will suggest" keep in mind, it is just a clean install of the stock software/firmware. It sounds like your issue may or may not be a hardware failure. But in the even it is, my forthcoming suggestion won't fix your issue. But it's worth trying, to at least see if the problem is in the software/firmware.
Click to expand...
Click to collapse
I am glad that you think it's a software issue. So now that I have HTC Sync and the Minimal ADB and Fastboot, is that sufficient for what you (I hope) suggest I do next or do I need the full ADB?
Judiver said:
I am glad that you think it's a software issue. So now that I have HTC Sync and the Minimal ADB and Fastboot, is that sufficient for what you (I hope) suggest I do next or do I need the full ADB?
Click to expand...
Click to collapse
I never said I thought it was a software issue. I said it may or may not be a hardware issue. It's worth a try (and probably won't hurt) restoring the full stock software image (RUU). Sometimes this fixes the problem with no connection, sometimes not (such as with a hardware issue).
Just about any fastboot installation will do. In fact, you will need to download the htc_fastboot to flash the RUU file in the following post:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note that you do not need to lock the bootloader (first 2 bold type lines in the above guide) since your bootloader is still locked.
Also note that the RUU will wipe all data from the phone. So backup/move anything you want to keep from the phone (photos, personal data, etc.).
redpoint73 said:
I never said I thought it was a software issue. I said it may or may not be a hardware issue. It's worth a try (and probably won't hurt) restoring the full stock software image (RUU). Sometimes this fixes the problem with no connection, sometimes not (such as with a hardware issue).
Just about any fastboot installation will do. In fact, you will need to download the htc_fastboot to flash the RUU file in the following post:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note that you do not need to lock the bootloader (first 2 bold type lines in the above guide) since your bootloader is still locked.
Also note that the RUU will wipe all data from the phone. So backup/move anything you want to keep from the phone (photos, personal data, etc.).
Click to expand...
Click to collapse
I'm sorry, I was reading fast and apparently did some 'wishful reading' concerning the software/hardware issue.
In bootloader mode there are a couple of options, like Recovery mode and Factory reset. Couldn't I try this first before loading on a new RUU?
Judiver said:
In bootloader mode there are a couple of options, like Recovery mode and Factory reset. Couldn't I try this first before loading on a new RUU?
Click to expand...
Click to collapse
Those options won't do anything. If they had any possibility to help, I would have mentioned those options. The stock recovery is pretty useless. It will give you options to factory reset (see more info on that, next paragraph), and wipe cache. You can try to wipe cache if you like (won't harm anything) but it won't help your issue, I can guarantee.
In regards to factory reset, many folks have a misunderstanding of what that means. The term "factory reset is somewhat of a misnomer. It won't magically restore the OS. The only way to do that, is to re-install the OS from somewhere, like an RUU. The only thing the factory reset option in bootloader/stock recovery does, is wipe user data.
redpoint73 said:
Those options won't do anything. If they had any possibility to help, I would have mentioned those options. The stock recovery is pretty useless. It will give you options to factory reset (see more info on that, next paragraph), and wipe cache. You can try to wipe cache if you like (won't harm anything) but it won't help your issue, I can guarantee.
In regards to factory reset, many folks have a misunderstanding of what that means. The term "factory reset is somewhat of a misnomer. It won't magically restore the OS. The only way to do that, is to re-install the OS from somewhere, like an RUU. The only thing the factory reset option in bootloader/stock recovery does, is wipe user data.
Click to expand...
Click to collapse
Hi Redpoint,
I downloaded the htc_fastboot.exe and the RUU, but couldn't find a download for the 1.4.3 version of the ADB Installer last night. So today, still no luck, I tried 1.3 and followed the instructions on the links you gave me. At first I thought it hadn't changed anything as it was asking for a PIN again and when connecting to my pc with a USB cable the drivers didn't install correctly (i.e. same 2 symptoms that had occurred when I found myself without a connection). But this time the standard 0000 of my operator worked for the sim card PIN and it appeared I had a connection! But it wouldn't call. After re-installing my wifi connection I started updating all of the software. That took a while. And then restore from HTC Sync Manager back-up and getting all my apps and settings back that the back-up hadn't adressed (the HTC back-up was not very exhaustive... no ringtones, no Whatsapp history...).
During all the updates the first sms I received was spam and this telephone, for some reason, can blacklist calls but not sms. Lots of bloat ware you cannot get rid of but no sms blocker! And I forgot which sms blocker app (free, no ads) I had downloaded previously. Hmmm... I'll keep looking for something suitable...
But that aside, all seems to work as it should now (fingers crossed) !
So thanks a lot for your help. It helped me greatly :good::good:.
And I learned, although I still think it is a bit of a drastic procedure to do every time a phone has a problem. You have no idea what the problem is, severe or minor, and have no clue where to look! If every time I have a problem with my pc I need to re-install Windows, I wouldn't be doing much other than just that! Mobile phones (at least as far as I know) seem to lack a system where you can do a scan and repair system files, or a way to find out where the problem is and replace just a part (leaving your stuff in tact). All I read everywhere on android websites is about flashing and rooting, hardly ever less drastic solutions... But then... that's the opinion of someone you just made her first steps in the Android world ...
Judiver said:
I downloaded the htc_fastboot.exe and the RUU, but couldn't find a download for the 1.4.3 version of the ADB Installer last night.
Click to expand...
Click to collapse
You already has adb installed when you installed HTCSync. And again when you used the minimal fastboot/adb installer. I mentioned as much earlier. Any of these would work. Not sure why you tried installing adb yet again (3rd separate installation).
In any case, it sounds like you sorted it out, so glad the RUU helped.
Judiver said:
And I learned, although I still think it is a bit of a drastic procedure to do every time a phone has a problem.
Click to expand...
Click to collapse
What you experienced was probably a pretty serious issue, and not that common. I used the M8 as my daily driver for over 3 years, and never had to use the RUU to recover from such an issue.
redpoint73 said:
You already has adb installed when you installed HTCSync. And again when you used the minimal fastboot/adb installer. I mentioned as much earlier. Any of these would work. Not sure why you tried installing adb yet again (3rd separate installation).
I wasn't sure whether the minimal fastboot / HTC Sync was enough to install a RUU.
redpoint73 said:
What you experienced was probably a pretty serious issue, and not that common. I used the M8 as my daily driver for over 3 years, and never had to use the RUU to recover from such an issue.
Click to expand...
Click to collapse
We will never know what the problem was, but I'm very happy it is gone Thanks for helping me out Redpoint.
Click to expand...
Click to collapse
Good morning my "dear", I'm new and this is my first topic, I'm sorry if you are in the wrong topic, can move, come humbly, ask your "wisdom", please, could someone explain to me if it is possible to relive a Moto G6 FullBrick - xt1922-5 - Aljeter, which is not calling, when I turn on the pc, he is flashing the led and recognizes as Qualcomm, I tried several "blankflash", unsuccessfully, the interesting thing is that I have 02 devices, a hard brick in this situation above and another working perfectly, already saved the partition "mmcblk0" of what is working, set up an sdcard in rufus, and tried to start the hard brick device, but without success, could anyone give me an idea ??
Hello, I performed a custom rom process on the moto g5 xt1671 and the rom used was from another smartphone and from another totally incompatible brand (a mistake) and therefore my phone was bricked and so I flashed blank and the fastboot was very buggy with words of start in green and the information below, I did fastboot by cmd tried to install stock rom always gives error in the first command and so I went to see the information through fastboot and it was fb: b8.25 (*) kernel: 000000000000 (multiple 0) and sku: 00000000 (several 0) without any information, how do I fix it - lot?:crying:
There is no blank flash for this device that I know of
You may need a motherboard replacement if you have flashed firmware etc from other devices
The only known solution to a hard brick for this device is below however as you have flashed unknown bootloaders & other firmware which is not meant for your device you may still end up needing a motherboard replacement
See my hard brick guide below
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Yesterday I got a update on my MG8P. It was about 155 mb and was containing feb 2020 security patch with "other bug fixes and improvement" as notification read.
I've also had this update, for about two weeks.
One when you try to install, i get an errorat 13 percent, and so every morning.
Does anyone know how to install it, or disable it?
MG8P +magisk +xposed
3dekstron said:
I've also had this update, for about two weeks.
One when you try to install, i get an errorat 13 percent, and so every morning.
Does anyone know how to install it, or disable it?
MG8P +magisk +xposed
Click to expand...
Click to collapse
i got the error also at 13 %, i have an unlocked bootloader, further i use the stock boot image because of a borked magisk module, so the only reason i can think of, is because of the unlocked bootloader
How do I turn it off? Which app is responsible for updates?
Maybe it would turn it off, as I would know what it was going for.
so factory reset my phone, so i could get root again....
after that the update still did not work.
also i could not get root ( i'll continue that one in my questions post on fixing the deinstallation of a broken magisk module)
anyway, i decided i needed a working phone, so i switched back to my old phone. and guess what, after removing the simcard and sd-card, i was suddenly able to update. i'm now on the latest build.
so i'm not fully sure if the removal of the simcard / sdcard, or simply the factory reset after a second or third boot made it work... / was the reason, but i'd thought, lets suggest it, maybe it works for you too just to remove sdcard and sim?
My phone was in software channel "vfeu" and did not get the update pushed (No my phone is not locked nor branded to Vodafone, I don't have Vodafone SIM's)... I did a check again today but still didn't have the update available, so I tried to changing my software channel from "vfeu" to "reteu" using fastboot:
Code:
[email protected]:~$ fastboot oem config carrier reteu
...
(bootloader) <UTAG name="carrier" type="str" protected="FALSE">
(bootloader) <value>
(bootloader) reteu
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see http://goo.gl/lojLh3
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~$
Unfortunately, this didn't seem to change anything at all, my about phone page still shows "vfeu" as software channel. However, suddenly I did get the OTA update and I was able to update successfully.
After the update, the software channel was still listed as "vfeu", so it may have been complete coincidence that after my fastboot action the update became available, but I'm not entirely convinced
isn't g8 power a slightly different/better phone?
G8 Power vs G Power
guest_2011 said:
isn't g8 power a slightly different/better phone?
Click to expand...
Click to collapse
G8 Power is definitely different from G Power:
"XT2041-4; XT2041-6; XT2041-7; XT2041-DL = Moto G Power, XT2041-1; XT2041-3 = Moto G8 Power."
From the comments of this article: w w w . gsmchoice.com/ en/ catalogue/ motorola/ motog8power/