Related
Hi.
I work in China ow and then and i bought my self a Lenovo K920 yesterday. A GREAT phone but sadly the it does not have any Google programs/system but just a similar Chinese system which i know nothing about. I have found some ROMs out there but on some forum people warns about flashing the Chinese K920pro as it will brick.
Any one here who could tell me how to proceed.... Thanks
__ZOOM__ said:
Hi.
I work in China ow and then and i bought my self a Lenovo K920 yesterday. A GREAT phone but sadly the it does not have any Google programs/system but just a similar Chinese system which i know nothing about. I have found some ROMs out there but on some forum people warns about flashing the Chinese K920pro as it will brick.
Any one here who could tell me how to proceed.... Thanks
Click to expand...
Click to collapse
There's a video showing how to unlock the developer option in settings and the switch to Google UI is inside the Developer Option. Looks quite awesome, im gonna own this phone later.
AyieStyx said:
There's a video showing how to unlock the developer option in settings and the switch to Google UI is inside the Developer Option. Looks quite awesome, im gonna own this phone later.
Click to expand...
Click to collapse
Yes, i read about this too..... I have the Developer Option available already (a few taps on the version number) but no Google UI option there, just 3 options to chose from. Or do you know how to get more options?
I did a try a russian "2014-10-14--10-16-45 K920_ROW_S126_140825.7z" with their "twrp_2.8.0.1_recovery_K920Pro.7z" file but it "killed" my phone....
I can still access the Lenovo Re ovey and the root menu though.. But the operating system just hangs at the Chinese 4G logo.....
Im not able to restart the TWRP again. I start to dislike this odd phone now after spending 30-40 hours to try to get google play, gmail etc to work.. I should have bought a HTC or Samsung instead..
__ZOOM__ said:
I did a try a russian "2014-10-14--10-16-45 K920_ROW_S126_140825.7z" with their "twrp_2.8.0.1_recovery_K920Pro.7z" file but it "killed" my phone....
I can still access the Lenovo Re ovey and the root menu though.. But the operating system just hangs at the Chinese 4G logo.....
Im not able to restart the TWRP again. I start to dislike this odd phone now after spending 30-40 hours to try to get google play, gmail etc to work.. I should have bought a HTC or Samsung instead..
Click to expand...
Click to collapse
You shouldn't do that at the early release of the phone. Even any phone. You need to wait for the official rom release. How about you try fastboot and flash the twrp/cwm recovery. From the recovery use sideload to reflash the stock rom. Keep in mind that you should wait for a review or someone who actually successfully flash the custom roms/non-official rom. Except root, theres a number of successful root.
AyieStyx said:
You shouldn't do that at the early release of the phone. Even any phone. You need to wait for the official rom release. How about you try fastboot and flash the twrp/cwm recovery. From the recovery use sideload to reflash the stock rom. Keep in mind that you should wait for a review or someone who actually successfully flash the custom roms/non-official rom. Except root, theres a number of successful root.
Click to expand...
Click to collapse
I know but i was desperate to get Google to work... Bricked or Chines system is same same for me...
Fastboot and TWRP cant find any device. Factory reset or wipe did not help either. Can access boot menu and Lenovo recovery, but need a recovery file first, and then we have problem with that i cant access the phones internal storage.... And this crap has no SD-memory either...
$700 down the drain for sure... Still have to buy a new phone though, and im still in China... Have to fly to HK to get a new phone... This is going to be expensive.
Thats what happen when you flash the unofficial rom. You know the risk. Make sure you have installed fastboot driver and adb driver. Im sure you can reflash the rom after you able to enter fastboot
AyieStyx said:
Thats what happen when you flash the unofficial rom. You know the risk. Make sure you have installed fastboot driver and adb driver. Im sure you can reflash the rom after you able to enter fastboot
Click to expand...
Click to collapse
Drivers are okay and have worked before. But now when running ABD Devices command, it show "? unautorized" so i get stuck there.
I SOLVED IT....... Except that the both SIM-card shows a red X.. but everything else seems, camera, GPS, WiFi to work AND it has GOODLE PLAY etc now.. Anyone know how to make the phone to work again?
I have tried ABD, Fastboot, TWRP, MiFlash, QPST, QMSCT_DL_EMMC_TOOL but nothing worked except following this instruction
I used the files in the Bin-folder of K920_ROW_S126_140825_user_1408251128 rom
https://forums.lenovo.com/t5/Lenovo-Phones/Lenovo-K910-Vibe-Z-bricked/m-p/1611710#M6838
Flashed back to the Chinese version and the SIM-cards works again... Any idea why the SIM-cards stops to work on the ROW rom?????
__ZOOM__ said:
Flashed back to the Chinese version and the SIM-cards works again... Any idea why the SIM-cards stops to work on the ROW rom?????
Click to expand...
Click to collapse
Slightly different hardware and radio modules.
On lenovo forum there is something about radio calibration.
Hi guys,
Im getting PMs about this...
Yes, I have resolved it. It works to 100% with all i have tested. I will share it with you as soon im back from my business trip in a week or two.
Z
__ZOOM__ said:
Hi guys,
Im getting PMs about this...
Yes, I have resolved it. It works to 100% with all i have tested. I will share it with you as soon im back from my business trip in a week or two.
Z
Click to expand...
Click to collapse
Hi,
can you share with us the method you used to flash row rom on a Chinese K920?
thanks
row rom on china k920
i have chinese version of k920 and i hate the chinese rom on it!Is it possible to explain how can i have the row version working on my phone and have the radio fixed and have the two sim working!I tested row rom and my sims didnt work (no signal).Any help will be appreciated!
lenovo K920 how to active sim card
Hello good friend merry christmas.I have lenovo k920 Chinese version and I flashed the rom k920_ROW_S126_140825, only sim that do not work, how did you solved this? rom the Chinese version was not able to install google play.Can you help me solve this problem ? thank you
flash row rom to china k920pro
-Download ROW firmware in needrom.com and download CN rom modem file.
-Copy the downloaded "NON-HLOS.bin" file.
-Paste "NON-HLOS.bin" to ROW Rom bin folder.
-Flash Row rom the phone (QPST)
Finaly simple and basicly solution.
CN rom Modem file: https://mega.co.nz/#!mMIilAzZ!9DB3fn-69ewVKzdwWFdeTeKL7Si7zf9gims6Cl7OTMk
soulfreem said:
-Download ROW firmware in needrom.com and download CN rom modem file.
-Copy the downloaded "NON-HLOS.bin" file.
-Paste "NON-HLOS.bin" to ROW Rom bin folder.
-Flash Row rom the phone (QPST)
Finaly simple and basicly solution.
CN rom Modem file: https://mega.co.nz/#!mMIilAzZ!9DB3fn-69ewVKzdwWFdeTeKL7Si7zf9gims6Cl7OTMk
Click to expand...
Click to collapse
Did you try it? Is it work?
vgiazitzis said:
Did you try it? Is it work?
Click to expand...
Click to collapse
of course it works otherwise i wouldnt post the solution.After you flash the rom everything works flawlessly but dont update ota to the latest version because you will lose the radio again.
Thank you very much. I will try it right now.
soulfreem said:
of course it works otherwise i wouldnt post the solution.After you flash the rom everything works flawlessly but dont update ota to the latest version because you will lose the radio again.
Click to expand...
Click to collapse
2 sims works? Could you explain me the what I do? The qualcomm program is in chinese. Please. Thank you
Hurray! Finally, I fix the touch calibration issue; many many thanks to God who showed me the right path.
After suffering hard in last 15 days, even not getting any help from YU Officials, finally God bestowed upon me his blessings and provided me the hint to fix the issue.
What caused the Issue?
YU Televentures recently released a new batch of Yureka Plus (YU5510A-LP) devices with VoLTE feature. This created a storm in Yureka /Plus section of the forum. Some users even bricked after flashing the new firmware since it was totally different from the previous Yureka firmware. I got the backup of /system and /boot from a YU5510A-LP user. I deodexed the files and made a ROM out of it and flashed on my device to test whether it boots or not (a common process of ROM porting). It didn’t boot but it went beyond the boot logo and since the Kernel of YU5510-A didn’t have the correct display drivers for AO5510, I was getting strange characters on the screen. After that I rebooted to TWRP recovery. I was shocked the touch was malfunctioning. If I touch up it was working down, it was totally a mess.
This issue is much dangerous than bricking the device. Even if we brick, we may recover it by following @ricks guide, but with malfunctioning touchscreen phone is utterly useless. It can’t be fixed even after flashing the EMMC backup.
After that I reported to the YU Officials about the touch calibration issue, they didn’t provide any fix, but created a Warning thread regarding it. So sad.
They were even not ready to provide me the touch firmware of Yureka AO5510. They told me that they are also trying to find the cause of touch calibration issue and don’t have the required files. Here is the quote of the reply from YU Officials:
I am afraid that we don't have any files for fixing the issue. To make sure that such thing does not happen we internally test every case before releasing the software. In your case, you got the software from unknown sources and flashed it on your device with your own consent and understanding. Yes, we have devs but they work on cases which have higher reproducibility rate like the proximity sensor issue.
Click to expand...
Click to collapse
After that I analysed the YU5510A-LP VoLTE firmware and found that it was created by Coolpad, a Chinese Smartphone Company. So YU Televentures has imported not only the smartphone (YU5510A-LP) but also the firmware from Coolpad. That’s why it has some unknown bugs which the YU Offical Devs don’t know because they haven’t made the firmware. That’s why the devs didn’t have fix for touch calibration issue. YU is spending very less on service and devs, which very much disappointing. YU, an Indian brand made Yureka for tech freaks and that’s why so many devs engaged in it and even some noobish users like me became devs to raise the company above cheap Chinese brands. But now it’s status is deteriorating, it broke its partnership with Cyanogen and lost the support of so many great devs; and now it is left with some official noobish devs who are taking time like hell to provide a VoLTE patch for other users, this shows how irresponsible is the YU Company. And now it has already been provided by a YU Forum user. Even the Official YU OS is provided by our friend dev @AudioGod.
I hope my above words reaches to the YU Company and they take this criticizing in the right way and improve itself. I want to see this Indian Company rise beyond heights.
After lot of analysis and research I found that the cause of touch calibration issue was the kernel of YU5510A-LP ROM. It changed the TP-Firmware version and touch parameters of Yureka AO5510 (HD) according to Yureka YU5510A-LP (FHD) device and messed up the calibration.
This TP firmware is different in Yureka and Yureka Plus and it never changes after flashing any firmware (fastboot or ROM).
Yureka AO5510 : Each:GT970:0x1039:0x46
Yureka Plus YU5510 : Ofilm:GT970:0x1039:0x48
And mine was : Each:GT970:0x1039:0x47
Yureka (Plus) Touch Panel is manufactured by Goodix, a Chinese Touch Panel and Fingerprint Sensor company.
What didn’t fix the issue?
These are the things which didn't fix the calibration issue:
[/SIZE]
Flashing stock COS 12.1 ROM through recovery
Flashing COS 12.0/12.1 fastboot firmware
Flashing COS 12.0 CPB using YGDP tool (which threw an error of incompatible device before flashing)
Flashing all other partitons (=EMMC backup)
Using Annabathina’s Yureka Unbricking Tool
How did I find a Fix?
While surfing through internet I found a way to check the touch firmware version. Then I checked mine and also asked about it from other Yureka users. Then I searched about the firmware version and got an XDA Thread and also got to know about Goodix Touch Firmware and Goodix Firmware Upgrade Tool (GTP ADB Tool) from Elephone (another Chinese company) forum which I didn’t get from YU.
I read the XDA thread learned about the whole thing and created a Goodix TP Firmware/Config myself.
How to Fix Yureka AO5510 Touch Calibration Issue?
STEP 1: Download GtpAdbToolV1.7_20140424.zip and GT970_1039_AO5510-TP-Firmware.zip on your Windows PC and extract it. Go to the extracted folder of Gtp Adb Tool and run the GtpAdbTool.exe application. Then connect you YUREKA AO5510 to your PC (be sure USB debugging is enabled in your device). You will see the GTP ADB Tool window similar to the screenshot below:
STEP 2: Now click on the button as indicated in the screenshot below and navigate for the GT970_1039_AO5510-TP-Firmware.cfg file (that you extracted in Step 1) and select it.
STEP 3: Then click on the button indicated in the screenshot below to execute firmware upgrade process. Once completed, you can unplug your device and reboot. Voila touchscreen issue fixed!
NOTE (Important):
If the GTP ADB Tool doesn't detect your device or TP firmware, then flash any of the following ROMs:
Official Lineage OS ROMs
Hexagon ROM by @MoreSushant48
Or any other ROM
OR
Go to TWRP Recovery and mount all the partitions. Then connect your phone to the PC. It should detect.
If any of the above methods doesn’t work then try flashing
CoolUI 6.0 for YUREKA (Test build): https://www.androidfilehost.com/?fid=457095661767103935
(After flashing this ROM you may see a 'root' indication on YU LOGO, but you can fix that using Annabathina's Tool)
Important Files
GTP ADB Tool: https://www.androidfilehost.com/?fid=385035244224387037
YUREKA AO5510 TP Firmware: https://www.androidfilehost.com/?fid=385035244224387256
More information: https://www.osbusters.net/2016/10/fix-yureka-ao5510-touch-calibration-issue.html
Credits
Special thanks to @iamreal2 (XDA member) and @Ethan (Elephone forum member)
Special thanks to @darshan1205, @ricks and @Men_in_black007 who supported me in bad times
Special thanks to @manis99 for providing me YU5510A-LP VoLTE Firmware
Special thanks to @prasoon Mehra for providing me original Yureka AO5510 TP Config.
And finally thanks to me for making this fix.
Original TP Firmware Files for Different Devices
These are Original Stock Touch Panel Firmware/Configs for users who are suffering calibration issue not due to VoLTE firmware but due to other unknown causes.
YUREKA (AO5510) : https://www.androidfilehost.com/?fid=457095661767104421 (Thanks to @Prasoon Mehra)
YUREKA PLUS (YU5510) : https://www.androidfilehost.com/?fid=385035244224388338 (Thanks to @darshan1205)
Users of other YU Devices may share their working TP Firmware to help others....
Mirror Links
https://mega.nz/folder/Z4ckFbDA#bw4HnjUntLbiOLcdT-qpLQ (MEGA)
[Guide] How to Backup or Edit Touchscreen Firmware using GTP ADB Tool (For all devices with Goodix touchscreen)For users of all devices. Backing up the current TP-firmware is useful for saving the device from any future accident.
STEP 1: Download GTP-ADB-Tool Zip on your Windows PC and extract it. Go to the extracted folder and run the GtpAdbTool.exe application. Then connect your smartphone to your PC (be sure USB debugging is enabled in your device). You will see the Gtp Adb Tool window similar to the screenshot below:
STEP 2: Now click on the Menu item as indicated in the screenshot below:
STEP 3: Now you will see a window similar to the screenshot below. Click on the indicated button to read the current TP configuration from your connected device.
STEP 4: Hereafter you will see a window similar to the screenshot below. Take a screenshot of your current window and click on the button indicated to export your current config. Save the resultant config file to your preferred place. Thereafter, if required, you can also edit the firmware by playing with the Hex values.
STEP 5: Upload the Screenshot and your exported config file and save it in a safe place. That's it.
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
shailesh1985 said:
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
Click to expand...
Click to collapse
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
shailesh1985 said:
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
Click to expand...
Click to collapse
I am glad that it worked for you...
BTW you better use TWRP Recovery to flash newer ROMs. CWM Recovery is very old and is abandoned and deprecated.
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
dhrtlockeroo9 said:
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
Click to expand...
Click to collapse
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
nitesh9
nitesh9 said:
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
dhrtlockeroo9 said:
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
Click to expand...
Click to collapse
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
dhrtlockeroo9 said:
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
Click to expand...
Click to collapse
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
nitesh9
nitesh9 said:
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
nitesh9 said:
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
dhrtlockeroo9 said:
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
Click to expand...
Click to collapse
Tried using OTG mouse?[emoji15]
nitesh9 said:
Tried using OTG mouse?[emoji15]
Click to expand...
Click to collapse
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
dhrtlockeroo9 said:
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
Click to expand...
Click to collapse
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
nitesh9 said:
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
Click to expand...
Click to collapse
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
dhrtlockeroo9 said:
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
Click to expand...
Click to collapse
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
nitesh9 said:
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
Click to expand...
Click to collapse
No it's KitKat version.
dhrtlockeroo9 said:
No it's KitKat version.
Click to expand...
Click to collapse
Still you are getting bricked now and then?
What are you flashing actually?
Discussion on problems faced by Miflash tool.
*So when used for the first time I was able to unlock phone without any problem.
*But after that when I used it for second time to unbrick my phone I was constantly getting errors like not enough memory,some errors like x800000 blah blah...
*I almost went through every solutions mentioned in miui forum and XDA...But I was unable to get it working...
So if anyone faced any problem like that comment your problem below..
Aftef a lot of research I was able to find a solution for that..
Hopefully it will be shared with you all as soon as possible. I have to finish touching up some final things..
As soon as I finish the work I will be releasing alpha version..
Will update the thread when I release it
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Murshad007 said:
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Click to expand...
Click to collapse
Hopefully I was able to make alpha version of the software...worked fine for me on fastboot mode..want some testers
Edit..was able to boot up successfully..once confirmed by some testers I will release stable one
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
exce1ia said:
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
Click to expand...
Click to collapse
Yeah I faced it many time...not enough memory, buffer size0000 error blah blah blah...hopefully I was able to develop an app for to unbrick via fastboot... tried by me 2 times worked smooth but need some testers
Mi Flash & Nougat
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
cleo1986 said:
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
No fastboot
adithyan25 said:
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
Click to expand...
Click to collapse
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can recognize it as Qualcomm device.
cleo1986 said:
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can
recognize it as Qualcomm device.
Click to expand...
Click to collapse
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Already TRIED
adithyan25 said:
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Click to expand...
Click to collapse
I already tried many times to flash in EDL via miflash but I have error 0x000..., hello packet, etc etc
PLEASE LET ME KNOW WHEN YOU HAVE EDL Tool!
Thank you very much
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Rapalax said:
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/fix-bootloop-redmi-note-3-recovery-edl-t3521297
This will work for a complete clean flash via edl
Yep.. I managed to do something similar with a newer FB ROM and the modded twrp so there is less chance to relock my BL.
Thanks for providing the post.. it makes me feel more comfortable knowing that this info is available in case I need it again
After installing RR, restore the original firmware of Xiaomi Mi A1, the problem is that no longer stable wifi connection, find networks but do not connect, try everything and there is no way to connect to a Wi-Fi network.
There is someone who has happened to him this before.
speedunderx said:
After installing lineageOS 15, restore the original firmware of Xiaomi Mi A1, the problem is that no longer stable wifi connection, find networks but do not connect, try everything and there is no way to connect to a Wi-Fi network.
There is someone who has happened to him this before.
Click to expand...
Click to collapse
yeah me too
---------- Post added at 06:21 AM ---------- Previous post was at 06:17 AM ----------
what to do,,some body Help please,is that going to Mi Service Center Is the Last Option ?
DebGourav said:
yeah me too
---------- Post added at 06:21 AM ---------- Previous post was at 06:17 AM ----------
what to do,,some body Help please,is that going to Mi Service Center Is the Last Option ?
Click to expand...
Click to collapse
I imagine that soon they will solve it, since the same thing is happening to many of them, what you can do for now is to install RR once again, since Wi-Fi works there.
same issue facing..
speedunderx said:
I imagine that soon they will solve it, since the same thing is happening to many of them, what you can do for now is to install RR once again, since Wi-Fi works there.
Click to expand...
Click to collapse
bhuvneshkapoor01 said:
same issue facing..
Click to expand...
Click to collapse
i flashed RR and went back and wifi doesnt work says its desabled, regreat my actions need a fix for this tho
Don't know what kind of bug is this, i flashed 7.1.2 and almost 3-5 firmare, still no luck. went back to RR.
Nautilus99 said:
i flashed RR and went back and wifi doesnt work says its desabled, regreat my actions need a fix for this tho
Click to expand...
Click to collapse
bhuvneshkapoor01 said:
Don't know what kind of bug is this, i flashed 7.1.2 and almost 3-5 firmare, still no luck. went back to RR.
Click to expand...
Click to collapse
gess we are stuck untill oficial 8.1
Nautilus99 said:
gess we are stuck untill oficial 8.1
Click to expand...
Click to collapse
Someone has tried installing an older version of RR, since in the last compilations made changes in the registry of the MAC of Wifi and difinitivamente is that the problem.
Take the following test,
* Install the latest Oreo Stock Firmware
* Download Kernel Meta Phoenix
* TWRP Boot & Install Kernel Meta Phoenix
See if WIFI works
https://forum.xda-developers.com/mi-a1/development/kernel-meta-phoenix-r1-t3768080
speedunderx said:
Take the following test,
* Install the latest Oreo Stock Firmware
* Download Kernel Meta Phoenix
* TWRP Boot & Install Kernel Meta Phoenix
See if WIFI works
https://forum.xda-developers.com/mi-a1/development/kernel-meta-phoenix-r1-t3768080
Click to expand...
Click to collapse
I just tried it and it does not work, after installing the kernel it does not recognize the mac on the device
I tried with scooti stock rom , and it works. but for orignal stock rom it didn't work. thanks mate.
speedunderx said:
Take the following test,
* Install the latest Oreo Stock Firmware
* Download Kernel Meta Phoenix
* TWRP Boot & Install Kernel Meta Phoenix
See if WIFI works
https://forum.xda-developers.com/mi-a1/development/kernel-meta-phoenix-r1-t3768080
Click to expand...
Click to collapse
RR is full of bugs. i flashed it too and i have the same problem. Tried reflashing stock nogut, latest oreo both (with full wipe including internal storage). none solved the problem. please post it if u find a fix.
sachin273 said:
RR is full of bugs. i flashed it too and i have the same problem. Tried reflashing stock nogut, latest oreo both (with full wipe including internal storage). none solved the problem. please post it if u find a fix.
Click to expand...
Click to collapse
We are in the same, I probe everything and there is no way to start the Wi-Fi with stock, hopefully some solution comes out soon, for now I stay in RR since there works the wifi.
I fixed flashing persist.img again on fastboot.
gsnmartinh said:
I fixed flashing persist.img again on fastboot.
Click to expand...
Click to collapse
Please share the procedure, how to flash persist.img
Well, just find persist.img in the stock file like C:\Users\memo\Desktop\tissot_images_V9.5.9.0.ODHMIFA_8.0\images
then turn off your phone and enter into fastboot mode (down volume + power)
connect the phone to pc
the search for cmd
write : fastboot devices and if it shows number it means that is connect
then write: fastboot oem unlock (to unlock bootloader)
fastboot flash persist and grab the file and push it to the cmd
it should be end like this: C:\Users\memo>fastboot flash persist C:\Users\memo\Desktop\tissot_images_V9.5.9.0.ODHMIFA_8.0\images\persist.img
sorry if i haven't explain myself, i'm not a native english speaker.
GOOD LUCK
gsnmartinh said:
Well, just find persist.img in the stock file like C:\Users\memo\Desktop\tissot_images_V9.5.9.0.ODHMIFA_8.0\images
then turn off your phone and enter into fastboot mode (down volume + power)
connect the phone to pc
the search for cmd
write : fastboot devices and if it shows number it means that is connect
then write: fastboot oem unlock (to unlock bootloader)
fastboot flash persist and grab the file and push it to the cmd
it should be end like this: C:\Users\memo>fastboot flash persist C:\Users\memo\Desktop\tissot_images_V9.5.9.0.ODHMIFA_8.0\images\persist.img
sorry if i haven't explain myself, i'm not a native english speaker.
GOOD LUCK
Click to expand...
Click to collapse
I tried with MetaPhoenix Kernel, and its working fine for me, one thing of this is best in the market, almost everytime 1.6Gb ram free, and stability and features are great. Thanks mate for the guide.
I do not speak English, but thanks to this page I was able to solve the problem. It's a persist.img that worked for me: D
xiaomifirmware com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1
gsnmartinh said:
fastboot flash persist and grab the file and push it to the cmd
it should be end like this: C:\Users\memo>fastboot flash persist C:\Users\memo\Desktop\tissot_images_V9.5.9.0.ODHMIFA_8.0\images\persist.img
sorry if i haven't explain myself, i'm not a native english speaker.
GOOD LUCK
Click to expand...
Click to collapse
i am on stock nougat now so i tried flashing nougat persist image through cmd. but it says failed-this image doesnt allow download
does that method from the site work??
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
i need to know if i flash latest stock rom with the persist the sit is giving will it work? i miss the stock...
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Wifi works, but sim = 0
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Thank you soo very much. you are the best, I followed your instructions step by step and my phone wifi is working as charm. my phone is alive now. Thanks a ton again.
-Bimlesh
colegui said:
Wifi works, but sim = 0
Click to expand...
Click to collapse
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
I'm trying some methods but I have not luck yet.
colegui said:
I'm trying some methods but I have not luck yet.
Click to expand...
Click to collapse
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
dmbardal said:
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
Click to expand...
Click to collapse
I'm fixing imei downgrade to 7.8.23 and repair imei with rbsoft tool, but when I upgrade to oreo with OTA, imeo=0 again....
I'm trying again other method....https://forum.xda-developers.com/mi-a1/help/efs-partition-eraised-boot-t3753619
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
Here is solution: : How to restore IMEI permanently after using factory flash
I have the same problem with IMEI, the fix is permanent.
After the repair can be uploaded any rom, including Oreo .
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
coda00 said:
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
Click to expand...
Click to collapse
Sorry I cant posting outside links,
You can try EDL mode:
solution how boot EDL mode via ADB or fastboot: link>> 99mediasector.com/edl-mode-boot-edl-mode-xiaomi-devicesI think this will not work for youBut you can try EDL:via Deep Flash Cable (how quickly make Deep Flash Cable): link>> en.miui.com/thread-310325-1-1.htmlorvia disassembly Mi A1 (Guide to Flash Bricked Mi A1): link>> en.miui.com/thread-1680467-1-1.html
Excellent
Ecoda00
Click to expand...
Click to collapse
amazing bro Thanks, i work fine for me...
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Now that my wifi issue is solved, can I delete the persist.img from my device? Please advice.
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
amithiel said:
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
Click to expand...
Click to collapse
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Bimlesh1681 said:
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Click to expand...
Click to collapse
Sure, here you go: https://forum.xda-developers.com/mi-a1/how-to/tool-persist-resurrector-v1-0-0-0-t3781095
Edit: But you need to have you original persist file
Thank you so much, Bro. You saved my day. I am getting the similar problem. And ended up flashing multiple ROMs. but nothing worked out until I found your post.
i used this tool to solve wifi issue.
while using this tool make sure you enable USB debugging or it won't work.
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
infuerano said:
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
Click to expand...
Click to collapse
try flashing the latest void kernel.