Develop Bugs

I bricked my G4 H812. No download mode, nothing on screen, only QHSUSB__BULK.

So I messed up flashing the rooted system.img:
Code:
dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
I used skip instead of seek
{
"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"
}
so I've wiped out the partition table and pretty much everything.
The good news is I have a backup of the entire /dev/block/mmcblk0 that I made before attempting to modify anything, so hopefully it's possible to recover, if I knew how...
When plugging the cable in, the phone appears as QHSUSB__BULK device in Windows, and "qcserial ttyUSB0: Qualcomm USB modem converter" in Linux. Otherwise, nothing happens. Whether I have battery/SD card inserted or not, holding volume up or any other buttons, there's no response at all. Blank screen, no LED, no vibrate, it does absolutely nothing. The only thing it will do is reconnect if I hold the power button for several seconds. fastboot.exe doesn't detect any devices. Windows device manager doesn't list any disks except the computer's actual hard drive.
I'm sure there must be some way to recover it using this QHSUSB__BULK mode, but I haven't found anything.

I'm in the same boat as you, but with H815. With proper drivers your device will be recognized as a Qualcomm 9008, I think. I have very heavily researched this, and unfortunately, there is no available way to recover. For G2 and G3, there was a tool called BoardDiag. Perhaps this will at some point be made compatible with G4.

I've heard about these drivers and BoardDiag but haven't found them. Maybe tomorrow I'll look for them more... otherwise I can probably take it to the shop under warranty, but I worry they'll give me back a new one with a new firmware and I'll have to wait for another root exploit... :|

Silly question that won't help you fix your problem but... Why did you type out that? Why not just copy paste?
Sent from my Nexus 7 using Tapatalk

Try this no promises
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142

tobesedated said:
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!

RenaKunisaki said:
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!
Click to expand...
Click to collapse
Stupid question but you are using linux to try this right? I don't know that it will work in Windows

Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...

RenaKunisaki said:
Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...
Click to expand...
Click to collapse
lemme know how that goes, im sitting on a brick too. i just figured id wait a few weeks see if any fixes pop up before i send back to lg. i meant to zero out laf.img to access fastboot mode to try oem unlock on ls991, but im a dummy and got way in over my head and deleted aboot by accident. my windows xp netbook doesn't even see a qualcomm device. i havent tried on the raspberry pi yet. the only response i can get from the phone is a battery symbol with a ? , and onlyif i plug in usb from pc with no battery in the phone

