Hi everyone, I bought this phone working from second hand but the seller told me he tried to unlock the bootloader without success and the phone still loose the fingerprint sensor, so I decided to unlock the bootloader successfully following THIS thread and made a downgrade to Android 9 according to THIS other tutorial hopping to get it work again but I wasn't able to do it, so I decided to just use LGUP to install the same Android 12 that I had but the problem started at this point because once the KDZ was installed successfully, the deviced got a bootloop but I still was able to get into EDL, Fastboot and Download Mode, so I tried the steps from THIS other thread to unbrick it but it got even worse at this point, I flashed all the abl, xbl, etc. partitions and the "rawprograme files" via QFIL and then the phone won't even gave any life signals. I contacted someone that some months ago had the same problem and he told me that I could get into EDL by short pining the test point on the motherboard, which actually worked, so I extracted the KDZ Android 9 rom that I flashed in the first place to get the original abl, xbl, etc. partitions that I crossflashed from a v50 (Which I downloaded from the corresponding thread for unbrick), in other words I flashed the same partitions with the correct v50s files instead other model ones. So now this is where I'm right now, the phone don't turns on at all but when I connect it to the PC it gets recognized as LGE Android Platform USB Serial Port (COM11) and the buttons combinations don't work at all, so still can't get into Download mode by any method or even turn off the device, but I still can disconnect the battery and short pin the Qualcomm 9008 mode to use QFIL.
Would someone please be so kind of telling me how could I recover the Download Mode to use the COM4 and COM5 ports to flash the phone via LGUP?. According to THIS other thread, I could get the correct XML "rawprograme files" for my device (which I crossflashed with the v50) from a KDZ using some tools and Python, but I have to be honest: I DON'T KNOW HOW, even with the step by step tutorial.
At this point I think this would be the right step, to flash all the original files for my model and get the Download Mode back to be able to flash the KDZ rom via LGUP and update via OTA to Android 12 again to avoid the bootloop problem.
try to reflash(QFIL method) modified abl should get the download mode back
darrelama said:
try to reflash(QFIL method) modified abl should get the download mode back
Click to expand...
Click to collapse
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
iMarzateD said:
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
Click to expand...
Click to collapse
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
darrelama said:
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
Click to expand...
Click to collapse
Hello again, already tried flashing the engineering abl but I still can't get into download mode. The phone keeps off the whole time and by plugging in the USB cable, no matter what button combination, the PC always recognizes it as the same LGE Android Patform USB Serial Port (COM11), the only other state of the device is the Qualcomm 9008 by pinning the motherboard. This specific COM11 state never was able to flash anything by PC, I don't know what actual mode is, but when I was able to set the devide in Download Mode the PC always showed 2 devices in the Device Manager, the COM5 and the COM4, that way I knew I was able to use the LGUP to flash. I'm thinking that I'm not setting the phone on the correct state to flash by any method, but since the buttons seems not to work, I don't know how could I do it.
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
ardian1899 said:
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
Click to expand...
Click to collapse
Thanks, I'll try that for sure to see if I can get into the Download Mode or something. I would appreciate so much if you could share your backup, since I think I could restore the whole firmware with it, but I don't have any experience on the "LUNs" tho. I'm any case, I don't have too much time every week to give it a try, so I hope tomorrow I could test the combo you say.
Related
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
EFAYSAL said:
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
Click to expand...
Click to collapse
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
SubwayChamp said:
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
Click to expand...
Click to collapse
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
EFAYSAL said:
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
Click to expand...
Click to collapse
Ok, I guess that your device is actually in bootloop and don´t booting.
Tutorial that you followed has many steps and don´t need to do all this to just root device and it contains some files like lk.bin that you can´t be sure that should be for your device.
Some users use this file (lk.bin) of an unlocked device and think that flashng in other device then get unlock it but no need, your device can be unlock it just follow some commands in fastboot mode.
Now you can do the next;
Try to flash again your rom stock (I guess that you don´t have a backup), if for some reason your official tool doesn´t work then use only some images like boot, system and userdata with the scatter.txt to flash them through SP Flash Tool.
Here a link to TWRP https://youtu.be/6vj_BY6xJdA, you can root it with supersu v2.78 0r v2.82 and here some files that can be usefull too https://drive.google.com/uc?id=0BwJgeCYTpnEHNlg2VUlieHFTYVU&export=download
Update steps that you are following to can assist. What extension has your rom and if it is recogniced for SP Flash Tool. I didn´t ask you if you can enter to fastboot mode and if you can then you can know if your bootloader is unlocked typing fastboot oem info
Most info that you give and some screenie will help to understand better
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
EFAYSAL said:
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
Click to expand...
Click to collapse
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
SubwayChamp said:
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
Click to expand...
Click to collapse
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
EFAYSAL said:
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
Click to expand...
Click to collapse
I´m not sure if you are connecting correctly your device at right time and form to can flash it properly. Every device has more or less a specific way to do it. My last alcatel it was connected just with device power off and after to tap on download, but in other device Blu Dash was connected pressing just vol_up and my last mt6757 Bluboo had to press both vol up and down at time to connect to pc and after to tap on download option. To have sure that is well done increase volume in your pc, you will hear a first sound that is cause pc is recognicing but then you have to hear a second sound that is when SPFlashTool is recognicing device and you will see a red line in down side of the tool window, release button inmediately and let tool to work.
This is a good rom for your device according the author is optimized https://droid1311.blogspot.com/2017/08/alcatel-fl02-aka-flash-plus-2-via.html and this is the link directly if you have troubles with pop-up-adds https://drive.google.com/file/d/0BwAGh1drb91SeDZwV1VXbXpjQWM/view
Also you can try with other versions of SP Flash Tool, most stable maybe should be v5,1628 https://androidmtk.com/smart-phone-flash-tool leth me know how you go
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
SPFlashTool 5.1628:
I try all the way with and without pressing any button but no luck . And when it work finishing with error.
SPFlashTool 5.1628:
I try all the way to get that mode but nothing works. So I try to click download button then conect the phone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
EFAYSAL said:
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
I try all the way to get that mode but nothing works. So I try to click download button then conect the pkone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
Click to expand...
Click to collapse
There is a part that is not variable in the way to use this tool, ever you have to tap on download before to connect device and is recommendable too connect cable usb to pc (not yet to device); from here is when the button that you have to press can vary but like I said you before in my last mt6757 (a very similar to yours) works pressing both vol at same time to connect terminal cable to device and now you will see a red line (could be violet-ish)
Try before just flashing only preloader file to recreate some partitions and then do other flash for the other files.
Of course you have to be sure that all drivers are installed correctly cause this tool needs to put your device in download mode (a special level) and also keep it in this state so find VCOM drivers for Alcatel and adb/fastboot installer and try to uninstalling some older drivers that you don´t use and many times we keep in our pcs and for a short data transmission can helo that all the rom move it in same folder where SPFlashTool is allocated.
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
EFAYSAL said:
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
Click to expand...
Click to collapse
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
- In what android version are you, 6.0?
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
- Did you try to flash just preloader, only this file?
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
SubwayChamp said:
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
Click to expand...
Click to collapse
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
SubwayChamp said:
- In what android version are you, 6.0?
Click to expand...
Click to collapse
Yes, last time it was 6.0 before the root
SubwayChamp said:
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
Click to expand...
Click to collapse
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
SubwayChamp said:
- Did you try to flash just preloader, only this file?
Click to expand...
Click to collapse
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
SubwayChamp said:
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
Click to expand...
Click to collapse
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
EFAYSAL said:
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
Yes, last time it was 6.0 before the root
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
Click to expand...
Click to collapse
You need to try two different ways to flash files and restore your device.
First method: fastboot mode
You need to get device enter to fastboot in order to flash some files like system, boot and userdata, then there are two main methods to do it:
- Pressing pwr + vol down
- And I mentioned that sometimes work pressing both volume button + pwr and a menu have to appear to can select an option to enter to (fastboot mode), in some devices this method is not working but you have to try several times attempting to.
Second method: SPFlashTool
You have to ever press first of all Download box and connect terminal cable to pc and the buttons thhat you need to press at time to connec cable usb to your device may vary, sometimes vol down, sometimes both vol but never pwr button; if pc recognice then you have to release all buttone an let it pc continue the flash process.
If SPFlashTool recognice device first flash only preloader file and select now lk.bin too. Flash only these two files and after do again a new flash with the rest of the files, Why you need to do this? your partitions are corrupted and you need to restore them with these files in order to can flash all another files.
Before all of this charge your battery, if you have a cover removable then extract it some minutes and put it again.
Also I read that for this model it´s used this tool instead of SPFlash Tool https://androidmtk.com/download-sugar-mtk-sp-flash-tool (inside the zip you will find a password to start the tool) but I´m not sure what kind of rom it needs, you have to connect your device to begin the process, you will find in product models section in the tool this variant for your device "FL02"
Try first the other tool and then this and let me know how you go, mtk devices are almost unbrickeable so it´s just to find the appropriate way to return it to the life.
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
EFAYSAL said:
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
Click to expand...
Click to collapse
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
I understand that you tried with Sugar tool with no lucky.
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Is there some custom development, recovery, roms for your device?
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
SubwayChamp said:
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
Click to expand...
Click to collapse
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
SubwayChamp said:
I understand that you tried with Sugar tool with no lucky.
Click to expand...
Click to collapse
Yes. After recognizing it keeps trying to download data but no luck.
SubwayChamp said:
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Click to expand...
Click to collapse
I know it is disappointing!. I try this but no luck.
SubwayChamp said:
Is there some custom development, recovery, roms for your device?
Click to expand...
Click to collapse
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
SubwayChamp said:
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
Click to expand...
Click to collapse
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
EFAYSAL said:
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
Yes. After recognizing it keeps trying to download data but no luck.
I know it is disappointing!. I try this but no luck.
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
Click to expand...
Click to collapse
I´ll tell you some ideas with no any specific order that you can try or see if works.
Really very strange that display stays in black, you told me that flashing files through fastboot is working but doesn´t appear not even bootlogo, connect to pc as it is and see how pc recognices in devices manager and my pc if appears like a determined drive d/e/f so it looks that some bad flashing burn your kernel and this case is similar to when a Samsung device need to use jtag method to revive, if in your country no-one knows about Alcatel devices this could be a similar case to what I´m saying then it could be a clue for a technician. I tell you this cause many time ago when I flashed by error a Samsung s4 and only this method revived my device.
Try this, flash your stock recovery only through SPFlash tool and flash after through Alcatel Download tool your stock rom cause some firmwares need to detect stock recovery first to can flash other partitions.
At this stage don´t you have stock recovery, no? so you can try to format data cause sometimes when bootloader is altered then avoid to boot and formatting data can solve this.
If this recovery twrp is for your device you can try flashing through SPFlash tool, you have to put recovery.img and scatter-txt in a same folder. then if succesfull format data, system, wipe cache and dalvik and maybe later try to port some custom rom would be a way to solve this.
To flash any partition through fastboot this is the syntax, just follow one by one any of the files that are in your rom folder so just follow these, if some of then can´t be flashed don´t worry then it´s not flashable:
fastboot flash boot bot.img
fastboot flash cache cache.img
fastboot flash lk lk.bin
and so on till the end
...But after try this if you didn´t get boot to recovery and obviously you can´t delete data nor system then delete first the next partitions trough fastboot typing:
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase boot
Try all this and let us see how it goes
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
EFAYSAL said:
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
View attachment 4518365
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
Click to expand...
Click to collapse
I see that Sugar tool detects your device like rooted and refuses to flash anything, compare imei number which is in the box, I hope that it couldn´t be changed.
Don´t tell me simply no luck, what it says in SPFlash tool when you tried to flash TWRP and I guess that you put scatter-txt and twrp renamed recovery.img simply in the same folder. Just to be clear, to can flash with this tool your device it has to be off not needed fastboot for this. (provide some screenie)
Other combination of keys to enter to fastboot to flash some partitions when something is missing is, try these three ways:
- Pressing only vol down and at same time connecting to charger (connect first one terminal of cable to your device and then to the charger)
- Pressing the three buttons till a menu appears (you must to release inmediately all)
- Pressing vol up + pwr till a menu appears (you must to release pwr button inmediately) then choose fastboot
In the post 4 I provided a link from Google Drive, in this zip there are 8 items;
- From the item 2 use this version of SP Flash tool, put the four files in a folder and flash them
- In the item 3 you will find some scripts for fastboot, maybe they´re working better and also you have here a subfolder with twrp image.
- And if you get sucessfully install twrp in the item 7 there is a backup with some files to restore from this recovery.
Try one by one and update the info, I hope that your motherboard is not damaged.
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
!!! Whatever you do, it is at your own risk !!!
This procedure will unbrick any Axon 7, returning it to stock. It fixes any kind of brick as long as your hardware is not damaged. You can't damage your hardware using software so if you have a healthy unit, you can recover it from any flashing "accident".
1. GET THE SOFTWARE
You need a Windows PC, Windows 10 is highly recommended. Do this:
01. Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
02. Download the EDL flashable stock firmware package for your model:
A2017 (China): B14_MIFAVOR5 Android: 7.1.1
A2017G (Europe): B10_NOUGAT Android: 7.1.1
A2017U (Americas): B35_NOUGAT Android: 7.1.1
03. Unzip the firmware ZIP file to a folder in your hard drive.
2. ENTER EDL MODE
Option A: USING THE REBOOT COMMAND
If you still have access to your system but not to recovery or fastboot, then you just need to install any terminal app, open it and at the app's command prompt enter:
Code:
reboot edl
. You device will reboot into EDL mode. Now you can safely plug your Device to your computer. In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you'll need to explore the next option.
Option B: USING THE BUTTON COMBO
04. Press the VolUp and VolDn buttons in your device and keep them pressed.
05. Now press the power button until the red LED flashes, it does it really quick. Then release the buttons, starting by the power button.
06. Plug the device to your computer.
In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you need an EDL cable.
OPTION C: USING THE EDL CABLE
So, you need to get a Qualcomm EDL cable. With it you can recover from any situation. I use this one, DrakenFX uses this other model. There are cables out there not working properly so do not try to save 4 or 5 bucks and get yours from a reliable source. Alternatively you can solder your own by following this guide. If you are in an emergency (or your patience threshold is very low) and have a thin wire around you, then you can follow this DIY hack video.
Do you already have the EDL cable? then follow these steps:
07. Connect your bricked Axon 7 to your PC using the EDL cable.
08. Press the EDL cable button and keep it pressed.
09. Press the Power button of your bricked unit and keep it pressed too.
10. Wait 20 seconds.
11. Release the power button.
12. Wait 10 seconds.
13. Release the button of the EDL cable.
Voilà, your device is now in EDL mode. The device manager in your PC, under the ports category, should detect it as Qualcomm HS-USB QDLoader 9008. Now you can proceed to the flash section. If this procedure doesn't work, then your unit could have a hardware problem. Your only hope is to dissemble it by following this last resort guide.
3. FLASH FIRMWARE
14. Open MiFlash in your computer.
15. Click Browse button and select the folder you created in step 03 with the stock firmware files.
16. Click Refresh button and your device will appear listed as virtual COM port.
17. Click Flash button and wait for a few minutes until it finishes. Note that the bottom options are not applicable.
18. Now you have a stock Axon 7. Your data partition will still have garbage data, so you should enter recovery by pressing VolUp while rebooting your device with the power button. Release VolUp only when you reach Recovery. Using Recovery do a Factory Reset of your device.
That was the last step. Hopefully now you have a fully functional stock Axon 7.
By the way, this guide can also be used to return to stock any working device for selling or service!!!!
Cheers!!!!
Nice! I just disassembled mine and did it that way the other day.
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
@Oki
Thnx for this guide :good:
Find the latest A2017G N-B10 here
Harmtan2 said:
Nice! I just disassembled mine and did it that way the other day.
Click to expand...
Click to collapse
Glad to see you solved your issue.
mb0 said:
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
Click to expand...
Click to collapse
I don't know what you mean about converting an A2017 into an A2017U. They are the same device except for the radio, that that's a hardware difference. You should always use the right modem firmware for your radio hardware so you should use the A2017 modem firmware. After unbricking your unit, you can unlock it again and flash any universal firmware the same way you did before. It is a long but safe process.
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
mb0 said:
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
Click to expand...
Click to collapse
If you flashed the A2017U radio in a A2017 hardware and worked fine for you, then you can use the A2017U B35 stock firmware.
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
My phone shows up as Handset Diagnostic Interface (DFU) (COM3) but it doesn't get detected on Miflash program......
aLexzkter said:
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
Click to expand...
Click to collapse
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Oki said:
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Click to expand...
Click to collapse
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3).
Edit: I managed to get into EDL mode thanks to Axon 7 EDL Tool but I got a "File analysis: error" "not important files found" so I went back to MiFlash and also got an error about the files. Will update the post when I get it to work.
aLexzkter said:
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3)
Click to expand...
Click to collapse
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Oki said:
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Click to expand...
Click to collapse
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
aLexzkter said:
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
Click to expand...
Click to collapse
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Oki said:
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Click to expand...
Click to collapse
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
aLexzkter said:
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
Click to expand...
Click to collapse
Well, I am considering to link the older Marshmallow ROMs since the Nougat ROMs have some issues with fastboot. Anyway. It is going to take some time to test the alternatives. Thanks for letting us know!
Some of the most recent firmware for Axon 7 (@NFound's B12 bootstack, I think) doesn't support the EDL button combo. But if you have TWRP installed, you can boot to recovery, then reboot to EDL from there.
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Flogisto said:
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Click to expand...
Click to collapse
There ate several ways to remove that. One involves TWRP 3.2.1-7 and the other Axon 7 EDL tool, if you dont have TWRP then use the second . Jusy go to the unlock menu and apply the google unlock.
A third way would be to setup the phone with your old google account and do afactory reset from within Android, not from the bootloader. That would remove also the owner safety.
Thank you so much for your guide and software bundle.
I even had to make a EDL cable to restore my device.
After flashing, I do not see vendor as a partition but looks like it is a folder. Is it OK for future ROMs ?
During a flash, the connection to my V30 was interrupted for some reason, probably a worn out USB cable getting knocked into and shifting around in the USB C port. Ever since then, the phone refuses to get past the bootloader or recovery if I hold down the proper keys.
I have used a modded version of LGUP that I originally downloaded to help frankenstein this phone to refurbish, upgrade, even chip erase (this does get rid of the IMEI and other important numbers but since this phone is no longer my daily it's fine if it has no IMEI to me, I'll be honest I'm not sure if chip erase gets rid of any other stuff that should absolutely never be touched). The phone still boots straight to the bootloader. I have also tried flashing custom recoveries (such as TWRP, this has been successful) and installing .zip format roms to the device through the recovery (not successful, still boots straight to bootloader without fail).
So uh... did I manage to brick my V30? Or does it sound like there's at least a bit of hope? Any help would be greatly appreciated, I really wanted to use this thing as a sort of glorified iPod because of that magical dac.
Jeebüüs said:
During a flash, the connection to my V30 was interrupted for some reason, probably a worn out USB cable getting knocked into and shifting around in the USB C port. Ever since then, the phone refuses to get past the bootloader or recovery if I hold down the proper keys.
I have used a modded version of LGUP that I originally downloaded to help frankenstein this phone to refurbish, upgrade, even chip erase (this does get rid of the IMEI and other important numbers but since this phone is no longer my daily it's fine if it has no IMEI to me, I'll be honest I'm not sure if chip erase gets rid of any other stuff that should absolutely never be touched). The phone still boots straight to the bootloader. I have also tried flashing custom recoveries (such as TWRP, this has been successful) and installing .zip format roms to the device through the recovery (not successful, still boots straight to bootloader without fail).
So uh... did I manage to brick my V30? Or does it sound like there's at least a bit of hope? Any help would be greatly appreciated, I really wanted to use this thing as a sort of glorified iPod because of that magical dac.
Click to expand...
Click to collapse
You've tried going into download mode manually, use Dev Patched LGUP in Refurbish mode to reinstall US998 20h KDZ?
ChazzMatt said:
You've tried going into download mode manually, use Dev Patched LGUP in Refurbish mode to reinstall US998 20h KDZ?
Click to expand...
Click to collapse
I've entered DL mode manually and I'm using the dev patched version of LGUP. I haven't tried that particular KDZ though, I could give it a shot for the hell of it. Anyways thanks.
Also, would using Qualcomm download mode work? I'm fine with opening up the phone to trigger the contacts, I just don't know if I'll be able to do any good once in that mode.
ChazzMatt said:
You've tried going into download mode manually, use Dev Patched LGUP in Refurbish mode to reinstall US998 20h KDZ?
Click to expand...
Click to collapse
Just tried that KDZ, didn't help.
Jeebüüs said:
Just tried that KDZ, didn't help.
Click to expand...
Click to collapse
Sorry.
What happens when you use ADB/fastboot commands to get to bootloader? It never finishes booting?
Jeebüüs said:
Also, would using Qualcomm download mode work? I'm fine with opening up the phone to trigger the contacts, I just don't know if I'll be able to do any good once in that mode.
Click to expand...
Click to collapse
First, you don't need to open the phone to enter QDLoader / EDL / 9008 mode:
With the phone connected to a PC (you don't need any special software loaded, just the USB connection), and with the phone powered on and unlocked, hold vol +, vol -, and power to shutdown the phone. Keep holding them till you get a countdown on the screen. The second the countdown completes, and the screen shuts off, let go of power, keep holding vol -, and start tapping the crap out of vol +.
If you have problems getting into recovery using the key combo, this is at least 5x as hard to get it right. When you do, the screen will be blank and the phone will show up in your OS as 9008. Example in Linux:
Code:
Bus 001 Device 015: ID 05c6:[B]9008[/B] Qualcomm, Inc. Gobi Wireless Modem ([B]QDL mode[/B])
To exit 9008 if you decide not to flash anything, just press and hold vol - and power until the phone reboots.
Now, with that said, you still need the firehose. I haven't looked for it yet because I haven't needed it, but there is a V30 (all models except the H932) firehose out there somewhere. Also, of course, you need QFIL.
Now will this help -- as long as there isn't a hardware problem with your phone, you can do anything you want in QDL mode with the understanding that signatures are still checked, so you can only flash V30 (non-H932) firmware. If flashing a KDZ doesn't fix your problem, you must have a problem with a partition that doesn't get flashed from a KDZ. Unfortunately, if you don't know which one, it will be trial and error and you will need a complete dump of a V30 minus EFS.
-- Brian
ChazzMatt said:
Sorry.
What happens when you use ADB/fastboot commands to get to bootloader? It never finishes booting?
Click to expand...
Click to collapse
Pretty much. Fastboot behaves normally and it does reboot with the fastboot reboot command but it just ends up right back at the bootloader unless I use the key combos required to get into LGUP DL mode/recovery.
That's great info Brian. Always thought opening phone, disconnecting battery ribbon, and shorting test points are only way to force qdl 9008 mode. Thanks for this info :good:
Hello
I tried to flash a custom rom on my Nord N10 --> [ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie] <--
At 47%, the flash stopped. I tried it a several times but always with the same result.
I did a factory reset in twrp, since then all was gone from internal storage.
And now I'm unable to flash ANY rom on the device.
I tried a lot of ways: flashing stock rom with stock recovery, flashing different custom roms in twrp and other recoveries, Msmtool, extracting payload.bin and flash all the images in fastboot (I followed the commands at the bottom of this page), ... but I haven't got the result I wanted.
I even got into "Qualcom crash dump mode". That's when I tried to use the MsmDownloadTool but it wouldn't recognize any COM port.
I can transfer .zip files to the internal storage when using twrp, but flashing always fails (see attached file).
Sideloading in PE or Lineage recovery works, but flashing fails (2nd attached file).
Overview:
Positives:
bootloader is unlocked
fastboot is accessible
fastboot commands are working so I'm able to flash by fastboot command
recovery is accessible and different versions can be flashed
internal storage is accessible and copying files is possible (though, folders like Android, DCIM, downloads, etc... are all gone)
Negatives
Msmtool doesn't recognize the COM ports
some images (like vendor.img) can't be flashed in fastboot when extracted from the rom by using Payload Dumper
error shown in twrp (file attached)
neither can a rom be flashed in PE recovery or Lineage recovery
Anyone able and wanting to help or provide a link to a tutorial? I don't care which rom is installed, I just want to get the phone working again and at this point I fail to see what I'm doing wrong.
Kind regards
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
I'll look into it and give it a try. Thanks!
SomeRandomGuy said:
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
Click to expand...
Click to collapse
Couldn't get into EDL mode (I tried EVERYTHING). I updated/repaired the Qualcomm drivers, re-flashed another version of twrp and was able to flash this rom in twrp after I copied the rom to the sd card. It worked, the N10 is back alive again.
I've hard bricked my phone. I can get it to EDL mode and that's it. But QFIL won't flash it, neither will software download by qpst. I'm sure I'm doing something wrong so can one of you fine members of this forum please tell me how to flash this device in edl mode, what program and step by step?
TweakybirdsTheWord said:
I've hard bricked my phone. I can get it to EDL mode and that's it. But QFIL won't flash it, neither will software download by qpst. I'm sure I'm doing something wrong so can one of you fine members of this forum please tell me how to flash this device in edl mode, what program and step by step?
Click to expand...
Click to collapse
I'm sorry to hear that you've hard bricked your phone. Flashing a device in EDL mode can be a complex process, and it's important to follow the correct steps to avoid causing further damage to your device.
Here's a step-by-step guide to flashing your phone in EDL mode using QFIL:
Download and install the Qualcomm USB driver for your phone model.
Download and extract the firmware package for your phone model.
Download and install the latest version of QFIL (Qualcomm Flash Image Loader) tool.
Put your phone into EDL (Emergency Download) mode. The method for entering EDL mode can vary depending on the phone model. Typically, you will need to turn off the phone, then connect it to your computer while holding down the appropriate button combination.
Open QFIL tool and select the flat build option.
Click on the "Browse" button next to the "Select Build" option and navigate to the firmware package you extracted in step 2. Select the XML file that corresponds to the partition you want to flash.
Connect your phone to your computer using a USB cable. QFIL should detect your phone in EDL mode.
Click on the "Download" button in QFIL to start the flashing process. This can take several minutes, so be patient and do not disconnect your phone from the computer during the process.
Once the flashing process is complete, QFIL should display a "Download complete" message. Disconnect your phone from the computer and try turning it on.
If the above steps do not work, you may need to try different firmware packages or seek assistance from a professional phone repair service. It's important to note that flashing a device in EDL mode carries some risk, and if done incorrectly, it can cause further damage to your phone. Proceed with caution and at your own risk.
hope this will be helpful to you.
thanks..
Nilesh112 said:
I'm sorry to hear that you've hard bricked your phone. Flashing a device in EDL mode can be a complex process, and it's important to follow the correct steps to avoid causing further damage to your device.
Here's a step-by-step guide to flashing your phone in EDL mode using QFIL:
Download and install the Qualcomm USB driver for your phone model.
Download and extract the firmware package for your phone model.
Download and install the latest version of QFIL (Qualcomm Flash Image Loader) tool.
Put your phone into EDL (Emergency Download) mode. The method for entering EDL mode can vary depending on the phone model. Typically, you will need to turn off the phone, then connect it to your computer while holding down the appropriate button combination.
Open QFIL tool and select the flat build option.
Click on the "Browse" button next to the "Select Build" option and navigate to the firmware package you extracted in step 2. Select the XML file that corresponds to the partition you want to flash.
Connect your phone to your computer using a USB cable. QFIL should detect your phone in EDL mode.
Click on the "Download" button in QFIL to start the flashing process. This can take several minutes, so be patient and do not disconnect your phone from the computer during the process.
Once the flashing process is complete, QFIL should display a "Download complete" message. Disconnect your phone from the computer and try turning it on.
If the above steps do not work, you may need to try different firmware packages or seek assistance from a professional phone repair service. It's important to note that flashing a device in EDL mode carries some risk, and if done incorrectly, it can cause further damage to your phone. Proceed with caution and at your own risk.
hope this will be helpful to you.
thanks..
Click to expand...
Click to collapse
Although the process that you've described will work to reflash the phone from being hardwrecked it's not going to be possible unless you get a two-factor authentication code directly from the OnePlus servers and that's only possible if you have the proper credentials so good luck with that. Now if you want a third party service that can unbrick it for you I can recommend somebody but other than that you're pretty much screwed when it comes to a OnePlus phone these days...
Are firehose programmers exclusive to the model of the device or are they exclusive to the firmware they're packaged with? I want to take a firehose programmers from a CPH2459 A.08 and put it with the full update to Android 12 since the full ota did NOT come with a programmer....
TweakybirdsTheWord said:
Are firehose programmers exclusive to the model of the device or are they exclusive to the firmware they're packaged with? I want to take a firehose programmers from a CPH2459 A.08 and put it with the full update to Android 12 since the full ota did NOT come with a programmer....
Click to expand...
Click to collapse
I believe tthey're exclusive to the chipset or motherboard that's in the phone.. because some phones can use the same firehose but have nothing other than the chipset/board being the same.. or i couild be wrong on that? Definitely might wannna google that before taking that as a concrete.
Well that's good news so far if it's true
none of this is necessary if you follow this guide:
[GN2200] simple recovery guide from fastboot + obtain root + more
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch. a major hand to PsYk0n4uT for the suggestions he's...
forum.xda-developers.com
Except I can't access fastboot. All I have is EDL.
dmtec said:
none of this is necessary if you follow this guide:
[GN2200] simple recovery guide from fastboot + obtain root + more
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch. a major hand to PsYk0n4uT for the suggestions he's...
forum.xda-developers.com
Click to expand...
Click to collapse
Except I can't access fastboot. All I have is EDL.
Good luck because all msm tools now require a 2FA to initiate data restore.. I've used the guy who helped create rom2box for 20 bucks.. I can vouche for his validity and success rate and usually responds within 20 minutes or so..
Here's his telegram contact info
Great news. I've figured out that firehose loaders are NOT specific to tool or firmware that they're packaged with BUT they are processor specific if I'm not mistaken.
TweakybirdsTheWord said:
Except I can't access fastboot. All I have is EDL.
Click to expand...
Click to collapse
You can use rom2box to reflash from EDL.
dmtec said:
You can use rom2box to reflash from EDL.
Click to expand...
Click to collapse
which version