Related
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
stream1313 said:
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
Click to expand...
Click to collapse
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
sbdags said:
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
Click to expand...
Click to collapse
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Help needed
stream1313 said:
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Click to expand...
Click to collapse
Hey people... Nobody can help me?
Asus help us
Hello ASUS !!!
You have to HELP us, in order to keep your consumer with you. Other vice people will start to think that your ASUS brand is not a trustful brand anymore. Using such tricks as providing consumer with possibility to open a "Pandora's box" with bootloader unlock, and after you pushing consumer to pay about 300 $ for "motherboard replacing".
Following such kind of policy you will collect some money but definitely you will loose much more.
Sincerely,
Stream1313
PS: I was started to use the "unlock" etc not because I do not have other business t do but because of the serious problem in your DEFAULT STOCK software.
To: Moderator - please do not delete this post, hopefully some ASUS people will read it.
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol
ebildude123 said:
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
Click to expand...
Click to collapse
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
stream1313 said:
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
Click to expand...
Click to collapse
Haha no relationship with Asus. I guarantee it. While I agree unlock tool shouldn't be thrown around, that's not what bricks your device, it's what you flash that does. Personally I think they should use fastboot unlock instead but meh. Yes of course everyone has their own opinions. I respect yours and hope you respect mine as well. Good luck with nvflash but I have doubts your current blob would work even if they made a tool compatible with tf701 tegra4.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol, hope your post do not really had any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Pls, if somebody already experienced, reply me!
Sent from my Xperia Arc S using xda app-developers app
stream1313 said:
lol, hope your post do not really has any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Please, if somebody already experienced, reply me...
Sent from my Xperia Arc S using xda app-developers app
Click to expand...
Click to collapse
anybody here?
stream1313 said:
anybody here?
Click to expand...
Click to collapse
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
sbdags said:
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
Click to expand...
Click to collapse
Hi sbdags,
Thanks for your message, currently I just trying to keep my brick charged, to prevent battery dead.. Will wait till smb from ASUS or from outside will broke the bloody encrypted bootloader, because I do not have possibility to replace he main board ((
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Kashban said:
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Click to expand...
Click to collapse
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
Sorry for being late.
That would be great and yes, I do have the tech skills. What do you want me to test?
Kashban said:
That would be great and yes, I do have the tech skills. What do you want me to test?
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
I also have recently experienced a hard brick on an asus tf700t running KatKiss-7.1_TF700T_026
APX mode & only a TWRP backup
I would also like to try your method to unbrick
Thanks in advance
perpetualxda said:
I also have recently experienced a hard brick on an asus tf700t
Click to expand...
Click to collapse
my solution works only for tf701t not tf700t
mr.bin said:
my solution works only for tf701t not tf700t
Click to expand...
Click to collapse
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
jeneral69 said:
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
If your tab "soft" bricked, then that must help...
There are a lot of people having trouble getting Windows 10 builds to run, even on supported phones. I am one. Last weekend I spent hours attempting every way I could to get the latest build on my Lumia Icon. I'm pretty sure my device has some issues, maybe some bad NAND or flakey RAM or something, because I get all sorts of different outcomes.
Needless to say, the one thing that always works is the Recovery Tool.
So, here's my question. Does anyone have the latest Windows 10 image available for download so that I could use the Recovery Tool to push that image instead of the 8.1 image? A quick review of the Thor2.exe program and how to use it would be awesome for this thread also.
Cheers!
-Nate
The lack of replies must mean I'm not asking the right questions here. Did some more digging and self-educating, maybe this is the right one?
Are the Windows 10 builds showing up in NaviFirm Plus? I've found the threads on how to flash a build once you find it, I guess all I'm looking for now is the .FFU.
Cheers!
hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Chouiyekh said:
hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Click to expand...
Click to collapse
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
tsongming said:
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
Click to expand...
Click to collapse
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Chouiyekh said:
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Click to expand...
Click to collapse
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
tsongming said:
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
Click to expand...
Click to collapse
i tried every single thing you wrote above, nothing helpful
I also have the same problem someone could already solve it?
Chouiyekh said:
i tried every single thing you wrote above, nothing helpful
Click to expand...
Click to collapse
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
sear01 said:
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
Click to expand...
Click to collapse
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
thank you very much it is global version Vipper use rom pixel.
thanks for your time
sear01 said:
thank you very much it is global version Vipper use rom pixel.
thanks for your time
Click to expand...
Click to collapse
Click
Okay then, here's the cliff notes.
I have good and not so good news, Keep in mind that repairing Mac address issues, Imei, QCn issues is the same for all Qualcomm processors, it doesn't matter if a post said this is for the Redmi 10, in fact I can't find the link at the moment but Qualcomm themselves published a guide with similar steps across the spectrum of chips. ( Just make sure that you only flash driver ( firmware images ) for your Global Mi8 and not the proprietary files from the links. Otherwise the instructions are the same, various versions of QPST will work, PC drivers, android drivers will also work. If will only benefit you to use the latest version of any of those files. If language is a issue, use chrome with the translator plugin .
I made copies of my personal persist files and spent the time to create the main files that you need and posted them Get the files here : https://mega.nz/#F!0NAXEK7S!Bj_hTKSz2_hMKDjOEocNrg
Install the version of TWRP that is on the link above, Create a folder called restore or whatever you want and place the downloaded files from my Megalink inside of that folder, make sure that they are not compressed. Next, place the folder inside the Twrp/Backup/ <<<< Place your folder there.
Boot to Twrp, click restore, and you should be able to restore the persist image.
If it doesn't work then use ADb to push to your phone. Google it, the steps are listed a billion times on countless sites, and I do not have enough server space to upload a complete recoveries, and plus I will not share my EFS or QCN
If that doesn't work read this post : https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551 ( Note the persist image, present. But also much older. However, it's still worth trying.
Worst case QPST, should absolutely resolve the issue
If what I listed above fails go here: https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-change-mac-address-mido-t3773026
(Again, be sure to only use Mi8 files) DO NOT use a QCN from another device.
Here is another guide that has illustrations, again use your own files for your device, Otherwise the steps are identical, I have completed these steps myself on other devices : http://en.miui.com/thread-348525-1-1.html
One last final option that I would suggest trying before using QPST
Did you happen to make a recovery of your phone, after initially installing TWRP for the first time?
If no, search the web for a full stock recovery
tsongming said:
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
Click to expand...
Click to collapse
I'm very sorry my friend ?, I'm just angry of that problem that's why i forgot to thank you, and I appreciate everything you did and you will. Yes English is not my first or second language, it's my third.
I've tried to flash persist.img through TWRP that what i got (image attached) and when i try to flash it through adb i got write failed
tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
Please don't be upset of me, and please accept my apologies
Chouiyekh said:
Please don't be upset of me, and please accept my apologies
Click to expand...
Click to collapse
No worries, it's all good Thanks.
You may not have seen the post I made earlier here: https://forum.xda-developers.com/showpost.php?p=79802367&postcount=11
If these things do not work come back here and report what happened and I will stay with you until we resolve the issue, there is always something else to try.
I have successfully solved similar issues on other devices, the issue here is possibly a permissions issue due to encryption, Read the post above and make sure that you use the version of Twrp that is linked on my Mega drive. That version has no problems with encryption, while many versions of Twrp have issues with decrypting. Plus, that version allows the option to select and restore each partition ( There is a lot!)
Check this post later, I am going to edit this post, and add a link to the Persist Image from the latest Global stable Rom. This will be an alternative and maybe better solution than using the persist images that I uploaded to my Mega drive.
UPDATE EDIT
Okay, I created a folder on the Mega Link called Method with a TWRP flashable persist image >>> Install the Official Xiaomi EU TWRP English version ( The one on my Mega Drive) Boot to TWRP, Mount the persist partition > Choose Restore and install to persist> Forget you WIFI and rejoin, it may and will probably work for you.
Three Options if it does not
One
First Option requires fully wiping your device, so back everything up
Assuming that your Device is a Global Device
Download this Fastboot Rom : http://en.miui.com/download-346.html Download the Full Stable fastboot version and not the Recovery version.
Unpack the Rom, place your phone into EDL Mode - This Rom comes with the Fastboot flashall script, it will fully restore your phone to the a Stable Rom and Overwrite every partition., this is as good as using Qfil to unbrick. In fact I recommend this over Qfil. This should definitely work, as long as your issue is software, and I am certain that it is.
Two
You are too afraid to wipe the phone and would rather try something else first, since you would need WIFI to restore your Google Services and Mi-Cloud.
No worries, here is a QPST alternative that has worked for many people, you basically create a new Mac address by following the steps in this thread, read the comments, it has worked for many people and it may save you time, and its not as difficult as it may seem.
This method has worked for people with WIFI Authentication issues.
https://forum.xda-developers.com/showpost.php?p=70408778&postcount=9
Use this tool to generate a Mac address to use for the above linked steps.
Three
IMEI Repair
http://en.miui.com/thread-260943-1-1.html
Note although, you may not have issues with data or with calling, this solution ay still be relative. But definitely try everything else first, and leave this as a last resort.
Let me know, if it works, and if it does work , change the name of the OP "Solved" at the end. this way others can benefit from the thread
Update,
I just found another, much easier method of restoring the persist partition
Use Google translator and follow instructions here Then go thank the_virus_ua
Note you do not need to download the files on the link the file that I shared on the earlier post will suffice
@Chouiyekh @sear01
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Chouiyekh said:
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Click to expand...
Click to collapse
Okay, no worries. Just use that last step first.
That one is the easiest and absolutely worked for another person that I was helping. He had exactly the same issue.
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hello dear, i'm sorry for the delay, i had some urgent work out of my country that why i late to answer, now i'm in my country and i started to apply what you wrote, but when i tried to flash twrp the on your reply i got black screen can't boot to twrp ( i think i made something wrong because i extracted the zip file and flash only twrp img through cmd fastboot ) please correct me or give another twrp img .
i read some comments on google that there is a risk to lose imei or something else, if that right how can we making a back up just in case
i hope to get your answer soon, and thank you sooooo much
anyway, i tried at my own risk, that's what i got in twrp ( see image ) then reboot to system but still have the problem ! no wifi no bluetooth !
** i tried factory reset too, not helping.
Hi guys, maybe I found a way to unlock the bootloader, I'll test it and report back, stay tuned.
Awesome
Thank God. The device isn't getting android 10 and was hoping that the bootloader could be unlocked and custom roms development could start.
Hopefully you succeed. Cheers
If everything works good, I will post the guide here.
I couldn't try it yet, because I've been at work.
When i will have my pc under my hands I'll keep you updated
devilyuri said:
If everything works good, I will post the guide here.
I couldn't try it yet, because I've been at work.
When i will have my pc under my hands I'll keep you updated
Click to expand...
Click to collapse
If you just didn't invented this method you could give some links to the guides you're using. May be your attempt has been tried already with no success
Anyway, please update this thread with additional information despite the results
Tried some minutes ago and... Nothing, at least I Tried.
I found a program that uses scripts created with pyton
Here is it
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
I saw that he asked for IMEI and can boot phone into rescue mode, but than it gives an error..
I made the script work but it's way too slow. It test around 10 codes peer minute. It's not worth it considering there are few (if none) custom rom for this phone.
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