Database Info

Droid 2 global Qualcomm download mode?!

I have tried to update my droid with update.zip. It failed with a weird message, smth like could not update modem (the phone was ok before)
Now i got mass of downloaded files, like rsdlite and two sbfs
VRZ_A956_2.4.33_1FF_01.sbf and DROID2WE_X6_2.4.29_FULL.sbf
both stop at 100% and i get a popup message telling new device is found QHSUSB_DNLD or something like that. I've checked ALL motorola drivers (5.2.x update) for subject of this string with the hardware id of PID_9008 but i have found nothing! It just simply DOES NOT exit!
I have found proper dirvers, it looks like MSM6600 default drivers. So when RSD switched to BP mode it won't see anything, tho i get the drivers running and in the device manager i clearly see smth like Qualcomm ..Download 9008 but the RSDLite keeps searching and fails to process - Phone disconnected...
So, maybe anyone here got the same problem or has a clue of how to get rid of bootloader screen? Wiping cache, erasing to factory does nothing, I don't just get what this rsdlite wants? which device appears when it switched to BP download mode? Isn't it the one i get?
I have tried 3 PC, 2xXP and 1xWIN7 so it's NOT the PC's fault.
RSDLite is 5.4.5 - latest, the drivers - latest!
Please guys, need your input!
EDIT: I have joined only 3 files: CG05, RDL1.smg and RDL3.smg to test faster - it will immediatelly switch to BP mode, so no need to erase or reflash whole device. Will upload to rapidshare if anyone wants to test.

jinns said:
RSDLite is 5.4.5 - latest, the drivers - latest!
Please guys, need your input!
Click to expand...
Click to collapse
This nice manual, does not help either
http: //droid.koumakan. jp/wiki/SBF

Try http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html — this is a bootable CD image (which can be also used with a USB stick) that performs the task.
Note: 2.4.29 is the recommended (at least by me, after quite some experience) image; it's best to update to 2.4.330 OTA.

Thank you.
But here is the fact:
"If you already use Linux as your OS of choice you can flash with your current system, grab sbf_flash and the SBF file then simply cd to where you put the files, then:
chmod +x sbf_flash
./sbf_flash filename.sbf"
I have Linux Ubuntu and i have tried it already. No use.

“No use” doesn't quite describe the problem, to be honest.

Gasai Yuno said:
“No use” doesn't quite describe the problem, to be honest.
Click to expand...
Click to collapse
Ok it will flash it flawlessly, no problem. But it does not flash the BP module. It just ignores the fact that in package there are AP and BP firmwares, so sbf_flash will flash only the AP part.

plz help
i have same problem ...................help plz...
Is there any solution for my droid

plz help me friendz i need help

shahjeee said:
plz help me friendz i need help
Click to expand...
Click to collapse
I am not yet able to help but at least i can give an answer that will probably point into the right direction.
What actually happens:
Droid 2 Global has 2 CPUs : OMAP (AP) & Qualcomm(BP)
At some reason the update via sdcard or failed sbf flashing in BP mode erases the BP content and fails to write the new data into the nand/emmc(whatever), so Qualcomm will jump into Emergency download more each time the RSDLite will try to switch to BP mode, thus you will see the QHSUSB_DLOAD device (COM PORT actually) that's it.
The chip is CDMA1x QSC6085 so it barely has any security on board, making it possible to use any Qcom flasher compatible with the chip and + ramdownloader.
What to do:
Get a qualcomm flasher (PSAS or other tools)
Get a ramdownloader (boot loader) for the 6085 (can be found, for older phones)
Extract the original SBF file content and use the *.mbn files and flash it.
This way may help.

Thank you alot of you reply me can you explain me step by step and software links ,................................thanks..
i have mac pc and windows both

[Q] [BRICKED]Cubot GT72

