Hello guys, I recently tried to Downgrade the Moto g30, but something went wrong, the screen was all black, the cell phone does not load, but it recognizes on the computer as Qualcomm HS-USB QDLoader 9008, I already downloaded the drivers from Motorola and Qualcomm, I downloaded BlankFlash and tried to make it go back to normal or when I do fastboot devices the cell phone does not recognize and perform the commands. I already downloaded the drivers but it still isn't going please I ask someone to 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"
}
My guess is that your phone isn't hard bricked but soft bricked:
When the phone has gone through problematic conditions such that it quits the detection of USB, charging and everything that you provide to it then the phone is unfortunately hard bricked.
A soft brick is something that occurs when you perform a dirty flashing, will say if you flash any ROM on your device without doing the factory reset. Or else if you flashed a ROM which was not made for your phone.
This is incredibly suspicious, my Moto G30 ceased to work yesterday as well. I found this discussion about Pixel 3 phones failing en masse, with similar symptoms. I'm still prodding the phone with whatever tools I can find, but I probably will try to get it back to the carrier to get it replaced.
Are you sure you flashed your channel Stock ROM?
I think that was it... Well, try to make Blank Flash with the file that I leave attached to this comment.
Instructions: Please press Volume Down and power on at the same time for 10 seconds, then connect to PC and run blank flash. Just in case it's the .bat file
Sammm77 said:
Are you sure you flashed your channel Stock ROM?
I think that was it... Well, try to make Blank Flash with the file that I leave attached to this comment.
Instructions: Please press Volume Down and power on at the same time for 10 seconds, then connect to PC and run blank flash. Just in case it's the .bat file
Click to expand...
Click to collapse
THANK YOU SOU MUCH REALLY THANK´S
Sammm77 said:
Are you sure you flashed your channel Stock ROM?
I think that was it... Well, try to make Blank Flash with the file that I leave attached to this comment.
Instructions: Please press Volume Down and power on at the same time for 10 seconds, then connect to PC and run blank flash. Just in case it's the .bat file
Click to expand...
Click to collapse
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
juninhovam said:
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
Click to expand...
Click to collapse
Do you have unlocked bootloader?
Sammm77 said:
Do you have unlocked bootloader?
Click to expand...
Click to collapse
yes, I installed android 11 but I blocked the bootloader that's where my problems started, at the moment the bootloader is blocked
juninhovam said:
yes, I installed android 11 but I blocked the bootloader that's where my problems started, at the moment the bootloader is blocked
Click to expand...
Click to collapse
Write to my Telegram
@Samw622
I'll help you better there
Hello
Sammm77The same for me. I try to downgrade from android 12 to android 11 but someting worked wrong. Right now I have no android installed and now my moto g30 start with fastboot. I can access recovery mode but I can`t access my phone to flash. Right now flash is locked and I don`t know how to activate the usb debbuging to access my phone on my computer to flash it. Any help please...
This is what I have now. And I try to
find a way to unlock usb debugging and set OEM unlocking. After that I presume I can reinstall android OS.
CristianPN said:
This is what I have now. And I try to View attachment 5584115find a way to unlock usb debugging and set OEM unlocking. After that I presume I can reinstall android OS.
Click to expand...
Click to collapse
I think you just killed your Moto g30. It can be recovered, but I have no idea how... :/
CristianPN said:
Isto é o que tenho agora. E eu tento View attachment 5584115encontrar uma maneira de desbloquear a depuração USB e definir o desbloqueio OEM. Depois disso, presumo que posso reinstalar o sistema operacional Android.
Click to expand...
Click to collapse
CristianPN said:
Isto é o que tenho agora. E eu tento View attachment 5584115encontrar uma maneira de desbloquear a depuração USB e definir o desbloqueio OEM. Depois disso, presumo que posso reinstalar o sistema operacional Android.
Click to expand...
Click to collapse
Como conseguio o desbloqueio do OEM
Sammm77 said:
I think you just killed your Moto g30. It can be recovered, but I have no idea how... :/
Click to expand...
Click to collapse
Hey Sam do you have discord i bricked mine while trying to root it
TwinCamTurbo said:
Hey Sam do you have discord i bricked mine while trying to root it
Click to expand...
Click to collapse
sure, i'm happy helping u
t.me/Samw622
only if it is brick, hard brick, soft brick. I DO NOT HAVE SUPPORT FOR OEM LOCK
Sammm77 said:
sure, i'm happy helping u
t.me/Samw622
only if it is brick, hard brick, soft brick. I DO NOT HAVE SUPPORT FOR OEM LOCK
Click to expand...
Click to collapse
i am getting no valid operating system found error while installing stock firmware , please help bro
juninhovam said:
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
Click to expand...
Click to collapse
most of programmer files with blank flash are locked and not allow system and boot.img flashing, try with qfil if works, otherwise jtag or try to find a similar lenovo phone (if exist) and use programmer from that
juninhovam said:
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
Click to expand...
Click to collapse
hey! bro i have the same problem as you. did you find any way to correct it.Please help am also stuck there.
jack_little_london said:
hey! bro i have the same problem as you. did you find any way to correct it.Please help am also stuck there.
Click to expand...
Click to collapse
unfortunately there is no repair brother only via box or sending the device to lenovo
Related
DISCLAIMER:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, or dead SD cards,
* nuclear war, penguin invasions or that you are getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and if
* If you point your finger at me for messing up your device, I will laugh at you. Hard
*/
Hey there! I know that very few people still have this 2012-era device, and that the stock ROM is (like most low-end devices at the moment) sluggish and REALLY laggy.
As I'm going to sell the device, just wanted to publish he port I've made!
What does work
Wi-Fi
Camera
Sound & Microphone
Graphic acceleration
USB
Sensors
Sd card
What doesn't work
RIL (SIM and such)
Bluetooth
Wi-Fi Direct
DOWNLOADS
TWRP for restoring the ROM (flashable through Odin/Heimdall)
The ROM backup in zip format (DON'T FLASH IT)
READ THIS:
This ROM is a port of the original CM11 built for the Fame by wulsic.
This ROM isn't a common flashable ZIP, as the patches I did in order to make it work were applied in the system itself. It may be possible to make a flashable zip form this, but meanwhile I will publish it as a TWRP backup.
PLEASE INSTALL TWRP BEFORE DOING ANYTHING ELSE, without it you can't restore the ROM backup.
The ROM is in Spanish language by default, so to set it back to English go to Settings icon at launcher, then the "Idioma e introducción de texto" section, tap "Idioma" and select English.
The ROM includes some gapps (as they need to be modified in order to work nicely)., If I need to remove them please contact me!
ADDED THINGS
Xposed Framework installed and running
GravityBox
XuiMod
Service Disabler (for making google play services usable on low end devices like this)
At developer settings, some options are enabled by me (like Show touches or Stay awake while USB connected). Disable them if you want.
The ROM includes Xposed just for some animations and GravityBox, you can disable most things at their respective modules (for animations disable XuiMod and for quick action tweaks and RAM bar in recents disable GravityBox). Those mods seemed to produce almost no lag so I did keep them.
HOW TO INSTALL THIS BACKUP
As I've said before, this ROM is a TWRP backup, so in order to install (restore) it you need to do the following steps:
Unzip the file and put the 4204134ec2ea3100 folder at /emmc/TWRP/BACKUPS (if BACKUPS folder doesn't exist create it) so the path looks like /emmc/TWRP/BACKUPS/4204134ec2ea3100/
Go to TWRP's main menu, select Restore and select the cm11-nevisvess-backup entry.
Iif it asks you for which partition restore, select ALL of them. They all are important (without data the system may not boot cause of xposed, for example).
After restoring everything, restart the phone. It should boot and you will get to the unlock screen (system done)
Credits:
Cyanogenmod for the base ROM
All fame devs as they work is the ground I'm building upon
The base ROM link, there's more info (like sources): https://forum.xda-developers.com/galaxy-fame/rom-cyanogenmod11-t2897673
The guy who published a surprisingly working way to port the ROM: https://www.htcmania.com/showthread.php?t=1161445
Screenshots:
{
"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"
}
Hola!! Gracias x el desarrollo! No hay nada parecido para este celular! Tengo un problema con la red movil. sera un problema de IMEI? que solución podria darla.
desde ya muchas gracias
Greetings!
I am trying to get a degoogled smartphone. Would you please upload a GApps-less version of this TWRP backup ROM?
Thanks.
galaxyfame said:
Hola!! Gracias x el desarrollo! No hay nada parecido para este celular! Tengo un problema con la red movil. sera un problema de IMEI? que solución podria darla.
desde ya muchas gracias
Click to expand...
Click to collapse
Please write in english, and read forum rules... (por favor escribe en inglés y lee las reglas del foro)
Check at settings->about phone->status if it recognizes your IMEI, if not you may need to flash modem with Odin
NotHereToStay said:
Greetings!
I am trying to get a degoogled smartphone. Would you please upload a GApps-less version of this TWRP backup ROM?
Thanks.
Click to expand...
Click to collapse
You can just check the opengapps package for APK file names, and delete them from /system/app or /system/priv-app.
Yes, the libraries will stay here but they can´t do much without the apps that manage them.
Anyway, I don't have the phone anymore, else I would upload such a modified version! Sorry
MLX said:
You can just check the opengapps package for APK file names, and delete them from /system/app or /system/priv-app.
Yes, the libraries will stay here but they can´t do much without the apps that manage them.
Anyway, I don't have the phone anymore, else I would upload such a modified version! Sorry
Click to expand...
Click to collapse
The OpenGApps package weighs a lot (100 KBps download speed by the way).
Can I use something like this instead? https://github.com/ANDROID2468/Remove-Gapps
EDIT: TWRP boots, but the touchscreen does not work. My device is GT-S6790L. Is that the reason why it does not work?
I thought this was a regular ROM, and I do not know where to get the original recovery ROM now.
EDIT 2: This guy's stock recovery worked. https://forum.xda-developers.com/t/q-galaxy-fame-lite-cwm-twrp.2779754/ God knows if this does something bad on the phone, but it seems to be exactly the same.
NotHereToStay said:
The OpenGApps package weighs a lot (100 KBps download speed by the way).
Can I use something like this instead? https://github.com/ANDROID2468/Remove-Gapps
Click to expand...
Click to collapse
It may work, never tested and can´t guarantee anything.
NotHereToStay said:
EDIT: TWRP boots, but the touchscreen does not work. My device is GT-S6790L. Is that the reason why it does not work?
Click to expand...
Click to collapse
Strange, mine was also a 6790L and it worked just fine. Did you change the touchscreen at any time? (It should work anyway).
NotHereToStay said:
EDIT 2: This guy's stock recovery worked. https://forum.xda-developers.com/t/q-galaxy-fame-lite-cwm-twrp.2779754/ God knows if this does something bad on the phone, but it seems to be exactly the same.
Click to expand...
Click to collapse
That guy just uploaded his stock recovery, that's not a problem. Anyway, I'm confused with TWRP not working for you, IDK what the problem is...
MLX said:
It may work, never tested and can´t guarantee anything.
Strange, mine was also a 6790L and it worked just fine. Did you change the touchscreen at any time? (It should work anyway).
That guy just uploaded his stock recovery, that's not a problem. Anyway, I'm confused with TWRP not working for you, IDK what the problem is...
Click to expand...
Click to collapse
I do not know if people changed the smartphone's touchscreen. It is an old smartphone from my grandma I am trying to fix (bootloop, I am privacy-conscious).
We live in Venezuela, so I think our stock ROM is the NBS (South American).
I would really like this ROM to be repackaged into a flashable ZIP, though. That would be so awesome.
NotHereToStay said:
I do not know if people changed the smartphone's touchscreen. It is an old smartphone from my grandma I am trying to fix (bootloop, I am privacy-conscious).
Click to expand...
Click to collapse
Okay then, anyway (as said) touchscreen should not be an issue...
NotHereToStay said:
We live in Venezuela, so I think our stock ROM is the NBS (South American).
Click to expand...
Click to collapse
I'm also Latin American, so we can talk better via PM if you want (in spanish)
NotHereToStay said:
I would really like this ROM to be repackaged into a flashable ZIP, though. That would be so awesome.
Click to expand...
Click to collapse
Sorry, as said I dont have the device anymore so I can't try doing so, however you should be able to install the ROM via ADB (using the console and ADB). Send me a PM for more details if you want to follow this way.
MLX said:
Okay then, anyway (as said) touchscreen should not be an issue...
I'm also Latin American, so we can talk better via PM if you want (in spanish)
Sorry, as said I dont have the device anymore so I can't try doing so, however you should be able to install the ROM via ADB (using the console and ADB). Send me a PM for more details if you want to follow this way.
Click to expand...
Click to collapse
I thought about it more carefully. I may or may not have accidentally discovered that the thing has the touchscreen broken.
I think it will be pretty complicated and time consuming for me to manually remove the GApps by myself and will probably regret the results if I accidentally delete stuff.
Does anybody have a debloated (includes degoogling) version of this ROM? This is giving me a headache. Almost literally, the back of my eyes hurt.
MLX said:
Screenshots:
Click to expand...
Click to collapse
Can this work with sim cards and data? (Claro argentina)
Ezet uwu said:
Can this work with sim cards and data? (Claro argentina)
Click to expand...
Click to collapse
Nope, sadly I never got it to work
Hi, i managed to root my blackshark 3 KLEN2008060OS00MP3 With this method https://forum.xda-developers.com/t/...-way-bl-unlocking-twrp-ota-fix.4147441/page-6 so up to my understanding i have magisk and havent changed the system too much (im very very noob) i only did this because the tutorial was very good and step by step.
my phone has warned me today that i have available the joyui update KLEN2102020OS00mp4, can i just press the download buttom and install the ota without losing root?. and if i cant can anyone give me a small tuto of how to do it?
thank you very much
mrleyva said:
Hi, i managed to root my blackshark 3 KLEN2008060OS00MP3 With this method https://forum.xda-developers.com/t/...-way-bl-unlocking-twrp-ota-fix.4147441/page-6 so up to my understanding i have magisk and havent changed the system too much (im very very noob) i only did this because the tutorial was very good and step by step.
my phone has warned me today that i have available the joyui update KLEN2102020OS00mp4, can i just press the download buttom and install the ota without losing root?. and if i cant can anyone give me a small tuto of how to do it?
thank you very much
Click to expand...
Click to collapse
You can't... It will fail after the download cus you need a clean stock ROM to update your BS3... Do you have this update to share here?
Is this the joyui 12 global update ?
It doesn't seems
{
"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"
}
USB connection of you with the computer continues to work ok after this 12/2020 update?
Mine no longer connects with the computer for data transfer and just keeps charging .... I posted on the topic of this and here also to find out if this update is causing this because I noticed it in my post after the update.
gilbermarcilio said:
USB connection of you with the computer continues to work ok after this 12/2020 update?
Mine no longer connects with the computer for data transfer and just keeps charging .... I posted on the topic of this and here also to find out if this update is causing this because I noticed it in my post after the update.
Click to expand...
Click to collapse
Sounds like you don't have the drivers for this phone... What name the device has when you connect it to the pc?
pleas please share the ota
SmokeAnDrink said:
Sounds like you don't have the drivers for this phone... What name the device has when you connect it to the pc?
Click to expand...
Click to collapse
Smoke there is the problem I connect the Black Shark 3 on the PC and simply the device only charges ...
On the PC nothing changes and I open the task manager simply not even recognize the device or appear as an exclamation that failed to install the driver.
I have already tested it on several USB PCs and on 3 USB cables and USB 3.0 speed and nothing the phone only charges and does not connect to the PC or Macbook Air that I tried too ...
This is very sinister because the phone simply lost connection to the pc and only charges or I can use OTG adapter to connect pen drive to it and that accepts ...
NOTE: The Developer is already active and I have already marked it in USB Settings for data transfer and without chance the pc does not even recognize anything and the problem is not with the PC because I have 3 more devices at home and tested and all normally connects a Poco M3 Cubot Note 20 Pro and an Umidigi Bison all connect with the PC without a problem except this black shark that died the connection with the PC very sad that.
sco-mito said:
pleas please share the ota
Click to expand...
Click to collapse
After several attempts to pause the download of the OTA at 100% (since upon reaching 100% was automatically deleted) I have it uploaded to mega, I hope it's all there and there is no problem and before anything else, make a backup in case something weird happens .... Anyway I will try to install it later, if anyone wants to do it before here's the mega link...
389.86 MB file on MEGA
mega.nz
SmokeAnDrink said:
After several attempts to pause the download of the OTA at 100% (since upon reaching 100% was automatically deleted) I have it uploaded to mega, I hope it's all there and there is no problem and before anything else, make a backup in case something weird happens .... Anyway I will try to install it later, if anyone wants to do it before here's the mega link...
389.86 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
You're my hero
@SmokeAnDrink TWRP says it's corrupted
SmokeAnDrink said:
After several attempts to pause the download of the OTA at 100% (since upon reaching 100% was automatically deleted) I have it uploaded to mega, I hope it's all there and there is no problem and before anything else, make a backup in case something weird happens .... Anyway I will try to install it later, if anyone wants to do it before here's the mega link...
389.86 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
TRied putting in sdcard/ota/update.zip
and *#*#1027#*#* , local update gives ota error (20) did u update it thru twrp?
you have to get the ota link by adb: https://forum.xda-developers.com/t/...our-android-device-using-logcat-file.3773083/
If you cant find the link you can pm me the logcat...
aerial4ce said:
TRied putting in sdcard/ota/update.zip
and *#*#1027#*#* , local update gives ota error (20) did u update it thru twrp?
Click to expand...
Click to collapse
Error 20 caused of device has twrp. I tried both, with or without custom recovery. Without twrp, 1027 able to update
Sorry, I was working and completely forgot about this. Here is the link from adb
"Model": "KLE-H0",
"Version": "KLEN2102020OS00MP4",
"URL": https://ota-oversea-1256119282.file...deltaota_8dfabcef45cda957295fbb9fb2340ba9.zip
kevin mitnick said:
Error 20 caused of device has twrp. I tried both, with or without custom recovery. Without twrp, 1027 able to update
Click to expand...
Click to collapse
Do you still have the recovery.img? If so, could you share it?
SmokeAnDrink said:
Do you still have the recovery.img? If so, could you share it?
Click to expand...
Click to collapse
yes i have. I will upload then share here. asap
SmokeAnDrink said:
Do you still have the recovery.img? If so, could you share it?
Click to expand...
Click to collapse
sorry for my mistake. I only have MP3 recovery. now I used CN MR1 and cant get backup recovery MP4..
That's the one I need. I'm still using the MP3 update.
kevin mitnick said:
sorry for my mistake. I only have MP3 recovery. now I used CN MR1 and cant get backup recovery MP4..
Click to expand...
Click to collapse
Can you share CN MR1 recovery as well?
I bricked my POCO F3 Global while converting it into Redmi K40 after BL unlocking - I have tried everything - did whatever it takes to bring it back to life - but for me, nothing works.
I need experts advice, I would really appreciate if you could do something to fix this phone. (After trying whatever it takes, I came to a conclusion, while flashing it via Mi-Flash-Tool it says that it requires an Xiaomi Authorized Account to flash it to life, and it is hard to have one, probably)
Any help would be appreciated.
Thank you for your time.
{
"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"
}
AndroidsKings said:
I have bricked my POCO F3 Global while converting it into Redmi K40 after BL unlocking - I have tried everything - did whatever it takes to bring it back to life - but for me, nothing works.
I need experts advice, I would really appreciate if you could do something to fix this phone. ( but I have noticed a thing when flashing it via Mi-Flash Tool it requires a authorized account to flash it to life, and it is hard to have one, because of scammers out there.
View attachment 5305857
Click to expand...
Click to collapse
What exact steps did resulted into this? Is bootloader not accessible? I also have global version of POCO F3 and I also did the same to convert to Chinese version from global version, but flash tools gave me multiple errors. And didn't let me Flash the ROM.
But soon when I rebooted the phone it got stuck in Fastboot screen. Later on I flashed TWRP Recovery and Flashed CrDroid which booted up the phone, But due to some bugs and personal preferences I switched to Xiaomi.eu 12.5 stable.
What rom did you had before bricking your device?
malick186 said:
What exact steps did resulted into this? Is bootloader not accessible? I also have global version of POCO F3 and I also did the same to convert to Chinese version from global version, but flash tools gave me multiple errors. And didn't let me Flash the ROM.
But soon when I rebooted the phone it got stuck in Fastboot screen. Later on I flashed TWRP Recovery and Flashed CrDroid which booted up the phone, But due to some bugs and personal preferences I switched to Xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I am having a black screen, and nothing but just my PC can detect it but in Qualcomm HS-USB QDLoader 9008 mode, I was flashing it as I have told, it was on Fastboot Screen but after giving it a restart, it didn't show any sign of light, and now my life is in darkness, but after a research I have found out that I am lost somewhere is EDL mode which is not easily flashable without a Mi Authorized Account as shown in the attached picture.
hexisg said:
What rom did you had before bricking your device?
Click to expand...
Click to collapse
I was on ( miui_ALIOTHGlobal_V12.0.3.0.RKHMIXM ) and I was flashing it/converting it into Redmi K40 12.5.20 after unlocking the bootloader.
AndroidsKings said:
I was on ( miui_ALIOTHGlobal_V12.0.3.0.RKHMIXM ) and I was flashing it/converting it into Redmi K40 12.5.20 after unlocking the bootloader.
Click to expand...
Click to collapse
Did u choose the clean all and lock option ?
AndroidsKings said:
I was on ( miui_ALIOTHGlobal_V12.0.3.0.RKHMIXM ) and I was flashing it/converting it into Redmi K40 12.5.20 after unlocking the bootloader.
Click to expand...
Click to collapse
Hold volume - and power for 15sec. If fastboot pop-up, Flash the original rom and select clean all
I wonder how you managed to do that because i was on stock EEA variant and i unlocked bootloader and flashed xiaomi EU 12.5.2 without issues.
If you cannot acces bootloader your only chance is EDL authorized account , which you have to pay someone who has one.
X0PIRAT3 said:
Did u choose the clean all and lock option ?
Click to expand...
Click to collapse
Yup did that.
X0PIRAT3 said:
Hold volume - and power for 15sec. If fastboot pop-up, Flash the original rom and select clean all
Click to expand...
Click to collapse
Not workking !
hexisg said:
I wonder how you managed to do that because i was on stock EEA variant and i unlocked bootloader and flashed xiaomi EU 12.5.2 without issues.
If you cannot acces bootloader your only chance is EDL authorized account , which you have to pay someone who has one.
Click to expand...
Click to collapse
I think you are right, an EDL authorised account must be needed.
you can use qfil and an approperiate flashable rom,not sure where you can get the qfil rom from but qfil itself is easily downloadable.
edit:actually with qfil you can flash the boot partition only and then you should be able to have a working fastboot again.i think.
metalspider said:
you can use qfil and an approperiate flashable rom,not sure where you can get the qfil rom from but qfil itself is easily downloadable.
edit:actually with qfil you can flash the boot partition only and then you should be able to have a working fastboot again.i think.
Click to expand...
Click to collapse
I am gonna try it tonight. Thank you, I'll report you back.
Now i undersand what you did: you used mi flash to flash stock redmi k40 12.5.2 rom on a stock unlocked Poco F3 Global and you had lock option thicked.That obviously did the trick by bricking your device.You did not searched for the right info on what you need to do.
metalspider said:
you can use qfil and an approperiate flashable rom,not sure where you can get the qfil rom from but qfil itself is easily downloadable.
edit:actually with qfil you can flash the boot partition only and then you should be able to have a working fastboot again.i think.
Click to expand...
Click to collapse
Tried this, but failed !
AndroidsKings said:
Tried this, but failed !
Click to expand...
Click to collapse
theres full EDL roms here:
Download Poco F3 Flash File Firmware EDL ROM
Download Poco F3 Firmware Flash File Stock ROM, here we share latest firmware for Poco F3 with flash tool & usb driver
romprovider.com
I see in mi flash tool the rom you try to flash is the global one not the china rom
metalspider said:
theres full EDL roms here:
Download Poco F3 Flash File Firmware EDL ROM
Download Poco F3 Firmware Flash File Stock ROM, here we share latest firmware for Poco F3 with flash tool & usb driver
romprovider.com
Click to expand...
Click to collapse
Thank you, I am having an error.
hexisg said:
Now i undersand what you did: you used mi flash to flash stock redmi k40 12.5.2 rom on a stock unlocked Poco F3 Global and you had lock option thicked.That obviously did the trick by bricking your device.You did not searched for the right info on what you need to do.
Click to expand...
Click to collapse
You might be right, I did something like that. I'll take care of this next time, mistakes teach a lot.
AndroidsKings said:
Thank you, I am having an error. View attachment 5306329
Click to expand...
Click to collapse
Not really sure but what happen is that something in that path (that's trying to access is wrong). Next time click on details (so we can see the call stack). Try to run it as administrator and extract the mi flash to a "shorter" path: "C:/Miflash"
At this point I think you want to try anything so...
Bootloader warning ⚠Have you recently unlock your bootloader and want to remove Warning Bootloader Unlock message that comes every time when your device is starting up? Then not worry this article is for you. This tutorial gives you the detail view of How to remove Warning Bootloader Unlocked message from your android devices.
What you need?
Your device.
Terminal (termux recommended).
Magisk patched recvory (you just need root for one time).
Steps to follow to fix Bootloader Unlocked Warning issue :
Download the Param file and move it to download folder (internal storage).
Download terminal (you can use termux).
Start terminal and gain root access using "su".
Type / copy this command into the terminal -
Code:
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/bootdevice/by-name/up_param
Now simply reboot to recovery or system.
Mission accomplished.
Download(in this case the param file is only for Samsung Galaxy A22, if you want it for your device message on telegram channel or comment below)Splash screens for other devices :
Galaxy Tab S6 lite
Galaxy A12
Galaxy M30s
Galaxy Tab A7 Lite
If you want it for your device comment below..
Conclusion :In this post I have talked about How to remove unlocked bootloader warning. Tell us What You Say About The Post by commenting and if you have any questions then comment below.
Reference : Razs Originals!
Download is now available
Enjoy
This is the correct A22 and will not cause a reboot
litepius said:
This is the correct A22 and will not cause a reboot
Click to expand...
Click to collapse
Hi, How to remove message bootloader unlocked on
Samsung Galaxy S22 5G 256GB white (SM-S901) ?
rafarin said:
Hi, How to remove message bootloader unlocked on
Samsung Galaxy S22 5G 256GB white (SM-S901) ?
Click to expand...
Click to collapse
Send me your bl folder from firmware
I'll send you the param file then you can easily flash it using termux or odin
there is no param file in the BL folder for A52S 5g (A528B) see screenshot.
{
"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"
}
bobfrantic said:
there is no param file in the BL folder for A52S 5g (A528B) see screenshot.
View attachment 5565297
Click to expand...
Click to collapse
your device have a exynos or a snapdragon based processor?
razs.originals said:
your device have a exynos or a snapdragon based processor?
Click to expand...
Click to collapse
Snapdragon...
bobfrantic said:
Snapdragon...
View attachment 5566851
Click to expand...
Click to collapse
ohh okay but unfortunately for now this method only works with exynos based devices only
razs.originals said:
ohh okay but unfortunately for now this method only works with exynos based devices only
Click to expand...
Click to collapse
I thought so, but any idea how to do this on snapdragon?
bobfrantic said:
I thought so, but any idea how to do this on snapdragon?
Click to expand...
Click to collapse
Send me your bl folder will try, let's see
razs.originals said:
Send me your bl folder will try, let's see
Click to expand...
Click to collapse
link sent to your pm. thanks
bobfrantic said:
link sent to your pm. thanks
Click to expand...
Click to collapse
Okay I'll check
razs.originals said:
Okay I'll check
Click to expand...
Click to collapse
I notice that exynos bl is a lot simpler than snapdragon... hope you can find where the file us hidden
not working for me on A225f any body help with file
razs.originals said:
Bootloader warning ⚠Have you recently unlock your bootloader and want to remove Warning Bootloader Unlock message that comes every time when your device is starting up? Then not worry this article is for you. This tutorial gives you the detail view of How to remove Warning Bootloader Unlocked message from your android devices.
What you need?
Your device.
Terminal (termux recommended).
Magisk patched recvory (you just need root for one time).
Steps to follow to fix Bootloader Unlocked Warning issue :
Download the Param file and move it to download folder (internal storage).
Download terminal (you can use termux).
Start terminal and gain root access using "su".
Type / copy this command into the terminal -
Code:
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/bootdevice/by-name/up_param
Now simply reboot to recovery or system.
Mission accomplished.
Download(in this case the param file is only for Samsung Galaxy A22, if you want it for your device message on telegram channel or comment below)Splash screens for other devices :
Galaxy Tab S6 lite
Galaxy A12
Galaxy M30s
Galaxy Tab A7 Lite
If you want it for your device comment below..
Conclusion :In this post I have talked about How to remove unlocked bootloader warning. Tell us What You Say About The Post by commenting and if you have any questions then comment below.
Reference : Razs Originals!
Click to expand...
Click to collapse
Greetings...
I would like to know if it will work on a Samsung A225M/DSN, because I had tried the other twrp bootloader and I had some issues with that.
I accomplish to patch my AP file with Magisk 24.3 and had installed this patched AP but it keeps showing the Bootloader Warning.
This is why I am asking you this question, since I read It did not worked on a A225F.
Thanks for your work.
PARA EL MODELO A225M
entrar a termux escribir
termux-setup-storage
su
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/mmcblk0p35
obiamente descargando el archivo que indica arriba y pegandolo en la carpeta download del dispositivo
funciona perfecto
Hello, does it work with tab s7 t870? It s snapdragon... thanks
proba con probar no perdes nada a veces las cosas se hacen a prueba y error. Asi descubri ayer como hacerlo
Mod translation via GT: try with trying you don't lose anything sometimes things are done by trial and error. So I discovered yesterday how to do it
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now...
Even I was aware which DDR model was my device, yes.. I did it - flashed by mistake DDR4 xbl.img to my DDR5 noodlep.
Of'coz, I wasn't that happy when I achieved it. Many googling, many searches - nothing. The only option was to return to OnePlus for repair.
But; there is a way. The idea came from Tom Marshall ( @tdm ) - he said that I can try to force "deep flash method" using EDL CABLE.
How to recover ? It's really simple.
Pre-requisites:
1. Windows 7 - 10 based PC (for msmtool) with properly installed 9008 COM port drivers.
Follow this guide to set and prepare: [OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
2. Buy EDL cable. it looks like that:
{
"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"
}
Now to revive your toy !
1. Start msmtool, click others (as it's recommended for msmtool), choose region of your device. Get ready to start flashing.
You'll see that the line with COM port says it's not connected (yet)
2. Connect the cable to your device - but not to PC yet.
3. Press the button on the cable - It's called "deep flash" button...
4. While you are still pressing the button, connect the other side of the cable to your PC (where msmtool is opened and ready to go).
5. Release the button and you'll hear that your device is connected. Check the line with COM port and you'll see it's connected.
EDL port will be opened for about 10 seconds. so you must be ready to start the installation.
6. Start the msmtool and wait till the finish.
7. The rest is well known msmtool flashing way.
Enjoy !!!
Credits goes to @tdm , @jabashque & @AnierinB for their support.
This method shall work on EVERY QUALCOMM device, as it's QualComm thing...
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
ppajdek said:
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
Click to expand...
Click to collapse
Actually available on Amazon or eBay for a few bucks.
ppajdek said:
Haha, thanks for the confirmation, everyone said that the ram is fried and you have to change mobo, i said that there is no proof of that, and i was right.
Btw could you share link to where you got that cable?
Click to expand...
Click to collapse
Okay first off Qualcomm has multiple things in their source code that tell you you can ram flash your phone back secondly software can't fry hardware
Thanks @samdoc, @tdm , @jabashque ! I was able to fix my phone and get it back to working . I'm very grateful for the help and wanted to express my appreciation. Without this post, I'm not sure what I would have done. Thanks again, samdoc!
jef_00 said:
Thanks @samdoc, @tdm , @jabashque ! I was able to fix my phone and get it back to working . I'm very grateful for the help and wanted to express my appreciation. Without this post, I'm not sure what I would have done. Thanks again, samdoc!
Click to expand...
Click to collapse
I'm trying it out tomorrow myself
AkayamiShurui said:
I'm trying it out tomorrow myself
Click to expand...
Click to collapse
Good luck brother
jef_00 said:
Good luck brother
Click to expand...
Click to collapse
I'm literally about to do it right now I'm just waiting for the MSM tool to finish downloading I got official qualcomm drivers on the computer
did you have success brother @AkayamiShurui
jef_00 said:
did you have success brother @AkayamiShurui
Click to expand...
Click to collapse
Trying again I downloaded the wrong MSM lol
Thank you @semdoc for the suggestion
Because I used similar like semdoc attached image deep flash cable and followed the steps, its seems to be not work. (no new notification in Device Manager)
@jef_00 do you mind share what type of deep flash cable/ shopping link?
After wrongly flashed XBL, is that normal the phone will be hot?
(I have just unplug the battery so it won't over heat mobo)
Hi @bingchilling sure!
1. I used a hydra EDL v2 cable i get mine from AliExpress
2. Not noticed that
AkayamiShurui said:
Trying again I downloaded the wrong MSM lol
Click to expand...
Click to collapse
Aah allright
jef_00 said:
Hi @bingchilling sure!
1. I used a hydra EDL v2 cable i get mine from AliExpress
2. Not noticed that
Click to expand...
Click to collapse
Thank you @jef_00, will give it a try!
bingchilling said:
Thank you @jef_00, will give it a try!
Click to expand...
Click to collapse
no problem!
i guess im a little bit late for this party? successfully switched motherboard, but broke the screen in the process (wrong screw into wrong hole)
anyway i'll pray and hope this works on your phones cause this issue needs to be tech fckd, just switched to OP9Pro for 200 bucks, dont ask how.. guess someone in much need at ebay
Hi everyone, I might need some help here...I have a OnePlus 8T EU model and I too have flashed the wrong xbl.img (DDR5 instead of DDR4X in my case). Reading this post gave me some hope and I bought an EDL cable, looking just as the one in the picture OP posted.
My phone has never been in EDL mode before, therefore it is not showing up at all in device manager, no QHUSB_BULK, no anything. It is therefore impossibile for me to try and install the drivers by updating the device entry there, as specified in the guide.
I tried to install the drivers in several other ways, using an installer executable or manually installing the .inf files, but the outcome is always the same: after following all the steps given, MSM, as well as Device manager, do not read my device.
What can I possibly try differently here?
joker925 said:
Hi everyone, I might need some help here...I have a OnePlus 8T EU model and I too have flashed the wrong xbl.img (DDR5 instead of DDR4X in my case). Reading this post gave me some hope and I bought an EDL cable, looking just as the one in the picture OP posted.
My phone has never been in EDL mode before, therefore it is not showing up at all in device manager, no QHUSB_BULK, no anything. It is therefore impossibile for me to try and install the drivers by updating the device entry there, as specified in the guide.
I tried to install the drivers in several other ways, using an installer executable or manually installing the .inf files, but the outcome is always the same: after following all the steps given, MSM, as well as Device manager, do not read my device.
What can I possibly try differently here?
Click to expand...
Click to collapse
İssues are with your Windows and quallcom drivers probably... I remember I had to switch to safemod in order to installl quallcom drivers.
I'm facing the same issue. Flashed ddr5 firmware instead of ddr4. The phone is completely hard bricked and is not showing on device manager as well.
Will the edl cable enable the connectivity so that i can do MSM?
Ordered youkiloon hydra v2 edl cable and planning to test tomorrow.
abhi92raj said:
I'm facing the same issue. Flashed ddr5 firmware instead of ddr4. The phone is completely hard bricked and is not showing on device manager as well.
Will the edl cable enable the connectivity so that i can do MSM?
Ordered youkiloon hydra v2 edl cable and planning to test tomorrow.
Click to expand...
Click to collapse
Could you Please share the result after testing