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
So, some days ago I've purchased a Mi A2 Lite. Right after starting it and testing it's basic functions, I headed right away to the computer to change ROMs. When I booted TWRP through fastboot, I wiped system to install another ROM, but the roms i'd downloaded wouldn't flash. Then, suddenly, TWRP touch stops working. I found then that it was a normal thing, and a guy posted in a thread that locking and unlocking his bootloader made TWRP work again (I did try to boot it again and didn't work). So I locked the device through a simple tool. Now, I can't unlock the bootloader in anyway. MiUnlock requires binding the device to an account (my device doesn't have an OS anymore since I wiped it), can't unlock it through fastboot (token verification failed), can't enter adb through commands because it is locked. MiFlash requires an authorized account to flash. QFIL doesn't flash because by entering in EDL Mode through test points, you have to start flashing fast, otherwise it won't be able to read hello packet, but the QFIL app takes too long to start flashing, I click it, it loads and loads, and just says it couldn't read packet. I'm trying to unbrick this device for 4 days long.
Now, the reason I say it is a faked Mi A2 Lite (can't know it for sure, actually) are these:
-Although the device came new from fabric, all the box and acessories had their plastics and stickers, the device came unlocked.
-The device came with Android One (which is right, as I bought a Mi A2 Lite), but has a Mi-Recovery 3.0, which is from MIUI systems, and Redmi 6 Pro has MIUI.
-When trying to unlock it through fastboot, I entered some commands to get info of the device, the interesting ones were these:
imei: (blank)
product: sakura (which is Redmi 6 Pro)
version-bootloader:MSM8953_DAISY1.0_20181019193735
I am from Brazil, and I am mostly sure that it is original and came this way from Xiaomi because the seller gave me the receipt and says he buys from authorized seller. And everything came with it's plastics on, the box was sealed-new, so I don't believe the seller did this, I believe Xiaomi did this mi a2 lite/redmi 6 pro confusion.
EDIT: I'm now sure it's Xiaomi's fault as I've found another identical cases where they had "sakura" devices with "daisy" bootloaders (exactly same versions), they probably chose to do this, which is worse than this being a mistake.
Could you guys help me, don't know what to do anymore. If you need more info to solve this problem, please ask, I'll post them right away.
@GNDawg
Well, I search around and it seems to be most likely a Xiaomi fault. they flashed a wrong firmware but it also could be that some seller in the chain took a bricked device, changed back over and flashed a rom that it had available either changing or not motherboard from the original but this is just a theory hard to proof.
Anyway now your best bet would be try to flash through an unnoficial tool like QPST download drivers and follow carefully instructions to update then onto your pc http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/ and here is a tutorial how to use it https://c.mi.com/thread-226346-1-1.html this tool gives error on several cases so you have to search probably a modded sahara file for other MSM8953 to fix it.
And here a thread with a different method, the idea is try to boot from the sdcard, you could need some files to do it like a part of the system dumped for other user with the same device, this thread is just a reference for other model https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
I did in the past the file to be flashed onto TWRP and dump it, I´ll try to search for it
SubwayChamp said:
@GNDawg
Well, I search around and it seems to be most likely a Xiaomi fault. they flashed a wrong firmware but it also could be that some seller in the chain took a bricked device, changed back over and flashed a rom that it had available either changing or not motherboard from the original but this is just a theory hard to proof.
Anyway now your best bet would be try to flash through an unnoficial tool like QPST download drivers and follow carefully instructions to update then onto your pc http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/ and here is a tutorial how to use it https://c.mi.com/thread-226346-1-1.html this tool gives error on several cases so you have to search probably a modded sahara file for other MSM8953 to fix it.
And here a thread with a different method, the idea is try to boot from the sdcard, you could need some files to do it like a part of the system dumped for other user with the same device, this thread is just a reference for other model https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
I did in the past the file to be flashed onto TWRP and dump it, I´ll try to search for it
Click to expand...
Click to collapse
Hey man, I didn't quite understand the tutorial you passed me, because it just says to build a EDL Cable and then flash it through MiFlash, as far as I understood. I'm so tired I think I'm gonna pay s-unlock to unbrick this damn phone, are they trustworthy? The service doesn't need TeamViewer anymore, they've built a tool which needs an account with credits (you pay for them), and then you can flash using these credits, I wonder if the process fails, will the credits be gone? hahaha man, look at the level we're at, thank you Xiaomi!
GNDawg said:
Hey man, I didn't quite understand the tutorial you passed me, because it just says to build a EDL Cable and then flash it through MiFlash, as far as I understood. I'm so tired I think I'm gonna pay s-unlock to unbrick this damn phone, are they trustworthy? The service doesn't need TeamViewer anymore, they've built a tool which needs an account with credits (you pay for them), and then you can flash using these credits, I wonder if the process fails, will the credits be gone? hahaha man, look at the level we're at, thank you Xiaomi!
Click to expand...
Click to collapse
In the post in spanish there are some useful links like Qualcomm 9008-USB drivers and other to explain how to avoid drivers verification on Windows, this could be necessary to get a perfect connection among your device and pc although I´m begin to suspect that motherboard is damaged at some level, I say you this cause I had similar problem in different circumstances with a Xiaomi device in the past; briefly explained an user uploaded incorrect files to some site and I flashed onto my device and some of the files were for other model; result: totally bricked, I tried a lot of guides and method but I didn´t give out till I was absolutely sure that there was nothing more to do with. Finally I had to buy other motherboard and that device now is working fine.
I commented about a method to "burn" a part of the image in an external SDcard, a part of the system image means just about 100 or 200 MB sized of the image, I shared year/s ago a zip to obtain it (I didn´t find now) so some user that have same device can flash it through TWRP and so dump this "part/fraction" of system, then they can share with you, you burn it using the disc image utility inbuilt on Windows and then apply to your device and this way your device do an attempt to boot from this SDcard, then you can flash normally all the whole rom through XiaoMi flash. But your case is slightly different, it seems like not a totally brick, in my case I didn´t have any partition working like fastboot, recovery, nothing at all. The third link refers to something similar to the exposed above.
Referent to this service, you have to be sure that they can do something with a device that can´t communicate correctly with XiaoMi flash and you said me first that the tool needs an account authorized but then you said that the tool began but finally failed to flash that mean that the tool can work without an authorization, if this is true you only have to refine the method to use it correctly.
Probably you can upload an image while you´re attempting in XiaoMi flash to see how is detecting it.
SubwayChamp said:
In the post in spanish there are some useful links like Qualcomm 9008-USB drivers and other to explain how to avoid drivers verification on Windows, this could be necessary to get a perfect connection among your device and pc although I´m begin to suspect that motherboard is damaged at some level, I say you this cause I had similar problem in different circumstances with a Xiaomi device in the past; briefly explained an user uploaded incorrect files to some site and I flashed onto my device and some of the files were for other model; result: totally bricked, I tried a lot of guides and method but I didn´t give out till I was absolutely sure that there was nothing more to do with. Finally I had to buy other motherboard and that device now is working fine.
I commented about a method to "burn" a part of the image in an external SDcard, a part of the system image means just about 100 or 200 MB sized of the image, I shared year/s ago a zip to obtain it (I didn´t find now) so some user that have same device can flash it through TWRP and so dump this "part/fraction" of system, then they can share with you, you burn it using the disc image utility inbuilt on Windows and then apply to your device and this way your device do an attempt to boot from this SDcard, then you can flash normally all the whole rom through XiaoMi flash. But your case is slightly different, it seems like not a totally brick, in my case I didn´t have any partition working like fastboot, recovery, nothing at all. The third link refers to something similar to the exposed above.
Referent to this service, you have to be sure that they can do something with a device that can´t communicate correctly with XiaoMi flash and you said me first that the tool needs an account authorized but then you said that the tool began but finally failed to flash that mean that the tool can work without an authorization, if this is true you only have to refine the method to use it correctly.
Probably you can upload an image while you´re attempting in XiaoMi flash to see how is detecting it.
Click to expand...
Click to collapse
So, there's this problem that happens when the software can't connect to the device if I take too long to flash after entering EDL Mode, I've seen a lot of other cases of this "problem" too. I have to test point and flash right after, which is no problem in MiFlash, but in QFIL and QPST it looks like it takes too long to connect with the device and then it fails. But I've seen that S-Unlock uses
their own tool called XiaomiTool, where they create an account for you which has credits. Then the tool uses the credits to flash. It's quite confusing... but you don't need to grant them TeamViewer access, which if way more safer than the previous method. Man... I had a ZUK device before, there was no AntiRollback ****, I didn't even had to unlock a bootloader in the first place you would just wipe and flash all day long for as long as you'd want, I was in heaven and didn't know it.
Also, I'm pretty sure the softwares detect the device just fine, the device connects through 9008 port, and they detect it right after connecting it.
GNDawg said:
So, there's this problem that happens when the software can't connect to the device if I take too long to flash after entering EDL Mode, I've seen a lot of other cases of this "problem" too. I have to test point and flash right after, which is no problem in MiFlash, but in QFIL and QPST it looks like it takes too long to connect with the device and then it fails. But I've seen that S-Unlock uses
their own tool called XiaomiTool, where they create an account for you which has credits. Then the tool uses the credits to flash. It's quite confusing... but you don't need to grant them TeamViewer access, which if way more safer than the previous method. Man... I had a ZUK device before, there was no AntiRollback ****, I didn't even had to unlock a bootloader in the first place you would just wipe and flash all day long for as long as you'd want, I was in heaven and didn't know it.
Also, I'm pretty sure the softwares detect the device just fine, the device connects through 9008 port, and they detect it right after connecting it.
Click to expand...
Click to collapse
You say that through XiaoMi Flash (also usually called MiFlash tool) the flash process begins then no need to an authorized account, right? if this is right then now the only challenge is get the tool to work fine and in this case I guess that the best would be to try with some tricks like:
- Uninstall all the drivers (I know you say that pc detects it but it seems that in the way it is disconnecting).
- Before to reinstall them again disable signature verification from Windows to avoid that some firewall/antivirus cut the drivers to be installed properly.
- Check that the folder where the images and the scripts are, be in the last directory/path in the tool an short the name where it contained for "6mipro" for example without spaces.
- Move all the files of the rom to the same drive and folder where XiaoMi flash is installed usually C drive.
- Prepare previously all the tool and the path and just to the end put device in download mode, with battery disconnected and fingerprint is also recommendable to get out.
- Try with firmware for 6 Pro and also for A2 Lite.
Regarding this service is extrange how they can take control over device, no remote service, nor IMEI required or IP digits, How they can put a firmware onto your device this way!. There are other services that you can consult before to accept this unless you find some positive reference about it.
SubwayChamp said:
You say that through XiaoMi Flash (also usually called MiFlash tool) the flash process begins then no need to an authorized account, right? if this is right then now the only challenge is get the tool to work fine and in this case I guess that the best would be to try with some tricks like:
- Uninstall all the drivers (I know you say that pc detects it but it seems that in the way it is disconnecting).
- Before to reinstall them again disable signature verification from Windows to avoid that some firewall/antivirus cut the drivers to be installed properly.
- Check that the folder where the images and the scripts are, be in the last directory/path in the tool an short the name where it contained for "6mipro" for example without spaces.
- Move all the files of the rom to the same drive and folder where XiaoMi flash is installed usually C drive.
- Prepare previously all the tool and the path and just to the end put device in download mode, with battery disconnected and fingerprint is also recommendable to get out.
- Try with firmware for 6 Pro and also for A2 Lite.
Regarding this service is extrange how they can take control over device, no remote service, nor IMEI required or IP digits, How they can put a firmware onto your device this way!. There are other services that you can consult before to accept this unless you find some positive reference about it.
Click to expand...
Click to collapse
No, it does need an authorized account, but first it has to connect to the device, after it suceeds, it then asks for the account. I don't think that it "disconnecting" is a big issue, only if the Xiaomi Tool that the S-Unlock guys use also takes a long time to connect to the device.
To explain the problem more precisely, the software tells me "cannot read hello packet if I press the button too long after connecting EDL, it fails seconds after clicking to flash. If I connect the device and flash right away, it suceeds and then proceeds to ask the authorized account.
And about the service, they don't actually take control over the device, I would do the flashing myself, the only thing they do is provide the account necessary to flash, but it isn't in the MiFlash tool, it's the XiaomiTool (they give the link to the app), where it first asks for an account, then only after logging in it can start the flashing process. One of those cases I've talked about that were just like mine were solved with these guys.
GNDawg said:
No, it does need an authorized account, but first it has to connect to the device, after it suceeds, it then asks for the account. I don't think that it "disconnecting" is a big issue, only if the Xiaomi Tool that the S-Unlock guys use also takes a long time to connect to the device.
To explain the problem more precisely, the software tells me "cannot read hello packet if I press the button too long after connecting EDL, it fails seconds after clicking to flash. If I connect the device and flash right away, it suceeds and then proceeds to ask the authorized account.
And about the service, they don't actually take control over the device, I would do the flashing myself, the only thing they do is provide the account necessary to flash, but it isn't in the MiFlash tool, it's the XiaomiTool (they give the link to the app), where it first asks for an account, then only after logging in it can start the flashing process. One of those cases I've talked about that were just like mine were solved with these guys.
Click to expand...
Click to collapse
Ok, now the things are most clear, I never need an authorized account (by fortune) I´m not sure and I expect that my actual doesn´t need it just in case.
When you connect for first time to the tool and try to flash then the tool allows you continue but of course then it prompts for an authorization, from here you can´t try a second attempt in the same time that it remains connected this will lead you then of a few minutes to a fail like "sahara fail" or "cannot read packet".
In my experience the second attempt didn´t work at all so you have to disconnect device and restart the tool to can try it again.
As far I understand this is similar to a patched Odin for Samsung devices to bypass some security controls but in this case they provide you a patched XiaoMi tool which is controlled remotely to get authorized. It has sense and it seems trustworthy.
I don´t know if actually Xiaomi authorizes new account users https://miui.blog/any-devices/mi-account-authorization-tips/
And Probably you can try first an older version of MiPhone, previous than XiaoMi flash https://www.xiaomiflash.com/download/
SubwayChamp said:
Ok, now the things are most clear, I never need an authorized account (by fortune) I´m not sure and I expect that my actual doesn´t need it just in case.
When you connect for first time to the tool and try to flash then the tool allows you continue but of course then it prompts for an authorization, from here you can´t try a second attempt in the same time that it remains connected this will lead you then of a few minutes to a fail like "sahara fail" or "cannot read packet".
In my experience the second attempt didn´t work at all so you have to disconnect device and restart the tool to can try it again.
As far I understand this is similar to a patched Odin for Samsung devices to bypass some security controls but in this case they provide you a patched XiaoMi tool which is controlled remotely to get authorized. It has sense and it seems trustworthy.
I don´t know if actually Xiaomi authorizes new account users https://miui.blog/any-devices/mi-account-authorization-tips/
And Probably you can try first an older version of MiPhone, previous than XiaoMi flash https://www.xiaomiflash.com/download/
Click to expand...
Click to collapse
Hey man, I bought the S-Unlock service, I tried to flash the daisy ROM but it wouldn't send the "firehose_emmc_something" succesfully, so I tried the Redmi 6 Pro ROM i'd downloaded (Xiaomi_Redmi_6_Pro_V9.6.4.0.ODMMIFD_20180730.0000.00_8.1_Global_XFT) and it succesfully flashed!!!!!
BUT, it doesn't boot. "This version of MIUI can't be installed on this device."
Any ideas? In the support group of S-Unlock they say this happens when you flash a global rom into a chinese device, which can only receive global roms with unlocked bootloaders. An admin from the group told me to flash chinese ROM.
EDIT: sent the command fastboot getvar all:
product: sakura_india
it ****ing changed hahaha, now I'll probably have to flash an indian ROM, but I'll have to pay again, I really want to give up this device...
GNDawg said:
Hey man, I bought the S-Unlock service, I tried to flash the daisy ROM but it wouldn't send the "firehose_emmc_something" succesfully, so I tried the Redmi 6 Pro ROM i'd downloaded (Xiaomi_Redmi_6_Pro_V9.6.4.0.ODMMIFD_20180730.0000.00_8.1_Global_XFT) and it succesfully flashed!!!!!
BUT, it doesn't boot. "This version of MIUI can't be installed on this device."
Any ideas? In the support group of S-Unlock they say this happens when you flash a global rom into a chinese device, which can only receive global roms with unlocked bootloaders. An admin from the group told me to flash chinese ROM.
EDIT: sent the command fastboot getvar all:
product: sakura_india
it ****ing changed hahaha, now I'll probably have to flash an indian ROM, but I'll have to pay again, I really want to give up this device...
Click to expand...
Click to collapse
The service is very limited, they had to guide you to a final success, it´s a shame.
It was hard to know exactly what firmware is the proper for this "hybrid" phone. The theory is right, this might be an indian version but I guess that you didn´t receive at first the getvar product as sakura_india.
It might be great if they can unlock bootloader and this way you can do anything on it.
Did you see bootloader status or if you can flash something now through fastboot?
Try with other tool for Qualcomm from here https://androidmtk.com/category/tools maybe some of them work.
SubwayChamp said:
The service is very limited, they had to guide you to a final success, it´s a shame.
It was hard to know exactly what firmware is the proper for this "hybrid" phone. The theory is right, this might be an indian version but I guess that you didn´t receive at first the getvar product as sakura_india.
It might be great if they can unlock bootloader and this way you can do anything on it.
Did you see bootloader status or if you can flash something now through fastboot?
Try with other tool for Qualcomm from here https://androidmtk.com/category/tools maybe some of them work.
Click to expand...
Click to collapse
The service is only to give me the EDL Authorization, they don't care if what I flash, they just grant me this permission to flash in EDL, which ****ing xiaomi requires. They have a bootloader unlocking service, but for MIUI v9 only, and there isn't an option for my phone (neither mi a2 lite nor redmi 6 pro). I'm willing to try again, it would cost me 10 dollars more, but I need to know what Rom works for this thing. I don't think these tools will work because the phone continues the same, but now with a ROM which the device doesn't accept because of locked bootloader which I can't unlock.
EDIT: I've read in an article from XDA that booting MIUI Roms in the Redmi 6 pro can brick it. I'll have to flash a custom rom?
GNDawg said:
The service is only to give me the EDL Authorization, they don't care if what I flash, they just grant me this permission to flash in EDL, which ****ing xiaomi requires. They have a bootloader unlocking service, but for MIUI v9 only, and there isn't an option for my phone (neither mi a2 lite nor redmi 6 pro). I'm willing to try again, it would cost me 10 dollars more, but I need to know what Rom works for this thing.
Click to expand...
Click to collapse
If the limit is according a certain time and not number of flashing sessions I think you have to follow these simple rules:
- Flash first an Indian version of 6 Pro http://en.miui.com/download-349.html#545 (choose stable not developer rom)
- Prepare/download if it exists a chinese version, I´m not sure it does so device was release for India but some guys are talking that they bought with a chinese firmware although in the official site there is only an Indian firmware.
- Keep in mind that this device has ARB so don´t try with a lower build number version.
I don't think these tools will work because the phone continues the same, but now with a ROM which the device doesn't accept because of locked bootloader which I can't unlock.
Click to expand...
Click to collapse
No, this tool can work as the same way that XiaoMi flash can, the same thing that both can´t achieve is that a wrong firmware can work/boot up on your device due to regional locking security. Maybe you can try this simple tool before https://androidmtk.com/download-emmc-dl-tool anyway if doesn´t result probably the best would be go for a second chance with that service.
SubwayChamp said:
If the limit is according a certain time and not number of flashing sessions I think you have to follow these simple rules:
- Flash first an Indian version of 6 Pro http://en.miui.com/download-349.html#545 (choose stable not developer rom)
- Prepare/download if it exists a chinese version, I´m not sure it does so device was release for India but some guys are talking that they bought with a chinese firmware although in the official site there is only an Indian firmware.
- Keep in mind that this device has ARB so don´t try with a lower build number version.
No, this tool can work as the same way that XiaoMi flash can, the same thing that both can´t achieve is that a wrong firmware can work/boot up on your device due to regional locking security. Maybe you can try this simple tool before https://androidmtk.com/download-emmc-dl-tool anyway if doesn´t result probably the best would be go for a second chance with that service.
Click to expand...
Click to collapse
No, every flash costs 10 credits, which costs 10 dollars. If I get it wrong, I have to pay again.
What I meant by the tools not working is that just like Xiaomi flash, they require the EDL authorization.
I tried with emmc tool, but I couldn't get it to work, it gives me "Failed to connect to phone"
Adding the edit I put in the previous reply, I read an article here in XDA saying that flashing MIUI Rom in Redmi6 pro (along with other devices) may brick the device just like my device is bricked right now (https://www.xda-developers.com/flash-miui-global-locked-bootloader-xiaomi-brick/
So, will I have to flash custom rom?
GNDawg said:
No, every flash costs 10 credits, which costs 10 dollars. If I get it wrong, I have to pay again.
Click to expand...
Click to collapse
Ah ok, then the best is go direct to the safest zone flashing the rom linked in my previous post.
What I meant by the tools not working is that just like Xiaomi flash, they require the EDL authorization.
I tried with emmc tool, but I couldn't get it to work, it gives me "Failed to connect to phone"
Adding the edit I put in the previous reply, I read an article here in XDA saying that flashing MIUI Rom in Redmi6 pro (along with other devices) may brick the device just like my device is bricked right now (https://www.xda-developers.com/flash-miui-global-locked-bootloader-xiaomi-brick/
Click to expand...
Click to collapse
Yes, this is now the scenario, to be honest your device is now "double" bricked, first time was bricked due to relock bootloader while a non-proper firmware was shipped with i.e. a Mi A2 Lite firmware on a different device. And the second time now when you flashed a a Global rom over a device that supposedly was (it had to be) shipped with an indian/chinese firmware.
But don´t worry about it, device at this way won´t boot due to a locked bootloader, if you still can enter to fastboot and recovery no signals of serious damages.
So, will I have to flash custom rom?
Click to expand...
Click to collapse
No, never try it yet with locked bootloader untill you unlocket it, this won´t result as same as try to modify any partition or file you can´t by now, your device simply won´t boot at all.
SubwayChamp said:
Ah ok, then the best is go direct to the safest zone flashing the rom linked in my previous post.
Yes, this is now the scenario, to be honest your device is now "double" bricked, first time was bricked due to relock bootloader while a non-proper firmware was shipped with i.e. a Mi A2 Lite firmware on a different device. And the second time now when you flashed a a Global rom over a device that supposedly was (it had to be) shipped with an indian/chinese firmware.
But don´t worry about it, device at this way won´t boot due to a locked bootloader, if you still can enter to fastboot and recovery no signals of serious damages.
No, never try it yet with locked bootloader untill you unlocket it, this won´t result as same as try to modify any partition or file you can´t by now, your device simply won´t boot at all.
Click to expand...
Click to collapse
Hey, so I downloaded the ROM you linked, but it is in .zip format, and the files inside are different from the other ROMs I downloaded, which are in .tgz (I think these are fastboot ROM files, dunno, but they are all in the same format and arrangement), I searched and found a ROM in MIUI site (http://en.miui.com/a-234.html).
The file name is sakura_india_global_images_V10.3.3.0.PDMMIXM_20190711.0000.00_9.0_global_400152c914.tgz
Looks like the same as the one you sent, but in tgz, since it is sakura india global image, 10.3.3.0 and 9.0.
GNDawg said:
Hey, so I downloaded the ROM you linked, but it is in .zip format, and the files inside are different from the other ROMs I downloaded, which are in .tgz (I think these are fastboot ROM files, dunno, but they are all in the same format and arrangement), I searched and found a ROM in MIUI site (http://en.miui.com/a-234.html).
The file name is sakura_india_global_images_V10.3.3.0.PDMMIXM_20190711.0000.00_9.0_global_400152c914.tgz
Looks like the same as the one you sent, but in tgz, since it is sakura india global image, 10.3.3.0 and 9.0.
Click to expand...
Click to collapse
Oh my bad, I linked the rom that is for recovery, the link that you have this is the right firmware to flash through fastboot.
SubwayChamp said:
Oh my bad, I linked the rom that is for recovery, the link that you have this is the right firmware to flash through fastboot.
Click to expand...
Click to collapse
**** man, I'm so frustrared, flashed this ROM and got the same ****ing thing. "This MIUI version can't be installed on this device."
fastboot getvar all
version-bootloader:MSM8953_DAISY2.0_20190711190946
(bootloader) hw-revision:10001
(bootloader) rollback_ver:2
(bootloader) serialno:09d58bc30805
(bootloader) kernel:lk
(bootloader) product:sakura_india
I found that if you send fastboot getvar anti you get if your phone has got antiroll or something like this
fastboot getvar anti
anti:
it gives me blank...
I think I may have another chance to flash, I have some credits, don't know if they are enough, what ROM should I try next if I can? I was thinking maybe chinese ROM?
GNDawg said:
**** man, I'm so frustrared, flashed this ROM and got the same ****ing thing. "This MIUI version can't be installed on this device."
fastboot getvar all
version-bootloader:MSM8953_DAISY2.0_20190711190946
(bootloader) hw-revision:10001
(bootloader) rollback_ver:2
(bootloader) serialno:09d58bc30805
(bootloader) kernel:lk
(bootloader) product:sakura_india
I found that if you send fastboot getvar anti you get if your phone has got antiroll or something like this
fastboot getvar anti
anti:
it gives me blank...
I think I may have another chance to flash, I have some credits, don't know if they are enough, what ROM should I try next if I can? I was thinking maybe chinese ROM?
Click to expand...
Click to collapse
Redmi 6Pro as same as Mi A2 Lite have ARB but actually bootloader revisions are not implementing it so it stays as blank (a kind of zero), when your device reach value 5 then you can´t downgrade anymore on locked bootloaders.
There is something very strange that unfortunately marked your device as practically unusable. The system partition seems to be wrong from the fabric.
It´s hard to know which firmware it´s the correct. Did you see those users with the same problem? maybe you can ask them in some forum for sure.
If exists a chinese version as stated in my previous post this would be the next chosing and the next if exists a chinese version of Mi A2 Lite so I wonder how they installed Android One previously.
SubwayChamp said:
Redmi 6Pro as same as Mi A2 Lite have ARB but actually bootloader revisions are not implementing it so it stays as blank (a kind of zero), when your device reach value 5 then you can´t downgrade anymore on locked bootloaders.
There is something very strange that unfortunately marked your device as practically unusable. The system partition seems to be wrong from the fabric.
It´s hard to know which firmware it´s the correct. Did you see those users with the same problem? maybe you can ask them in some forum for sure.
If exists a chinese version as stated in my previous post this would be the next chosing and the next if exists a chinese version of Mi A2 Lite so I wonder how they installed Android One previously.
Click to expand...
Click to collapse
I think the main problem is the locked bootloader, the device came unlocked so they must've installed android one easily.
I was searching for those similar cases I'd said and found at least 4 more, where they had Mi A2 Lite with sakura product name. Some of them said they had LineageOS installed... I don't remember seeing any Lineage symbols when I booted the device and I know it because I used on my previous device, I only know it was Android One.
In one of the cases, the buyer talked to the seller who showed him all of the other A2 Lite he had were just like his, with LineageOS installed. That's so bad man...
Another useful info, in the back of the phone there's a Model Number, and it matches the box model number, so it isn't counterfeit or scammed, I'm sure this came from Xiaomi.
And one of the cases were solved flashing MIUI China version, I believe that the only way these are not from Xiaomi is everybody having bought from the same chinese seller who did this, so it would make sense that only MIUI Chinese version works, I'll try it, since it's the only option.
I think I'll not be able to flash daisy ROMs, when I tried two daisy ROMs, in both cases the firehose thingy wouldn't send correctly and the flash would fail, sakura ones work fine.
GNDawg said:
I think the main problem is the locked bootloader, the device came unlocked so they must've installed android one easily.
Click to expand...
Click to collapse
Well, here is where my theory that some reseller had to do the whole mistake so the device come locked by default and if Xiaomi flashed Android One also they have to make an A/B partition scheme and this didn´t happen, anyway this is just for the record BUT this could be useful to claim your rights to the seller so if they didn´t do by itself then they had the obligation to buy from a reseller a good device to can sell it to a client in a well form and this is achieve without any technical skill just comparing the IMEIs declared from the box with device itself. Also atleast in my country R6Pro is cheaper than Mi A2 Lite so has sense that they bucked some dollars with it.
I was searching for those similar cases I'd said and found at least 4 more, where they had Mi A2 Lite with sakura product name. Some of them said they had LineageOS installed... I don't remember seeing any Lineage symbols when I booted the device and I know it because I used on my previous device, I only know it was Android One.
In one of the cases, the buyer talked to the seller who showed him all of the other A2 Lite he had were just like his, with LineageOS installed. That's so bad man...
Another useful info, in the back of the phone there's a Model Number, and it matches the box model number, so it isn't counterfeit or scammed, I'm sure this came from Xiaomi.
Click to expand...
Click to collapse
I guess they confussed LineageOs with Android One, in Pie there is not many differences at a quick view,
And one of the cases were solved flashing MIUI China version, I believe that the only way these are not from Xiaomi is everybody having bought from the same chinese seller who did this, so it would make sense that only MIUI Chinese version works, I'll try it, since it's the only option.
I think I'll not be able to flash daisy ROMs, when I tried two daisy ROMs, in both cases the firehose thingy wouldn't send correctly and the flash would fail, sakura ones work fine.
Click to expand...
Click to collapse
In this site there are many firmware versions https://xiaomifirmware.com/roms/download-official-roms-for-redmi-6-pro/ probably you have to choose the chinese version that came first with device and not try to upgrade it to the latest contrarily as we think before. I read that Redmi 6 Pro did come with Oreo 8.1 and although it had a Pie firmware was from other device and it won´t be considered as a downgrade in this case so never had Pie firmware based on Miui.
I did find this but I don´t know if it´s reliable, if unlocking bootloader can be done device will free for any rom http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=5997528&pid=35773053
Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!
HyphenZzX said:
Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293
reg66 said:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293
Click to expand...
Click to collapse
but i don't understand i am already on ww fingerprint???
HyphenZzX said:
but i don't understand i am already on ww fingerprint???
Click to expand...
Click to collapse
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
hi thank you for the response when i open flash thing it just opens the cmd and closes again? what do i do?
edit never mind its doing it now thanks!
reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
thank you so much it works now quick question can i do manual updates now and get the latest firmware?
HyphenZzX said:
thank you so much it works now quick question can i do manual updates now and get the latest firmware?
Click to expand...
Click to collapse
Well, up until 1910.44, we were able to just download the updates from asus and put them in the root of internal storage... But this changed for many users with the .44 update, so I'm not sure... We'll have to see how the next update goes, but yeah, it'll either be through download of ota or by flashing raw rom... Either way it'll be posted here by someone. Won't be long to wait as China versions already have update .52 update, WW comes shortly after
Hi there I am in a similar situation with a tencent rog 2 purchased on ebay that is on android 9 WW version. Is it possible to flash WW_ZS660KL_17.0240.2107.100_M3.23.44.20-ASUS_1.1.232_Phone-user.raw to get to android 10 immediately? I have attempted it just now but it appears the flashall_AFT.cmd is stuck and i have waited around 20 minutes.
edit: I waited an hour and nothing seemed to happen. so I restarted the phone and it seems like nothing happened at all. Any ideas?
edit: accidental double post
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.
.