I bought a Cubot GT72 from the net - its basically a chinese knock-off with some very nice specs. And it was working great out of the box; but I had to experiment - right?
Edit: cannot post links; but if you got to www cubot net - you can find the phone easily. The stock ROM is also available.
I fired up MTK-Tools and rooted the phone - no problem there. Then I tried to create a custom CWM and install - that's when things starting going down the drain. It overwrote the recovery and boot partitions - so the phone stopped working. And since then I have been trying various ways to unbrick it.
Luckily, I have another phone with the exact same specs - and was able to download a backup using MTK-Tools and another one using SPFlash.
Problem - the phone is not switching on at all. When I connect it to the computer (after installing the MTK drivers) - nothing happens. When I connect without battery and keep the Up volume pressed - the computer detects an "MTK COM Port", installs it and within 5-10 seconds the port disappears, comes back after 5-10 seconds - and this cycle keeps repeating. I'm not able to connect to the phone using wither MTK-Tools or SPFlash.
When I connect the working phone - it shows up as "MTK VIA COM Port" and I can connect to it using SPFlash.
Have opened the phone and looked for test points - found one that switches on the phone and connects to the computer - but the result is the same as when I connect with the volume up pressed.
Please help - I'm at my wits end.

Drivers
dushyantahuja said:
I bought a Cubot GT72 from the net - its basically a chinese knock-off with some very nice specs. And it was working great out of the box; but I had to experiment - right?
Edit: cannot post links; but if you got to www cubot net - you can find the phone easily. The stock ROM is also available.
I fired up MTK-Tools and rooted the phone - no problem there. Then I tried to create a custom CWM and install - that's when things starting going down the drain. It overwrote the recovery and boot partitions - so the phone stopped working. And since then I have been trying various ways to unbrick it.
Luckily, I have another phone with the exact same specs - and was able to download a backup using MTK-Tools and another one using SPFlash.
Problem - the phone is not switching on at all. When I connect it to the computer (after installing the MTK drivers) - nothing happens. When I connect without battery and keep the Up volume pressed - the computer detects an "MTK COM Port", installs it and within 5-10 seconds the port disappears, comes back after 5-10 seconds - and this cycle keeps repeating. I'm not able to connect to the phone using wither MTK-Tools or SPFlash.
When I connect the working phone - it shows up as "MTK VIA COM Port" and I can connect to it using SPFlash.
Have opened the phone and looked for test points - found one that switches on the phone and connects to the computer - but the result is the same as when I connect with the volume up pressed.
Please help - I'm at my wits end.
Click to expand...
Click to collapse
Ok Google "mt6572 com port drivers" and look for ***.ftdichip.com/Drivers/VCP.***‎, install the software off that site and see if your computer recognizes the com port, hopefully you'll be able to flash the original rom back to it, let me know how you get on :good:

neosnake991 said:
Ok Google "mt6572 com port drivers" and look for ***.ftdichip.com/Drivers/VCP.***‎, install the software off that site and see if your computer recognizes the com port, hopefully you'll be able to flash the original rom back to it, let me know how you get on :good:
Click to expand...
Click to collapse
Thanks Neo, The driver is installed - the problem I'm facing is that the phone keeps going offline every 30-40 seconds and hence am unable to flash.

okies
OK thanks for the reply. Its obvious these MTxxxx devices wait for a signal when you plug them in.
1.Try going to the SDK folder and open a command prompt, type fastboot flash boot "boot.img" > point the boot.img to where you have downloaded the original boot.img for the device.
2.When the fastboot gives you the [waiting for device] prompt plug in your phone.
Let me know how you get on, i'm going to be working on a program to flash these phones from windows. :good:
p.s if the above works then flash your original recovery as well

neosnake991 said:
OK thanks for the reply. Its obvious these MTxxxx devices wait for a signal when you plug them in.
1.Try going to the SDK folder and open a command prompt, type fastboot flash boot "boot.img" > point the boot.img to where you have downloaded the original boot.img for the device.
2.When the fastboot gives you the [waiting for device] prompt plug in your phone.
Let me know how you get on, i'm going to be working on a program to flash these phones from windows. :good:
p.s if the above works then flash your original recovery as well
Click to expand...
Click to collapse
Hi Neo - tried. The phone gets detected, but fastboot remains stuck at [waiting for device]. Please see screenshot.
Also, I think the preloader is also gone

Diffrent Drivers
Ok i noticed on there website that there are a different set of drivers, where the ones you have installed emulates a com port the other ones gives you direct access to the USB port, go to adb and type adb devices so that your phone will show up in the device manager, uninstall those drivers and install these ones ftdichip.com/Drivers/D2XX.htm.
Then try and flash the preloader in the usual way, first type flash preloader {name of file} then connect your phone and hopefully you will be able to flash your phone again.
Let me know how you get on again :good:

