Related
Hey guys I've run into an issuei bought a Mi 8 off swappa two weeks ago I've been using it and it's been absolutely amazing I love it but a few days ago global miui 9 came out and they phone came bootloader unlocked so I figured I'd flash the firmware and then lock the bootloader I flashed the firmware through Miuitool it worked fine I set it up and then went to lock the bootloader using the same tool I did it and then it started to boot but detected no os anymore so it was bootlooping. I can only access the recovery and fastboot mode I tried wiping didn't work I tried flash the firmware using miflash tool and manually doing the commands also tried getting into edl mode but says it's locked. I tried calling support but they told me they didn't do phone repairs and to call the manufacturer of which I bought it from (swappa) I'm kinda losing hope I'm not sure what to do I've tried so much maybe I'm missing something. If anyone has any suggestions I would love that thanks and here's what my recovery says if that helps
Did you try to flash twrp with fastboot and then from twrp flash the new rom?
xristos9 said:
Did you try to flash twrp with fastboot and then from twrp flash the new rom?
Click to expand...
Click to collapse
I did not but I doubt I could because the bootloader is locked
Had you try flashing it with Deep Flash Cable?
http://en.miui.com/thread-1597002-1-1.html
Mi 8 Fastboot ROM can be downloaded here:
https://forum.xda-developers.com/mi-8/development/firmware-global-china-stock-firmware-t3818194
Disclaimer: I had not tested this method but shared from the internet. The IP of the method is from the link shared above and I hold no responsibility in any event it cause damage to your phone.
To resurrect the phone, you will need a MI account with authorized access to the EDL. Look at the topic of Redmi 5 as they resurrect bricks. On our forum, several MI 8 & MI 8 SE have already been resurrected in this way.
Instructions (RU)
dogsly said:
To resurrect the phone, you will need a MI account with authorized access to the EDL. Look at the topic of Redmi 5 as they resurrect bricks. On our forum, several MI 8 & MI 8 SE have already been resurrected in this way.
Instructions (RU)
Click to expand...
Click to collapse
I can not register in your forum, could you give us the contact of the people taht can give us account EDL permissions?
BR
thanks for the suggestions guys I was thinking before getting super technical opening up my phone and modding a cable to let you guys know of an update. Last night I stayed up a while i found adb flash tool for recovery mode to flash back to official software (http://www.xiaomitool.com/adb) I downloaded both global and both china otas of stable and beta. First i flashed global successfully but forgot that going from china to global requires unlock boot loader to boot up so it did not boot next I tried china stable but the file is an older version and did not flash since it was "downgrading" and last I tried china beta which was newer in theory but did not flash since it was not stable. So i am going to wait for a new china stable rom to come out whenever it does because in theory it will flash correctly and completely fix the phone because its china miui thats newer than the one global version now i can only wonder if it can flash because i will be going from global to china but again I will let you guys know when i attempt it, I understand I will be waiting a while for a stable version those dont come often but in the meantime i can focus on other things and thankfully i have multiple back up phones. thanks guys
StarwarsMissionary said:
I tried china stable but the file is an older version and did not flash since it was "downgrading"
Click to expand...
Click to collapse
Theoretically and my previous experience with Nexus phone, older version of official ROM should be fine as it should get OTA to latest version. So, I think it is worth a try.
At the same time, I'm still patiently waiting for my 1st Mi 8 to arrive at door step.
ZhenMing said:
Theoretically and my previous experience with Nexus phone, older version of official ROM should be fine as it should get OTA to latest version. So, I think it is worth a try.
At the same time, I'm still patiently waiting for my 1st Mi 8 to arrive at door step.
Click to expand...
Click to collapse
I agree with you and I used to own a nexus too so I understand what your saying but I tried flashing miui 9 china stable and the error said it was an older version and it was "illegal to downgrade" which is weird so I'll just wait for an updated version which might take a while
Never lock a boatloader with aftermarket global on a China Xiaomi.
I think because of the flashing the bootloader is locked again, maybe try to unlock it with miui unlock.
Maby Xiaomi enable the anti roll back also for the Mi 8 after they did it to the Xiaomi redmi note 5 whyred? Many people have ended up with bricked phones.
Edit
Same problem solution is unlock boatloader
https://xiaomi.eu/community/threads/mi-8-safetynet-android-pay-and-related-issues.45286/
I faced the same problem with my Mi 8 when I locked the bootloader after installing Global ROM. Simply put your phone in Fastboot, and again Unlock the Bootloader using Xiaomi official Unlock tool. Once bootloader was unlocked, phone booted normally with Global ROM.
Hello, I have blocked bootloader and now I am with the bootloader loop.
I've tried to unlock again from console and from the Xiaomi tool, but it has not been possible. The tool says that the device is not associated. Any solution to this?
I have also tried from Recovery (With MiFlash) to put the stable Chinese version, but having a higher version installed does not leave me.
If I re-flash the same version, it completes it but when restarting, the loop returns.
Any solution?
Hi I have the same problem but now I have a new and BIG new problem...
When I try to unlock the bootloader with my account the software said me that my account is not bounded in this device... cry cry cry!!!
Somebody knows if it is normal and if I will fixed?
BR
The mi unlock tool problems are mainly because of either it's not verified with your account or because before it bricked you forgot to go to development settings and add your phone for unlock which I forgot to so whenever I try to unlock it again it says it isn't verified because I'm a moron and forgot to add my Mi8 to my account in case something like this happened, now I gotta wait for a stable newer miui 9 China version to flash from the adb software
Any news on how to solve the brick?
The perfect solution would be to have access to an account with EDL permissions to re-unlock the bootloader.
Enviado desde mi SM-G930F mediante Tapatalk
StarwarsMissionary said:
The mi unlock tool problems are mainly because of either it's not verified with your account or because before it bricked you forgot to go to development settings and add your phone for unlock which I forgot to so whenever I try to unlock it again it says it isn't verified because I'm a moron and forgot to add my Mi8 to my account in case something like this happened, now I gotta wait for a stable newer miui 9 China version to flash from the adb software
Click to expand...
Click to collapse
When you have any update on this, please let me know I have the same issue and did same mistake.
Let me know if you were able to un-brick it.
Looking fwd to see an update from you.
This. Is. F****d. Up. Someone needs to say it. They do totally crazy things and we saw too many bricks coming from their unexplained tinkering with ARB and locking. Additionally, their each new flagship gets always one step closer to the prices of better competition. We are getting too screwed and we desperately need a new, reasonably priced and logical brand. Nokia? Wouldn't say so. Essential? US only and seems to close down. OnePlus? Getting costlier. Google? Got really costly. **** happened. Really, sorry for OT, but my empathy and sociological thinking just hurts me when I see this.
j1505243 said:
This. Is. F****d. Up. Someone needs to say it. They do totally crazy things and we saw too many bricks coming from their unexplained tinkering with ARB and locking. Additionally, their each new flagship gets always one step closer to the prices of better competition. We are getting too screwed and we desperately need a new, reasonably priced and logical brand. Nokia? Wouldn't say so. Essential? US only and seems to close down. OnePlus? Getting costlier. Google? Got really costly. **** happened. Really, sorry for OT, but my empathy and sociological thinking just hurts me when I see this.
Click to expand...
Click to collapse
Yeah, I thought I was the only one thinking like this.
Companies want as much money as possible. Oneplus is increasing prices not because the components cost more but because they waste money on ads and want more profit. And they pull it off because people will still buy their phones.
Honestly, the Mi 8 is a " flagship killer-killer",it provides almost the same stuff as the OP6 for less money but people either never heard of Xiaomi or are hesitant when it comes to buying their phones ( I don't understand why, though ) .
As for their phones dying, I only saw bricks from people who tried tinkering with deep level stuff without actually knowing what they were playing with.
They don't suddenly die/lose basic functions out of the blue like e.g. Moto phones and I don't know of a single device which beats them at this price along with what you get in a phone.
The Marionette said:
I only saw bricks from people who tried tinkering with deep level stuff without actually knowing what they were playing with.
Click to expand...
Click to collapse
Just let me tell that you can do the **** even actually knowing what you are playing with. You just need to forget to change the "clean all and lock" option which comes selected by default. And believe me, it's not that difficult at 3 a.m. after some successful flashes.
I think it's not necessary to dive into the hurt, you know.
Cheers
descarao81 said:
Just let me tell that you can do the **** even actually knowing what you are playing with. You just need to forget to change the "clean all and lock" option which comes selected by default. And believe me, it's not that difficult at 3 a.m. after some successful flashes.
I think it's not necessary to dive into the hurt, you know.
Cheers
Click to expand...
Click to collapse
There is a need for that. This is an expensive toy and you shouldn't be playing with it if you are not 100% that you can undo the thing you will do if it goes wrong ( you are free to do it but then at least try to find a solution yourself ) .
After seeing posts which are pretty much like " uwu I made a f*cking boo boo, a weal f*cky wucky, pweese help me guys ;((((( " ( which could've been avoided by following some logic or by actually investigating before flashing stuff ) , it's high time people who are thinking about unlocking the bootloader actually see what they might be getting into if they "touch wrong things in the wrong way".
Hi!
It was a bad idea to flash 356510B0982Axon M RU image (available on Russian zte website) to my ATT ZTE Z999.
Phone bricked and only visible by my PC as QUSB_BULK. Looks like there is a way to restore it, but i need full original working stock ATT image (any version). Does someone can share it?
Found at many places, but all of them wants money I would pay, if it will be 5 but not 25euro
I flashed mine using this[Leakite]ROM_AXON_M_VDF_SDCARD_SOFTWARE_PACKAGE_MR00a and it's not turning on anymore. We need help :crying:
Looks like we need 348010B3014Z999V1.0.0B30.zip
But i can't find it in free access, only payment sites like easy-firmware and grt-dongle
Any idea how we can flash a rom on edl mode?
No ideas for now. But friend of mine works in cellphone service center, he helped me many times to unbrick some devices. For now he is found firmware to restore Chinese axonM, can't find at&t
Ok, i got image... 10$ wasted It really looks like correct AT&T image, but QFIL, MiFlash, QPST, QComDownloadTool (ZTE util) can't flash it
https://drive.google.com/file/d/1n0qjH1vaTQVwckFPizSAMDHrBh6uA8b6/view?usp=sharing
BRuTe007 said:
Ok, i got image... 10$ wasted It really looks like correct AT&T image, but QFIL, MiFlash, QPST, QComDownloadTool (ZTE util) can't flash it
https://drive.google.com/file/d/1n0qjH1vaTQVwckFPizSAMDHrBh6uA8b6/view?usp=sharing
Click to expand...
Click to collapse
You need the firehose programmer and use parts of that firmware to flash with it
BRuTe007 said:
Ok, i got image... 10$ wasted It really looks like correct AT&T image, but QFIL, MiFlash, QPST, QComDownloadTool (ZTE util) can't flash it
https://drive.google.com/file/d/1n0qjH1vaTQVwckFPizSAMDHrBh6uA8b6/view?usp=sharing
Click to expand...
Click to collapse
... If you can get to edl mode, try those Axon 7 firehose programmers. Since they are the same platform. QFIL should flash this image zip with no problem.
Honami754 said:
... If you can get to edl mode, try those Axon 7 firehose programmers. Since they are the same platform. QFIL should flash this image zip with no problem.
Click to expand...
Click to collapse
Are you sure because im under the impression you can only use the exact specific firehose even if its the same chip i think its hard encoded into the shara protocol it will only except the same firehose but mabye im wrong thats just what ive known
Tried Axon 7 EDL Tool and it's won't work
stopped futher research and replaced MB from broken one that bought on ebay
Anyone attempted to flash this? I just got a new one and I'm scared flashing again. I'm thinking of just buying an At&t prepaid sim just to get the latest update.
tidus1ph said:
Anyone attempted to flash this? I just got a new one and I'm scared flashing again. I'm thinking of just buying an At&t prepaid sim just to get the latest update.
Click to expand...
Click to collapse
No reason to flash it if your axon not bricked. I's a stok ATT version.
BRuTe007 said:
No reason to flash it if your axon not bricked. I's a stok ATT version.
Click to expand...
Click to collapse
The one my phone got is the october 1, 2017 patch with build number Z999V1.0.0B21. So the download file is the newer-ish right? Because on the website the latest is sept 18, 2018 patch with build number Z999V1.0.0B35.
tidus1ph said:
The one my phone got is the october 1, 2017 patch with build number Z999V1.0.0B21. So the download file is the newer-ish right? Because on the website the latest is sept 18, 2018 patch with build number Z999V1.0.0B35.
Click to expand...
Click to collapse
This one was named 348010B3014Z999V1.0.0B30.zip and i think B35 newer then this one.
Here are the Z999 and Z-01K firehose files, extracted from an Internal ZTE tool I have. Hope it helps people out
Z-01K (Japanese Axon M)
https://www.androidfilehost.com/?fid=1395089523397896977
Z999
https://www.androidfilehost.com/?fid=1395089523397896976
All I ask is if you use these files in a guide or anything that you credit me for providing them because i needed to pay to grab these.
deadman96385 said:
Here are the Z999 and Z-01K firehose files, extracted from an Internal ZTE tool I have. Hope it helps people out
Z-01K (Japanese Axon M)
https://www.androidfilehost.com/?fid=1395089523397896977
Z999
https://www.androidfilehost.com/?fid=1395089523397896976
All I ask is if you use these files in a guide or anything that you credit me for providing them because i needed to pay to grab these.
Click to expand...
Click to collapse
Forgive my ignorance. But what does these files do? z999 is the at&t's version right?
tidus1ph said:
Forgive my ignorance. But what does these files do? z999 is the at&t's version right?
Click to expand...
Click to collapse
The firehose is needed to flash the device with QFIL, miflash, etc so a device can be unbricked.
deadman96385 said:
The firehose is needed to flash the device with QFIL, miflash, etc so a device can be unbricked.
Click to expand...
Click to collapse
Tried to flash with Miflash but that failed starts flashing but then says : Cannot Read Port and stops flashing.
Also tried QFIL But also fails with this message : Download Fail:Sahara Fail:QSaharaServer Failrocess fail
hope somone can clarify if its even possible to recover.
this brick happend after update.
Reverender said:
Tried to flash with Miflash but that failed starts flashing but then says : Cannot Read Port and stops flashing.
Also tried QFIL But also fails with this message : Download Fail:Sahara Fail:QSaharaServer Failrocess fail
hope somone can clarify if its even possible to recover.
this brick happend after update.
Click to expand...
Click to collapse
Sounds like you have a driver issue make sure you install the Qualcomm drivers
deadman96385 said:
Sounds like you have a driver issue make sure you install the Qualcomm drivers
Click to expand...
Click to collapse
UPDATE:
figured out what is wrong with QFIL
the Firehose File you send reads only 0 bytes this is why qfil stoped working. might also be the problem with the rest of the flashers i tried.
anycase the elf file in the zip is broken ?
any case you have a .MBN version instat of a .ELF maybe that works ?
Seems im making progress.
im using ToolStudio right now.
the only thing i guess is holding me back is im missing 2 files: RAM and Boot image.
these are not present in the firmware file.
is there anyway i could get them ?
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
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?
Hello everyone, im new to this Forum.
I need to ask if someone can help me. I remember using the cleaning Tool on my Mi11 on the Bus and seconds after closing the App the Phone suddenly Turned off & after Turning it back on it just displayed the Message
"your System has been destroyed" and constantly bootlooping.
Recovery Mode was not working, i can only get into fastboot Mode.
I tried flashing new Firmware with the tools provided by Xiaomi but they always tell me to unlock the bootloader wich i havent done and now i cant cause i cant get into the Phone.
I also tried unlocking the Bootloader with MiFlash Unlock but it tells me to add my account in the MIUI Developer Options..
I then contacted some Xiaomi unlocking Service and pay him 30€ to unlock my Phone in a teamviewer Session via AvatarAuthTool and some other stuff but even he was not able to do it.
I removed the backplate from the Phone and shortened the testpoint pins and he tried again with no luck..
i have no Idea how to get this Phone usable again and im desperatly looking for any help or advice bcuz im currently rocking my old Sony Erricson Walkman Phone..
thanks in advance for anyone who is taking the time to read all this and trying to help
You didn't mention if it's still on warranty and whether you can get it repaired from there?
You don't need to unlock the bootloader if you're using the right firmware for your variant.
Do you happen to remember whether it was EEA, MI, IN or etc version for your device?
Unknown.Guy said:
You didn't mention if it's still on warranty and whether you can get it repaired from there?
You don't need to unlock the bootloader if you're using the right firmware for your variant.
Do you happen to remember whether it was EEA, MI, IN or etc version for your device?
Click to expand...
Click to collapse
I dont think i still have warranty cause i bought it as used from a friend, How do i find the correct Firmware as you say i dont need to unlock anything i might have tried with the wrong version. Also i believe its a global version.
Coolpenisbro said:
I dont think i still have warranty cause i bought it as used from a friend, How do i find the correct Firmware as you say i dont need to unlock anything i might have tried with the wrong version. Also i believe its a global version.
Click to expand...
Click to collapse
No worries. You will have to try a couple of fastboot firmwares.
For each of them, you need to use the latest MiFlash Tool and make sure that CLEAN ALL only option is selected.
One thing to note here is that once you select the firmware folder in MiFlash, it automatically switches to Clean All and Lock
So you better make sure to look well and switch to CLEAN ALL only again before you hit the Flash button.
Latest Global:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Latest Global EEA:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Not so latest China Stable:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I couldn't find the latest fastboot version for China. Make sure you download fastboot versions for all of these and try one by one. At least one of these have to work for your bootloader.
If these don't work then we could try Indonesia, Turkey, Taiwan and Russia firmwares. No way none of them works.
Edit: Idk how it selected Bold but nvm. Also, these steps will wipe all data on phone. Will be like a factory reset.
Give this a try first, who knows it might work lol.
How to Fix “The System Has Been Destroyed” Issue on Xiaomi Phones - Techtrickz
Xiaomi smartphones usually work flawlessly, but sometimes it may act weirdly. An OTA update can cause the issue and sometimes it happened without any intervention by users. OTA updates sometimes will brick the phone leaving the message ‘the system has been destroyed’ on the boot screen. For...
techtrickz.com
Unknown.Guy said:
Give this a try first, who knows it might work lol.
How to Fix “The System Has Been Destroyed” Issue on Xiaomi Phones - Techtrickz
Xiaomi smartphones usually work flawlessly, but sometimes it may act weirdly. An OTA update can cause the issue and sometimes it happened without any intervention by users. OTA updates sometimes will brick the phone leaving the message ‘the system has been destroyed’ on the boot screen. For...
techtrickz.com
Click to expand...
Click to collapse
Dude thanks for your efforts in trying to Help. In the end i refunded my Money wich i paid to the first unlocking guy and looked on Telegram, where i found a 100% legit dude. he flashed it on first try. also he was ok with an afterwards payment + he was only 25€. I can link his page if someone is interested.