NOTICE: This tutorial only works for Snapdragon 415 variant, and i am currently working on the SD616 variant. thanks for understanding.
hello ladies and gentlemen,
in this tutorial i'll show you how to install TWRP into Vibe K5 a41 variant, which is known for having an un-unlockable bootloader, and flashing using traditional ways like fastboot won't work.
But if you go low-level, you can ignore the bootloader.
To be honest, i found this tut long ago on the internet, so i thought it would be good to recreate it by updating it. Thanks for those who came with this awesome idea.
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features
included in the products you find here before flashing!
YOU are choosing to make these modifications, and
if you point your finger at me for messing up your device, I will
laugh at you. A lot.
Anyway,
STEP 1
First reboot your windows with driver signature enforcing disabled.
Ref.: [url]https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/[/URL]
You can also run (as admin ofc)
Code:
bcdedit.exe /set nointegritychecks ON
. However, i did not test it.
STEP 2
Then install the drivers and qfil.
https://mega.nz/#!1Dpy0JaK!D_D5JWnjUzi9rGRWCsnTHekgBd6MiEMv5Rrawl4PVvA
STEP 3
run
Code:
adb reboot edl
to reboot into download mode.
how to install adb: [url]https://www.xda-developers.com/install-adb-windows-macos-linux/[/URL]
Make sure your phone appers as a COM port in Device Manager (and QFIL)
STEP 4
Select as in screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Vibe K5: https://mega.nz/#!hXxiwazQ!kRSfPAMm28v8ZOnMepy6ir65Brqmyv9gC2Fx83siMi8
Vibe K5 plus: https://mega.nz/#!sbBUVC7C!FF9abiFe7MXD-VT3O8opwqs_NnKOVJedK6l72goFGYo
Download these accordingly to your SoC and extract anywhere you like.!!!THESE FILES ARE OBSOLETE. DOWNLOAD FROM THE BOTTOM OF THE POST!!!
I have tested this on my SD415 device. SD616 users may need the "k5 plus" file. Do at your own risk.
Also, i'm in no way responsible for anything you flash through recovery.
have fun!!!
UPDATE 21.03.18: i kinda changed the technic how this tutorial works. Now instead of flashing the files above i will give you stock roms with twrp built in for you to flash. just don't forget to boot into recovery so that stock rom does not overwrite the twrp.
phones with Snapdragon 616: https://mega.nz/#!H7RTUQbR!5P6ZP4F_rcuFR2DYuJ63M4z1U6hfqKpYx5PfTPtsSTkThese files appear not to work. Flash if you are okay with no cellular connection.
phones with Snapdragon 415: https://mega.nz/#!PmgGGI6I!9Gda2ZHNNG6lE_0dt4ag11Ng6Q1v_2DxgCGsFOHcga4
to find out what chipset you have, look at specs on your original box.
Some Notes:
+ to run qfil, go to Program files (x86) folder and find there qfil exe. Make sure to run as admin.
+ if you get sahara error, that's likely because of misconfigured drivers.
Sahara error
Thanks for the tutorial ... but i get the Sahara error, how can I solve this or the misconfigured drivers?
Regards!
ceanunez said:
Thanks for the tutorial ... but i get the Sahara error, how can I solve this or the misconfigured drivers?
Regards!
Click to expand...
Click to collapse
first, make sure you are running windows in test mode (driver signature disabled mode). Run cmd as admin, type "bcdedit /set testsigning on" without quotes.
After a reboot, connect your phone to pc in download mode and open Device Manager (run: devmgmt.msc). if your device shows up as "QUALCOMM HS-USB" or similar, then your drivers are fine.
Which way did you take to get into download mode?
PS: to get out of test mode, type "bcdedit /set testsigning off".
UPDATE: new download links
windows sees the phone as a qualcom device, everything is okay with the drivers but sahara fails, please help
Pandemicc said:
windows sees the phone as a qualcom device, everything is okay with the drivers but sahara fails, please help
Click to expand...
Click to collapse
what model number and what SoC do you have?
eurodiesel said:
what model number and what SoC do you have?
Click to expand...
Click to collapse
model: a6020a41
hw code: 49
i dont know what do you mean by soc, so i send the hw code. if you ask for completely another thing, tell me that how can i find it
Pandemicc said:
model: a6020a41
hw code: 49
i dont know what do you mean by soc, so i send the hw code. if you ask for completely another thing, tell me that how can i find it
Click to expand...
Click to collapse
SoC, or System on Chip, is what is called Snapdragon. in your case it is either Snapdragon 415 or 616. judging by your hw code, it must be SD616. plus, it must be written on your oem box.
try the link for vibe k5 plus, maybe that will solve sahara.
eurodiesel said:
SoC, or System on Chip, is what is called Snapdragon. in your case it is either Snapdragon 415 or 616. judging by your hw code, it must be SD616. plus, it must be written on your oem box.
try the link for vibe k5 plus, maybe that will solve sahara.
Click to expand...
Click to collapse
yes you are right, I have checked it and it is 616. please tell me that you can help me with that
Pandemicc said:
yes you are right, I have checked it and it is 616. please tell me that you can help me with that
Click to expand...
Click to collapse
follow tutorial step by step and use vibe k5 plus files
Hi,
i saw your answer in : https://forum.xda-developers.com/vi...p-a6020a41-t3745060/post75451263#post75451263
i have two questions.
1- i think drivers are true. because i can flash indian and device's factory stock rom with qfil. is it true?
2- i flahed custom roms after flashing twrp. but gsm network not exist too. is it possible extract modem.img of factory firmware? if i can extract it, i think i can flash it with fastboot.
thanks for your answers.
agritux said:
Hi,
i saw your answer in : https://forum.xda-developers.com/vi...p-a6020a41-t3745060/post75451263#post75451263
i have two questions.
1- i think drivers are true. because i can flash indian and device's factory stock rom with qfil. is it true?
2- i flahed custom roms after flashing twrp. but gsm network not exist too. is it possible extract modem.img of factory firmware? if i can extract it, i think i can flash it with fastboot.
thanks for your answers.
Click to expand...
Click to collapse
i have an idea: install lenovo moto smart assistant, select device rescue, enter your model name & hw code, and continue. it should be easy.
eurodiesel said:
i have an idea: install lenovo moto smart assistant, select device rescue, enter your model name & hw code, and continue. it should be easy.
Click to expand...
Click to collapse
i can return stock with qfil and factory image.
let me explain my issue again.
i can not install twrp on my device with factory image. with fastboot commands it says bootloader locked.
So i installed indian a40 rom. i can install twrp with fastboot command on indian rom. but on indian rom i do not have gsm network. so i need a41 modem.img i think.
i installed twrp on indian rom and installed custom roms but no signal again.
so i returned stock firmware with qfil. now everything is stock and i have gsm network signal. but no root no twrp no custom rom.
i want to install custom rom
agritux said:
i can return stock with qfil and factory image.
let me explain my issue again.
i can not install twrp on my device with factory image. with fastboot commands it says bootloader locked.
So i installed indian a40 rom. i can install twrp with fastboot command on indian rom. but on indian rom i do not have gsm network. so i need a41 modem.img i think.
i installed twrp on indian rom and installed custom roms but no signal again.
so i returned stock firmware with qfil. now everything is stock and i have gsm network signal. but no root no twrp no custom rom.
i want to install custom rom
Click to expand...
Click to collapse
thats ok. now follow the tutorial you're now on.
let me explain what i did:
since fastboot won't allow me to flash twrp, i did flash it forcefully via qfil.
if you've got sd415 chipset, then go for vibe k5 files.
if sd616 then vibe k5 plus files.
Download
---------- Post added at 04:21 PM ---------- Previous post was at 04:02 PM ----------
eurodiesel said:
first, make sure you are running windows in test mode (driver signature disabled mode). Run cmd as admin, type "bcdedit /set testsigning on" without quotes.
After a reboot, connect your phone to pc in download mode and open Device Manager (run: devmgmt.msc). if your device shows up as "QUALCOMM HS-USB" or similar, then your drivers are fine.
Which way did you take to get into download mode?
PS: to get out of test mode, type "bcdedit /set testsigning off".
Click to expand...
Click to collapse
I got the solution by this command: "bcdedit.exe /set nointegritychecks ON" ... I used the "adb reboot edl" command for download mode and now it works fine.
Thanks!
ceanunez said:
---------- Post added at 04:21 PM ---------- Previous post was at 04:02 PM ----------
I got the solution by this command: "bcdedit.exe /set nointegritychecks ON" ... I used the "adb reboot edl" command for download mode and now it works fine.
Thanks!
Click to expand...
Click to collapse
thank you very much. i'll add to tutorial sometime.
Edit: i've added it.
@agritux how's going? did you flash twrp?
eurodiesel said:
@agritux how's going? did you flash twrp?
Click to expand...
Click to collapse
i couldn't if i have twrp, i have no gsm signal
agritux said:
i couldn't if i have twrp, i have no gsm signal
Click to expand...
Click to collapse
did you follow the tutorial at the first post? did you flash using K5 Plus files?
because right now, i am using my a41 device with a locked bootloader running an Android Nougat based ROM, with all kinds of mods installed, and i am sure you can do it too.
PS: i live in Turkey too and i have no idea how all a41 users except me have a SD616. ? where did you buy your phone?
hi
I finally flashed successfully k5 plus files to my sd616 a41 device but the phone won't boot now, the device vibrates when I power it up but won't boot. can you help please?
Related
YU YUNIQUE YU4711 STOCK ROMDisclaimer: Flash this at your own RISK!! I AM NOT RESPONSIBLE FOR ANY TYPE OF BRICK
YU Yunique AOSP STOCK ROM Files so I am sharing with you all. I have personally Tested the Files on my Device and these files are completely working.
Now You Can Escape Soft Brick and Revert To stock anytime
Contents of the ZIP :
Drivers
Firmware
Flash Tool
REQUESTING YOU ALL TO READ THE FLASHING MANUAL THOROUGHLY AND PROCEED ACCORDINGLY
YOU WILL FIND A FLASHING MANUAL IN THE ZIP { DO NOT FOLLOW THAT IT IS NOT WORKING }
Procedure :
Download my working and tested Flashing Manual And Follow it LINK
Press The LIKE Button ,Which you all forget most of the times
Download Section :
LINK
Please Share your Feedback and Press THANKS if you are Thankful to ME
Unable to flash it...
Hey dude... i m using ur SEMI CYANOGEN Mod on my YU YUNIQUE... but now i wanna revert back to the STOCK ROM.. and i m unable to do it.. plz can u upload a video tutorial or post a more detailed method?
Thank YOU
What is semi cyanogen mod??? Can i install cm themes in it??
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
Huh
Suyashwon semi cyanogen means that it contains most of the features of cyanogen but is unofficial
My phone is softbricked and I am only able to open fastboot mode
Please help me..
I just forgot to enable usb debugging and my phone crashed while flashing official cyanogenmod 12.1 (jalebi). Now it shows a 2 second yu icon and gets switched off while pressing power button. On pressing power+vol up it gives me a fastboot screen.
Flashing twrp recovery through cmd gives me message "oem is locked" inputing unlocking instructions give me message "oem unlock not allowed"
I dont know what to do now, help me please. I think there myst be coding to unlock oem or bootloader, help me anyone.
please help
i'm having a problem when we turn off the phone and press volume up+down , npthing happens on ETS , no progress, and i dont get USB port 801 , i get USB101
please help
unlock bootloader.. plz help
ajay46 said:
I just forgot to enable usb debugging and my phone crashed while flashing official cyanogenmod 12.1 (jalebi). Now it shows a 2 second yu icon and gets switched off while pressing power button. On pressing power+vol up it gives me a fastboot screen.
Flashing twrp recovery through cmd gives me message "oem is locked" inputing unlocking instructions give me message "oem unlock not allowed"
I dont know what to do now, help me please. I think there myst be coding to unlock oem or bootloader, help me anyone.
Click to expand...
Click to collapse
i have the same problem... i called to the yu customer care... they told me.. they will charge rs-3339.. my phone is only rs-5000... plz help someone to fix it..
Alternative Method
Hello friend,
Thanks for the post.
But is there any alternative way by which i can flash the rom, because no matter what I do ETS does not show my device.
I have followed the procedure correctly. It shows in the usb in normal mode but when I go to download mode "VOL Up+VOL Dn>>USB Plugging", the screen goes blank and nothing on ETS.
Any suggestions ?
sahil bro pls apna phone number dedo .help chahidi c
Plz help me dude
This is my personal num. 7044959434 Plz help me
anuragdc said:
YU YUNIQUE YU4711 STOCK ROMDisclaimer: Flash this at your own RISK!! I AM NOT RESPONSIBLE FOR ANY TYPE OF BRICK
YU Yunique AOSP STOCK ROM Files so I am sharing with you all. I have personally Tested the Files on my Device and these files are completely working.
Now You Can Escape Soft Brick and Revert To stock anytime
Contents of the ZIP :
Drivers
Firmware
Flash Tool
REQUESTING YOU ALL TO READ THE FLASHING MANUAL THOROUGHLY AND PROCEED ACCORDINGLY
YOU WILL FIND A FLASHING MANUAL IN THE ZIP { DO NOT FOLLOW THAT IT IS NOT WORKING }
Procedure :
Download my working and tested Flashing Manual And Follow it LINK
Press The LIKE Button ,Which you all forget most of the times
Download Section :
LINK
Please Share your Feedback and Press THANKS if you are Thankful to ME
Click to expand...
Click to collapse
hello sir....
I have an YU YUNIQUE YU4711 and while trying to flash CM12.1 i soft-bricked my phone....
so i cant boot my phone and also cant open recovery.... and also my bootloader is locked and i cant unlock it since i turned off oem unlocking...
So can I use this process to recover my phone...
Sir please help me, I am stuck in the fastboot mode and I m not able to use my phone
SO sir plzzz help me
yogeshk972 said:
My phone is softbricked and I am only able to open fastboot mode
Please help me..
Click to expand...
Click to collapse
hey i just install drivers and flash using fastboot commands
input these in your cmd (open in the folder of rom using shift+leftclick)
pm me for help
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash
fastboot reboot-bootloader
fastboot flash system
fastboot flash userdata
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot
fastboot flash recovery
fastboot erase cache
fastboot flash cache
this will restore your devices to stock
thank me if i helped you
Hi everyone. I got my Yu yunique YU4711 bricked when I tried to relock the bootloader. What I did: First I reflashed stock recovery via fastboot, then typed the command "fastboot oem lock-go". It successed, but after reboot, the device is not loading neither recovery or system. Only fastboot mode is available.
How can I unlock my bootloader? The "fastboot oem unlock-go" does not help.
Thanks
anuragdc said:
YU YUNIQUE YU4711 STOCK ROMDisclaimer: Flash this at your own RISK!! I AM NOT RESPONSIBLE FOR ANY TYPE OF BRICK
YU Yunique AOSP STOCK ROM Files so I am sharing with you all. I have personally Tested the Files on my Device and these files are completely working.
Now You Can Escape Soft Brick and Revert To stock anytime
Contents of the ZIP :
Drivers
Firmware
Flash Tool
REQUESTING YOU ALL TO READ THE FLASHING MANUAL THOROUGHLY AND PROCEED ACCORDINGLY
YOU WILL FIND A FLASHING MANUAL IN THE ZIP { DO NOT FOLLOW THAT IT IS NOT WORKING }
Procedure :
Download my working and tested Flashing Manual And Follow it LINK
Press The LIKE Button ,Which you all forget most of the times
Download Section :
LINK
Please Share your Feedback and Press THANKS if you are Thankful to ME
Click to expand...
Click to collapse
I tried flashing my Yu Yunique. I am getting this error. Please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot says the lines are incomplete when typing these commands.
I got a problem with my yunique mobile its OS gone now am unable to understand what happened
Plzz help me friends
Anil nani said:
I got a problem with my yunique mobile its OS gone now am unable to understand what happened
Plzz help me friends
Click to expand...
Click to collapse
i got the same problem....i tried flashing using adb, didn't work. im clueless
installing stock using TWRP
hi
is there a way to install the factory rom back using fastboot or download mode
I had CM13, but got screwed up while updating... now it keeps booting itself to recovery all the time even if I use system.
I have tried the TWRP 3.0.0-2
and also the nightly cm12 recovery image
Basically I did a OTA update from existing cm13 nightly, when it did that it want into that mode where it shows the android being operated on.
usually it keeps that screen until the update is done and then reboots to the new system, however this time it shows the android for a flash, and then screen blanks
then it flashes again then it goes blank again, then after a while i just screen flashing lightly and the android does not come back.
I was having cm13 recovery, so I try to get into it by using power+v-down but it does the same thing, if I do power+vUp it goes to fastboot.
so I flashed twrp 3.0.0.2 now it does get into recovery, I can flash, format partitions, wipe factory reset (all tried) but every time I say "reboot to system" it boots itself back to twrp
if I flash the cm13 recovery it again does the andriod flash for a few times, and then screen flashing ... I have kept it in that mode overnight but nothing happens.
From what I understand, or guess there is some partition which has some setting to tell it to always go back to recovery... instead of system as the initial cm13 OTA did not complete cleanly
does any one know how to reset that setting.
It is something of the line of
http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
but for the YU4711
Any hints...
G
P:
How to enable debug mode in my case when I cant even boot to the OS. The instructions provided with the firmware are useless..
I can put the phone in download mode using Power+VUp+VDown
ajay46 said:
I just forgot to enable usb debugging and my phone crashed while flashing official cyanogenmod 12.1 (jalebi). Now it shows a 2 second yu icon and gets switched off while pressing power button. On pressing power+vol up it gives me a fastboot screen.
Flashing twrp recovery through cmd gives me message "oem is locked" inputing unlocking instructions give me message "oem unlock not allowed"
I dont know what to do now, help me please. I think there myst be coding to unlock oem or bootloader, help me anyone.
Click to expand...
Click to collapse
Sorry bro, but now nothing can be done.
Since you have not enabled oem unlocking, therefore you can not do nothing now. You have to give the phone to service centre and ask for replacement.
Tell them you dont know anything and play dumb.
Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too too.
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257
Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo
Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?
i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_edl-v2.zip from Here.
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3.
Proof:
Thanks to @emuzychenko for the Idea!
This is AWESOME!! Just tested and worked amazingly.
Thank you!
Edit: the included command prompt didn't work for me though, launched standard and traversed to this folder
It would've been better if the source of this guide is also mentioned, just my thoughts
Sent from my Redmi Note 3 using XDA-Developers mobile app
Harish_Kumar said:
It would've been better if the source of this guide is also mentioned
Click to expand...
Click to collapse
Especially since most of text had been copied "as is".
Please add this to op
=> https://youtu.be/-6uErg52nKs
kaushal64 said:
Please add this to op
=> https://youtu.be/-6uErg52nKs
Click to expand...
Click to collapse
I have updated the fastboot.exe and the method also. Update your video with this and I will add it to OP.
I had replaced link for modified fastboot file please add it to op.
Harish_Kumar said:
It would've been better if the source of this guide is also mentioned, just my thoughts
Click to expand...
Click to collapse
emuzychenko said:
Especially since most of text had been copied "as is".
Click to expand...
Click to collapse
Thumbs up!
This is great
My problem solved
Many thanks
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.
BRoy_98 said:
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.
Click to expand...
Click to collapse
Where to find it?
Zarko007 said:
Where to find it?
Click to expand...
Click to collapse
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.
BRoy_98 said:
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.
Click to expand...
Click to collapse
Maybe stupid question, but wouldn't phone go to edl mode (with red led flashing) before flashing rom and what then mbn file has to do? According to your manual it is the last step?
thanks
Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk
sator02 said:
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk
Click to expand...
Click to collapse
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
Don't use this tool if your device is not bricked, your rom is a distributor rom that's why you cannot unlock your device, you have to flash miui rom prior to unlocking, you can do it thru edl mode using adb, search on miui forums and you'll find it.
Edit: check this out: http://en.miui.com/thread-235865-1-1.html
Sent from my kenzo using Tapatalk
Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.
BRoy_98 said:
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.
Click to expand...
Click to collapse
I have tried it already many Times but no success...
Zarko007 said:
I have tried it already many Times but no success...
Click to expand...
Click to collapse
This must be driver problem. Install MI PC suite and it will install all necessary drivers. Then try it again.
This is an initial work in progress which may or may not work for you. This worked for me and it may cause brick on other devices if tried. So don't try this unless you are ready to take the risk. And whatever happens i won't take the blame.
What is it?
When you unlock your device, mi unlock tool writes the unlock code in the devinfo partition. This is a partition dump of my device in its officially unlocked state. If you still wish to follow this guide, then continue or else look somewhere else. Again this is only tested on my device and may or may not work for you.
Download: Here
Extract the files.
Run your phone in edl mode
Open device manager or miflash and note your port number.
example: com10 or com4
run the unlock.bat file.
it will ask port number, enter the port number.
example: com10 or com4.
and press enter.
If your phone is in edl mode and has a proper port alloted with qualcomm hs-usb qdloader 9008(%port no%)
everything should work fine.
Will upload a few screen shots later.
rev
ttt
Not working .
Archit9169 said:
This is an initial work in progress which may or may not work for you. This worked for me and it may cause brick on other devices if tried. So don't try this unless you are ready to take the risk. And whatever happens i won't take the blame.
What is it?
When you unlock your device, mi unlock tool writes the unlock code in the devinfo partition. This is a partition dump of my device in its officially unlocked state. If you still wish to follow this guide, then continue or else look somewhere else. Again this is only tested on my device and may or may not work for you.
Download: Here
Extract the files.
Run your phone in edl mode
Open device manager or miflash and note your port number.
example: com10 or com4
run the unlock.bat file.
it will ask port number, enter the port number.
example: com10 or com4.
and press enter.
If your phone is in edl mode and has a proper port alloted with qualcomm hs-usb qdloader 9008(%port no%)
everything should work fine.
Will upload a few screen shots later.
Click to expand...
Click to collapse
tried twice but was unable to unlock
milankumarn said:
tried twice but was unable to unlock
Click to expand...
Click to collapse
Describe me the whole procedure.
Did the files flashed successfully.
Were there any problems aside from not unlock.
What was written in the cmd window.
A screen shot of the cmd windows after the process is done.
What port no did you input in it.
Archit9169 said:
Describe me the whole procedure.
Did the files flashed successfully.
Were there any problems aside from not unlock.
What was written in the cmd window.
A screen shot of the cmd windows after the process is done.
What port no did you input in it.
Click to expand...
Click to collapse
1.booted into fastboot mode then EDL mode
2.ran the bat file.
3. rebooted
here are the screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
milankumarn said:
1.booted into fastboot mode then EDL mode
2.ran the bat file.
3. rebooted
here are the screenshots
View attachment 3988863
View attachment 3988864
View attachment 3988865
Click to expand...
Click to collapse
Is your phone fine...no bootloops or anything wrong.
Maybe it is tied with the device. I have to read and edit it.
Wait for a few days and ill try to mod it to be universal.
For info it works fine in mine. I used it to unlock and the device was working fine.
Archit9169 said:
Is your phone fine...no bootloops or anything wrong.
Maybe it is tied with the device. I have to read and edit it.
Wait for a few days and ill try to mod it to be universal.
For info it works fine in mine. I used it to unlock and the device was working fine.
Click to expand...
Click to collapse
No there is no bootloop and i did not notice any problem after doing it.
and that might be the problem .. please let me know when you mod it to be used universal.
just tried it. said that it was successful but then on resets it bootloops (tries to boot twice) then black. When i check device info it says false.
edit: recovery also doesnt work anymore. I had flashed zcx twrp.
neoblast said:
just tried it. said that it was successful but then on resets it bootloops (tries to boot twice) then black. When i check device info it says false.
edit: recovery also doesnt work anymore. I had flashed zcx twrp.
Click to expand...
Click to collapse
Sorry to hear that. Just use edl mode to flash the rom again. Or wait for a few hours and ill make an undo script.
Can you help me with my problem?
I sent a request to unlock my bootloader.They accepted it, but if i try to unlock it through miflashunlock program,at 50% it says "Couldn't verify device" and under this error it says "No need to unlock this device".
I saw people got errors that they don't have the same mi account logged in the program and on the phone, but i have a different error...
I have Redmi Note 3 Pro
Android version : 5.1.1 LMY47V
MIUI Version : MIUI Global 7.4 Stable
7.4.9.0(LHOCNDD)
Scrapperr said:
Can you help me with my problem?
I sent a request to unlock my bootloader.They accepted it, but if i try to unlock it through miflashunlock program,at 50% it says "Couldn't verify device" and under this error it says "No need to unlock this device".
I saw people got errors that they don't have the same mi account logged in the program and on the phone, but i have a different error...
I have Redmi Note 3 Pro
Android version : 5.1.1 LMY47V
MIUI Version : MIUI Global 7.4 Stable
7.4.9.0(LHOCNDD)
Click to expand...
Click to collapse
I have the same thing appeared when i tried to unlock mokee bl as it can be unlocked without a token from fastboot command.
Just unlock it from fastboot command that is
Code:
fastboot oem unlock-go
---------- Post added at 08:37 AM ---------- Previous post was at 08:32 AM ----------
Archit9169 said:
Sorry to hear that. Just use edl mode to flash the rom again. Or wait for a few hours and ill make an undo script.
Click to expand...
Click to collapse
I think they have to unlock from fastboot after flashing devinfo partition
Camlin3 said:
I have the same thing appeared when i tried to unlock mokee bl as it can be unlocked without a token from fastboot command.
Just unlock it from fastboot command that is
Code:
fastboot oem unlock-go
---------- Post added at 08:37 AM ---------- Previous post was at 08:32 AM ----------
I think they have to unlock from fastboot after flashing devinfo partition
Click to expand...
Click to collapse
No. It was my partition dump and i unlocked officially.
I dont know why people say they have trouble unlocking.
My only trouble was that i had to wait a while to get the unlock permission.
And my other problem that without using miunlock i cant unlock it again.
I mean everytime i have to unlock i have to login to that damn program.
Scrapperr said:
Can you help me with my problem?
I sent a request to unlock my bootloader.They accepted it, but if i try to unlock it through miflashunlock program,at 50% it says "Couldn't verify device" and under this error it says "No need to unlock this device".
I saw people got errors that they don't have the same mi account logged in the program and on the phone, but i have a different error...
I have Redmi Note 3 Pro
Android version : 5.1.1 LMY47V
MIUI Version : MIUI Global 7.4 Stable
7.4.9.0(LHOCNDD)
Click to expand...
Click to collapse
Download miui 8.11.3 and flash it using edl.
After that boot into fastboot and unlock your bootloader.
Do not wait for the first boot.
neoblast said:
just tried it. said that it was successful but then on resets it bootloops (tries to boot twice) then black. When i check device info it says false.
edit: recovery also doesnt work anymore. I had flashed zcx twrp.
Click to expand...
Click to collapse
Try flashing miui 8.11.3 and then use my program. Maybe it is vecause of different bootloader.
Archit9169 said:
Download miui 8.11.3 and flash it using edl.
After that boot into fastboot and unlock your bootloader.
Do not wait for the first boot.
Click to expand...
Click to collapse
U mean, 6.11.3 .i know that is your dev- info partition but is there any one who give a try to unlock from fastboot after flashing ur partition
Edit:- i too want to dump my dev-info in img .is it just dd command will do the stuff.(i too find it hazy to use that **** of crap
Camlin3 said:
U mean, 6.11.3 .i know that is your dev- info partition but is there any one who give a try to unlock from fastboot after flashing ur partition
Edit:- i too want to dump my dev-info in img .is it just dd command will do the stuff.(i too find it hazy to use that **** of crap
Click to expand...
Click to collapse
Yes just flash 6.11.3 using edl. Then use miunlock tool to unlock. It will work without any problem.
Some who tried to flash my partition either had no changes, bootloader remained locked or either had bootloops in which they had to flash using edl again.
Yes that will work.
Archit9169 said:
Yes just flash 6.11.3 using edl. Then use miunlock tool to unlock. It will work without any problem.
Some who tried to flash my partition either had no changes, bootloader remained locked or either had bootloops in which they had to flash using edl again.
Yes that will work.
Click to expand...
Click to collapse
Mine is already unlocked officially in july, only suggesting for struggling folks.
Yeah dd went well
thanks for sharing it
Archit9169 said:
Download miui 8.11.3 and flash it using edl.
After that boot into fastboot and unlock your bootloader.
Do not wait for the first boot.
Click to expand...
Click to collapse
Why 6.11.3 and not another version? I can't find a link to download,they keep sending me to this site http://en.miui.com/download-301.html#439 but the oldest firmware i can find is 6.11.24
I bought the Mi A1 some weeks ago and it was working just fine. I flashed twrp, rooted and was happy with it until I found out that I could no longer install OTAs so I decided to flash the fastboot ROM, downloaded the lastest one from www.xiaomifirmware.com, attemted to flash it but couldn't. The MiFlashTool for some reason simply didn't have a flash option in it which it was supposed to have so uninstalled the flash tool and tried installing older versions of it but still no signs of the flash option, this got me frustrated and I was searching for other ways to flash the fastboot rom, I did found some and tried putting the rom in the minimal adb and fastboot tool, it did flash it but the slot a or b, i don't remember, was stuck on recovery mode, mean while i could boot from the another slot normally, I agan istalled twrp on the working slot(Idk why) and
the wifi was broken. I simply couldn't turn it on(the wifi). So I was back to flashing the fastboot rom and in the process I figured a way to find the flash option that was missing using the tab key on the keyboard but the flash itself didn't go very well, i got a modem_a error so I was back to other ways of flashing it and in the process the phone turned off and a Qualcomm driver began to install, it got installed and I was extremely happy that I could flash the rom with the MiFlashTool but after the flash completed and I got the sucess message, the phone got stuck on the bootlogo and rebooted normally in the next automatic reboot, I was greeted with the basic setup and I was happy but after 30-60 sec it got hung and the device started to repeat this process. I tried flash the older versions of the rom but still no luck. Can some one help me with this issue???
*************************************************************************
Video shocasicg the issue: https://www.youtube.com/watch?v=3YcWsWYQVGQ
This issue has been fixed, Try following these steps:
1) Unlock the bootloader.
2) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
3) Download and Install minimal adb and fastboot , persist.img from august build link will be below.
4) Copy the persist.img to the where the minimal adb fastboot tool is located.
5) Goto the minimal adb fastboot tool folder where you had put the persist.img.
6) Open cmdhere.exe
7) Put your phone in fastboot mode (Volume - and Power)
8) Type the following commands:
- fastboot devices (you should something like this:
Fastboot dsad5454sfs, If not, re-install the the fastboot drivers correctly. )
- fastboot erase persist.img
- fastboot flash persist persist.img
Voila! Done but please note that you can just do it once and not repeatedly.
Adb and fastboot tool: https://forum.xda-developers.com/sho....php?t=2317790
i have the same issue look at the video
https://www.youtube.com/watch?v=3YcWsWYQVGQ
I don't know the specifics but you're going to have to go for a very basic low-level wipe and re-flash of the stock ROM from Xiaomi. Be *very* careful to get the correct ROM files and flashing tools. I'd head to the official Xiaomi EN (english) forums or ask here on XDA. I think the reason you haven't had more replies is because your post was a difficult to read wall of text.
If you're currently booting up but then it's rebooting on it's own - that's actually a good sign that you hopefully should be able to restore it to stock firmware and then go from there. Beyond that I can't help you but I'm sure someone else here can. Good luck! And if you figure it out make sure to come back and let us know how you fixed it in case anyone else has similar problems.
Just take it to service center they will do it.
info:
If you can flash anything using fastboot then do fastboot flash partition gpt_both0.bin and you'll enter edl mode and should be able to flash the FASTBOOT ROM through the mi flash tool if you have installed the drivers properly.
alsheron said:
I don't know the specifics but you're going to have to go for a very basic low-level wipe and re-flash of the stock ROM from Xiaomi. Be *very* careful to get the correct ROM files and flashing tools. I'd head to the official Xiaomi EN (english) forums or ask here on XDA. I think the reason you haven't had more replies is because your post was a difficult to read wall of text.
If you're currently booting up but then it's rebooting on it's own - that's actually a good sign that you hopefully should be able to restore it to stock firmware and then go from there. Beyond that I can't help you but I'm sure someone else here can. Good luck! And if you figure it out make sure to come back and let us know how you fixed it in case anyone else has similar problems.
Click to expand...
Click to collapse
So I did got it fixed and to a working state but my dissatisfaction led me to some more trouble and it's currently hard bricked or need to be flashed using a deep flash cable to be presice. Basically it's on its way to the service centre.
So how I fixed the issue?
1) Unlock the bootloader.
2) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
3) Download and Install minimal adb and fastboot , official fastboot rom.
4) Extract the fastboot rom and copy the persist.img located in the Images folder of the fastboot ROM to the where the minimal adb fastboot tool is located.
5) Goto the minimal adb fastboot tool folder where you had put the persist.img.
6) Open cmdhere.exe
7) Put your phone in fastboot mode (Volume - and Power)
8) Type the following commands:
- fastboot devices (You should see something If not re-install the the fastboot drivers correctly. )
- fastboot erase persist.img
- fastboot flash persist persist.img
Voila! Done but please note that you cant just do it once and not repeatedly.
Links:
Adb and fastboot tool: https://forum.xda-developers.com/showthread.php?t=2317790
fastboot rom: http://bigota.d.miui.com/7.11.18/tissot_images_7.11.18_20171117.0000.00_7.1_3ac9b1f856.tgz
headshotde said:
i have the same issue look at the video
https://www.youtube.com/watch?v=3YcWsWYQVGQ
Click to expand...
Click to collapse
Look up ^^^^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
khkalam said:
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
Click to expand...
Click to collapse
The same hapend to me... Please how can i fix it!
khkalam said:
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
Click to expand...
Click to collapse
Why tiffany? Mi A1's code name is tissot, Mi 5x's codename is tiffany.
I have both device, Mi 5x and Mi A1
NicoNewbie said:
Why tiffany? Mi A1's code name is tissot, Mi 5x's codename is tiffany.
Click to expand...
Click to collapse
I have Mi 5x and Mi A1. Tried this method and fail to flash. Also I am using A1 ported rom on my Mi 5x.
Thanks
khkalam said:
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
Click to expand...
Click to collapse
Why don't you just use the batch file already provided in the stock image folder? Install adb fastboot system wide drivers. Connect your phone to pc in fastboot mode. And just run the batch file in tissot_images folder (I prefer flash_all_except_storage.bat)
Please just have a look at this thread: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
It includes a guide and already a lot of answered questions.
solution
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
here's how to flash persist
N.B YOU NEED TO DOWNLOAD THE FILE FROM THE GUIDE (32 mb Iin size)
Edwin Hamal said:
I bought the Mi A1 some weeks ago and it was working just fine. I flashed twrp, rooted and was happy with it until I found out that I could no longer install OTAs so I decided to flash the fastboot ROM, downloaded the lastest one from www.xiaomifirmware.com, attemted to flash it but couldn't. The MiFlashTool for some reason simply didn't have a flash option in it which it was supposed to have so uninstalled the flash tool and tried installing older versions of it but still no signs of the flash option, this got me frustrated and I was searching for other ways to flash the fastboot rom, I did found some and tried putting the rom in the minimal adb and fastboot tool, it did flash it but the slot a or b, i don't remember, was stuck on recovery mode, mean while i could boot from the another slot normally, I agan istalled twrp on the working slot(Idk why) and
the wifi was broken. I simply couldn't turn it on(the wifi). So I was back to flashing the fastboot rom and in the process I figured a way to find the flash option that was missing using the tab key on the keyboard but the flash itself didn't go very well, i got a modem_a error so I was back to other ways of flashing it and in the process the phone turned off and a Qualcomm driver began to install, it got installed and I was extremely happy that I could flash the rom with the MiFlashTool but after the flash completed and I got the sucess message, the phone got stuck on the bootlogo and rebooted normally in the next automatic reboot, I was greeted with the basic setup and I was happy but after 30-60 sec it got hung and the device started to repeat this process. I tried flash the older versions of the rom but still no luck. Can some one help me with this issue???
*************************************************************************
Video shocasicg the issue: https://www.youtube.com/watch?v=3YcWsWYQVGQ
This issue has been fixed, Try following these steps:
1) Unlock the bootloader.
2) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
3) Download and Install minimal adb and fastboot , persist.img from august build link will be below.
4) Copy the persist.img to the where the minimal adb fastboot tool is located.
5) Goto the minimal adb fastboot tool folder where you had put the persist.img.
6) Open cmdhere.exe
7) Put your phone in fastboot mode (Volume - and Power)
8) Type the following commands:
- fastboot devices (you should something like this:
Fastboot dsad5454sfs, If not, re-install the the fastboot drivers correctly. )
- fastboot erase persist.img
- fastboot flash persist persist.img
Voila! Done but please note that you can just do it once and not repeatedly.
Adb and fastboot tool: https://forum.xda-developers.com/sho....php?t=2317790
Click to expand...
Click to collapse
hey mate i'm getting "image not allowed to download" error
how to fix this ?
neither do i see Fastboot dsad5454sfs
i see my device's no like 193a22 in CMD
can you help ?
i have 7.12.7 build can i still flash the persist that u have shared or do i need to extract it from 7.12.7 build?
anybody manage to solve the problem stuck at Android One logo ?
For MI5x with ported A1 rom