Database Develop

Fastboot Unlocked?

So I decided just to see what my fastboot looked like - attached.
{
"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"
}
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.

mxgoldman said:
So I decided just to see what my fastboot looked like - attached.
Is that normal for it to be unlocked? Everything I've heard says this is supposed to be super locked down.
Click to expand...
Click to collapse
I think it says "bootloader LOCKED" in the fastboot screen. That means, you can ONLY flash motorola compiled operating systems (specifically kernels).;
If you want to try, run a fastboot unlock-bootloader command when running in fastboot. A locked bootloader will tell you something along the lines of "command not valid"

Do not flash anything on your phone. That looks to be a unlocked bootloader!
Sent from my DROID4 using Tapatalk 2

jsnweitzel said:
Do not flash anything on your phone. That looks to be a unlocked bootloader!
Click to expand...
Click to collapse
Wait, wouldn't that be a positive that would make flashing them easier?

I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Sent from my DROID4 using Tapatalk 2

mxgoldman said:
Wait, wouldn't that be a positive that would make flashing them easier?
Click to expand...
Click to collapse
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!

podspi said:
I think he meant "don't flash anything that might overwrite your unlocked bootloader" :laugh:
Anyway we could pull it or something? Probably not eh? OP, where did you get?!
Click to expand...
Click to collapse
Makes more sense.
That's my little secret.
I could probably pull whatever from it, but I'd need some help for what you'd like pulled. Haven't rooted it or anything yet.

didnt this happen with a GSM RAZR before? dont get me wrong, i'd love to unlock my bootloader! someone bring this to their attention

FYI, on Milestone XT720, Motorola left a partially working fastboot--we can "fastboot boot boot.img" to boot self-built kernels and this bypasses the signature checks. But you have to boot via USB each time, if you use "fastboot flash boot.img" fastboot will write the kernel and reboot, but the signature check will fail after reboot.
http://forum.xda-developers.com/showthread.php?t=821210
Here's one way to muck with a kernel to change uname strings:
http://forum.xda-developers.com/showthread.php?p=11975260#post11975260

jsnweitzel said:
I emailed someone who knows these things. He says its an engineering model. So it doesn't help the rest of us.
Click to expand...
Click to collapse
FWIW, the "SE" is the giveaway. If it said "S", you would be in business.

Rzrbck, how so, if it could be retrieved from the phone? Maybe I'm not understanding, but if we had that bootloader is it not like the normal S model with full permissions to the phone?

what makes it an engineering model? are the physical components the same, or is it a software setting that if we changed could unlock the phone?

would it be possible via hardware to dump an SE bootloader, and flash it to a S devic? I would be willing to give this a go if its possible.

if we could get the bootloader images off that phone an unlock for the Droid 4 might be possible. Assuming, of course that both the S and the SE model use the same keys.

Tell me what I can do to help.

I wish I knew what to do, but in the mean time, here's some literature on how the lock works (it's for the milestone, but the d4 might use the same infrastructure).
The bootchain:
http://www.droid-developers.org/wiki/Booting_chain
The mbmloader: this loads the bootloader, if this is replaced with a version that doesn't check signatures, the bootloader can be permanently replaced:
http://www.droid-developers.org/wiki/Mbmloader
The mbm (bootloader) does it's own signature check of the kernel before booting it.
If either the key burned into the phone's fuse, or the key the mbmloader uses to check the mbm are the same on both devices, one or both of those partitions can be flashed with with the unlocked version. If they're both different, this is a dead end.
The only other option after this (aside from espionage)would be to crack the signature system directly by either creating an unlocked version of the bootloader and patching it in a way that it generates the same hash, or discover a new way to factorize large (2048 bit) numbers, and reverse engineer motorola's private signing key. (If you were to discover this factoring method, nearly every security company would have to retool.)
edit: careful updating your phone, an OTA can relock your phone. The more I read, it seems less likely that the bootloader is encrypted. Dumps should be made, but this is going to require someone with greater knowledge than I.

