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
Related
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.
After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"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"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?
ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said
I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet
Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot
uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something
After flashing i get Mi logo, vibration and reboot, please help
Guys is that a way to root redmi 3s without unlocking bootloader?
Edit: Practically it's not possible....Unlock bootloader first then install twrp now root in just 7 days.
Note: Don't use any tricks available in forums and it won't work, just wait minimum 6days after U get permission because ur profile will get update to mi server slowly and it takes time then after 6th day use miunlock otherwise U will get 50% error.
Requirements: switch on OEM unlock and debug option that's all and login in to the same mi account which U got permission.
Please refer: http://en.miui.com/thread-298586-1-1.html
I guess so.. It can be done with MiFlash Tool (EDL)
SILF0X said:
I guess so.. It can be done with MiFlash Tool (EDL)
Click to expand...
Click to collapse
tried but failed so i think we need unlocked bootloader...
First thing first..
1. Download and install latest MiFlashTool
2. Reboot into EDL mode
3. Flash this like you flash fastboot rom using MiFlashTool
TWRP FLASHER
If you're done, please let me know..
Note: only for redmi 3s/Prime/3x
SILF0X said:
First thing first..
1. Download and install latest MiFlashTool
2. Reboot into EDL mode
3. Flash this like you flash fastboot rom using MiFlashTool
TWRP FLASHER
If you're done, please let me know..
Note: only for redmi 3s/Prime/3x
Click to expand...
Click to collapse
But it needs unlocked bootloader right? Did u tried it
drganbds said:
But it needs unlocked bootloader right? Did u tried it
Click to expand...
Click to collapse
I made this tool, of course i tried it.
Just flash this package, you'll get TWRP installed. Even if you're on locked bootloader. After that, you can flash SuperSU.
Just try it..
SILF0X said:
I made this tool, of course i tried it.
Just flash this package, you'll get TWRP installed. Even if you're on locked bootloader. After that, you can flash SuperSU.
Just try it..
Click to expand...
Click to collapse
Flash through updater app? Why can't u make this as public and as for as I search a lot in Google forums they told without unlock u can't root our device and im using 3s+ variant.
drganbds said:
Flash through updater app? Why can't u make this as public and as for as I search a lot in Google forums they told without unlock u can't root our device and im using 3s+ variant.
Click to expand...
Click to collapse
Flash it using the latest MiFlashTool.
I found it yesterday, doesn't have much time to publish it.
Redmi 3s+ ? Maybe its Redmi 3x?
SILF0X said:
Flash it using the latest MiFlashTool.
I found it yesterday, doesn't have much time to publish it.
Redmi 3s+ ? Maybe its Redmi 3x?
Click to expand...
Click to collapse
In MI flash tool latest tried but it does nothing and didn't flash anything. Do I need to put in fastboot mode manually?
drganbds said:
In MI flash tool latest tried but it does nothing and didn't flash anything. Do I need to put in fastboot mode manually?
Click to expand...
Click to collapse
You have to enter EDL mode.
adb reboot edl
SILF0X said:
You have to enter EDL mode.
adb reboot edl
Click to expand...
Click to collapse
Edl means downloader mode right? then in mi flash i have to select the entire .zip file or the recovery.img alone?
drganbds said:
Edl means downloader mode right? then in mi flash i have to select the entire .zip file or the recovery.img alone?
Click to expand...
Click to collapse
How To Boot Into EDL Mode :
1. Turn off your phone completely.
2. Press Volume Up (+) and Power buttons simultaneously. This will bring your phone into Recovery Mode.
3. You will see several options in Recovery menu. Choose “Downloadâ€
4. Your phone should reboot into Download mode / EDL.
5. Finally you can connect it to PC using its USB cable.
{
"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"
}
Download : MiFlash (Beta)
a. Extract TWRP_FLASHER_HM3SX.zip into D:\TWRP_FLASHER_HM3SX
b. Run MiFlash and select folder D:\TWRP_FLASHER_HM3SX that contains flash_all.bat
c. Select "clean all"
d. Select "Refresh"
e. Select "Flash"
SILF0X said:
How To Boot Into EDL Mode :
1. Turn off your phone completely.
2. Press Volume Up (+) and Power buttons simultaneously. This will bring your phone into Recovery Mode.
3. You will see several options in Recovery menu. Choose “Downloadâ€
4. Your phone should reboot into Download mode / EDL.
5. Finally you can connect it to PC using its USB cable.
Download : MiFlash (Beta)
a. Extract TWRP_FLASHER_HM3SX.zip into D:\TWRP_FLASHER_HM3SX
b. Run MiFlash and select folder D:\TWRP_FLASHER_HM3SX that contains flash_all.bat
c. Select "clean all"
d. Select "Refresh"
e. Select "Flash"
Click to expand...
Click to collapse
Did as u told and it didn't flash twrp rather It showed success. Have u unlocked your bootloader?
Device can't go to EDL mode and it says device locked
Regarding to ur root with out unlocking bootloader
Dont get me Wrong guys
I already tried this method a long time ago..where my device is locked
Here's What i did.... before i have locked bootloader..i downloaded fastboot images put the device in edl mode and change the recovery file img to twrp img and rename it to recovery.img..And flash the All os files.. flashed successfully but still it shows stock recovery
that's why i'm wondering about that .
.And i changed the boot file to twrp image and rename it to boot .. it flashed the files succesfull But it stuck on mi logogo and lead me to qualocom diagonostic mode 900E Because of partioning mismatch [i guess ]
luckily i'm having fastboot because the flasher first flashes the bootloader and mbn files
i initiate
Code:
fastboot oem edl
command then i'm in edl mode and flashed the device to previous state ..After that i stopped the work it's a new phone guys [1 week ] i got feared
So my query is how it still can't boot into twrp recovery mode if it's flashed successfull in edl mode [ i checked the log file ]
I guess because of encryption process of system partition after flashing ..so again what i did is after flashing the fles immediatly i boot on to recovery still the device automatically loops .. and start encryption
Now i Need Some one who's bootloader is locked to continue my work/test
Here's My Contact info 7396884287. Named Tyson... Give Me a Missed Call
drganbds said:
Did as u told and it didn't flash twrp rather It showed success. Have u unlocked your bootloader?
Click to expand...
Click to collapse
yes, i unlock my bootloader. Sorry, my bad..
---------- Post added at 09:03 AM ---------- Previous post was at 08:55 AM ----------
Tyson12 said:
Dont get me Wrong guys
I already tried this method a long time ago..where my device is locked
Here's What i did.... before i have locked bootloader..i downloaded fastboot images put the device in edl mode and change the recovery file img to twrp img and rename it to recovery.img..And flash the All os files.. flashed successfully but still it shows stock recovery
that's why i'm wondering about that .
.And i changed the boot file to twrp image and rename it to boot .. it flashed the files succesfull But it stuck on mi logogo and lead me to qualocom diagonostic mode 900E Because of partioning mismatch [i guess ]
luckily i'm having fastboot because the flasher first flashes the bootloader and mbn files
i initiate
Code:
fastboot oem edl
command then i'm in edl mode and flashed the device to previous state ..After that i stopped the work it's a new phone guys [1 week ] i got feared
So my query is how it still can't boot into twrp recovery mode if it's flashed successfull in edl mode [ i checked the log file ]
I guess because of encryption process of system partition after flashing ..so again what i did is after flashing the fles immediatly i boot on to recovery still the device automatically loops .. and start encryption
Now i Need Some one who's bootloader is locked to continue my work/test
Here's My Contact info 7396884287. Named Tyson... Give Me a Missed Call
Click to expand...
Click to collapse
I try to flash twrp and mirecovery using that package, and it works. I'm on unlocked bootloader now
SILF0X said:
yes, i unlock my bootloader. Sorry, my bad..
---------- Post added at 09:03 AM ---------- Previous post was at 08:55 AM ----------
I try to flash twrp and mirecovery using that package, and it works. I'm on unlocked bootloader now
Click to expand...
Click to collapse
R u saying that you flash twrp & succeed to have twrp while your bootloader was locked.
Sent from my Redmi 3S using XDA-Developers Legacy app
Tyson12 said:
R u saying that you flash twrp & succeed to have twrp while your bootloader was locked.
Sent from my Redmi 3S using XDA-Developers Legacy app
Click to expand...
Click to collapse
I meant that succeed to have twrp while the bootloader was unlocked.
Tyson12 said:
Here's What i did.... before i have locked bootloader..i downloaded fastboot images put the device in edl mode and change the recovery file img to twrp img and rename it to recovery.img..And flash the All os files.. flashed successfully but still it shows stock recovery
Click to expand...
Click to collapse
You said that you flash twrp.img in edl mode, flashed successfully, but still it shows stock recovery.
i flash twrp.img in edl mode too. Flash successfully, and it shows TWRP.
R u already download my package?
SILF0X said:
I meant that succeed to have twrp while the bootloader was unlocked.
You said that you flash twrp.img in edl mode, flashed successfully, but still it shows stock recovery.
i flash twrp.img in edl mode too. Flash successfully, and it shows TWRP.
R u already download my package?
Click to expand...
Click to collapse
U r package is working for unlocked bootloader..
But in my case my bootloader is locked..
So...
Sent from my Redmi 3S using XDA-Developers Legacy app
Guys I'm stuck at 50% always( couldn't verify device) in MI flash tool please help on unlock.
How u guys had unlock without errors?
I am experiencing some serious issues with wifi
Signal drops and connection fails while other gadgets in the same range of the router have stable wifi connection
I never had a such a problem with my previous Xiaomi phone
This one seems has got some serious connectivity problems
I even did a reset after oreo update but it's still the same
To have a stable wifi connection I have to keep so close(like in the same room or next room) to router which is definitely not a solution
I really regret buying this phone
I have the same problem... I need to use my mobile data!
I have the same issue with a dual band (2.4 and 5GHz) modem both using same SSID. Seems as my A1 locked onto the 5GHz frequency and then when I move away refuses to change to 2.4GHz. "Switching off" the 5GHz solved the problem.
Am still looking for other solutions.
I thought the issue was just on my handset but seems it was not. I've been facing this issue since god knows how long. Thanks for the confirmation.
I had the same problem (Wi-Fi connected, No internet) on Mi A1 and checked almost everything. I tried different firmwares, I've even erased EFS and rewrote QCN calibrations, but no luck. But once I've downgraded this phone to Android 7 (fw ver 7.8.23), my bootloader was already unlocked (you can do it by simple command (fastboot oem unlock) in cmdline). I took persist partition (persist.img) from folder with unpacked 7.8.23 firmware and flashed it manually via edl ("fastboot oem edl" command for reboot to edl mode, and then flash persist.img separately) and IT HELPS!! Wifi now connects ok. Maybe problem appears because of persist partition isn't included in firmware configuration file by default. I've checked this method on 7.8.23, then updated via ota to 8.1.10 firmware, and after to 9.5.4.0, works like a charm!
I've created files for miflash for WiFi fixind almost on all firmwares. It is in attachment below. It will not erase your data. It must be flashed only in EDL mode, because fastboot mode doesn't allow to flash persist
AlexAiS said:
I had the same problem (Wi-Fi connected, No internet) on Mi A1 and checked almost everything. I tried different firmwares, I've even erased EFS and rewrote QCN calibrations, but no luck. But once I've downgraded this phone to Android 7 (fw ver 7.8.23), my bootloader was already unlocked (you can do it by simple command (fastboot oem unlock) in cmdline). I took persist partition (persist.img) from folder with unpacked 7.8.23 firmware and flashed it manually via edl ("fastboot oem edl" command for reboot to edl mode, and then flash persist.img separately) and IT HELPS!! Wifi now connects ok. Maybe problem appears because of persist partition isn't included in firmware configuration file by default. I've checked this method on 7.8.23, then updated via ota to 8.1.10 firmware, and after to 9.5.4.0, works like a charm!
I've created files for miflash for WiFi fixind almost on all firmwares. It is in attachment below. It will not erase your data. It must be flashed only in EDL mode, because fastboot mode doesn't allow to flash persist
Click to expand...
Click to collapse
Does this work on March 2018 patch?
And do I need to do this after every ota or is just one time?
Thanks!
AlexAiS said:
I had the same problem (Wi-Fi connected, No internet) on Mi A1 and checked almost everything. I tried different firmwares, I've even erased EFS and rewrote QCN calibrations, but no luck. But once I've downgraded this phone to Android 7 (fw ver 7.8.23), my bootloader was already unlocked (you can do it by simple command (fastboot oem unlock) in cmdline). I took persist partition (persist.img) from folder with unpacked 7.8.23 firmware and flashed it manually via edl ("fastboot oem edl" command for reboot to edl mode, and then flash persist.img separately) and IT HELPS!! Wifi now connects ok. Maybe problem appears because of persist partition isn't included in firmware configuration file by default. I've checked this method on 7.8.23, then updated via ota to 8.1.10 firmware, and after to 9.5.4.0, works like a charm!
I've created files for miflash for WiFi fixind almost on all firmwares. It is in attachment below. It will not erase your data. It must be flashed only in EDL mode, because fastboot mode doesn't allow to flash persist
Click to expand...
Click to collapse
Thanks for this and I have a question: Can I flash this if I'm on Oreo or should I downgrade to Nougat like you did?
berezker said:
Does this work on March 2018 patch?
Click to expand...
Click to collapse
Didn't test on march 2018 but should work
berezker said:
And do I need to do this after every ota or is just one time?
Click to expand...
Click to collapse
just one time, if you have described problem
Edwin Hamal said:
Thanks for this and I have a question: Can I flash this if I'm on Oreo or should I downgrade to Nougat like you did?
Click to expand...
Click to collapse
Downgrade isn't mandatory. Can be flashed from any fw without data lost. The easiest way is on unlocked bootloader, because it allows reboot to EDL (do "fastboot oem unlock" for it, then "fastboot oem edl". Then flash patch via latest MiFlash and turn on phone manually by holding Power for 10 seconds. If you need bootloader locked, perform "fastboot oem lock" after all operations)
AlexAiS said:
Didn't test on march 2018 but should work
just one time, if you have described problem
Downgrade isn't mandatory. Can be flashed from any fw without data lost. The easiest way is on unlocked bootloader, because it allows reboot to EDL (do "fastboot oem unlock" for it, then "fastboot oem edl". Then flash patch via latest MiFlash and turn on phone manually by holding Power for 10 seconds. If you need bootloader locked, perform "fastboot oem lock" after all operations)
Click to expand...
Click to collapse
Does this fix the issue where the phone sometimes can't detect 5 ghz connections?
A restart can temporarily fix it for at least 1 hour but all 5 ghz disappear again
AlexAiS said:
I've created files for miflash for WiFi fixind almost on all firmwares. It is in attachment below. It will not erase your data. It must be flashed only in EDL mode, because fastboot mode doesn't allow to flash persist
Click to expand...
Click to collapse
Thank you so much for this! For some reason with the stock ROMs I was having no Wi-Fi issues on either band. But on RR and Pixel Experience ROMs, the 5GHz connection would work for less than 30 seconds before dying and I was going crazy trying to figure it out! How can anyone use 72Mbps 802.11n when 433Mbps 802.11ac is just sitting there
Can u describe the correct procedure for flash the patch?
@l36320
{
"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"
}
May you, please, correct your profile signature?
Mi A1 isn't a bad phone at all, it really depends on the phone's owner.
berezker said:
Does this fix the issue where the phone sometimes can't detect 5 ghz connections?
A restart can temporarily fix it for at least 1 hour but all 5 ghz disappear again
Click to expand...
Click to collapse
It should help I guess
AndroidianoSr said:
Can u describe the correct procedure for flash the patch?
Click to expand...
Click to collapse
procedure is usual for almost all Qualcomm-based Xiaomi. I'll describe it in short. But if you have zero experience in flashing phones, try to search any extended manual for qualcomm flashing.
1. Power Off your phone
2. Hold Volume- and Power together until you see rabbit, then release both buttons
3. Connect phone to PC, install fastboot drivers
also unzip this archive to C:\
4. Run cmd.exe as Administrator, change active directory to C:\Tools (in cmdline type "cd C:\Tools" without quotes)
5. execute command "fastboot oem unlock" (without quotes, sure)
6. fastboot oem edl
7. now you're in EDL mode, install drivers from the same folder if necessary
8. Open XiaoMiFlash, select folder with unpacked Wifi Patch
9. Press Refresh, and after port appearing, press Flash
10. When you see green Success, disconnect phone and power it on by holding Power for 10 seconds
11. That's all. If you need locked bootloader, boot phone to fastboot mode again (as in 1st step), and perform "fastboot oem lock" and then "fastboot reboot" in cmdline
thx
thx bro...its fixed love you
Thank you very much??? I used this on April stock rom it worked like charm?
Tank you AlexAiS it works on last 9.5.9
AlexAiS said:
It should help I guess
and then "fastboot reboot" in cmdline
Click to expand...
Click to collapse
You are my hero
AlexAiS said:
It should help I guess
procedure is usual for almost all Qualcomm-based Xiaomi. I'll describe it in short. But if you have zero experience in flashing phones, try to search any extended manual for qualcomm flashing.
1. Power Off your phone
2. Hold Volume- and Power together until you see rabbit, then release both buttons
3. Connect phone to PC, install fastboot drivers
also unzip this archive to C:\
4. Run cmd.exe as Administrator, change active directory to C:\Tools (in cmdline type "cd C:\Tools" without quotes)
5. execute command "fastboot oem unlock" (without quotes, sure)
6. fastboot oem edl
7. now you're in EDL mode, install drivers from the same folder if necessary
8. Open XiaoMiFlash, select folder with unpacked Wifi Patch
9. Press Refresh, and after port appearing, press Flash
10. When you see green Success, disconnect phone and power it on by holding Power for 10 seconds
11. That's all. If you need locked bootloader, boot phone to fastboot mode again (as in 1st step), and perform "fastboot oem lock" and then "fastboot reboot" in cmdline
Click to expand...
Click to collapse
Thanks for your patch. it fixed the wifi problem going from RR back to stock. What is wired is that i flashed the whole stock rom via fastboot and edl. i also flashed the stock persist.img via edl mode. i flashed it even via dd in twrp but your patch did it. did i something wrong?
hey my mi flash says hello packet error etc ;_;
---------- Post added at 07:05 PM ---------- Previous post was at 06:24 PM ----------
AlexAiS said:
I had the same problem (Wi-Fi connected, No internet) on Mi A1 and checked almost everything. I tried different firmwares, I've even erased EFS and rewrote QCN calibrations, but no luck. But once I've downgraded this phone to Android 7 (fw ver 7.8.23), my bootloader was already unlocked (you can do it by simple command (fastboot oem unlock) in cmdline). I took persist partition (persist.img) from folder with unpacked 7.8.23 firmware and flashed it manually via edl ("fastboot oem edl" command for reboot to edl mode, and then flash persist.img separately) and IT HELPS!! Wifi now connects ok. Maybe problem appears because of persist partition isn't included in firmware configuration file by default. I've checked this method on 7.8.23, then updated via ota to 8.1.10 firmware, and after to 9.5.4.0, works like a charm!
I've created files for miflash for WiFi fixind almost on all firmwares. It is in attachment below. It will not erase your data. It must be flashed only in EDL mode, because fastboot mode doesn't allow to flash persist
Click to expand...
Click to collapse
what do i need to do it gives error on march update on mi flash
raiden2332 said:
Thanks for your patch. it fixed the wifi problem going from RR back to stock. What is wired is that i flashed the whole stock rom via fastboot and edl. i also flashed the stock persist.img via edl mode. i flashed it even via dd in twrp but your patch did it. did i something wrong?
Click to expand...
Click to collapse
Problem in persist.img files you've tried. I've also tried a lot, and only this one (included in fix) works perfect
Nautilus99 said:
hey my mi flash says hello packet error etc ;_;
what do i need to do it gives error on march update on mi flash
Click to expand...
Click to collapse
looks like drivers problem. The easiest way is to try on another PC with this drivers
Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock
Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?
Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.
@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.
Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!
Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.
MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?
No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.
But adb seems to work, adb devices returns my phone ID.
It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.
Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)