neosnake991 said:
Ok i noticed on there website that there are a different set of drivers, where the ones you have installed emulates a com port the other ones gives you direct access to the USB port, go to adb and type adb devices so that your phone will show up in the device manager, uninstall those drivers and install these ones ftdichip.com/Drivers/D2XX.htm.
Then try and flash the preloader in the usual way, first type flash preloader {name of file} then connect your phone and hopefully you will be able to flash your phone again.
Let me know how you get on again :good:
Click to expand...
Click to collapse
Apologies for the late reply - tried your method - the phone gets detected as MediaTek DA USB VCOM port - but fastboot or SP flash are unable to detect.
Also, now I have managed to brick the other phone also. Was trying to upgrade the ROM from cubot's website. And even that one is bricked
Really frustrated here.

dushyantahuja said:
Apologies for the late reply - tried your method - the phone gets detected as MediaTek DA USB VCOM port - but fastboot or SP flash are unable to detect.
Also, now I have managed to brick the other phone also. Was trying to upgrade the ROM from cubot's website. And even that one is bricked
Really frustrated here.
Click to expand...
Click to collapse
Also, is there a way I can create a scatter file from the ROM I downloaded using SP Flash?

dushyantahuja said:
Also, is there a way I can create a scatter file from the ROM I downloaded using SP Flash?
Click to expand...
Click to collapse
The full ROM dump has been uploaded here - is there any way I can simply flash the entire dump back into the phone.
http://www.4shared.com/file/wtNcfbRu/ROM_0.html

hi, did you manage to work out anything? i have the exact same problem with my GT72, and i'm out of ideas.

I finally gave up and sent it for repairing. The vendor has been trying to repair it for the last 2 weeks and has given up too. The problem with my phones is that they are not original cubot - the seller on aliexpress is selling fake cubot phones - and we're unable to find the correct files to write to the phone.
Now if only I could find a way to write back the ROM0 file without the scatter files - I had though that would be easy, but am unable to do anything about it
megariffer said:
hi, did you manage to work out anything? i have the exact same problem with my GT72, and i'm out of ideas.
Click to expand...
Click to collapse

dushyantahuja said:
I finally gave up and sent it for repairing. The vendor has been trying to repair it for the last 2 weeks and has given up too. The problem with my phones is that they are not original cubot - the seller on aliexpress is selling fake cubot phones - and we're unable to find the correct files to write to the phone.
Now if only I could find a way to write back the ROM0 file without the scatter files - I had though that would be easy, but am unable to do anything about it
Click to expand...
Click to collapse
maybe i have a fake one, too then. wierd stuff, that is. faking a $60 phone...
anyway, i'm guessing you can only use that ROM_0 file to create a proper preloader.bin for the phone, but you need a working one for that.
you could do that in MTK droid root & tools, but since our phones doens't get detected, we're stumped.
i think having the right preloader could push us to the right direction, but i'm not planning to order a new phone to revive my dead one
anyway, if you make any progress, let us know!

megariffer said:
anyway, i'm guessing you can only use that ROM_0 file to create a proper preloader.bin for the phone, but you need a working one for that.
Click to expand...
Click to collapse
I backed up the ROM_0 file from a working phone (had 2 - broke both); have uploaded it and shared in this thread. So, if you can create the preloader.bin from it - please be my guest.

dushyantahuja said:
I backed up the ROM_0 file from a working phone (had 2 - broke both); have uploaded it and shared in this thread. So, if you can create the preloader.bin from it - please be my guest.
Click to expand...
Click to collapse
i know you uploaded it, but the problem is that i can't do anything with it in MTK droid root & tools, since it only works if there is a working phone connected to the pc.

megariffer said:
i know you uploaded it, but the problem is that i can't do anything with it in MTK droid root & tools, since it only works if there is a working phone connected to the pc.
Click to expand...
Click to collapse
I had even created a scatter file using MTK Droid - the only problem is the scatter doesn't work with the phone. See if it helps you.

dushyantahuja said:
I had even created a scatter file using MTK Droid - the only problem is the scatter doesn't work with the phone. See if it helps you.
Click to expand...
Click to collapse
here's my "progress":
i was able to salvage a preloader.bin from your dump, this was the only one i could get flash tool to start preparing flashing.
i ran into numerous errors after that, but i managed to build a seemingly flashable rom, but it just does not work.
i could format the nand with it, but when i try to flash, it says that the bootlader exceeds partition boundary, whatever that means.
so i'm pretty much stuck at this point, but i'll attach the preloader for you, maybe it will work with your scatter.
the scatter btw did not work for me, since the addresses were wrong (i guess that scatter is for 512MB version, too).
so i built a scatter from scratch with notepad++ it's in the zip, too.
now i just wish there would be someone with a 256MB version able to make a backup with mtk droid and share with us.