how would we go about doing this?

dewhashish said:
how would we go about doing this?
Click to expand...
Click to collapse
It seems like you load a special kernel module to unhide the bootloader partitions then simply use the dd command to make an image copy onto the sdcard.
iow, we need a dev.

well the only ones i know might be kholk, hashcode, and p3droid

This got quiet. No news on this yet?

I think I bricked it - CWM unable to mount Ext SD & Data

First few things: I've searched already, can't find any similar threads that actually help. I have the international version. I was running the CM10.2 Rom prior to 'the accident'. I will put a bounty on this if I have to.
There's a bit of a story to this so I'll go over it all - not sure what's relevant.
I've been running out of storage for days, a 64GB SD card is in the mail. I currently have an 8GB one as well as the internal 16GB, both of which were near full, but the external one had relatively more than the internal one, so I decided to use foldermount and link2SD to move some space over. That all went fairly well.
This morning I got invited to the Aviate Beta launcher, which looked interesting. Tried to install, didn't have enough space. So I decided to make a backup of Nova, go into the play store, uninstall nova to free up space and then install Aviate without leaving the playstore. It worked, turns out I don't like Aviate much, so I worked backwards. Uninstalled Aviate, went to install Nova. Not enough space (idk how). Uh oh.
So I deleted some less-necessary apps that I could reinstall later. Not enough storage. Notification comes up in the bar along the lines of "storage critically low, device may malfunction". Now whenever I attempted to enter settings, the process crashed. Great. Simple fix, flash a NANDroid back-up in CWM. I can't remember what the message was, but there was something wrong with the back-up.
Wiped everything and tried to flash CM10.2 from the external SD Card but it wouldn't mount. Data also wouldn't mount. I tried several SD Cards ( ie about 10, different brands, sizes, classes, etc out of hope). So I decided I'll open up and Odin and just re-do everything per /showthread.php?t=2387980.
Turn the phone back on, stock Jelly Bean lockscreen was there, and once unlocked only the notification bar was there (no launcher). So I used different versions of Odin, different cables, downloaded the image several times, etc etc. Nothing fixed it. In fact, it's worse now. after booting past the Samsung logo, the screen just goes black now. smh
Can anyone help? It would be extremely appreciated. It's also a time sensitive issue as I need the device for work on Monday.
Sorry if I've missed anything. Yes I'm a noob, but you great people at XDA have helped a lot of people out before so I'm hoping you can help me.
Thanks!

Sorry to bump...
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.

tiskael said:
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.
Click to expand...
Click to collapse
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.

Devo7v said:
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.
Click to expand...
Click to collapse
Yes, the i9295 - the international version. The Odin md5 can be found on this thread: /showthread.php?t=2387980.
Sorry if this sounds rude (it's not, I just don't know how to use kies) but what's that supposed to do? I can't find a way for Kies to fix anything... I tried this thread: /showthread.php?t=1984717 but when I have to enter my phone model (GT-i9295) it says "Please check the model name and enter it" and closes the pop-up window within kies. Any more help?
Thanks for trying so far.

Sorry for bumping but i need this fix. $100 to the first person who can fix this by Monday.

I can't possibly believe that no-one knows how to fix this, or at least whether it's fixable or not. Is anyone willing to answer my question?

Check this threads or ask the guys who helped me there, they are Awesome
So after boot you get an totally black screen? Only theorigial Samsung boot logo before it turns dark?
I had this problem twice, but can you tell me if you start the phone after the dark screen do you have sound (like the phone still works, but only no screen) or nothing?
The first time i had sound, need to say that i never solved this problem, re-installed stock firmware, (recovery still works, you only need to know wat to puch) Unrooted my phone, and send it in for waranty, They send me a new phone, never know what was the problem, it can be o broken screen, but i never believed it totally... check this thread for that: http://forum.xda-developers.com/showthread.php?t=2363185&page=9
The other time i had this i installed a other CWM Recovery Version, i had one installed, but some problems with it, installed an other version, after Reboot the Same Samsung Logo...Dark screen, installed this CWM: http://forum.xda-developers.com/attachment.php?attachmentid=2464887&d=1387533161
Good Luck with it M8

