Hello, I will use the Google translator because I am Brazilian
Today I ended up trying to install a custom rom on my moto g8, but it ended up giving some errors and I ended up blocking my bootloader manually, but now it doesn't start the phone and I can't install any stock rom with the bootloader blocked, all end up showing an error.
{
"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"
}
This website has instructions to flash stock firmware on Sofia. Everything but the link to download firmware should apply to Rav. https://www.droidwin.com/install-stock-firmware-on-motorola-g8-power-via-fastboot-commands/
Not because my bootloader is not unlocked
andr3ycarvalho said:
Not because my bootloader is not unlocked
Click to expand...
Click to collapse
A week ago I bricked my Moto g fast by attempting to flash RetUS firmware without unlocking the bootloader first. Even though most of the fastboot commands failed a handful succeeded and that was enough to prevent my phone from booting to anything but bootloader mode.
I downloaded and flashed the official Boost firmware from lolinet and while the flash succeeded my phone was still bricked.
I installed the Lenovo Motorola Rescue and Smart Assistant tool from https://support.lenovo.com/us/en/downloads/ds101291 and used it to download official firmware for my phone but the rescue tool failed at 14%.
I tried a few other things that also didn't help before I ran the LMSA rescue tool again. This time it took several minutes to complete and my phone worked again. I am not sure why it failed at first but happy to have a working phone again.
hello, i'm also brazilian and i have a problem similar to yours, after leaving a custom rom the other day, and reinstalling the stock and blocking the bootloader, my phone called with the message that it was corrupted and it wouldn't start and now i can only access his bootloader and I can't flash anything, not even the stock rom, I don't know how to solve it, but I'm in a situation similar to yours
Hello, I have a problem with my Moto G8 (XT 2045-1). I tried to install a stock rom to fix a bug, however the phone no longer connects in bootloader mode, nor does it unlock the same and I can't even install any stock rom. Can someone help me?
Related
Hi,
I used a long time CyanogenMod 12 and 13 with my LG G3 (d855). Suddenly some problems occurred. I flashed a lot of images and TWRP versions.
Last days I tried to flash wit the LG Tool 2014 original kdz images from LG.
{
"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"
}
I tried:
D85521C_00_1204 (21C).kdz
D85530C_00_0211 (30C).kdz
D85530F_00_0329 (30F).kdz and
Europe D85530B_00_1217 (30B).kdz.
Normally KingRoot and AutoRec worked fine. A short time. After using my phone a few minutes or hours i got bootloops and I had to flash again a clean official ROM. Sometimes I couldn't enter TWRP via buttons.
I think my phone has a hardware failure.
In the past few minutes I tried to flash the 30F image above. Android started regular and asked my which language I want to use. I scrolled down, selected German and the phone rebooted. Now I've a bootloop again. After a few seconds after flashing a original ROM.
Can you help me? Is the phone hardware bricked?
Best regards
Tim
Now I will try http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
Katzenstreu said:
Hi,
I used a long time CyanogenMod 12 and 13 with my LG G3 (d855). Suddenly some problems occurred. I flashed a lot of images and TWRP versions.
Last days I tried to flash wit the LG Tool 2014 original kdz images from LG.
I tried:
D85521C_00_1204 (21C).kdz
D85530C_00_0211 (30C).kdz
D85530F_00_0329 (30F).kdz and
Europe D85530B_00_1217 (30B).kdz.
Normally KingRoot and AutoRec worked fine. A short time. After using my phone a few minutes or hours i got bootloops and I had to flash again a clean official ROM. Sometimes I couldn't enter TWRP via buttons.
I think my phone has a hardware failure.
In the past few minutes I tried to flash the 30F image above. Android started regular and asked my which language I want to use. I scrolled down, selected German and the phone rebooted. Now I've a bootloop again. After a few seconds after flashing a original ROM.
Can you help me? Is the phone hardware bricked?
Best regards
Tim
Edit 1:
Now I will try http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
Click to expand...
Click to collapse
Edit 2:
Same Problem
https://youtu.be/6MlxVDFYpW0
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.
I have a Mi 11 lite 4G . I was using Indian rom and switched to global rom recently to try out Android 12 and miui 13.now here I am not able to use Google apps like gplay,mail,chrome. And even camera isn't working .I want to go back to older rom but it shows this error which I have attached here. Please someone help me ..
{
"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"
}
Hey bro you somehow softbricked your device. make sure you have a backup and flash latest firmware through mi flash tool. This wil format complete storage and reinstall it as new.
if you have unlocked the bootloader before you should not use the relock option in mi flash tool.
Download Xiaomi Flash Tool - Xiaomi Mi Flash Tool Download
Download Xiaomi Flash tool is for Xiaomi smartphone and tablet device users that runs on Windows PC platforms to flash fastboot firmware files on Xiaomi smartphones. All versions of Xiaomi Mi Flash Tool download is available here
www.xiaomiflash.com
Unless modded, patched or worked around, SafetyNet wouldn't pass on that device.
Certification could... if the Play Store doesn't take ctsProfileMatch into account because that part would be false, at the very least because of the unlocked bootloader.
In any case, the usual procedure should suffice:
Set phone to Fastboot mode (Vol- pressed at power on).
Flash the appropriate ROM either manually or using any of the Fastboot GUIs (e.g. Mi Flash).
That's about it, re-lock bootloader if you wish, don't think it's necessary.
Besides, if you get the same outcome after the procedure (say the unlocked bootloader mattered and you don't want to root or patch anything), you can always lock it, and then clear the data of the Play Store and Google Player Services (for good measure haha); it should force it to reevaluate its certification status.
And yeah, clearing user data is probably appropriate when flashing.
Don't be so hasty with MIUI 13, you're not missing much
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"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"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse
As the title says... I messed up when I was trying to flash the EUR version on my Global Pad 5... I did't check and the boot loader got loked and now I can't start the tablet....
Is there a way to fix this...
{
"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"
}
Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.
tobyw121 said:
Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.
Click to expand...
Click to collapse
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.
You should be able to unlock it again using the xiaomi unlock tool, because it should keep oem unlock setting open.
You must boot at fastboot and Unlovk with the Tool. You dosnt wait 7 days. It works Instant and then you can flash fastboot Rom of your choice
You mean you unlocked a global one and flashed a Europe official rom and locked it and it got stuck?? I'm in the same boat, i have TR and i want to flash EU. I'm waiting the 7 days at the moment to unlock the bootloader. Advice pls
TDrkKnight said:
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.
Click to expand...
Click to collapse
Update... The bad I wasn't able restore it (I'm not up to date with all the "new" locks on android). The Good, I was able to return it, thats how I resolved the issue...