Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -Just for example - the script would be located in:"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"And the firmware files would be in:"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P
Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.
.
Related
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
TT TT said:
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
Click to expand...
Click to collapse
Hi, on russian site they have already done it
ttp://4pda.ru/forum/index.php?showtopic=749517&st=560#entry51150598
Add "h" in the beginning (I don't have permission to publish links )
And use google translate
PS. Don't forget to create backup before all manipulations. Especially IMEI
HoboMoe said:
Hi, on russian site they have already done it
ttp://4pda.ru/forum/index.php?showtopic=749517&st=560#entry51150598
Add "h" in the beginning (I don't have permission to publish links )
And use google translate
PS. Don't forget to create backup before all manipulations. Especially IMEI
Click to expand...
Click to collapse
Nice!!
Good reason to practice my Russian :victory:
Thanks a lot, Sir!
altrom also has a rom can be installed via TWRP. Not sure how legit it is though.
TT TT said:
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
Click to expand...
Click to collapse
I finally made it to flash TWRP with a flash tool I found via a doogee-blog, a official doogee Q&A site and a blog on doogeemobile.
Why do I have to verify so often?
EDIT: I had a look at my documents, got the flash tool from dogeemobile.com and the TWRP 3.0.2 from needrom. You have to pay attention that you use ROMs for the particular processor of the maxpro (MT6737 M). SU from here of course. :good:
HTH
Why do I have no verification to do any more??
still cant do it
messing around for a week and still no sucess.
flash tool says !sucessful! but i reboot and get stock recovery - not what i expect (twrp)...
also cpu-z says is mt6735- but if i try that one i get :
chip type not match
targetef use value 0xA4020000
but it works with mt6737 - it just dont reboot into that other loader....
any ideas
mlcrip co uk/DooGee/i1.jpg
also tried both x5pro and x5maxpro...
(TWRP-Doogee-X5-MAX-PRO.zip)
(TWRP_Recovery_X5_Pro.rar)
dev enabled, usb debugging, oem unlocking on,
also yes, i do imediately go for bootloader (volume up while turning on)- doesnt work no matter what.
UPDATE:
DooGee X5Max_Pro MT6737M (Android 6.0, 20161123, kernel 3.18.19+)
i sorted it. turns out i had to use x32TWRP (fund it here somewhere on this site)
MT6737M_Android_scatter.txt (plus image come with it)
SuperSU-v2.78-SR3-.zip
also i randomly went for adb commandline to 'unlock rom' not sure if it was necessary, but wont hurt.
so if any noob wanna easy way,
1. 'minimal adb and fast boot' to unlock rom (few cmd commands and you done)
2. start flash tool, set CORRECT scatter file (MT6xxx- if you set wrong model it will give you error popup)
3. set DOWNLOAD ONLY' on drop down box. press DOWNLOAD button.
4.REMOVE BATTERY off your phone. Plug usb cable. youll get 'sucess' pop up window. close the flash tools. disconnect phone but keep it OFF!
5.pop in the battery. press volume up+on button.
at this point you should get some proper user interface, not the black screen with some letters (stock bootloader) something went wrong.
what you should see imediately once you turn it on- just google TWRP images lol.
techbeasts.com/wp-content/uploads/2014/10/TWRP-Recovery.bmp
also all files needed (incl flash tool) i dropped here:
one by one (in case if someone needs scatter file or something)- or inside 'all' folder- all tools compressed into rar
mlcrip.co.uk/android/rooting/files/
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.
Real appreciated, will keep you updated, if anything works ill post it here.
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536
Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?
mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu
mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.
mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo
TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards
ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers
Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers
Ok, definitely will do that. Thank You very much for Your help
UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.