Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
steinwayer said:
Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
Click to expand...
Click to collapse
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
compu829 said:
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
Click to expand...
Click to collapse
After doing some heavy research i managed to find it!! Here it is, the TCL 950 firmware
http://pan.baidu.com/s/1geDBRnt
It is the official firmware directly from TCL i managed to talk with their assistance in China
@compu829 how can i flash this firmware now on my idol 4s??
Thank you so much in advance
@steinwayer I will need to download and extract it. I'll take a look later today.
Thanks @compu829
Did you find anything interesting ?
I'm interested in the possibilities here too. Thanks for your research and sharing it!
steinwayer said:
Thanks @compu829
Did you find anything interesting ?
Click to expand...
Click to collapse
I can't download it. Can you? If so can you put it somewhere like mega.co.nz?
I was able to download the package and re-upload it to mega with some help from my friends. Here is the link: https://mega.nz/#!ITJhjYIS!R_iUZhGZMcslAK_u1wdsJ-7q-0D5ma_KrHl4pu2CPqo
I took a quick look, and it is pretty much all mbn files that the factory would flash during assembly, so you will (most likely) need a copy of QPST. We may also be able to use WDRT to flash it. In either case, flashing will fail miserably if the certificates don't match.
So how would you suggest to do this @compu829?
steinwayer said:
So how would you suggest to do this @compu829?
Click to expand...
Click to collapse
compu829 said:
... In either case, flashing will fail miserably if the certificates don't match.
Click to expand...
Click to collapse
^^^ You probably won't be able to easily. At this point, no one here knows, but as @compu829 stated, if the certificates don't match (which they most likely don't), then you're not going to be flashing it at this point.
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
steinwayer said:
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
Click to expand...
Click to collapse
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
It makes perfect sense
What i was thinking tho is that probably the two devices have even a different bootloader. Meaning that it would be a total wipe of the entire disk including swap partition and try to flash that rom.
I was thinking: imagine a bricked device, sometimes is possible to wipe out completely the memory on it and just flash the right rom. Sadly i do not habe much experience in mobile devices.. been developing only for desktops for years.
But if you guys manage to accomplish that it would be great.
The alcatel idol 4s is a great phone for both specs and design and is currently EXTREMELY cheap to. Buy on ebay (you can even find it at 100 bucks) mainly because of its OS
Being able to turn it into an Android phone would be an amazing feat
snickler said:
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
Click to expand...
Click to collapse
Also, a very important factor is that the phones are made by the same shenzhen manufacturer most likely in the same plant. The only thingthey really change is the logo on the back, which comes later on, and the OS.from aanufacturing perspective it would not make much sense to lock with certificates the devices,slowing quite a bit he manufacturing process.it would have sense if the two devices were to be released in the same country, but in this case, tcl 950 is just available in asia, where idol 4s isnot. How can we verify this certificate thing @compu829 ? We have an Idol 4s
hello @snickler do you think that doing this: https://www.youtube.com/watch?v=Iwkx5CFRFKo
would give me a chance of success?
Also, in case of failure for differente certificates, do you think the process would not even start or would it start and brick my device?
Thanks
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
snickler said:
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
Click to expand...
Click to collapse
Which method would you suggest me to try??
steinwayer said:
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
Click to expand...
Click to collapse
I don't know what QFIL is, but vol up and power will put the windows phone in a flash mode that is compatible with WDRT. This mode is completely different than the Qualcomm mode. You most likely need to intentionally brick your device to enable Qualcomm recovery mode.
steinwayer said:
Which method would you suggest me to try??
Click to expand...
Click to collapse
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
snickler said:
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
Click to expand...
Click to collapse
If only i could put my hands on the software they use at tcl to flash their devices...
This is oje of the reasons why smartphones are still way behind computers. Not much freedom of choice and yet theorically it would be more than possible to allow a certain level of freedom on it
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
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.
I know that there are so many threads about this, but in every thread everyone is talking different.
I want to just know, which is the tested method to flash European ROM to Chinese phone?
I also dont have a proper link for european rom ( I have seen some people flashing Indian rom and what is difference between indian and european?)
So lads please help me, I dont want to brick my phone, because there are no OP support team near my country. So it would be a garbage.
By personal experience, don't do that.
My phone is just bricked from just trying to flash the same rom again.
I've always did on my htc, xiaomi, samsung and many others and OnePLus 10 pro was the first one to give me problem. If you get in a state that you need to run fastboot flashing unlock_critical and for some reason your device reset then it's dead with no chance to recover.
There is no tool available to us that can recover from that. The phone don't turn on screen, it's not recognized by the computer and even on the charger it just don't turn on. So completely dead.
The best way is to just buy the model NE2213, that comes with a global rom.
zopostyle said:
By personal experience, don't do that.
My phone is just bricked from just trying to flash the same rom again.
I've always did on my htc, xiaomi, samsung and many others and OnePLus 10 pro was the first one to give me problem. If you get in a state that you need to run fastboot flashing unlock_critical and for some reason your device reset then it's dead with no chance to recover.
There is no tool available to us that can recover from that. The phone don't turn on screen, it's not recognized by the computer and even on the charger it just don't turn on. So completely dead.
The best way is to just buy the model NE2213, that comes with a global rom.
Click to expand...
Click to collapse
It is too late, cause I have bought chinese version and waiting to delivery.
Also there is no chance me to leave this ColorOS. So I will somehow flash or sell this phone
Lukagiunashvili said:
It is too late, cause I have bought chinese version and waiting to delivery.
Also there is no chance me to leave this ColorOS. So I will somehow flash or sell this phone
Click to expand...
Click to collapse
Check this: https://forum.xda-developers.com/t/...-roms-and-how-to-make-for-any-device.4461243/
zopostyle said:
Check this: https://forum.xda-developers.com/t/...-roms-and-how-to-make-for-any-device.4461243/
Click to expand...
Click to collapse
Yes I have seen this and much more posts about flashing.
Someone was lucky and made it, someone was not lucky and bricked phone...
Wish i have seen these failures before I buy phone
Get Fastboot Enhanced & files needed to access adb/fastboot from computer. Unlock Bootloader. Download the OOS ROM you want then extract the file you need for Fastboot Enhanced. Make sure no cow files exist on device with Fastboot Enhanced and then if all checks out you flash.
I've kept this very vague because like you've mentioned there are a few different tutorials explaining (including mine here: https://forum.xda-developers.com/t/...lobal-rom-region-change.4462591/post-87151395) but the basic steps I quickly explained should exist in them all. You'll just need to find one you can follow that makes the most sense to you!
I personally used NE2213 on my device that I converted from NE2210 and am using that device to reply to this thread. I am in Canada and this is Chinese Model OP10 Pro and all works fine on my end. Hopefully you can accomplish the same for yourself if this is your intention.
Lukagiunashvili said:
I know that there are so many threads about this, but in every thread everyone is talking different.
I want to just know, which is the tested method to flash European ROM to Chinese phone?
I also dont have a proper link for european rom ( I have seen some people flashing Indian rom and what is difference between indian and european?)
So lads please help me, I dont want to brick my phone, because there are no OP support team near my country. So it would be a garbage.
Click to expand...
Click to collapse
BL4KMRK8 said:
Get Fastboot Enhanced & files needed to access adb/fastboot from computer. Unlock Bootloader. Download the OOS ROM you want then extract the file you need for Fastboot Enhanced. Make sure no cow files exist on device with Fastboot Enhanced and then if all checks out you flash.
I've kept this very vague because like you've mentioned there are a few different tutorials explaining (including mine here: https://forum.xda-developers.com/t/...lobal-rom-region-change.4462591/post-87151395) but the basic steps I quickly explained should exist in them all. You'll just need to find one you can follow that makes the most sense to you!
I personally used NE2213 on my device that I converted from NE2210 and am using that device to reply to this thread. I am in Canada and this is Chinese Model OP10 Pro and all works fine on my end. Hopefully you can accomplish the same for yourself if this is your intention.
Click to expand...
Click to collapse
Should I use the link you pinned here? Is there a rom download link inside?
If you can help me ill be very glad.
Lukagiunashvili said:
Should I use the link you pinned here? Is there a rom download link inside?
If you can help me ill be very glad.
Click to expand...
Click to collapse
If you can make sense of all the steps then go for it lol. My tutorial is more of a gathering of others work put together in a way that I hoped others could follow. I didn't want to re re re make another tutorial from scratch as your already seeing how confusing and inconsistent having so many guides can be!
I typically use Oxygen Updater on the PlayStore. Then in settings I'll do this (check photo). Then go back to the first page of application and you should see a download option (also check photo). Once you've downloaded the file just transfer it to the computer and you should be good to go. This is usually how I get the files...
Thanks so much, You made a great job lad.
Will try when I get a phone and I will let you know how it goes.
Lukagiunashvili said:
Thanks so much, You made a great job lad.
Will try when I get a phone and I will let you know how it goes.
Click to expand...
Click to collapse
Just remember to keep reading over everything while you wait for your phone. Make sure to check everything over and over and just read all the threads here on XDA to get an understanding for what everyone else has done (the good and the bad) to ensure you yourself don't make any mistakes when the time comes.
I have the Chinese Model also and don't even understand one word let alone writing in the language but this is the phone I got and I gotta make it work so I can relate to your situation with buying it already and it being too late to change your mind lol.
my mind is blowing, everyday reading so much failures and bricked phones thats not good for mental health.
planned to go with your guide step by step and pray same time, maybe that helps lol