Here is something that could/couldn't help you...
I am not sure/not tested this so i am not responsible for anything that happenes to your phone
1.DOWNLOAD A STOCK FRESH SAMMY ROM FROM SAMMOBILE
2.Use odin3.7
3.Open ODIN AND CHOOSE PDA THEN CHOOSE THE FIRMWARE YOU EXTRACTED /DOWNLOADED
4.Now flash the firmware
5.When reached at the state you previsouly in reboot to download mode again and do step 3 again
6.Now download the pit file from HERE
7.In odin screen make sure 3 buttons are checked F.rest time , auto reboot , REPARTITION
8.Now choose frimware in pda
9.CHOOSE THE FILE YOU HAVE ALREADY DOWNLOADED FROM ATTACHMENT IN SIDE THE PIT BOX LIKE THE PICTURE UNDER
{
"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"
}
10.hit start and let the device flash like normal
11.it will auto reboot ...hope this fixes your issue
THE PIT FILE IS CALLED i9295.pit and is from here
HERE IS SOME INFO ABOUT PIT FILES
What are pit files ?
A pit file is a kind of file often used in samsung phones / tablets , these files contain partition tables of the device and the spaces of them with the arragment of each partition with there corresponding mount points ; these files can difenitly dangerous and can kill your tab/phone with a breeze if not used with care
Click to expand...
Click to collapse
What do pit files really do ?
Pit files can help in fixing a broken mmc for ex:
Click to expand...
Click to collapse
NOTE: I AM NOT RESPONSIBLE IF THIS WILL MAKE THINGS EVEN WORSE
make a try and let me know

try this too..
When my DATA is not mounting, i feel bad as well for in my case, i can't do what mythi's solution by flashing PIT file and stock rom using odin, coz my usb port isn't functioning anymore.. in short, my phone is just charging and not syncing to PC anymore... what i did is go to cwm, tried to mount /data there but gives me an error... what i did next is format /data and /data/media (/sdcard) then flash the new cm11 KITKAT they just finished building... reboot, waited for 2 min or so, boom my phone is back to life..

[GUIDE] Unlock bootloader of Lenovo Tab 4 10 with OEM unlock "greyed out" (TB-X304F/L and other Qcom tablets)

