Related
Hey guys, I think I may have permanently bricked my device :/ As it is a H810 there is no recovery available so I can only enter download-mode and fast-boot mode. Basically I accidentally flashed the wrong files
dd if=/sdcard/modemst1.img of=/dev/zero of=/dev/block/mmcblk0p24
dd if=/sdcard/modemst2.img of=/dev/zero of=/dev/block/mmcblk0p25
dd if=/sdcard/modemst3.img of=/dev/zero of=/dev/block/mmcblk0p26
as I transferred the incorrect backed-up files from my computer (I ended up flashing my friends H815 backed up files by mistake). This meant that the phone was unable to boot and is now stuck in a boot loop. I have tried flashing the partitions using fastboot flash mmcblk0p24 modemstl1.img without success and in download mode the device is not recognised so I cannot perform an adb push/pull command.
Thankfully I do have the correct img files to flash back on my computer but I cannot figure out how to actually transfer them to the device. A side note- LGUP does work successfully to flash a stock TOT file to Lolipop so if that is able to copy the new ROM to the device and flash the system partition there might be a way to transfer the files over. The only problem I can see is there really is no way to unlock the bootloader and as the files are not 'stock' this may not be possible.
If anyone has any ideas that would be greatly appreciated. Cheers.
But if LGUP is working for you, why dont you use the option to "upgrade" the phone to the version of the ROM you were using ?
My lg g4 h810 is stuck in fastboot mode not recovery mode not downloading please any one have any idea
Mine motog5s updated to stock fw and root uninstalled after it it hangs on boot screen. I flashed stock fw again with fastboot but after restart mobile didn't display anything not even vibrate just blinking notification when connect usb wire . how to unbrick only shows qualcomm hs dloader 9008 what to do, pls. reply.
You cannot log into fastboot mode?
qualcomm hs dloader 9008 = EDL mode, you should be able to restore with QFIL: https://forums.lenovo.com/t5/MOTO-E-1st-Gen/Moto-E-Not-Boot-Up/td-p/3231144 but it looks like motorola doesn't provide the files ... most likely you'll need a service center
Do not use QFIL. To unbrick, we need the blankflash file for G5S. And it is not on the Internet yet. Do not use the blankflash of any other models. Your best bet is to take the phone to a service center.
---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------
Did you try holding the power down button and turning on the phone to enter bootloader?
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
ASHDCBZ said:
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
Click to expand...
Click to collapse
You downloaded the unlock key from Moto website by giving them your device serial number. That's how they know you unlocked bootloader. Service center won't help you. But fortunately, there is a way to revive your phone. But I'm not getting the blankflash file anywhere.
Tell me what exactly did you do to your phone.
Thank you,
Ok I just flahsed & tried stock roms, root & custom roms. Then I flashed stock rom of mine region firmware npp26.102.19 then motorola gave the updates to npp26.102.55-1 Dec. patch. Then next day new update came Feb patch npp26.102.55-4 just after it mobile started hanging & when restart it stuck on boot, not booting just stuck on boot animation. I tried TWRP recovery it said encrypted then I entered the unlock pin then it shows all the folders. Then I again fastboot npp26.102.19 to solve the issue but after flashing & restart it did not boot nor screen on no vibration tried several times but no response, when connect with pc or charger a white notification light blinking only & it detected as QHUSB_BULK something like that then I searched for it & install driver then shows as qualcomm dloader 9008.
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
ShattrdChain said:
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
Click to expand...
Click to collapse
Hmmmmmmmm
Please provide blankflash soon file I'll try.
there is no notification light on my g5s. what is blinking on yours?
Andrew Joseph said:
there is no notification light on my g5s. what is blinking on yours?
Click to expand...
Click to collapse
Next to front flash right side a white light is blinking. Try pressing power button then it will show.
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Andrew Joseph said:
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Click to expand...
Click to collapse
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
does this only happen when you root your phone?
Can someone Help Us?
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
brunovsc said:
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
Click to expand...
Click to collapse
Yes tried this & other blank flash it show only this-----
Failed identify board. Wrong package?
ERROR: error loading package
FAILED: qb_flash_singleimage()->error loading package
other tried this also----------
Found this can anyone try
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
qfil also not flashing sahara error.
I have tried this but there's an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
ASHDCBZ said:
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
Click to expand...
Click to collapse
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
brunovsc said:
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Same error shows in Qfil.
Andrew Joseph said:
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
Click to expand...
Click to collapse
So is it not switch on or displaying anything.
I foolishly ran a
Code:
fastboot flash partition gpt_both0.bin
and rebooted the device without re-flashing the partitions. As a result everything is gone including fastboot and the edl partitions that permit mounting as a mass storage device. The device does show up as a HS-USB QDLoader 9008, however, so I haven't given up just yet, but I don't have a firehose or a complete contents.xml (rawprogram_unsparse.xml and others missing).
Should I abandon all hope??
Thanks!
muddyhikers said:
I foolishly ran a
Code:
fastboot flash partition gpt_both0.bin
and rebooted the device without re-flashing the partitions. As a result everything is gone including fastboot and the edl partitions that permit mounting as a mass storage device. The device does show up as a HS-USB QDLoader 9008, however, so I haven't given up just yet, but I don't have a firehose or a complete contents.xml (rawprogram_unsparse.xml and others missing).
Should I abandon all hope??
Thanks!
Click to expand...
Click to collapse
I think you have to ask how to do in mibqyyo forum to an administrator.
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
durrant111 said:
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
Click to expand...
Click to collapse
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
you can fomat data : - and power before click power
durrant111 said:
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
Click to expand...
Click to collapse
Boot to EDL mode by holding the vol - and power button while your G8 is plugged in your computer, after you hear a disconnection sound immediately press the vol + until you hear a connection sound from your computer.
Now, open QFIL then look for the abl a and b then flash your backed up abl_a nd abl_b accordingly and reboot. And you're good to go again.
I can help you. Do you fix problem ???
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Anybody?
Ratty696 said:
Anybody?
Click to expand...
Click to collapse
.
Ratty696 said:
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Click to expand...
Click to collapse
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
Used method in beginning of this thread. Tried flashing backup
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Ratty696 said:
Used method in beginning of this thread. Tried flashing backup
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Click to expand...
Click to collapse
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
armodons said:
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
Click to expand...
Click to collapse
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Ratty696 said:
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Click to expand...
Click to collapse
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Nobody able to help me?
Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
I'm new to the G8 (not LG), so just now browsing these posts.
First and foremost, this thread shouldn't be in this forum. This forum is for roms, kernels, recoveries and other development.
This thread is a question about a guide (which is in guides forum). This 'question' is not development of a rom, kernel or recovery, it's a question.
I'd suggest, if you want people to respond that can help, ask the question in it's individual guide thread, that's where the people that know the most about it will be. If you get no response in that thread, then maybe think about posting the question in the questions forum.
but here? in dev forum? absolutely the wrong place for a question about a guide.
cheers
Thread moved to Q&A section.
Thanks!
woodman
Senior Moderator
@durrant111
So to the original OP; 2 things; If your device isn't recognized when in fastboot mode, that's because you don't have the right driver installed in WinBlows.
You have to download the LG USB drivers, install them, then in device manager select the "! Android" and install the driver (usually says ADB) and then 'fastboot devices' will see the phone.
Second; if you ever get a message telling you that 'Data Overflow' then you are absolutely making a big mistake. When you did the backup of your abl(s) (and other partitions), you should have renamed then one by one, that way you don't make the mistake of naming the laf_a partition as the abl_a partition (or any name other than what ti should be). If you flash the wrong partition you run the risk of overwriting the nearby partition, which would make the device essentially unusable except only to qfil.
Lastly, yer lucky the device is VZW, as they make their kdz available and you can use use lg up to get back to stock. If it was Sprint or At&t you'd be scrambling to find a qfil or bkerler backup someone luckily made that you come across (a much more unlikely scenario).
Good luck, you've probably already moved on from this, but just in case, thought I'd mention the above.
cheers
Ratty696 said:
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Click to expand...
Click to collapse
Unfortunately at&t doesn't make their kdz available. You can be 99.9% positive the only thing this person that wants to charge you 30$ is going to give you is the partitions backed up by qfil or bkerler edl stuff.
With both at&t and sprint, because no kdz, you can only restore (if you didn't back up the files yourself originally), with someone elses backup, and then you have to use qfil or bkerler edl utilities to restore. If you look around in the G8 forums (or the tele group), there's a decent chance someone has already make their backup available.
cheers and good luck.
Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Yarib said:
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Click to expand...
Click to collapse
Lol no still haven't solved my problem. I need the abl_a and abl_b files for a lg g8 at&t. My phone only goes in fastboot or qfil and Fastboot says its a lmg850um because I tried using the files from my lg g8x and it didn't work. I have also now bricked my lg g8x it only boots into qfil. Any help would be great. My g8x is canada version
Hi there, I am encountering the following issue.
It is a hindi op9 pro
The situation:
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
Any ideas or advice? Plz help
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
it keeps on cycling back to 9008 so what you meant by xbl or abl is broken? Any solution ?
Renate said:
Can you locate the Firehose loader?
Click to expand...
Click to collapse
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
My msm tool from that
Renate said:
Have you tried various USB problem solving, different cables, different ports?
Click to expand...
Click to collapse
Yes I think it is no issues with my cable
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
FOR MORE DETAILS
I tried upgrading my device using fastboot firmware according to the following according to this article
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
when I reached to put commands in cmd and wrote
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
then reboot by
fastboot reboot fastboot
it gets stuck in edl mode and no anything showing just " Qualcomm HS-USB QDLoader 9008" showing in the device manager, appearing and disappearing about every five seconds
so the situation is
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in the device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Click to expand...
Click to collapse
Fastboot commands already worked and I used them to upgrade my phone according to the article above, so when finished, I put a reboot command, and then it got stuck on EDL mod, so I tried to repair it using MSM tool it always says Sahara communication failed, any way to fix it plz my phone is new
Click to expand...
Click to collapse
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Renate said:
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Click to expand...
Click to collapse
thank you but is there a video explaining it bcz I am a noob in this stuff plz.
or you can contact my device using TeamViewer and try to fix it plz.
I don't know your partitions well enough.
If it wants a two stage reflash with 1/2 by (abl) fastboot and 1/2 by (recovery) fastbootd then you need a working recovery and I'm not sure that you have one.
The original post didn't indicate that you were able to reach/use fastboot.
I jumped on this because it seemed to be about USB/Sahara which I know something about.
We need the advice of somebody who knows more about your model.
Sorry
Can you tell how you ended up in this state? If you are a noob, why did you start wipe stuff from your phone without knowing how to what you are doing?
I would guess you thought a custom rom sounded nice but you don't have a clue what to do when things are starting to go south..
Edit: We, as a community always try to help out as much as we can but (and there is a BIG but) you have to understand the basics before you even start to do stuff or you will learn the hard and in some cases expensive way.
Read and do research at least for a few month, like reading most of the threads here and try to figure out how things work.
recovered my noodlep a week ago using this:
How to recover your device after flashing incorrect DDR xbl images
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now... Even I was aware which DDR model was my device, yes.. I did it :D - flashed by mistake DDR4 xbl.img to my DDR5 noodlep...
forum.xda-developers.com
You may want to check it out....
Best luck. and don't worry. Just follow the steps and you'll recover your device.