megariffer said:
but i'll attach the preloader for you, maybe it will work with your scatter.
Click to expand...
Click to collapse
Thanks - let me try to flash the preloader this weekend and see how things go...

dushyantahuja said:
Thanks - let me try to flash the preloader this weekend and see how things go...
Click to expand...
Click to collapse
how's it going?

arsenal3008 said:
how's it going?
Click to expand...
Click to collapse
Didn't get any time last weekend - will update this weekend.

Wrong firmware.
dushyantahuja said:
Didn't get any time last weekend - will update this weekend.
Click to expand...
Click to collapse
Hi, the same problem, have you figured it out? Thanks for your help ...

Nexus 5 QPST/QDLoader Mode

So, messing around with kernels and stuff, I wound up with a bricked device (wouldn't turn on, no response to anything, etc [I did eventually manage to get it functional again through a combination of button mashing and praying])
However, when plugging it into my computer, it showed up as "Qualcomm HS-USB QDLoader" which seemed interesting.
Searching the internet, I found several things. The QPST (Qualcomm Product Support Tool) Software suite, as well as other less useful links about the LGFlash tool, etc.
The programs also makes reference to debug and other modes, but there isn't a lot of documentation on the internet.
What I want to know is, is there a way to put the device back into the QDLoader or other QPST related modes so as to either update the firmware again, or just make backups for future use?
If there is, this seems like it would be a great tool for undoing any damage to the phone that isn't hardware related (the documentation says this part resides on a read only chip[which it seems fastboot doesn't])

It looked like you borked your phone to the point where there was nothing recognizable as Android left on it. I don't know anything about this loader but based on my past experiences dealing with proprietary OEM tools (Samsung KIES), I hope I never find myself in a situation where I'd need to learn. :crying:

Turn off your phone. Press all the keys if nothing happens your phone bricked. If you end up qualcomm 9008 mode we cant do much, because we dont have a working flash programmer and a working bootloader which would be flashed to the phone with the flash programmer. You can do 2 things. Replace your motherboard, or find the emmc pins on the motherboard to get direct acces to the storage then with a modified sdcard reader you could have access to the storage content then you could restore the bootloader. This is pretty hard method almost impossible.
If you have qualcomm 9006 mode then you can restore the bootloader with any kind of linux, because in 9006 mode the phone acts like a external hdd.

May I ask how exactly you messed around with the kernels to get this? Did you flash an incompatible kernel or something?

It sounded like he resolved his issue and wanted to know if this hidden mode can be used.

Wakamatsu said:
It sounded like he resolved his issue and wanted to know if this hidden mode can be used.
Click to expand...
Click to collapse
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off

It works!
bitdomo said:
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off
Click to expand...
Click to collapse
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...

caffeinatedangel said:
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...
Click to expand...
Click to collapse
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.

Well darn
bitdomo said:
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.
Click to expand...
Click to collapse
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!

I've never bricked my phones that bad man when I was a noob I installed safestrap on a device with an unlocked boot loader and tried to flash a ROM it didn't work out to well,man that was about two years ago

caffeinatedangel said:
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!
Click to expand...
Click to collapse
There were two placed where qualcomm documentatiosn could be found. One was a chinese forum where you have to be veteran or admin to get access to the files. This forum not exist anymore. The other is a chinese ebay like website where they are selling qualcomm documents for 3000 usd.
If you search for msm8974 boot flow or sahara protocol you will find file names for qualcomm pdf documents. Sadly just file names no download possibilty.

2.0.4DJB TCL 10 Pro Firmware Update

This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch

KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.

JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.

KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.

JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to

KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.

Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.

JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar

Well you're in luck as it is just a .bat file program simple notepad++ will do.

I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.

Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol

@KaptinBoxxi Sounds like you have Ambient Display on for notifications.

mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD

that sucks... could try reseating the screen's ribbon cable :-/

can anybody share the full update rom about android 11?

top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page

LG W41 (LM-K610IM) dead bricked by my stupidity. Could it be somehow revived?

Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.

Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient

Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore

The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers

you should be able to repair preloader from bootrom mode (BROM)

How to enter bootrom mode. I am sorry if it is a noob question

Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html

Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved

you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.