Related
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.
I found it support qualcomm 9008. We can flash twrp for A6 then get root.
I bought fastboot ROM from taobao.com cost my 15$, I hope someone can make twrp in QPST 9008.
https://drive.google.com/file/d/1D3R531XnI52dzwHL21rRTGszs12on_sr/view
C:\Program Files (x86)\>fastboot getvar all
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3996
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B445F7800
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x148000000
(bootloader) secure:yes
(bootloader) serialno:5242da66
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.060s
We need twrp for hisense A6，someone can help with it? I want to do it but I dont' know how to do that.
I have the rom of current version and wonder how to make twrp....
You can get it free on the official forum of Hisense.
evilwjg said:
I have the rom of current version and wonder how to make twrp....
You can get it free on the official forum of Hisense.
Click to expand...
Click to collapse
Hisense official doesn't releases fastboot flashing ROM, only offers SD flashing ROM including 2 bin files. So please use my ROM.
yklaxds said:
Hisense official doesn't releases fastboot flashing ROM, only offers SD flashing ROM including 2 bin files. So please use my ROM.
Click to expand...
Click to collapse
You are right,I misunderstand of them.Thanks!
hi thank you for open qpst rom.
I made gapps rom by your rom.
working in progress
most of function working.
I will open gapps rom.
it is not working ota update. so old version only
if you can accuire latest rom.
let me know thanks.
joygram said:
hi thank you for open qpst rom.
I made gapps rom by your rom.
working in progress
most of function working.
I will open gapps rom.
it is not working ota update. so old version only
if you can accuire latest rom.
let me know thanks.
Click to expand...
Click to collapse
Does hisense deleted some apps? I dont know why I installed google play store and it not work(just always loading……). And does A6 rooted possiblely?
Thanks.
I don't root but modified system.img
and working all of them.
please wait. I'll open custom rom.
hisense a6 custom rom thread
https://forum.xda-developers.com/android/general/hisense-a6-l1488-6-4-01-custom-rom-t3932041
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
This Moto G Power is currently running QPMS30.80-63-6-8-3 and therefore I downloaded XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, patched the boot.img with Magisk and wrote to the phone with fastboot.
Phone on reboot has no touch screen control and erroneously indicates no battery charge. Appears to be a symptom of mismatch of boot.img from downloaded firmware and what is actually on the phone. I don't know how as I downloaded the same version. Obtained firmware from Lolinet. It is a carrier unlocked phone.
Suggestions to other ops in other posts refer to Lenovo's Rescue and Smart Assistant (LRSA) however I have no Microsoft Windows machines in my environment. I have access to Mac and Linux.
Im not sure why the firmware was a mismatch. My phone clearly indicates it is model model XT2041-4 and QPMS30.80-63-6-8-3 which should be a match for what I downloaded. Undocumented variants?
How can I recover this phone using a Linux machine since LRSA is not an option? What are my options? It was my intention to simply root patch to boot.img with magisk (Ive done before with other phones) and apply with fastboot.
What I have tried thus far: booting with unpatched boot.img .. fail and downloading firmware from another source, writing boot.img .. fail.
moto g power
model XT2041-4
software: US Retail
Android 10
QPMS30.80-63-6-8-3
Phone did not come as QPMS30.80-63-6-8-3 it was OTA updated to QPMS30.80-63-6-8-3.
coltswalker said:
This Moto G Power is currently running QPMS30.80-63-6-8-3 and therefore I downloaded XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, patched the boot.img with Magisk and wrote to the phone with fastboot.
Phone on reboot has no touch screen control and erroneously indicates no battery charge. Appears to be a symptom of mismatch of boot.img from downloaded firmware and what is actually on the phone. I don't know how as I downloaded the same version. Obtained firmware from Lolinet. It is a carrier unlocked phone.
Suggestions to other ops in other posts refer to Lenovo's Rescue and Smart Assistant (LRSA) however I have no Microsoft Windows machines in my environment. I have access to Mac and Linux.
Im not sure why the firmware was a mismatch. My phone clearly indicates it is model model XT2041-4 and QPMS30.80-63-6-8-3 which should be a match for what I downloaded. Undocumented variants?
How can I recover this phone using a Linux machine since LRSA is not an option? What are my options? It was my intention to simply root patch to boot.img with magisk (Ive done before with other phones) and apply with fastboot.
What I have tried thus far: booting with unpatched boot.img .. fail and downloading firmware from another source, writing boot.img .. fail.
moto g power
model XT2041-4
software: US Retail
Android 10
QPMS30.80-63-6-8-3
Phone did not come as QPMS30.80-63-6-8-3 it was OTA updated to QPMS30.80-63-6-8-3.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
```
(bootloader) version-bootloader: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) date: 11-03-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-63-6-8-3/3a94d:user/release
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Oct 8 14:0
(bootloader) kernel.version[3]: 2:49 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-201101
(bootloader) git:tz: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:hyp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:devcfg: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:keymaster: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) gitrov: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:abl: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-201101
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
```
coltswalker said:
```
(bootloader) version-bootloader: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) date: 11-03-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-63-6-8-3/3a94d:user/release
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Oct 8 14:0
(bootloader) kernel.version[3]: 2:49 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-201101
(bootloader) git:tz: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:hyp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:devcfg: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:keymaster: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) gitrov: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:abl: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-201101
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
```
Click to expand...
Click to collapse
Looks ok to me.
Maybe the boot.img you downloaded is corrupt.
Did the .zip look like right size?
I guess I would download the next newest firmware and try to flash that boot.img
If that works flash the rest.
I have some Windows instructions Linux should be the same.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
I am confused by reading your response. By "next newest" you mean to go backwards to the previous firmware version?
You say "flash boot.img if that works then" so you mean to flash an older boot.img from the previous firmware onto
the phone which is running a newer firmware? That seems like a bad idea since the boot.img from a previous firmware would not be of the same version. Finally it looks like you advise to flash the entire firmware if the phone is
able to boot with the boot.img from previous.
Id like to clarify before proceeding.
On another note: In all of the research I have done online with this model there are some sites that confuse sofia and sofiar as I have seen firmware for G advising sofiar which is clearly wrong. I hope that lolinet is offering the true sofia firmware and not that for sofiar G8 as I have a G not G8. As I understand the model XT2041-4 is the G however some other sources online have it the other way. It is unfortunate that Motorola / Lenovo made the distinction of models of such similar hardware so confusing.
coltswalker said:
I am confused by reading your response. By "next newest" you mean to go backwards to the previous firmware version?
Click to expand...
Click to collapse
Yes
You say "flash boot.img if that works then" so you mean to flash an older boot.img from the previous firmware onto
Click to expand...
Click to collapse
yes
the phone which is running a newer firmware? That seems like a bad idea since the boot.img from a previous firmware would not be of the same version.
Click to expand...
Click to collapse
I meant if it flashes without error, not fit boots.
Finally it looks like you advise to flash the entire firmware if the phone is
able to boot with the boot.img from previous.
Id like to clarify before proceeding.
Click to expand...
Click to collapse
You posted
Code:
writing boot.img .. fail.
If you could flash the older boot.img maybe flashing older firmware will get the phone booting again.
You also could compare the older boot.img size with the newer.
I hope that lolinet is offering the true sofia firmware and not that for sofiar G8 as I have a G not G8.
Click to expand...
Click to collapse
Unlikely they got it wrong
see
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
sd_shadow said:
You posted
Code:
writing boot.img .. fail.
If you could flash the older boot.img maybe flashing older firmware will get the phone booting again.
You also could compare the older boot.img size with the newer.
Unlikely they got it wrong
see
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
Click to expand...
Click to collapse
I am sorry I think I failed to articulate that well enough. The flash process itself did not fail. I have had no trouble writing to the phone from the computer in any event. What failed was seeking a solution to the problem of the phone not responding to touch screen activity. Every time I have used "fastboot" to write to the phone the write process itself completed successfully.
So, what I wanted to test on that occasion was if Magisk corrupted the boot.img so I flashed the unpatched boot.img, which also resulted in the same problem of the phone not responding to touch screen activity. This way I eliminated Magisk as the culprit and decided that the firmware I got from lolinet was not an exact match for my phone or firmware version.
Also, I have read "all about official firmware and where to find it" and I note some issues with that document. Firstly, it is very Microsoft Windows tool centric. Secondly, it fails to recognize that there are two models of the Moto G like mine for US market, one having more memory to better match the G8, although it is still a Moto G.
If the firmware from lolinet was an exact match, I would not be in this sticky situation as of right now the phone is rather useless to me. I have no idea how to obtain a boot.img that matches the phone firmware since the one from loli and one from another place neither worked thus far.
coltswalker said:
I am sorry I think I failed to articulate that well enough. The flash process itself did not fail. I have had no trouble writing to the phone from the computer in any event. What failed was seeking a solution to the problem of the phone not responding to touch screen activity. Every time I have used "fastboot" to write to the phone the write process itself completed successfully.
So, what I wanted to test on that occasion was if Magisk corrupted the boot.img so I flashed the unpatched boot.img, which also resulted in the same problem of the phone not responding to touch screen activity. This way I eliminated Magisk as the culprit and decided that the firmware I got from lolinet was not an exact match for my phone or firmware version.
Also, I have read "all about official firmware and where to find it" and I note some issues with that document. Firstly, it is very Microsoft Windows tool centric. Secondly, it fails to recognize that there are two models of the Moto G like mine for US market, one having more memory to better match the G8, although it is still a Moto G.
If the firmware from lolinet was an exact match, I would not be in this sticky situation as of right now the phone is rather useless to me. I have no idea how to obtain a boot.img that matches the phone firmware since the one from loli and one from another place neither worked thus far.
Click to expand...
Click to collapse
I was having issues reverting to stock boot.img earlier today. I had forgot that it needed to be flashed with fastbootd instead of fastboot. As far as I know, the only way to get into fastbootd is from the stock recovery.
justinr34gtr said:
I was having issues reverting to stock boot.img earlier today. I had forgot that it needed to be flashed with fastbootd instead of fastboot. As far as I know, the only way to get into fastbootd is from the stock recovery.
Click to expand...
Click to collapse
Code:
fastboot reboot fastboot
I stupidly locked my OEM and Flashing ability before wiping the disk through the bootloader, after a while of trying to get an operating system back on the phone and failing miserably due to the flashing being locked, the error I mostly seen :FAILED (remote failure). Now, I cant even get into Recovery Mode, it just goes to the Fastboot Flash Mode again. I can't flash or boot any disc, it wont let me unlock flashing or unlock the OEM again, even though i have the unlock code..
Is there anyway to get an operating system on my phone again? I just switched from xfinity to boost and it was working good all but some apps didnt work.
When you say you locked your OEM, did you re-lock your bootloader with a fastboot command or simply re-lock the OEM unlocking switch in Developer options in Settings? In the first case, you most likely now have an expensive paperweight - in the second case you may still be able to recover. Suggest you go to the Lolinet telegram channel and give a detailed description of what you did, what firmware version you were on and the output from the fastboot command: getvar all
Try booting into twrp but not flashing if you haven't on the off chance. Fastboot boot recovery (twrp.img). If that doesn't work try getting the unlock code from fastboot oem get_unlock_data and get the unlock code from Motorola again. If that doesn't work try getting it into edl mode and blank flash it with one of the blank-flash roms from here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work come back here and share your results. I agree share the "getvar all" command will be helpful to know more just delete your IMEI before posting
Update: I can now access the recovery boot option from the initial bootloader
lolinet seems to be down for me and everything I try results in an error
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.522s]
booting...
(bootloader) Fastboot boot command is not available in locked device
FAILED (remote failure)
finished. total time: 1.603s
fastboot oem unlock (the key from moto website)
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.083s
fastboot getvar all info
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-borneo_retail-22355d27121-22
(bootloader) version-bootloader[1]: 0601
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(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_KAMORTA_H 1.0
(bootloader) serialno: ZY22D68BLF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x96
(bootloader) uid: 6F927615
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35689$%$&%*$&%*(
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 08-21-2021
(bootloader) sku: XT2117-4
(bootloader) carrier_sku: XT2117-4
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4315
(bootloader) iccid: 89148000007142793377
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: comcast
(bootloader) ro.build.fingerprint[0]: motorola/borneo_retail/borneo:11/R
(bootloader) ro.build.fingerprint[1]: ZBS31.Q2-143-27-13/b542c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_29.11.02.95.01R BORNEO_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-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 Wed J
(bootloader) kernel.version[4]: un 1 01:20:19 CDT 2022
(bootloader) git:xbl: MBM-3.0-borneo_retail-df5e9403f-220601
(bootloader) git:xbl_config: MBM-3.0-borneo_retail-df5e9403f-220601
(bootloader) git:abl: MBM-3.0-borneo_retail-22355d27121-220601
(bootloader) git:rpm: MBM-3.0-borneo_retail-834e250d-220601
(bootloader) git:tz: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:hyp: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:devcfg: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:keymaster: MBM-3.0-borneo_retail-6bd3d249-220601
(bootloader) git:storsec: MBM-3.0-borneo_retail-6bd3d249-220601
(bootloader) git:uefisecapp: MBM-3.0-borneo_retail-6bd3d249-220601
(bootloader) gitrov: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:qupfw: MBM-3.0-borneo_retail-d308e84-220601
(bootloader) frp-state: protected (77)
(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: 6
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D12963
(bootloader) primary-display: tm_ili9881x_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.178s
snuffinaround said:
Try booting into twrp but not flashing if you haven't on the off chance. Fastboot boot recovery (twrp.img). If that doesn't work try getting the unlock code from fastboot oem get_unlock_data and get the unlock code from Motorola again. If that doesn't work try getting it into edl mode and blank flash it with one of the blank-flash roms from here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work come back here and share your results. I agree share the "getvar all" command will be helpful to know more just delete your IMEI before posting
Click to expand...
Click to collapse
not sure how to access this edl mode any tips?
withinwaves said:
not sure how to access this edl mode any tips?
Click to expand...
Click to collapse
Your problem is here in the getvar all : "(bootloader) securestate: flashing_locked"
First you'll have to download and install QDLoader_HS_USB_Driver_64bit_Setup.exe
In fastboot mode, try this command: fastboot oem edl
- other wise you'll have to use button combinations - you can google for a how to.
First, however, you might want to down load and try the
Rescue and Smart Assistant Tool - Motorolaif you haven't already, since you can get into fastboot mode.
Re-locking your bootloader is a big no-no ...
I repeat, if you re-locked your bootloader, you may now have an expensive paperweight - again, I suggest you get on the Lolinet Telegram channel - they have some VERY experienced core members who know their stuff when it comes to these problems, unlike some of the members here.
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Do you have download instructions for getting QDLoader_HS.. and installing? After it installs it doesn't seem to do anything.. fastboot oem edl prints "waiting for devices..." and never attaches to the phone. Thanks in advanced
sdembiske said:
Your problem is here in the getvar all : "(bootloader) securestate: flashing_locked"
First you'll have to download and install QDLoader_HS_USB_Driver_64bit_Setup.exe
In fastboot mode, try this command: fastboot oem edl
- other wise you'll have to use button combinations - you can google for a how to.
First, however, you might want to down load and try the
Rescue and Smart Assistant Tool - Motorolaif you haven't already, since you can get into fastboot mode.
Re-locking your bootloader is a big no-no ...
I repeat, if you re-locked your bootloader, you may now have an expensive paperweight - again, I suggest you get on the Lolinet Telegram channel - they have some VERY experienced core members who know their stuff when it comes to these problems, unlike some of the members here.
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Click to expand...
Click to collapse
withinwaves said:
Do you have download instructions for getting QDLoader_HS.. and installing? After it installs it doesn't seem to do anything.. fastboot oem edl prints "waiting for devices..." and never attaches to the phone. Thanks in advanced
Click to expand...
Click to collapse
You really must learn to Google ... a simple search could have yielded this ...
Link: https://www.droidwin.com/boot-android-edl-mode/
any further questions, log in to the Lolinet telegram channel and get help there.
P.S. It is a long standing XDA tradition to use the Like (formerly known as the Thanks button), bottom right of the post when you are logged in - please learn to use it when members try to help or provide directions, roms etc., for download.
sdembiske said:
You really must learn to Google ... a simple search could have yielded this ...
Link: https://www.droidwin.com/boot-android-edl-mode/
any further questions, log in to the Lolinet telegram channel and get help there.
P.S. It is a long standing XDA tradition to use the Like (formerly known as the Thanks button), bottom right of the post when you are logged in - please learn to use it when members try to help or provide directions, roms etc., for download.
Click to expand...
Click to collapse
Thanks for the response(s), I've spent a few hours now searching google for the solution. There are a few ways to fix this problem and yet some website are kind of scammy and may have resulted in increasing the severity of my phones issue. I truly do appreciate the help provided thus far but I haven't found a solution yet. Once I do I will surely hit the thanks button. Honestly downloading all these files and installing them may have bricked my phone so I want to find the proper solution before I express my gratitude. I will be sure to update you all once I've locked down the solution that best suits my problem, thanks for taking the time to try and understand my phones problem!
OK made some headway, turns out I was in edl mode this whole time but how do I boot to TWRP or install operating system from edl mode?
{
"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"
}
withinwaves said:
De acuerdo, hice algunos avances, resultó que estuve en modo edl todo este tiempo, pero ¿cómo iniciar TWRP o instalar el sistema operativo desde el modo edl?
[ADJUNTAR=completo]5707961[/ADJUNTAR]
Click to expand...
Click to collapse
puedo ayudarte a llegar a mi facebook Licandro Burzum y tratare de revivirlo