WARNING: DO THIS AT YOUR OWN RISK !!!!
I AM NOT RESPONSIBLE IF YOU START CRYING INTO YOUR BRICKED TABLET
This guide is only for devices with "OEM Unlocking" option greyed out !!!
Others can follow the simpler procedure mentioned in the TWRP thread...
Prerequisites:
QDLoader_HS_USB_Driver (Google it and find)
Hex Editor (eg. HxD)
PC and some brain to understand....
Procedure:
Install the drivers and hex editor.
Clone this repo to PC - https://github.com/Naveen3Singh/BLUnlocker (Thanks to the dev )
Extract the firehose file from stock rom. (eg. "prog_emmc_firehose_8917_ddr.mbn" for TB-X304)
Boot into edl mode using key combo
or using adb
Code:
adb reboot edl
Check the port number in device manager and run " dump_devinfo.bat ".
Mention port number and full path to "*.mbn" file (eg. D:\where\every\it\is\prog_emmc_firehose_8917_ddr.mbn)
A file named " devinfo.img " will be dumped to the working dir. Edit it using an HEX editor as shown below.
{
"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"
}
Save the devinfo.img after editing and run " unlock.bat "
Reboot after success message.
Voila !! You have Successful unlocked the bootloader. Reboot to system by holding the power button.
EDIT (13/01/2020): After unlocking bootloader and restarting, if it asks for password, Reboot to recovery and format data...
Flash TWRP and Enjoy rooting...
PS: The same procedure can be done using QFIL tools (QPST)
Attached:
Firehose file of TB-X304F and TB-X304L (DONT USE ON OTHER DEVICES!!!)
Credits:
Thanks to the dev who wrote the code ( https://github.com/Naveen3Singh )
@hk96 (Myself)
Hit thanks if this helped....

Reserved !!!

Thank you very much! It worked perfectly!

Firehose file for X304L if anyone needs it

Hb20032003 said:
Thank you very much! It worked perfectly!
Click to expand...
Click to collapse
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!

njascgil said:
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!
Click to expand...
Click to collapse
After unlocking, when u Boot into system it asks for a password, even if u didn't set one to start with (atleast in my case).
So you need Boot into recovery and wipe data.
Short answer: yes, factory reset is necessary.
Regarding file version, I hav no idea... May be u can give it a try...

Hb20032003 said:
Firehose file for X304L if anyone needs it
Click to expand...
Click to collapse
Thanks...
Let me add this to OP, so that it is easier for others.

Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.

Chhayank_Sharma said:
Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.
Click to expand...
Click to collapse
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.

hk96 said:
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.
Click to expand...
Click to collapse
ok thanks.

hk96 said:
Regarding file version, I hav no idea... May be u can give it a try...
Click to expand...
Click to collapse
I was going to try it, but it's my daughter's tablet and she didn't let me do it... She is afraid of loosing some games' progress...

Nothing work for me

Eagle-no1 said:
Nothing work for me
Click to expand...
Click to collapse
May be you would have missed something....
This seems to work for most people.

hk96 said:
May be you would have missed something....
This seems to work for most people.
Click to expand...
Click to collapse
I got to work now, I had an old bad cable in use. Thank you.

hk96 said:
PS: The same procedure can be done using QFIL tools (QPST)
Click to expand...
Click to collapse
How? I watched a video and I can load the mbn but I don't know what to put in the xml thing box. I tried doing the method steps but it says Failed to write hello response back to device Did not receive Sahara hello packet from device

Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
could you explain how you did it pleasssee

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
Haha... Everything happens gradually...
rustyrust said:
could you explain how you did it pleasssee
Click to expand...
Click to collapse
I think, the instructions are crisp and clear as possible...
Can u tell where u got stuck ??

Work! You're GENIUS

hello,
I already root some device but here I'm stuck because I don't find the port number in device manager :-( drivers installed and "lenovo tab4 10" displayed in device manager. in properties I have : port_#0002.hub_#0005
I tried use 0002 or 0005 as port number but the .bat script failed each time. do I have correct port number ?
[EDIT] I have "failed to write hello response back to device" message and my tablet is in FFBM Mode.
[EDIT] in FFBM mode, my device is recognized in device manager (but i'm not sure to find the correct port and the script don't work) and in FastBoot Mode (first menu), my device seems to be not recognized in device manager. I guess that the script must be launched in this mode but I miss a driver. I install "adb drivers" + QDLoader-HS-USB_Driver_64bit_Setup drivers. What do I miss ?

Pixel 4xl bricked itself

Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.

You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.

So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.

#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com

#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .

Question My mobile phone suddenly stops working and can only enter 9008 mode

Anyone can take some time to help me extract the rawprogram.xml and patch0.xml of zenfone8. I need these two files to try to repair my mobile phone. At present, the official forum has been closed. I spent four days on Google and saw that many mobile phone users have this problem, I advise friends who want to buy zenfone8 to consider carefully. Thank you. I urgently need these two documents

davinlin said:
Anyone can take some time to help me extract the rawprogram.xml and patch0.xml of zenfone8. I need these two files to try to repair my mobile phone. At present, the official forum has been closed. I spent four days on Google and saw that many mobile phone users have this problem, I advise friends who want to buy zenfone8 to consider carefully. Thank you. I urgently need these two documents
Click to expand...
Click to collapse
Where are the files located?

Sebi673 said:
Where are the files located?
Click to expand...
Click to collapse
Hello, thank you for your attention and help, but I don't know what documents to provide. Can you be more detailed? I'm a novice, please understand

{
"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"
}

Those can't just be extracted and you need the firehose file as well as a minimum (preferably a full EDL flash rom but if you have the 3 components, you can manually flash each partition. Unfortunately I haven't seen the EDL files for this device around..

Andrologic said:
Those can't just be extracted and you need the firehose file as well as a minimum (preferably a full EDL flash rom but if you have the 3 components, you can manually flash each partition. Unfortunately I haven't seen the EDL files for this device around..
Click to expand...
Click to collapse
Thank you for your reminder. Would you like to ask if it's a“ prog_ firehose_ Ddr.elf file”? In addition, I have a manually flash each partition

Andrologic said:
Those can't just be extracted and you need the firehose file as well as a minimum (preferably a full EDL flash rom but if you have the 3 components, you can manually flash each partition. Unfortunately I haven't seen the EDL files for this device around..
Click to expand...
Click to collapse
Are these two documents? If so, that's great. When I enter 9008, it always reminds me that I need rawprogram0.xml and patch0.xml files. Can you teach me how to do it and how to do it? Thank you very much!!!

Sebi673 said:
Where are the files located?
Click to expand...
Click to collapse
Dear sebi673：HI ! are these two files? Can you help me

davinlin said:
Dear sebi673：HI ! are these two files? Can you help me
Click to expand...
Click to collapse
Hi, if you're still covered by warranty, just send it in. The other option would be to flash the phone via EDL, which might not work at all. I didn't mess with that, I just sent It and they changed the motherboard within 3 days.

davinlin said:
Thank you for your reminder. Would you like to ask if it's a“ prog_ firehose_ Ddr.elf file”? In addition, I have a manually flash each partition
Click to expand...
Click to collapse
Correct. I've written a guide on this for the ASUS ROG 5 (linked below)- Follow Method 1. I'm not sure you can get access to flashing partitions without the Rawprog & patch XML's but you can try....
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com

davinlin said:
View attachment 5449999
Click to expand...
Click to collapse
There is nothing much you can do except sending to Asus service centre (most likely motherboard change).
I encountered the same issue last month and had my motherboard changed too - this is a common problem with this phone and many people are complaining.
See thread here

Sebi673 said:
Hi, if you're still covered by warranty, just send it in. The other option would be to flash the phone via EDL, which might not work at all. I didn't mess with that, I just sent It and they changed the motherboard within 3 days.
Click to expand...
Click to collapse
Hi, my mobile phone has only been used for two months and is still under warranty, but if I send it back for repair, it will generate tariff and freight, about $100, but it doesn't matter. I see many people have this problem on the Internet. I want to try to help you solve this problem, although I'm a rookie, ， I want to learn something with your help and finally solve it

Andrologic said:
Correct. I've written a guide on this for the ASUS ROG 5 (linked below)- Follow Method 1. I'm not sure you can get access to flashing partitions without the Rawprog & patch XML's but you can try....
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, thank you for your reply. I will try the method you provided. If it is successful, I will come back and share the method and results with you. Thank you again

napster79 said:
There is nothing much you can do except sending to Asus service centre (most likely motherboard change).
I encountered the same issue last month and had my motherboard changed too - this is a common problem with this phone and many people are complaining.
See thread here
Click to expand...
Click to collapse
Hi，Thank you for your advice and attention. This is the first time I use ASUS mobile phone, and probably the last time. If it takes me time to solve it, it can be regarded as my counterattack to ASUS. Why can't I admit that this is their problem? I can't understand. For such a large company, I read the history of ASUS mobile phone, which seems to be a common problem