Related
friends, how are you?
It's the following .. I have a serious problem with my Moto G5.
When he went to do the update for Oreo he gave a problem ... Of which I can not leave.
It starts in fastboot mode or attempts to initialize Android but stops on screen (M) as picture.
The bootloader is locked, I tried to unlock by cmd and put the key sent by the motorola, signaled as if it worked and continues as (oem_locked).
I do not have root, my bootloader is locked, and I can not access recovery despite entering fastboot mode.
I tried installing several roms by adb, but I could not succeed with any (Always giving FAILED REMOTE).
Yesterday until it managed to enter the initial configuration of the android (where it places the wifi) but then restarted and never again.
I've tried everything a little bit, and I could not succeed with anything.
Help me, please, I do not know what else to do!
Thank you
:confuso:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
.....
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
TheFixItMan said:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
Click to expand...
Click to collapse
sonmota said:
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
Click to expand...
Click to collapse
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
....
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
TheFixItMan said:
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
sonmota said:
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
Click to expand...
Click to collapse
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
I saw there was an October update in the ROM. I will try here in the community this ROM and try to blink and bring the result here ..
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
TheFixItMan said:
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
Click to expand...
Click to collapse
sonmota said:
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
Click to expand...
Click to collapse
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
I can not get into recovery. Would not it be a problem with the motherboard?
TheFixItMan said:
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
Click to expand...
Click to collapse
sonmota said:
I can not get into recovery. Would not it be a problem with the motherboard?
Click to expand...
Click to collapse
Could well be
As long as gpt flashed successfully without giving a downgrade warning which will call it to fail then the recovery part of the firmware should flash and you should have access to recovery mode via entering recovery from bootloader then holding power button and volume up at the picture of the android screen
It could be a motherboard issue but since you have no problem getting into bootloader it's more likely a firmware issue/user error
Preparation:
Notes are important, please pay attention
ONLY use stock USB-A to USB-C cable
I have tried the stock cable from Axon 7, fail fail and more fail, don't make this mistake
DON'T store flash files on USB storage.
fastboot will timeout if your flash files are stored at a slow storage device such as a USB drive, or slow computer with eMMC drive
Download and extract the patched MSM download tool and related flash files (credit)
Download and extract TWRP 3.4.0-2 Test by mauronofrio (credit)
Download and extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip (credit)
Optional: Unlock bootloader at this official OnePlus page with those steps
automated process you have to wait 1 whole week for
if you take this route, you will have an easier time get into EDL
Optional for Driver and boot into EDL: Download and extract the TOOL ALL IN ONE (credit) (untested) (can skip this step if you have driver and completed preparation step 7)
Flash Operations:
Run the MSM executable with Administrator Privilege
Boot into bootloader on 7T (if you already have adb connection, adb reboot bootloader would work as well)
Restart device: Vol Up + Power
Boot into recovery: when system reboot from step 4, immediately press and hold Vol Down + Power until recovery screen
Boot into fastboot: English -> Advanced -> fastboot
Boot into EDL on 7T
If you have OnePlus unlock token from Preparation step 7
Connect USB cable to both PC and 7T
on MSMDownloadTool, click Enum to display your device
fastboot flash cust-unlock unlock_token.bin
fastboot oem unlock
fastboot boot twrp.img
when TWRP boot: adb reboot edl
on MSMDownloadTool it will now show connected
If you don't want to wait for token (untested)
Use TOOL ALL IN ONE
Or, hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts (credit)
When MsmDownloadTool display connected, hit Start until 7T display CORRUPT message (normal behavior) and reboot into fastboot by ITSELF. If your 7T doesn't get into fastboot screen automatically, something is wrong with previous step, redo EDL flashing and do NOT proceed.
Start Power-Shell with Administrator Privilege and go to the extracted path of 10.0.13-global-oneplus7toxygen_14.o.19_ota_019_all_2009281709_1026-fastboot.zip (DO NOT USE DOS, it will fail you miserably)
Unlock bootloader: .\fastboot flashing unlock_critical (suggested, because it works, so I didn't test the oem unlock method)
To avoid potential conflict with installed fastboot binary (possibly lower version), you can either
edit the flash-all.bat, and change fastboot to .\fastboot, such that only the local fastboot binary will be invoked instead of pathed binary
OR run those identical commands with copy and paste
Code:
.\fastboot -w
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot flash reserve reserve.img
.\fastboot flash recovery recovery.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot reboot fastboot
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cmnlib cmnlib.img
.\fastboot flash cmnlib64 cmnlib64.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash LOGO LOGO.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash odm odm.img
.\fastboot flash oem_stanvbk oem_stanvbk.img
.\fastboot flash opproduct opproduct.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash storsec storsec.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot flash system system.img
.\fastboot flash vendor vendor.img
.\fastboot flash product product.img
.\fastboot reboot
Few notes
User data is wiped, again, lol
reserve partition flashing can produce error msg: FAILED (remote: '(reserve_a) No such partition'), it is OK but others should not Fail
Device will reboot once during the flashing process
After reboot, device will NOT go into fastboot screen but instead go into stock recovery screen, however fastboot will pick up and resume flashing the rest, ONLY IF YOU ARE UNDER POWER-SHELL, so DO NOT flash under DOS
if anything else fails besides the reserve partition, repeat step 7
Device will boot into system, you may use the OS updater to upgrade to the lastest firmware then relock bootloader or proceed with root with Magisk
Hope this will save you some precious time. Major kudos for previous contributions from post 1 and post 2.
All steps are recorded from memory, please let me know if any mistakes are in need of correction.
Tested working on Dec 5, 2020
I have followed this method (and literally anything else I can find) to a T and the farthest I get is when flashing the ROM, I get "Flashing is not allowed for critical partitions" - which I can only find people saying that means the bootloader needs to be unlocked, but it is?! It's definitely, fully unlocked. No matter what I try I can't get around that error during the flashing process and it stays stuck on the T-Mobile ROM.
I had the same issue with the critical partition error when I was under DOS and during the reboot process, 7T will only boot into the normal fastboot screen. In here, I always gets that error over and over. I stopped getting it when 7T boot into the recovery screen under power-shell.
Few things to make sure:
Stock cable
Power-shell in admin priv
Use local fastboot binary
If things still not looking up, I would try a different PC.
Good luck.
Yup, those are all correct and I have tried another PC. Now I'm scared I may have bricked it, because other than booting it into FastBoot it just loops on the "Your device is corrupted" screen. Any thoughts? It did this after I re-locked the bootloader to try unlocking Critical again.
Is your device is corrupt screen the one that gets displayed after the MSM EDL flashing?
If so, does your device auto boot into fastboot afterwards?
My thinking is after MSM tool, your device is corrupted, then you unlock critical flashing. Afterwards, the partitions being flashed in by the fastboot should prevent the corrupt msg being displayed. If you are all getting corrupt msg after the fastboot reboot, then something is off with the first part of your fastboot flashing.
It's that same screen, yes, but the phone is just stuck in a boot loop. It says "Your device is corrupt. It can't be trusted and will not boot." and goes black and says it again, over and over. It will not automatically boot to Fastboot, but if I mess with the volume/power keys, I can get it to the fastboot screen. But no matter what else I do it goes back to an endless loop with the corrupt message.
I think some error could have been carried over from the MSMDownloadTool flashing process. My 7T always auto boot into fastboot screen after the corrupt msg display without interaction on my end.
Try your EDL flashing part again, and at the same time, re-download the preparation step 4 file over again and try use that instead afterwards if you are still stuck on the boot loop, just to prevent possible discrepancies might be caused by corrupted file (unlikely, but it doesn't hurt right?)
Gotcha, thanks. Got it into EDL mode and am running MSM right now.
Okay, EDL/MSM was successful, then I tried flashing the ROM per the instructions again but got the same error of being unable to flash to Critical. It no longer does the "device is corrupt" error boot loop, but the phone ONLY boots to Fastboot now, no matter what I do.
Best of luck. Hope the pain stops for you soon, hah.
Can you post your power-shell display message for the last flash-all.bat invocation?
Also, are you using .\fastboot flashing unlock_critical in admin priv power-shell to unlock the bootloader after MSM flashing?
Yes, that's what I was using. Unlocking it wasn't an issue, and when I try any type of unlock command it says it's already unlocked, which I believe to be true. But it still refuses to write to critical.
I can post my powershell message when I get back home. But basically it ran fine at first, it did fail at the "reserve" portion which I read to be normal, but after that it kept saying cannot flash to critical.
I just got the phone today so I hope it's not already bricked. But the fact that I got it out of the "corrupt" loop gives me hope I can fix it. Is there any place to download the stock T-Mobile ROM so I can try and start over? Assuming it will even let me flash it. I couldn't find any by searching.
One observation I found to be very interesting.
The device should have been locked by the MSM tool through EDL flashing; yet, your device shows it's already unlocked.
I think the issue is still with your EDL flashing process as it should lock the bootloader then use flashing unlock critical to prevent critical partition flashing errors.
Also, your device is not bricked as long as you can still perform EDL flash. Just kept going and you can get it working without having to EDL flash anything else.
I see, thanks for the insight. So just so I don't mess anything up further, exactly what steps in what order do you recommend I perform?
My first instinct is to keep trying the EDL flashing until you can perform flashing critical unlock properly.
If things keep on failing, try to change your PC, driver, or other environmental variables.
It's just a painful process of elimination that you have to stick to.
Also, unless there are potential hardware issues, flashing like this shouldn't carry any more risk to brick your device compare to just using your device regularly. You aren't changing the hardware/software that is responsible for facilitating EDL.
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
seryniti said:
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Click to expand...
Click to collapse
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Let me know what you find. I didn't even know there was other versions of MSM so I'll try that as well. I'd love to just at least get mine out of only being able to boot to Fastboot.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Your 7T should be on the stock recovery screen when fastboot reboot fastboot completes. If your device boots into T-Mobile boot screen or bootloader, something is wrong with your env on PC.
You should never see T-Mobile boot screen at any given time during fastboot flashing process.
The final reboot should complete the conversion and boot into the intentional version OS.
Sorry for my english, translated by google
Hi. Can someone help or at least tell you in which direction to look. Moto (lenovo) G5 XT1675 cedric RETGB device. CEDRIC_OPP28.85_19_4_2_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml (the latest firm on Android 8.1.0) and over it via tvrp lightweight stock on 7.0 android was flashed. In search of a problem, I went through a lot: I replaced the board with yusb, flashed the Rescue and Smart Assistant program from Lenovo (with the firmware that the program told me), unlocked the bootloader + tvrp and root. I tried a lot of custom, but I didn’t solve the problem. The essence is the phone in the included state. does not see usb (in any way, neither charging nor connecting to a computer) but it is worth rebooting the device with the cable connected and everything works. But if you disconnect the phone cable. It no longer sees it until the next reboot. If the menu is loaded into Factory mode through the fastboot without connecting. cable, then when the bodies are connected, it sees it but only the first time. comp. the bodies are normally charged, stitched, etc., the TVRP also does not see the cable (also resolves with a reboot) I personally think about the bootloader, but having the latest version, there is nothing to update and it is risky to roll back to a version below (you can get a brick that cannot be cured with a simple firmware)
I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Note backup any personal files from internal storage to your pc first
TheFixItMan said:
I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Note backup any personal files from internal storage to your pc first
Click to expand...
Click to collapse
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works
Smartphone Killer said:
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works
Click to expand...
Click to collapse
Like I said - if you flashed stock firmware exactly like I posted above with the latest retail firmware from the site in the link and you still have issues it's a hardware problem - either the board or the USB cable you are using
hay i flashed the open beta android 12 on my le2123
i noticed thet i dont have root so i trying download twrp and flash magisk.zip
i boot the phone into fast boot and run this commend
"fastboot boot twrp.img"
and then i flash magisk
the phone refuse to boot normal
i able to boot it to fastboot, what should i do now?
i convart to payload of the open beta via payload dumper and i have now a lot of .img file
should i flash them 1 by 1?
there is any order of doing that?
edit:
first i sorry for my bad english
i finally boot up the phone by first download stock rom and extract the .bin file into payload dumper (i found it on xda)
after that i flash allmost any of the output img the phone came to liva again.
(i have to download the fastboot from android sdk, the minimal adb and fastboot not incloude the specific command of "reboot fastboot.
the command boot the phone into fastbootd (new to me, i never heard about it))
this is the command i use if any one here do my mistake
1. fastboot -w (this will erease anything on the phone)
2.now you need to flash the following img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
3. now use this command to reboot the fastboot into fastbootd
fastboot reboot fastboot
4. Flash the remaining files
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
5. finnaly use this command to reboot your phone into stock rom
fastboot reboot
i really hope this will halp anyone who stuck on the same situation as me
credit to other forum for the flash guide
How to Root Android 12 via Magisk patched boot.img (without TWRP)
In this tutorial, we will show you the steps to root your Android 12 device via Magisk patched boot.img, without using TWRP Recovery.
www.droidwin.com
FizzyAps said:
How to Root Android 12 via Magisk patched boot.img (without TWRP)
In this tutorial, we will show you the steps to root your Android 12 device via Magisk patched boot.img, without using TWRP Recovery.
www.droidwin.com
Click to expand...
Click to collapse
i'll do it after i get my phone boot, you have any idea what should i do now? im stuck on fastboot
msm tool
awesome
but not all thats need to flash stock
FizzyAps said:
awesome
but not all thats need to flash stock
Click to expand...
Click to collapse
so for the next time, how to flash stock?
i was on 12 beta and back to 11 so i flash all the files
elad0elad said:
so for the next time, how to flash stock?
i was on 12 beta and back to 11 so i flash all the files
Click to expand...
Click to collapse
On 12 you can actually downgrade using the updater app they provi
Or
I have a fastboot script .bat flash the essential that are need to flash
FizzyAps said:
On 12 you can actually downgrade using the updater app they provi
Or
I have a fastboot script .bat flash the essential that are need to flash
Click to expand...
Click to collapse
The phone refuse to boot so I can't use the app...
I'll be glad If you can send the script
After not receiving any OTA updates since I bought my phone last year, I decided to VPN to Britain and let it download from there.
To keep this short, I don't like the changes RealUI 3.0 has made and I'm wondering what the easiest way to go back is.
Some searching shows me there's a rollback package for the 3360 model, but I'm concerned it may have detrimental effects for my 3363 device.
Any advice would be appreciated.
Edit: I tried a handful of things and ended up bricking the device. Fastboot is the only thing I can get to load.
My current situation is that the phone only boots into fastboot mode. I've tried running the opporealme ofp flash tool a few times with "RMX3363GDPR_11_C.08_2022062322010228.ofp", but it doesn't seem to help.
Not sure what changed, but after more tinkering I've got back into android on RMX3363_11_C.08
cobatts said:
My current situation is that the phone only boots into fastboot mode. I've tried running the opporealme ofp flash tool a few times with "RMX3363GDPR_11_C.08_2022062322010228.ofp", but it doesn't seem to help.
Not sure what changed, but after more tinkering I've got back into android on RMX3363_11_C.08
Click to expand...
Click to collapse
how you did it, my device only boots in fastboot mode
I don't really know. I just ran the flash tool several times in different active slots and trying to change them afterwards. sometimes it would hard lock during the slot change, but one time it worked.
but now my cell service is extremely spotty and I'm looking to replace the phone entirely. If anyone smarter than me wants to buy a gt master in almost perfect physical condition, hit me up (us only though)
for any who is bricked use this and u will be good to go
extract all from the DOWNLOADED FIRMWARE using mct_ofp_extractor
copy all adb fastboot and adb files in that folder
open cmd in that folder
paste all given below commands there
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
finally fastboot reboot
i don't know why i don't have the sames files when i do extract from ofp so this lot of this command don't work anymore