Yeah, I heard some people wouldn't get the Qualcomm device popup, but would get the question mark battery icon. For me it was the opposite; the device shows up (as QHSUSB__BULK in Windows and ttyUSB0 in Linux) but absolutely nothing on the screen no matter what I do.
My guess is because some people only wiped out laf or aboot or a couple other things that are used later in the boot process (so it will boot, but fail quickly when it can't find them), whereas I wiped out the entire partition table, so the very first step fails; probably the hardware itself (the modem, CPU, or who knows), upon not finding a bootable partition, goes into some backup mode where it can be flashed over USB. (Just nobody seems to know how to flash it from there...) Or the very first sectors of the MMC contain the actual stage 1 bootloader (I noticed partition 1 starts at sector 32768, so some 16MB at the beginning is unaccounted for), and that code is responsible for disabling the QHSUSB__BULK mode, but having wiped out even that, it stays enabled. (Possibly another way for root/unlock if someone examined it closer...)

Yeah no easy way you need a direct flashing eMMC tool

I'm guessing no one managed to fix their brick? Same thing happened to me after attempting to revert to an earlier version bootstack.zip.
From my reading of G3 unbricking, the attempted-downgrade flag got tripped and so it's in the same 9008 state. Without access to the LG supplied .mbn files, there's no way to do any sort of fix. i.e. this problem could be easily fixable, just not by anyone without LG tech tools.

Contact @vn_mobile

Has a system image been posted? I'm kinda in the same boat...

dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
mean 3955228672 byte (~ 3.9GB) of eMMC (mmblk0) is CLEAR
If can go to my country i can recovery for you or

Hi,
Read this web pages.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
http://www.androidbrick.com/lg-g3-hs-usb-qdloader-9008-unbrick/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/

Looking at some of the other posts on here, I think the only thing to do at this point is hope you still have warranty.
(Not really sure how I'll fare though, I just got this one as a replacement for a bootlooping G4 yesterday)

I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay

xxxwalo said:
I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay
Click to expand...
Click to collapse
This phone isnt even a year old yet... why would you buy another instead of sending it off to LG for Warranty repair. There are a lot of these that have bricked from OTA update.

If someone simply post the AP Chipset driver for BoardDiag.exe to start, it will be solved....
I solve my G3 with BoardDiag.exe and flashing all original image partition extracted from TOT file.... But I can't find any AP CHipset that support G4 yet.

HTC M9 Qfil flash help needed (Qualcomm MSM8994) {Images Attached}

In my position I'm having bricked HTC M9 which need to recover user data (Photos of new born kid which don't have backups)
Symptoms :-
NO power LED (Even charger connected)
NO HTC Logo
NO boot menu
NO vibrations
Power On button do nothing
Power + Volume down nothing
But when it connected to PC it shows Qualcomm service port "Qualcomm HS-USB QDLoader 9008 (COM8)"
After spending long time on reading I figure out If I'm able to fix the partition table & connect Qualcomm HS-USB QDLoader 9006 interface,
Then the eMMC can be mounted to local PC via USB. then I can recover my data,
So I'm planing to use Qfil to flash required data to mobile
So I downloaded Qfil from here
Downloaded stock firmware from here or here
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
prog_emmc_firehose_8994_lite.mbn file found & attaching
I'm still unable to find above three files any where from internet,
Please can some one help me to find this files (or extract the from some where)
I'm attaching some Images of device manage view, Qfile & stock ROM I have respectively
{
"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"
}

Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.

shivadow said:
Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi My Friend, thanx for take your time,
Yep I read it, but the problem is
1. to use this tool we need "prog_emmc_firehose_8994_lite.mbn" file
2. we can only get "rawprogram0.xml" file from this, still need "patch0.xml"
Any one could help me with this will be a great help.
Thanx Mate

Good news , I have found the programmer for MSM8994 "prog_emmc_firehose_8994_lite.mbn"
I'm attaching it above for any one who is in the same boat as me.
Please some one help me to find "rawprogram0.xml and patch0.xml" files for HTC M9
https://drive.google.com/file/d/0BzypAwIfVp1gV1Vjc2FSQlhlaHM/view?usp=sharing

Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.

Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR

war357 said:
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR
Click to expand...
Click to collapse
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.

Sneakyghost said:
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.
Click to expand...
Click to collapse
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br

Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
Actually these phones are pain to me ? taking them apart and reassembling them isn't easy at all. Sadly. And the new HTC U isn't much better
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
war357 said:
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br
Click to expand...
Click to collapse
It's m possible Right now. Or I don't know any way. We don't have the resources for that. I could be wrong, but it gets harder getting these Files

Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.

war357 said:
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
Click to expand...
Click to collapse
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml

shivadow said:
Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.
Click to expand...
Click to collapse
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR

For info: https://forum.xda-developers.com/showpost.php?p=68390222&postcount=11

Bro, that was a great help,
That was a huge favor.

That was a huge favor.....
Thanx bro, thanx a lot
One more file & I'm goor to go
See you mate!

Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
and converted to rawprogram0.xml
Click to expand...
Click to collapse
war357 said:
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR
Click to expand...
Click to collapse
Thanx a lot bro, taking your time for me is much appreciated,
If possible please help me to get patch0.xml also
Thanx again

Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml
Click to expand...
Click to collapse
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR

war357 said:
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR
Click to expand...
Click to collapse
Try to use the zeroed file (empty content)

Golv said:
Try to use the zeroed file (empty content)
Click to expand...
Click to collapse
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G

gda_scooby said:
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G
Click to expand...
Click to collapse
Hi,
No Bro, Still no luck,
I don't know exact way to extract patch0.xml,
Normally it should come with firmware file,
But no sign of that on internet,
Seems really bad luck,
Any way Bro, thanx for your support,:good:

Possible Brick - Flashing Unlock Not Allowed

I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!

So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?

Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).

I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?

ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.

That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk

ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.

I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"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"
}
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?

Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.

ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.

Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk

I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?

Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.

ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:

0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk

Aiit.tnx

@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.

SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.

Question RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU

Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and Voilà!
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^

THANK YOU SIR

To ask a dumb question, but is this only the 6 or for the pro as well?

Works for both

Thank you so much, it work after someone help me erase flash

Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?

anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol

Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI

CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning

Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.

cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine

Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?

cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out

Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.

Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks

Same issue for @CyberWolf92

Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.

Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.

Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"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"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge

Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot

Question Meta mode in Nokia G10 TA-1334

Dear Experts,
I'm trying to rewrite lost IMEI after flashing stock rom (No backup). Tried everything in my sleeve. I am trying to find out how to enter in Meta mode so I can use the SN write tool or Modem meta. Tried following things:
adb reboot meta - nothing happening except reboot.
Vol button combo - nothing but fastboot and recovery.
Root - bootloader/oem can't be unlocked
Tried verity of tools nothing happening.
Brom mode - TP needs to be connected all the time (This is how I flashed the Rom).
Does any of you guys know how to activate Meta mode in this device. Seems nobody shared that detail over internet. Please help..
Thanks in advance.

eb60700 said:
Dear Experts,
I'm trying to rewrite lost IMEI after flashing stock rom (No backup). Tried everything in my sleeve. I am trying to find out how to enter in Meta mode so I can use the SN write tool or Modem meta. Tried following things:
adb reboot meta - nothing happening except reboot.
Vol button combo - nothing but fastboot and recovery.
Root - bootloader/oem can't be unlocked
Tried verity of tools nothing happening.
Brom mode - TP needs to be connected all the time (This is how I flashed the Rom).
Does any of you guys know how to activate Meta mode in this device. Seems nobody shared that detail over internet. Please help..
Thanks in advance.
Click to expand...
Click to collapse
Please head on to download the official tool

mvikrant97 said:
Please head on to download the official tool
Click to expand...
Click to collapse
I did it from the same website, but still not detecting.

eb60700 said:
I did it from the same website, but still not detecting.
Click to expand...
Click to collapse
Please make sure you have all the required drivers installed. If not please just install HMD Device Kit and it will install all the necessary drivers or you can manually install drivers from here.

Hi mvikrant97,
Sorry for the belated reply, I have installed HMD Device Kit drivers as per your link. but still its not detecting by Modem meta or SN Writer tool. While I connect the switched off phone this shows up in device manager.
{
"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"
}
Thanks for the helping hand mate.

eb60700 said:
Hi mvikrant97,
Sorry for the belated reply, I have installed HMD Device Kit drivers as per your link. but still its not detecting by Modem meta or SN Writer tool. While I connect the switched off phone this shows up in device manager.
View attachment 5822495
Thanks for the helping hand mate.
Click to expand...
Click to collapse
Were you able to connect device before when it was in working condition?
It also seems like the cable you are using is malfunctioned or the device USB port itself.
I'm sorry but I will have to ask you questions to diagnose the problem.

mvikrant97 said:
Were you able to connect device before when it was in working condition?
It also seems like the cable you are using is malfunctioned or the device USB port itself.
I'm sorry but I will have to ask you questions to diagnose the problem.
Click to expand...
Click to collapse
As I have mentioned before, I flashed this device with stock ROM using the same usb cable by triggering Test point in Brom Mode, So I highly doubt this is because of the faulty usb cable. Thereafter I lost my IMEI, but fortunately I had one IMEI noted down beforehand. I am trying to rewrite that IMEI so that I can use my SIM. Seriously what is this Meta Mode? This means nokia G10 doesn't support Meta Mode?
Please feel free to ask any question or suggestions mate.

eb60700 said:
As I have mentioned before, I flashed this device with stock ROM using the same usb cable by triggering Test point in Brom Mode, So I highly doubt this is because of the faulty usb cable. Thereafter I lost my IMEI, but fortunately I had one IMEI noted down beforehand. I am trying to rewrite that IMEI so that I can use my SIM. Seriously what is this Meta Mode? This means nokia G10 doesn't support Meta Mode?
Please feel free to ask any question or suggestions mate.
Click to expand...
Click to collapse
You will need Pandora Tool to fix up the IMEI.
But as much I know you need to have the backup beforehand to fix the issue.
You may refer to the video below

Thanks for the heads up. Looked up the tool, seems expensive than the G10 itself. Still wondering why the phone is not detected though.

eb60700 said:
Thanks for the heads up. Looked up the tool, seems expensive than the G10 itself. Still wondering why the phone is not detected though.
Click to expand...
Click to collapse
Maybe because the phone does not support Meta mode