Related
Hello everyone.
I am newbie. I just buy an Huawei Honor Y6 from my friend.
Model Number: Huawei SCC-U21
Build Number: SCC-U21C900B130
CPU / RAM: Quad Core 1.1 Ghz 2.0 GB
Lollipop 5.11 EMUI 3.1
Kernel Version: 3.10 49-g2d5b1a0 [email protected] #1 Mon Sep 7 16:05:29 2015
Custom Version: CUSTC636D001
I try to update all software in Google Play but failed and can't install any software to (error -501). So i come here and try to fix with some notes but also failed. I try to attach t with many root software because I think it was rooted. So lastly I try Kingoroot and it shows it was rooted. But there was no Kingo Root or Superuser software installed into my handphone. It also can't connected to HiSuite in my laptop. It will stuck at System Recovery (devices unsopported). now my hp just like a new hp without any access to install / update software, no Google Account signed. Just for Hotspot that I use to post in this forum. :|
this show in adb
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.011s]
finished. total time: 0.013s
I need help to fix this. What I have to do? Please. Help me. Teach me step by step.
Hi there!
It's been a couple of hours I pass trying to install a new Rom on my Oneplus X.
First thing I do was to return it Stock and install OOS at last update to have the last firmware.
I've unlock the bootloader, do the OEM unlock thing, I flash the recovery to TWRP 3.2.1.0 (it was a pain in the ass to do.... don't know exactly why)
As I had difficulties installing the TWRP, I install the OPXBLUpdateOOS3.1.zip which help me installing the recovery
I ran this command to be sure it is unlock
PS C:\adb> fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
And than, I try to install roms with TWRP... I select my Rom (I want to install Oreo from AOSPA, but I also try Lineage 14 and Cyanogen 13 which was the one I had before)
I always got this error :
Checking for Digest files
Skipping Digest check: no digest file found
And than, the recovery reboot...
What have I done wrong? What can I do now to install at least android N ?
What twrp are you using? Flash the latest official or the one by CheckYourScreen. It's under original android development forum. It looks more like an issue with twrp than from the zip files.
i am having the same problem with latest twrp
Try using the 3.2.3-0 TWRP recovery bcoz everything you mentioned which you did seems to be correct. So try the TWRP 3.2.3-0 and report back.
I have the same issue with the latest twrp: 3.2.3-0 on samsung galaxy a5 2016. Can't install an official ROM from sammobile.
I have the same message on Note 4 but it doesn't affect installation. I just ignore it.
I have the same fcking issue with missing digest fcking ****. I can't flash the Magisk more SuperSU. **** off!
I had problem in flashing ROM file in Samsung galaxy grand 2 .the error says "No digest file found "and "zip is corrupt" .pls help me to resolve the issue
I am facing the same problem. No digest file found!
C:\Users\Nabil\Downloads\adb>fastboot oem device-info
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.006s]
Finished. Total time: 0.007s
omkolte17 said:
Try using the 3.2.3-0 TWRP recovery bcoz everything you mentioned which you did seems to be correct. So try the TWRP 3.2.3-0 and report back.
Click to expand...
Click to collapse
I just had this with my S5 Plus on 323 , I downgraded twrp and voila ..fixed roms that ended with (no rom installed are you sure you want to reboot?) are working perfectly !!!
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
this files?
eLaDiio said:
this files?
Click to expand...
Click to collapse
I've never noticed them. Actually I've never checked in the ota packages, so thanks maybe those files can help me even if normally there should be only one gpt main 0.bin, so i don't know how can i merge them and if it's possible
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
The Marionette said:
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
Click to expand...
Click to collapse
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
MasterJack1697 said:
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
Click to expand...
Click to collapse
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
The Marionette said:
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
Click to expand...
Click to collapse
Can you please give me te link to this blank flash? I can't find the oreo based one
MasterJack1697 said:
Can you please give me te link to this blank flash? I can't find the oreo based one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
i'll try as soon as possible thanks
eLaDiio said:
this files?
Click to expand...
Click to collapse
anyway those file are totally useless to me, or at least i don't know how to merge them in one file so i can't use them
The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
MasterJack1697 said:
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
Click to expand...
Click to collapse
Yeah, you're welcome.
Issue with partition table
Thanks for the blankflash, it did work on Moto Z. I was able to get my phone back to recovery mode.
But now i get the below message when i run "fastboot flash partition gpt.bin"
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
If i try to run other commands, below is the error:
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name xbl
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name pmic
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.281s
Please see if you can help me to overcome these errors.
Thanks.
MasterJack1697 said:
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
Click to expand...
Click to collapse
bmskartik said:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Please see if you can help me to overcome these errors.
Thanks.
Click to expand...
Click to collapse
Did you try deducing the output? I think I even mentioned this.
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
C:\Downloads\XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsi
dy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.09(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 5552ed0g
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E778AC6200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.09-0-g7de07a7
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.140s
The Marionette said:
Did you try deducing the output? I think I even mentioned this.
Click to expand...
Click to collapse
bmskartik said:
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
Click to expand...
Click to collapse
https://www.merriam-webster.com/dictionary/deduce
You are trying to flash an older bootloader over your current one.
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The Marionette said:
You are trying to flash an older bootloader over your current one.
Click to expand...
Click to collapse
bmskartik said:
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
One page backwards, I put a link to my post, where I explained everything I did. The OTA or the whole update zip should have the newest bootloader.
Again, I mentioned everything I did there.
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
bmskartik said:
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
Click to expand...
Click to collapse
Mine did the same, now try flashing the gpt.bin from the whole Oreo firmware, not the OTA.
Hi,
I hope someone help i just flash my phone using EMUIFlasher 1.1.apk to upgrad my phone i always did bad thing and i resolved and i said it will be the last time but this time the problem bacame seriouss
I success many time to downgrade from 9.1 (because i had unknow version in settings and hisuite did not recognize the phone and can't make backup or recover) to 8.0 and i success to back to 9.1 using emuiflasher1.1.apk with correct version and all informations in setting and not even this i success to root 9.1 with magisk, so when i saw another version in firmware finder i try to install it (approuved version ) this time the situation is bad for me because the screen is black and plug the cable i can hear the sound of usb device, i can access to bootloader i can flash anyhting but the screen is always black any help please.
fastboot devices
9WVDU18313009100 fastboot
fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.170(C185)
OKAY [ 0.004s]
finished. total time: 0.005s
fastboot oem check-rootinfo
...
(bootloader) status : RISK
(bootloader) version : v1.1
(bootloader) current status: SAFE
(bootloader) old status : SAFE
(bootloader) change_time : 0
(bootloader) item: root-prop, status: SAFE, credible: Y
(bootloader) item: setids, status: SAFE, credible: Y
(bootloader) item: verifyboot, status: SAFE, credible: N
(bootloader) item: verity-enable, status: SAFE, credible: Y
(bootloader) item: fblock, status: SAFE, credible: Y
(bootloader) item: userlock, status: RISK, credible: Y
OKAY [ 0.031s]
finished. total time: 0.032s
Please
what is loader + oeminfo solution
Hi all,
I am a newbie to custom ROM's world and this is my attempt to it. My device is Moto G5s Plus.
To start with I had an encrypted phone running Android 8. Encryption was mandatory to install some work related apps. Because of sluggish performance I thought to install custom ROM.
Here are the steps I followed:
1. Installed minimal ADB on my laptop running Win10. Connected phone and successfully unlocked bootloader.
2. Rebooted phone in recovery mode and installed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'.
3. Rebooted the device and everything was working fine till now (restored from google backup and restarted several times to make sure things were working fine).
4. Now as I mentioned I need to encrypt phone for bussiness reasons. So I selected 'Settings->Encrypt Phone'. For very small time a green iconed screen appeared and then phone rebooted.
5. After reboot, a screen with google logo (G) with a small progress bar (kept moving left to right and vice-versa) appeared. I left it for more than 12 hours still hung at same screen.
6. Now I tried to wipe Dalvik/ART cache and cache. This is where problem started happening. I tried few other things (could not recollect exactly). I even tried to erase 'data' from fastboot using 'fastboot erase userdata'.
7. When nothing worked, I thought of installing Pixel Experience 11 plus again from TWRP. The process went smooth but towards the end it showed:
'Failed to mount '/data' (invalid argument)' error.
I am attaching snapshots and logs. Its been more than 3 days being stuck on this issue. Really appreciate any help.
Please let me know if any info is required.
Also since I dont have any data to worry about, so I am open to any suggestion (wipe/format). I have SD card and OTG with me.
Once the phone is up and running, I need to encrypt it back. So please suggest steps while keeping this requirement in mind.
Look for this issue on youtube and you'll find the steps to fix it.
It looks like you have a corrupt file system.
You can fix it using TWRP.
Good luck !
Hi,
I tried multiple steps to fix this issue but none helped.
As for now looks like I have made some progress. What I did was i flashed official firmware for Moto G5s plus as mentioned on below page:
Flash official firmware Moto G5s Plus [sanders]
So far, we have had the guides for you to unlock the bootloader in Moto G5s Plus or how to install TWRP on Moto G5s Plus and today, I am going to show you how to download and Install stock ROM in Moto G5s Plus. So if you probably have already...
forum.xda-developers.com
With this I got the device up and running with Android 7. Below is the full log of fastboot getvar all command:
<<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all > and7_var
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 4:57:41 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-4/4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.201.4.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g419eefd0-000
(bootloader) kernel.version[1]: 54-g1b4a83e ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Mon Oct 16 22:03:44 CDT 2
(bootloader) kernel.version[4]: 017
(bootloader) sbl1.git: git=MBM-NG-VC2.06-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) devcfg.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) keymaster.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib64.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) prov.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) aboot.git: git=MBM-NG-VC2.06-0-g1e22c44
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.121s
>>>
Now i have Android 7 up and running. Now I opened TWRP again, and flashed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'. Though this process works fine but after reboot it is again stuck at Google logo (G) screen.
Please help. I have spent 2-3 days working this out.
Regards.
Hey man.
In order to flash PE 11, like the ROM topic says, you "MUST" be on latest modem baseband ...
You "ONLY" obtain that by flashing the latest OREO 8.1 ROM.
So, you should flash latest Oreo you have and update it till there are no more updates.
Read PE 11 topic again. There you can find out about what i'm saying here.
Hope this helps and again,
Good luck !
Thanks a lot Damage1972 for showing the way forward
Between how did you figured out if this is the issue here?
Based on your suggestion, I flashed stock Android v8.1 and updated it till there are no updates. Phone was rebooting fine. After this, I flashed PE 11 plus and again phone is stuck at Google logo (G) screen.
Between below are logs:
<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot 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: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 9:30:53 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: no protection (0)
(bootloader) ro.carrier: retin
(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.065s
>>
Please suggest.
Thanks and Regards.
No problem,man.
About the issue, it's listed on the pre requests in order to flash PE 11 !
It's very clear written on the first page and comments on the topic.
Carefully read the ROM's topic before flashing...
About your phone still stuck on boot : did you go through the steps to correct your phone file system ? And (sorry to ask you this) how did you flash the ROM ?
Did you do a Clean Flash ?
Check your messages.
Also, try this , that's what worked for me :
How to fix unable to mount data internal storage 0mb in twrp permanently :
Note : This will wipe/format your Data partion and your data will be reset. INSTRUCTIONS : 1) Reboot your device into TWRP Recovery. 2) Go to Wipe menu. 3) Go to Advance Wipe. 4) Select Data and go to Repair or Change File System. 5) Click...
forum.xda-developers.com
So few updates:
1. Looks like my mount data internal storage 0 mb issue is resolved (flashed stock ROM and then custom ROM and did not see this error).
2. Regarding how I flashed stock ROM Android 8.1. I downloaded 'Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0.zip' image from:
Motorola Moto G5S Plus XT1804 Stock ROM Firmware (Flash File)
Download the official Motorola Moto G5S Plus XT1804 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
and executed below commands in order:
<<
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition sanders81/gpt.bin
fastboot flash bootloader sanders81/bootloader.img
fastboot flash modem sanders81/NON-HLOS.bin
fastboot flash fsg sanders81/fsg.mbn
fastboot flash dsp sanders81/adspso.bin
fastboot flash logo sanders81/logo.bin
fastboot flash boot sanders81/boot.img
fastboot flash recovery sanders81/recovery.img
fastboot flash system sanders81/system.img_sparsechunk.0
fastboot flash system sanders81/system.img_sparsechunk.1
fastboot flash system sanders81/system.img_sparsechunk.2
fastboot flash system sanders81/system.img_sparsechunk.3
fastboot flash system sanders81/system.img_sparsechunk.4
fastboot flash system sanders81/system.img_sparsechunk.5
fastboot flash system sanders81/system.img_sparsechunk.6
fastboot flash system sanders81/system.img_sparsechunk.7
fastboot flash system sanders81/system.img_sparsechunk.8
fastboot flash system sanders81/system.img_sparsechunk.9
fastboot flash system sanders81/system.img_sparsechunk.10
fastboot flash oem sanders81/oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg sanders81/fsg.mbn
fastboot oem fb_mode_clear
fastboot reboot
>>
After that I was able to turn ON phone with Android 8.1.0. Checked for updates and installed them (i guess there were 3 security updates). Once done, entered bootloader and installed TWRP and flashed PE 11 plus. After reboot, it is again stuck at google logo (G) screen.
One more suggestion i need: Since I have spent a lot of time debugging this and ultimately I have to encrypt my phone. So below queries:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
andromeda1410 said:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
Click to expand...
Click to collapse
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Thanks sBinnala for help. At this point I am convinced that I will not install custom ROM. So I want to have stock ROM (Android 8.1) preferably.
Thing is yesterday I installed Android 8.1 stock rom (exact steps mentioned above), worked fine. Flashed PE 11 plus and phone got stuck at google logo screen. Searched again and though it to be some modem related issue hence I did below steps as mentioned on https://forum.xda-developers.com/t/rom-11-sanders-pixelexperience-normal-plus-aosp.4247243/ by Jorge:
<<
It is recommended that you are using the latest firmware for the Moto G (5S) Plus.
to update via twrp:
Modem only:
https://sourceforge.net/projects/ne...5-36-14_v2.0-modem-only_20210307.zip/download
Modem, Fsg & dsp:
https://sourceforge.net/projects/ne...S28.65-36-14_v2.0-modem_20210307.zip/download
>>
So I flashed Modem, Fsg & dsp: (second zip) and re-flashed PE 11 plus. Again that did not worked. Now again I tried to flash stock Android 8.1 ROM. It worked but now it is not detecting SIM., showing IMEI as 0 or not available.
I have found multiple pages on similar issue but none is working. Looks like this issue is because of persist file and epf partition which I dont have (infact i dont have any backup).
So can someone please help me in installing stock Android 8.1 which should work fine (sim should be detected). Any help will be deeply appreciated.
Edit: Tried installing Validus and following steps mentioned on https://forum.xda-developers.com/t/...ork-imei-0-after-flashing-custom-rom.3745474/ but issue not resolved.
If it matters, mine is 4 GB/64 GB, XT 1804 variant.
On some threads, i found inconsistency in architecture (like 32 bit and 64 bit). What is that? I know i have 32 bit TWRP running on a 64 bit Windows 10 machine. I am not sure about stock ROM architecture. Can someone tell me how to check stock ROM architecture?
On another notes: I have tried flashing below stock roms but none of them are working fine (device boots but unable to recognize SIM):
- Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0_Android8.1.zip
- SANDERS_NPSS26.116-26-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_Android7.zip
- SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
- Stock-Sanders_OPS28.65-36-14_v2.0-modem_20210307.zip
- Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
Regards.
Further update:
Looks like I have created a backup using TWRP of original ROM (which was Android 8.1 but encrypted). Zipped it using Android app and then I transferred it to Windows laptop (later realized i should not have done it). Unzipped in android device and placed it in OTG. Restored using TWRP but it is not booting.
Can I do anything now? That is, should I preserve any file which I can later use with stock Android 8.1 ROM which can help me with getting sim signal/IMEI number back.
sBinnala said:
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Click to expand...
Click to collapse
Encryption works flawlessly with Arrow 11 vanilla.
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
okayk said:
Encryption works flawlessly with Arrow 11 vanilla.
Click to expand...
Click to collapse
Arrow isn't enforcing - it's permissive, which in itself is a huge security risk. Like I said, we don't have a ROM which supports both SELinux enforcing and encryption at the same time.
andromeda1410 said:
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
Click to expand...
Click to collapse
Normally in such cases, restoring EFS backup will do the trick. Have you already tried that?
After days of investigation, debugging and trying out everything which any post said, I have resolved my issue now. I now have a fully functional Android 8.1 installed on my phone, I am able to make calls, IMEI number is back.
In interest of wider public let me post what worked for me:
Note:
My device is Moto G5S Plus XT1804, 4 GB/64 GB, Retin Channel, India based phone. It is unrooted but has unlocked bootloader.
I have tried a lot many things, flashed many ROMs from different channels but none of them worked.
Below is what worked for me.
Probable issue: During flashing gpt.bin I was getting below error:
<<
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.074s
>>
I guess this is the core issue. I searched on it and got many forums. Finally below solution worked for me:
Downloaded stock Android 8.1 rom 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' for my device from: https://www.stockrom.net/2020/04/xt1804-retin-oreo-ops28-65-36-14.html
Unzipped this file and placed it at 'C:\Program Files (x86)\Minimal ADB and Fastboot'.
Created my own batch file using instructions mentioned in 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/flashfile.xml'.
Imp note: Do not use fastboot commands mentioned on any forum. Every rom (custom/stock) has a flashfile.xml or servicefile.xml. Open this file and create your own batch file with steps in order mentioned in xml file.
Booted my phone in fastboot mode (volume down + power). Connected phone with PC using usb cable.
Launch 'Minimal ADB and Fastboot' on windows PC. Note: i am attaching all tools that i used to rest version related questions.
Run the batch file you created in step #3.
With these steps, I was able to get my phone up and running. Thanks a lot to all members for their help.
Regards.
Reference links:
How to Restore Stock Firmware on Moto G (All Models)
Follow this guide to restore stock firmware on Moto G. The instructions will work for Moto G 1st Gen, 2nd Gen, 3rd Gen, 4th Gen, Moto G5/Moto G5 Plus, and Moto G5S/Moto G5S Plus. The Moto G series is…
www.thecustomdroid.com
G5s Plus XT1804 RETIN (SANDERS) 8 Oreo StockRom OPS28.65-36-14
Download Firmware + Tutorial Completo para Instalação Stock Rom Moto G5s Plus XT1804 (SANDERS) Android 8.1.0 Oreo Loop, Boot Infinito ou Hard Reset
www.stockrom.net
Tutorial – Instalação Stock Rom Motorola no Modo Fastboot (Snapdragon, Moto G, Moto E, Moto X, Moto Z, Moto C, Moto M, One) + Video Tutorial - Stock Rom
Como instalar firmware nos motorolas com processadores snapdragon, moto g1 ao g7, procedimento simples, instalador com 1 clique, sem linhas de comando.
www.stockrom.net
(These pages are in non-english. I used google translator for understanding it)