Related
[RUU] Google Edition Conversion. 4.4.2- 1.16.1700.16 -RUU Zip Non-Rooted & Pre-Rooted
This will NOT work on a CDMA HTC One GSM ONLY!
[PSA: People have been reporting not being able to flash back to sense. When investigating this further I found that the system partition on the GPE is about half the size of the sense system partition. (just over a gig compared to like 2.8) This was not the case on the M7
So as of now once you convert, YOU CAN NOT GO BACK TO A SENSE BASED ROM UNTIL A RUU is RELEASED! Rest assured nothing is wrong with the RUU. If you did convert and want to go back you just have to wait for a RUU to be released then you can go back but flashing a sense rom in recovery wont work.
This thread is NOT to support changing your MID, Changing your CID, Rooting or Flashing a custom recovery. If you need to learn how to do any of those do NOT use this thread to post in. Post in the respective dedicated threads to complete these processes. This thread is ONLY to support flashing the RUU. Nothing more, nothing less.
This is NOT a general 4.4.2 discussion thread.
Furthermore, if you need any more detailed instructions than what's stated in this post then you really shouldn't be doing this to your device. If you need a "video" or ask for "step by step" instructions you will NOT get anything more than what's in this post (at least from me). There is no easier way to do this process, there is no easier way to explain it. If you read the post and still don't understand what to do then I advise you to leave your phone alone... Read and then read some more until you understand everything.. WE WILL NOT SPOON FEED YOU IN THIS THREAD!
This procedure is not easy and is not really noob friendly, well flashing the RUU is not really difficult but it's the prerequisites that are more complex/risky. If the instructions aren't clear enough for you or you require further hand holding then I'm sure most of us would advise you stay away from the process.
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Instructions:
First you are going to have to have s-off on your device. Thread for S-off (and support for S-off) http://forum.xda-developers.com/showthread.php?t=2708464
Full Conversion 4.4.2 RUU ZIP containing System, Boot and all Firmware 1.16.1700.16
This will wipe EVERYTHING INCLUDING YOUR INTERNAL SD CARD!!!! PLEASE REMOVE YOUR EXTERNAL CARD IF YOU HAVE ONE so make sure you back up the contents before running this, but you'll end up with a factory-fresh GE. Of course, there's still no support, warranty or responsibility implied or otherwise.
The 4.4.2 RUU Zip supports the following MIDs and CIDs if your MID or CID is not in this list you will have to modify the android-info.txt file in the zip to match your MID/CID
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B*****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
(please note.. If your model id or cid is not supported you can open up the android-info.txt file that's in the zip and replace one of the model ids or cids listed to match yours.)
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip/CODE]
you will the following message:
[CODE]FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
Code:
fastboot reboot
Stock Non-Rooted 4.4.2-1.16.1700.16 RUU Zip: http://www.androidfilehost.com/?fid=23329332407584639
Mirror:
MD5: eb56e73af883aa2d175032c7dc527dc8
Stock Rooted + busy box pre-installed 4.4.2-1.16.1700.16 RUU Zip: http://www.androidfilehost.com/?fid=23329332407584640
Mirror:
MD5: b380f51a4a2b0e2a83c4d7bd92075ce5
If you want to flash a custom recovery you will have to flash back to stock recovery to get the OTA's
You can get the GPE Stock recovery here
Special thanks to @pasker17 for allowing me to walk him through pulling all the partitions!!
@beaups and crew for S-off
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, or flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. This process is not for the faint of heart so I am not responsible.... It was the other guy... I swear....
reserved
this one too
Worked like a charm the first time thanks! One thing to note is my dot view case works fine with calls the voice gesture down is missing though I'm not missing it. I mention this as some reviews say the gpe edition can't answer calls with the case.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Pre-rooted + busybox RUU added to op
ill probably hold off on fully converting for now but what is the advantage of doing so VS just flashing a GPE rom?
fix-this! said:
ill probably hold off on fully converting for now but what is the advantage of doing so VS just flashing a GPE rom?
Click to expand...
Click to collapse
OTA updates.
Sent from my HTC One_M8 using Tapatalk
BONED
had to change name
Thank you. Confirmed works on Rogers M8. Thank you again. Would be nice if HTC can release the photo edit app on play store in the future.... and maybe the burst mode for the camera
Questions
First off I wanted to say thanks!
But I'm having a few issues getting the IR blaster to work. The app detects it but when I put a camera up to the button I'm not seeing any flashing.
Also how to we use the HTC photo edit?
Thanks again!
lordpelvis said:
First off I wanted to say thanks!
But I'm having a few issues getting the IR blaster to work. The app detects it but when I put a camera up to the button I'm not seeing any flashing.
Also how to we use the HTC photo edit?
Thanks again!
Click to expand...
Click to collapse
What IR app are you using? I'm using Smart Remote and it is working perfectly. As for the camera, sorry, but we lost pretty much all functionality with the GPe camera.
I've tried power IR and a few others. Have a link to the remote you're using?
Sent from my HTC One_M8 using xda app-developers app
---------- Post added at 11:01 AM ---------- Previous post was at 10:54 AM ----------
I actually bought the app and nothing happens.
Sent from my HTC One_M8 using xda app-developers app
You can download the HTC TV app from the playstore.. Again.. To remind you guys.. That type of discussion is off topic and does not belong in the thread.
Sent from my HTC One_M8 using Tapatalk
I did want to mention that when trying to flash the RUU, I did get a second "error" after the listed first one. I've attached the code from ADB below.
Code:
Daniels-iMac:~ Daniel$ fastboot flash zip /Users/Daniel/Downloads/RUU-HTC_One_M8_GE-1.16.1700.16.zip
target reported max download size of 1830715392 bytes
sending 'zip' (510598 KB)...
OKAY [ 20.133s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=9
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,76
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,6
(bootloader) [RUU]UZ,adsp,13
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,27
(bootloader) [RUU]UZ,adsp,34
(bootloader) [RUU]UZ,adsp,41
(bootloader) [RUU]UZ,adsp,48
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,61
(bootloader) [RUU]UZ,adsp,68
(bootloader) [RUU]UZ,adsp,74
(bootloader) [RUU]UZ,adsp,81
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,94
(bootloader) [RUU]UZ,adsp,99
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,26
(bootloader) [RUU]WP,adsp,53
(bootloader) [RUU]WP,adsp,79
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,6
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,18
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,33
(bootloader) [RUU]UZ,boot,43
(bootloader) [RUU]UZ,boot,55
(bootloader) [RUU]UZ,boot,62
(bootloader) [RUU]UZ,boot,68
(bootloader) [RUU]UZ,boot,74
(bootloader) [RUU]UZ,boot,80
(bootloader) [RUU]UZ,boot,87
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,99
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,8
(bootloader) [RUU]UZ,recovery,16
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,37
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,60
(bootloader) [RUU]UZ,recovery,68
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,85
(bootloader) [RUU]UZ,recovery,93
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,66
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,20
(bootloader) [RUU]UZ,sp1,41
(bootloader) [RUU]UZ,sp1,77
(bootloader) [RUU]UZ,sp1,97
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 40.913s
For those who may think something is wrong, it may not be the case. Although I received the error above, my phone continued to go through the process of flashing the RUU. I was patient and let it finish. The last step running the "fastboot reboot" command will not work as I was at a black screen that looked like fastboot except I had none of the usual fastboot options (hboot, etc.), just the listing of the hardware info (model, CID, etc.). I held the power button for several seconds until the phone shut off completely. Turned it back on and it booted up fine. Ran through the setup process and everything seems to be working fine. I will update if my phone explodes or anything else I notice is wrong, but otherwise it's been great so far. Thanks graffixnyc!
Thanks for this. I did this and want to know what app do you recommend for visual voicemail? The original app was great. Anyway I can download the one that came with the phone? Thanks
xoulu said:
Thanks for this. I did this and want to know what app do you recommend for visual voicemail? The original app was great. Anyway I can download the one that came with the phone? Thanks
Click to expand...
Click to collapse
Use Google voice for vvm. It will even text you a transcription of the phone message.
Sent from my HTC One_M8 using Tapatalk
Hey guys, I'm going to close this thread and ask you guys that you use the main thread in the m8 section (the RUU is the same) It's just easier for me to maintain one thread instead of 3 so head on over to the main thread: http://forum.xda-developers.com/showthread.php?t=2708589
I bought a Redmi Note 5 6 months ago.Last night i was watching youtube but I recieved a low battery warning so I paused the video and put mobile in sleep because I didn't wanted to charge it for like 6 hours.Next morning it was switched off I though IT was already low on battery maybe thats why the battery died.So I charged it and turned it on but its not going any further than the MI logo screen.
I have very important data and pics in there thats why I can't format it.Please help me to get back my data.All the pics I took in last 8 years its all in there.Unfortunetely I don't have a backup (Maybe I will have to regret it for the rest of my life or maybe if anyone of you guys can help me so that I don't have to regret it for the rest of my life).Its booting in MI recovery 3.0 which only gives the option to wipe all data and its also booting into fastboot mode.It doesn't have root access and the bootloader is locked.But the data is too important.I am literally crying as I am typing this post.Please HELP ME!!
Somewhere deep inside I know its the youtube temp data which is causing the problem but I don't know what to do.I will do anything just tell me what to do please.Service center clearly said that they can't save the data.You guys are my last HOPE.Please Do Something.Can I do anything through Fastboot Mode.How do they install OTA updates without deleting the DATA.If you guys will help me get my old life back you will for sure go to heaven!!
THANKS!!!
AND DAMN ME FOR NOT TAKING ANY BACKUP . . . .
Hi , you can try to backup your data with Mi Assistant ( Mi PC Suite)
download from here inside your PC:
http://pcsuite.mi.com/
Boot your device into Recovery mode , you should see :
Main Menu
- Recovery
- Wipe Data
- Connect with Mi Assistant ( click on that and plug the USB cable in PC )
Wait for drivers to be installed , and next you have in this post for Backing up data : )...
https://webcazine.com/14790/how-to-back-up-and-restore-your-xiaomi-device-using-mi-pc-suite/
After you do backup , you can Wipe data from recovery or to update your device using Mi PC Suite .
Good Luck : )
Thanks For Replying. You have no idea how much this means to me. . .
Teddy Lo said:
Hi , you can try to backup your data with Mi Assistant ( Mi PC Suite)
download from here inside your PC:
Boot your device into Recovery mode , you should see :
Main Menu
- Recovery
- Wipe Data
- Connect with Mi Assistant ( click on that and plug the USB cable in PC )
Wait for drivers to be installed , and next you have in this post for Backing up data : )...
After you do backup , you can Wipe data from recovery or to update your device using Mi PC Suite .
Good Luck : )
Click to expand...
Click to collapse
I already tried that.But it said device not supported.So I googled it then found out that MI PC suite doesn't support devices over lollipop.Please tell me if you have any other idea.Because you are the only one to even reply to my thread.I thought there is a lot of devlopers here who can easily help me out.But I see no one helping me.If you know someone with more knowledge please discuss this situation with them PLEASE!!
Can I flash stock ROM through fastboot on a locked bootloader without deleting internal storage content??
Please suggest something I can't live with this kind of stress.PLEASE!!
THANKS!!!
Try this :
put your device into fastboot mode, now On PC in fastboot command line write :
fastboot getvar all
You will be looking for version-main the number beside it is your firmware version
Now , once you find it , google on the internet for that firmware , and extract from that firmware just boot.img and flash with fastboot command line like for example:
fastboot flash boot boot.img and press Enter , I'm not 100% sure it will work like that but you can try ...
Teddy Lo said:
Try this :
put your device into fastboot mode, now On PC in fastboot command line write :
fastboot getvar all
You will be looking for version-main the number beside it is your firmware version
Now , once you find it , google on the internet for that firmware , and extract from that firmware just boot.img and flash with fastboot command line like for example:
fastboot flash boot boot.img and press Enter , I'm not 100% sure it will work like that but you can try ...
Click to expand...
Click to collapse
There is no such option like version-main however there is is an option called just version.
This is what it gives . . . .
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) token:nTFW03JTw76SJqewmdnCYQAA
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4232000
(bootloader) variant:QRD eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_DAISY1.0_20180914131349
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd43779e00
(bootloader) partition-type:cust:
(bootloader) partition-size:cust: 0x34000000
(bootloader) partition-type:logdump:
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:dpo:
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:msadp:
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x40000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x40000
(bootloader) partition-type:cmnlib64bak:
(bootloader) partition-size:cmnlib64bak: 0x40000
(bootloader) partition-type:cmnlib64:
(bootloader) partition-size:cmnlib64: 0x40000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x40000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x40000
(bootloader) partition-type:lksecappbak:
(bootloader) partition-size:lksecappbak: 0x20000
(bootloader) partition-type:lksecapp:
(bootloader) partition-size:lksecapp: 0x20000
(bootloader) partition-type:mcfg:
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:syscfg:
(bootloader) partition-size:syscfg: 0x80000
(bootloader) partition-type:mdtp:
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:dip:
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:mota:
(bootloader) partition-size:mota: 0x80000
(bootloader) partition-type:limits:
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-typeem:
(bootloader) partition-sizeem: 0x10000000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0xb00000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-typeDR:
(bootloader) partition-sizeDR: 0x8000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-type:dsp:
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:devcfgbak:
(bootloader) partition-size:devcfgbak: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x5400000
(bootloader) rollback_ver:0
(bootloader) serialno:8a7dd21a0904
(bootloader) kernel:lk
(bootloader) product:vince
all:
finished. total time: 1.172s
Click to expand...
Click to collapse
Please tell me what should I do now?
I even raised the guts to try fastboot erase cache But it said that the device is locked.I tried to flash twrp which I knew I can't on a locked bootloader still I tried but it said Partition flashing is not allowed.So I literally can't do ****.
Hi you have Xiaomi Note 5 also know as Xiaomi Note 5 Plus
MIUI Version 10
Security Patch : 2018.09.14
Code Name is : vince
Probably Redmi Note 5 India (MEl7) version
I didin't find any of those firmare with security patch 2018.09.14 in order to use the same boot.img in order to try to boot your device normaly .
But you can try this one :
https://ufile.io/cw9x3
flash with fastboot , or try to boot with fastboot
like fast bootboot boot boot.img ....
aasifehsan said:
I bought a Redmi Note 5 6 months ago.Last night i was watching youtube but I recieved a low battery warning so I paused the video and put mobile in sleep because I didn't wanted to charge it for like 6 hours.Next morning it was switched off I though IT was already low on battery maybe thats why the battery died.So I charged it and turned it on but its not going any further than the MI logo screen.
I have very important data and pics in there thats why I can't format it.Please help me to get back my data.All the pics I took in last 8 years its all in there.Unfortunetely I don't have a backup (Maybe I will have to regret it for the rest of my life or maybe if anyone of you guys can help me so that I don't have to regret it for the rest of my life).Its booting in MI recovery 3.0 which only gives the option to wipe all data and its also booting into fastboot mode.It doesn't have root access and the bootloader is locked.But the data is too important.I am literally crying as I am typing this post.Please HELP ME!!
Somewhere deep inside I know its the youtube temp data which is causing the problem but I don't know what to do.I will do anything just tell me what to do please.Service center clearly said that they can't save the data.You guys are my last HOPE.Please Do Something.Can I do anything through Fastboot Mode.How do they install OTA updates without deleting the DATA.If you guys will help me get my old life back you will for sure go to heaven!!
THANKS!!!
AND DAMN ME FOR NOT TAKING ANY BACKUP . . . .
Click to expand...
Click to collapse
If you can boot to recovery, you can wipe the cache partition, that will remove the temporary data. If there were any stock OTA updates released for the device, you can manually download the update and flash it via stock recovery via adb if your stock recovery has the "apply update from adb" or via sdcard if your recovery has "apply update from sdcard"
Note: this will not work with the full stock firmware file that is meant to be flashed via flashtool using PC, it has to be an official OTA update.zip in downloadable form.
Using fastboot isn't going to work unless you unlock your bootloader and if you unlock it that will wipe your data.
Sent from my LGL84VL using Tapatalk
I don't know your device, or if it is even possible while in some kind of bootloop. But try searching if its possible to boot into safe-mode.
Hello all, same problem.. Please if you have recovered data than tell me.
Hello all, I have also same problem. While watching YouTube my Redmi note 5 pro freezed. So I restarted and it stucked on mi logo. I tried recovery option by pressing volume up+power button , but it still came to mi logo. Only it shows fastboot. While charging it shows charging icon.
I tried mi flash tool but it shows flash xbl error.
Please help me soon.. I have important data in it of my exams. I don't have backup.
Xiaomi should also take a note on this.
Hello I have also same problem
There is important data and i am stuck on mi logo
i cant wipe data
if anyone have recovered the data plz plz give solution
Droid6pro said:
Hello I have also same problem
There is important data and i am stuck on mi logo
i cant wipe data
if anyone have recovered the data plz plz give solution
Click to expand...
Click to collapse
If you can access the phone by means of ADB then you may have a chance.
Interesting to see if it can be recovered.
If you do recover it, suspect malware is present.
Physically isolate phone/recover data from critical data drives.
I would have wrote it off by now... I've lost important data in other ways.
Learning from this is may be all you can do.
Always assume a OS drive will fail without warning... as well as the attached data drive.
Best wishes.
Sorry for my broken English,
Hey guys i just unlocked the boot-loader to install android 9.0 in it to just enjoy android PIE
and another day i didn't find that custom ROM stable so i flashed the android 7.0 nougat Rom in it through a video a guy posted(how to go back to stock Rom)
Stock Rom name - XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (this is the Rom that i had flashed)
and after that an OTA update just arrived and i quickly started downloading it and after it was going to update through restating the phone it just got hard bricked
i searched the whole day then got a fix through QCOM blank-flash file okayyy then went back to boot-loader,
and after this i have tried every moto g5 plus rom out there but none of it works
i have even tried to flashed the latest firmware
Name - XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
but still the boot-loader says security version downgrade,
.
.
This is exactly what it says :
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.501s
.
i have tried to boot into recovery through TWRP and the Stock and had done everything but it loops in this
{ Your device has been unlocked and cant be trusted.
to learn more , visit motorola bla bla bla
ID: bad key
Your device will boot in 5 seconds. }
.
.
.
.
This is the fastboot getvar all about bootloader
-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(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: ZY2243GTRP
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 00409F3400000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351892082852554
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 13 20: 0: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
.
.
.
please guys every help is appreciated
thank you in advanceeeee
Use this tool here: https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
It is old but it does the job for unbricking your phone. (Have tried it on my device)
outis151 said:
Use this tool here: https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
It is old but it does the job for unbricking your phone. (Have tried it on my device)
Click to expand...
Click to collapse
thank you but still nothing is working
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
devhere_ said:
thank you but still nothing is working
Click to expand...
Click to collapse
@outis151 is right, all you have to do is flash a new (new means in this case newer than the one you were on before you changed to a custom ROM).
I don't like tools so I would prefer to fastboot flash the latest available signed Motorola firmware which is 28.85.17.6.2:
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
I'm not sure if this is the correct one for your region but that doesn't matter, there won't be any further OTA updates in the future and the firmware is running on every Moto G5+, you just don't get any OTA updates anymore.
So take this flashall.bat :
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
(or write the commands by hand) and flash this firmware on your device (attention, your data will be lost).
This should make your device work again.
outis151 said:
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
Click to expand...
Click to collapse
Sent from my Moto G5 Plus using XDA Labs
outis151 said:
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
Click to expand...
Click to collapse
yes exactly this way but no luck still looping in bootloader
Wolfcity said:
@outis151 is right, all you have to do is flash a new (new means in this case newer than the one you were on before you changed to a custom ROM).
I don't like tools so I would prefer to fastboot flash the latest available signed Motorola firmware which is 28.85.17.6.2:
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
I'm not sure if this is the correct one for your region but that doesn't matter, there won't be any further OTA updates in the future and the firmware is running on every Moto G5+, you just don't get any OTA updates anymore.
So take this flashall.bat :
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
(or write the commands by hand) and flash this firmware on your device (attention, your data will be lost).
This should make your device work again.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
okay sir i have done the same way you told me to do but the same process is happening with this rom also
what should i do next?
devhere_ said:
okay sir i have done the same way you told me to do but the same process is happening with this rom also
what should i do next?
Click to expand...
Click to collapse
Directly after flashing that firmware take a recovery.log in TWRP and attach it here. You can grab it with TWRP terminal.You'll find the log in the root directory under cache/recovery/last_log.
To attach it here change the ending from log to txt or upload it to some kind of hoster or pastebin.
Most probably the OTA has downgraded your bootloader which could have caused a hard brick.
Have you tried to flash a custom ROM?
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Directly after flashing that firmware take a recovery.log in TWRP and attach it here. You can grab it with TWRP terminal.You'll find the log in the root directory under cache/recovery/last_log.
To attach it here change the ending from log to txt or upload it to some kind of hoster or pastebin.
Most probably the OTA has downgraded your bootloader which could have caused a hard brick.
Have you tried to flash a custom ROM?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
i cannot even boot into my recovery not stock nor TWRP
how can i attach that recovery.log here ??? if i could boot into twrp i"ll flash a custom rom but unfortunately i cannot boot into recovery
all i can do things is my boot-loader nothing else is working
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)
My system crashed and I can't do anything with fastboot(access denied). But I watched a video that if I can play the same rom it might work. Does anyone have this rom version of the moto g8 power?
version-bootloader: MBM-3.0-sofiar_retail-0f8934adaf-210928
version-baseband: M6125_43.45.03.48R SOFIA_LATAMDSDS_CUST
I've already searched the main google sites.
C:\Users\charl\Desktop\platform-tools> fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiar_retail-0f8934adaf-210928
(bootloader) product: sofiar
(bootloader) board: sofiar
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF5233S5VJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 9B49D2F1
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 353623111368835
(bootloader) imei2: 353623111368843
(bootloader) meid:
(bootloader) date: 08-15-2020
(bootloader) sku: XT2041-1
(bootloader) carrier_sku: XT2041-1
(bootloader) battid: SB18C64833
(bootloader) battery-voltage: 4099
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_retail/sofiar:11/R
(bootloader) ro.build.fingerprint[1]: PES31.Q4U-47-35-9/54bc43:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.11.r1-02100-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.48R SOFIA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.180-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue S
(bootloader) kernel.version[4]: ep 28 11:07:44 CDT 2021
(bootloader) git:xbl: MBM-3.0-sofiar_retail-1186df2c3-210928
(bootloader) git:xbl_config: MBM-3.0-sofiar_retail-1186df2c3-210928
(bootloader) git:rpm: MBM-3.0-sofiar_retail-2579863-210928
(bootloader) git:tz: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:hyp: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:devcfg: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:cmnlib: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:cmnlib64: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:keymaster: MBM-3.0-sofiar_retail-7bae8fe-210928
(bootloader) gitrov: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:abl: MBM-3.0-sofiar_retail-0f8934adaf-210928
(bootloader) git:qupfw: MBM-3.0-sofiar_retail-7c7ba69-210928
(bootloader) git:uefisecapp: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) frp-state: protected (144)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 4
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C65089
(bootloader) primary-display: tm_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.106s
What kind of moto g power is it? Can you still get into bootloader?
When I'm asking this what service was it bought under?
Your baseband and bootloader say that it is a sofia and a sofiar? did you make a backup first with rescue and smart assistant?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
that could be the right one, but if its not you can hard brick it. I got lucky I accidentally flashed my visible g power with the vzw 10 one thinking that'd work...
Mine is actually the sofia Retus builds.... Retus stands for no carrier....
if your not on any of the carriers listed id try retus first if you don't have a backup....
Whatever carrier you got your phone with at certain time of year try googling that with xda or duckduck go....
Also use latest version! https://github.com/Vachounet/moto_flash_toolhttps://github.com/Vachounet/moto_flash_tool
to flash a stockrom from the bootloader.....
I wish they had better guides here. Also save yourself some headache, I tried to use twrp and I'd just recommend to not use it. Use fastbootd instead...
There is no how to guide in here just grab the how to from whatever rom your downloading.
Be sure to flash a android 10 stock rom not a 11. All of the customs here are based on 10....
I swear it took me hrs of reading just to gather all of that intel and why they don't have a guide here for new people is beyond me....
revengesrage said:
... Retus stands for no carrier....
Click to expand...
Click to collapse
More precisely Retail US, which means the unbranded US version
revengesrage said:
What kind of moto g power is it? Can you still get into bootloader?
Click to expand...
Click to collapse
sofiar xt2041-1 64 gb pvt (from brazil). Yes, but flashing_lock :/ I can't run anything, access is always denied.
revengesrage said:
When I'm asking this what service was it bought under?
Click to expand...
Click to collapse
I didn't really understand the question, I'm translating it.
revengesrage said:
Your baseband and bootloader say that it is a sofia and a sofiar? did you make a backup first with rescue and smart assistant?
Click to expand...
Click to collapse
Yes, baseband sofia and bootloader sofiar_retail-0f8934adaf-210928. I didn't backup.
revengesrage said:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
that could be the right one, but if its not you can hard brick it. I got lucky I accidentally flashed my visible g power with the vzw
Click to expand...
Click to collapse
I'm traying flashing several roms, so far without success.
revengesrage said:
10 one thinking that'd work...
Mine is actually the sofia Retus builds.... Retus stands for no carrier....
if your not on any of the carriers listed id try retus first if you don't have a backup....
Whatever carrier you got your phone with at certain time of year try googling that with xda or duckduck go....
Also use latest version! https://github.com/Vachounet/moto_flash_toolhttps://github.com/Vachounet/moto_flash_tool
to flash a stockrom from the bootloader.....
I wish they had better guides here. Also save yourself some headache, I tried to use twrp and I'd just recommend to not use it. Use fastbootd instead...
There is no how to guide in here just grab the how to from whatever rom your downloading.
Be sure to flash a android 10 stock rom not a 11. All of the customs here are based on 10....
I swear it took me hrs of reading just to gather all of that intel and why they don't have a guide here for new people is beyond me....
Click to expand...
Click to collapse
I need the exact rom to make the cell come back to life. :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:/
EDIT: Looking at your first post again, looks like your bootloader is locked.... if it is
EDIT" If you skipped unlocking your bootloader theres a guide on here for unlocking the bootloader.
Since you still have access to your bootloader refer to that guide and unlock the ***** and then jump back to these instructions....
according to that picture you shared your using the wrong stock rom. I love rescue and smart assistant hehe. Give this one a shot here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
or more specifically, since your trying to go custom use this link below.
Download BELOW!
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Also since you can get into the regular boot loader follow these instructions
below...
Download this
moto_flash_tool_windows_v0.6.6.zip | by Vache for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
extract to folder on desktop
copy zip from above into firmware folder
"Firmware Folder Example"
moto_flash_tool_windows\firmware\XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
"firmware folder example"
on phone hold vol - and power key to enter bootloader
on pc run moto_flash_tool-win.exe from within moto_flash_tool_windows
if it doesn't run, redownload the tool and reextract it again using a different zip program, reboot pc......
select flash/extract stock firmware
and choose your firmware in the folder.
Let the process run till your phone reboots a couple of times, Don't interrupt it as it will take 5-10 min to do its thing. the first reboot you'll see the software do is bring you into fastbootd and then flash a couple more things. So its going to do all the work on auto pilot....
After you do all of this, DO NOT USE TWRP! If you do don't flash it and don't reboot from side "B!" it will BRICK...
Good luck....
revengesrage said:
EDIT: Looking at your first post again, looks like your bootloader is locked.... if it is
EDIT" If you skipped unlocking your bootloader theres a guide on here for unlocking the bootloader.
Click to expand...
Click to collapse
I can't activate oem unlocking and usb debugging because I can't access the system which is broke. And as a consequence I can't unlocking the bootloader.
revengesrage said:
Since you still have access to your bootloader refer to that guide and unlock the ***** and then jump back to these instructions....
Click to expand...
Click to collapse
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_retail/sofiar:11/R
(bootloader) ro.build.fingerprint[1]: PES31.Q4U-47-35-9/54bc43:user/rele
I have a question, why can't I find a rom with the same specification? I've looked everywhere.
there are several roms.... ex: RPES31.....QPES31 ........less than I want. (PES31.Q4U-47-35-9). <----
(bootloader) version-bootloader: "MBM-3.0-sofiar_retail-0f8934adaf-210928" <----
The only way to bring my cellphone to life is to get this rom that I update in motorola.
revengesrage said:
according to that picture you shared your using the wrong stock rom. I love rescue and smart assistant hehe. Give this one a shot here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
or more specifically, since your trying to go custom use this link below.
Download BELOW!
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Also since you can get into the regular boot loader follow these instructions
below...
Download this
moto_flash_tool_windows_v0.6.6.zip | by Vache for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
extract to folder on desktop
copy zip from above into firmware folder
"Firmware Folder Example"
moto_flash_tool_windows\firmware\XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
"firmware folder example"
on phone hold vol - and power key to enter bootloader
on pc run moto_flash_tool-win.exe from within moto_flash_tool_windows
if it doesn't run, redownload the tool and reextract it again using a different zip program, reboot pc......
select flash/extract stock firmware
and choose your firmware in the folder.
Let the process run till your phone reboots a couple of times, Don't interrupt it as it will take 5-10 min to do its thing. the first reboot you'll see the software do is bring you into fastbootd and then flash a couple more things. So its going to do all the work on auto pilot....
After you do all of this, DO NOT USE TWRP! If you do don't flash it and don't reboot from side "B!" it will BRICK...
Good luck....
Click to expand...
Click to collapse
The stock rom your referring to is this one. " You really can't figure out that rescue and smart assistant shows your ro carrier as retbr?" I'm being really nice about giving you the same location and everything on it. In Fact I'd say your pretty go lucky that the same one is there.
I'm gonna be a good human here and give you the link again.
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_11_RPES31.Q4U-47-35-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Your phone is not retail it is RETBR. look at the 47 35 9. I forgot about checking the unlock option in the developer options. Actually you don't need usb debugging. If it is retail go get it! Go TRY IT! all the stock roms are there....
If I were You I'd try to load this stock rom through rescue and smart assistant first. If it don't work then also try the moto flash tools.
if you don't know how to put the stock rom there google it...
I showed you the links and pointed out that your retbr. Its up to you to figure this mess out that you created now.
revengesrage said:
The stock rom your referring to is this one. " You really can't figure out that rescue and smart assistant shows your ro carrier as retbr?" I'm being really nice about giving you the same location and everything on it. In Fact I'd say your pretty go lucky that the same one is there.
I'm gonna be a good human here and give you the link again.
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_11_RPES31.Q4U-47-35-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Your phone is not retail it is RETBR. look at the 47 35 9. I forgot about checking the unlock option in the developer options. Actually you don't need usb debugging. If it is retail go get it! Go TRY IT! all the stock roms are there....
If I were You I'd try to load this stock rom through rescue and smart assistant first. If it don't work then also try the moto flash tools.
if you don't know how to put the stock rom there google it...
I showed you the links and pointed out that your retbr. Its up to you to figure this mess out that you created now.
Click to expand...
Click to collapse
Each folder is an attempt. I've tested almost everything, I think it's time to give up.
Anyway, I appreciate it, I really created the problem and it's up to me to solve it. Thanks!
colingbcc said:
View attachment 5455045
Cada pasta é uma tentativa. Já testei quase tudo, acho que é hora de desistir.
De qualquer forma, agradeço, realmente criei o problema e cabe a mim resolvê-lo. Obrigado!
Click to expand...
Click to collapse
olá queria saber se voce conseguiu resolver este problema?
LEVI TEC said:
olá queria saber se voce conseguiu resolver este problema?
Click to expand...
Click to collapse
Please use English on XDA
Google translation below.
LEVI TEC said:
Hi, I was wondering if you managed to solve this problem?
Click to expand...
Click to collapse
sd_shadow said:
Por favor, use o inglês no XDA
Tradução do Google abaixo.
Click to expand...
Click to collapse
hello I wanted to know if the problem was solved after I have a moto g8 power I tried to downgrade from android 11 to android 10 and the device simply does not turn on or connected to the charger it does not charge nor does the pc recognize it, can someone help me and me explain what happened, thank you in advance
LEVI TEC said:
hello I wanted to know if the problem was solved after I have a moto g8 power I tried to downgrade from android 11 to android 10 and the device simply does not turn on or connected to the charger it does not charge nor does the pc recognize it, can someone help me and me explain what happened, thank you in advance
View attachment 5553437
Click to expand...
Click to collapse
Managed to solve?