Hello people! The truth did not know where to put this but if it's wrong because there is no problem and relocated!
I have a x900 LeTV I bought several months ago! Two weeks ago you installed a beta version of android 6.0.1. and I was working fine few days and one night, suddenly he went out and caught no more! Hard has a brick because no load, does not light, does not enter or fasboot recovey mode, any PC with any version of Windows recognizes it and have been for days following guidelines to resuscitate through QPST.2.7.429.msi without but although follow the steps one by one PC with Windows 7 simply does not recognize me! I am in despair and can not think of anything else! Some genius of the community could help me? There is a guide for x800 that is very similar to x900, yet still do not achieve much !!!
Same
Same issue, did u manage to fix it?
Hello dear all,
after a long time of rush*around different solutions I finally figure it out how to hard brick Indian le max x900
(note hard brick means ur phone is completely dead no charging,no restart, *no fastboot etc....becoz of may be wrong rom flashing)
1. Install qualcom driver and latest qpst 2.7*(link:*https://androiddatahost.com/np4wq)(qualcomm driver present in qfil file for x800 link in step4)
2. Installed qpst*will be present at c:/program files(x86)/qualcomm/qpst/bin....inside it find qfil flashing*application...open it
3. connect ur dead indian le max to computer and see if qualcomm usb driver can detect it(u may notice qfil flashing appln will also show some com no connected)....if u r unsuccessful just press both volume key/or power key and both vol key at a time for around 1 min when phone is connected to pc.*(in any case u failed no big issue try to install it manually by searching in google, well I have used win10 and it simply worked for me)
4. Download the qfil file for x800 and extract it somewhere, it also have qualcomm driver inside it so once extracted install that driver too (link:*https://mega.nz/#!G0ozxZwb!vowHBNjQGC1AtVOx2ThrWpYt6yHEnAACFvq90XDF4n0)....actually i tried qfil for x900,x1, line brush tutorials etc but none of those worked for me and x800 aks le 1 pro have the same processor so it can make x900 alive....sahara error all the time...*( a big thx to*UNBRICK X800 X900*Started by*mxmax)
5. if all done correctly u can see ur dead indian lemax*phone connected to qualcomm mode with some com no, that u can notice in qfil flashing appln.
6.in the flashing appln select Flat Build,
* * * * * * * * * * * * * * * * * * * * *in browse select ur extracted qfil x800 folder (path\qfil x800\x1_na_dvt1_fastboot\prog_emmc_firehose_8994_lite.mbn,
* * * * * * * * * * * * * * * * * * * * *in load xml select rawprogram_unsparse (present inside folder x1_na_dvt1_fastboot)....after that patch0 that automatically comes,
* * * * * * * * * * * * * * * * * * * * than finally click on download....u can see process started and once completed exit it.
7. So now ur phone have qfil of x800 flashed, try to boot it by pressing power button for 1 min.....u can see blue led blinked and ur phone start to boot (if not means ur phone's battery is very less simply connect it with charger by pressing power button u can see phone starts to show orange led flashing after some time....ie it start charging)
8. once it start in step 7 the phone show chinese letv logo...but it doesn't boot becoz it is for x800 not x900....phone simply tries to boot again and again...so once the phone start to reboot by itself simply press power button and vol down key at a time....u can see small penguin that means ur phone is in fastboot mode.
9. its time now to install twrp 3.0 to ur x900 connected to pc in fastboot mode(link:*https://www.androidfilehost.com/?fid=24533103863139522)...simply install twrp from link extract it open the twrp installer appln ....and install it by pressing backspace key that u find during instrution)....great thing about twrp recovery is it can charge ur phone too while connected to power source.
10.So after step 9 ur phone should be in twrp 3.0 recovery mode....u can see internal storage of it shows in pc of around 10 gb not 52 gb.....so inside twrp\wipe\format data...type yes, and advanced wipe select all and wipe......once done u have 52 gb avail in internal storage that u can see in ur pc too.
11. put indian version any rom inside ur internal storage and flash it...once done ur phone will successfully rebooted links for roms are below...simply download any as per ur choice
* * * * *https://drive.google.com/file/d/0B6m-wM0vYiL8U0U4cUhUM2NlMGc/view*(this is stock 12s rom)
* * * **https://www.androidfilehost.com/?fid=24533103863139959* (this is also stable 12s rom made bu cuoco with extra settings and dolby presinstalled)
* * * **http://evolutionletvx900.blogspot.in/* *(this will give u link for 12s and 13s rom which have nova and google launcher preinstalled)
* * flash any rom and if any any file after flashed make big vibrate ur phone with blue led on...don't panic...simply press power button for long time it will reboot ur phone
A big thx to memerbers of leeco.re for proving international support for leeco becoz it had gone from India, and I request u to make support for Indian x900 also since we cant able to install eui 5.8 based roms....tried to install several roms by deleting lines for check in update-script...even though it installed make it brick/dea again...so plz help for android 6*
Hi, I'm a x900 user
I have the same issue than some of you guys, my phone is detected in Qualcomm mode in QFIL, I have to charge the phone like an hour or two, I can tell its chargin because It has the blue led on, when it has no charge the led is blinking red and after sometime it becomes blue.
Put the phone in Qualcomm mode, download finish succesfully, pressed Vol Up + Power, my phone starts but with blue led and black screen, although its detected as a hard drive (LeTV), it'srecognized as an adb device (serial number ----- recovery). I ran the command "x1_na_fastboot" in command prompt inside folder CEXCNFN590......zip., I got rebooting in fast mode device, but it stops in "awaiting devices".
Thats were I'm stuck. Got any ideas?
2 Rahulraj2012
Thanks bro it is work exactly as you say !!! X900 Unbriked for now ;-)
Related
I went stock DI01 by Odin, and tried re-rooting by Superoneclick 1.7, but it doesn't respond at "Waiting for device". it freezes.
I tried the other way from terminal, and it keeps on saying that the device isn't connected.
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
error: device not found
I can access the SD card, but rooters are not working when I turn on usb debugging.
I have Samsung driver installed, android sdk installed, and tried turning on and off while connected to computer. still no root.
how can I get it working?
With the number of pre-rooted roms we have why even root? After odin restore boot but don't sign in and power down. Pull battery/Flash CWM_recovery.tar/ insert battery 3 finger salute to recovery flash desired (rooted) rom. Depending upon what package you used you might have to flash a current modem in odin. Continue to restore set up.
good day.
One Click doesn't work anymore. I did this yesterday, after going back to stock and doing an OTA update, works wonderfully and it's really easy, very low possibility of bricking your phone and having to go through the hassle of fixing that. Go to this thread and follow along. http://forum.xda-developers.com/showthread.php?t=913470 I recommend using the Clockwork Packages from here though they are the most recent and everything seems to be fixed on them. http://forum.xda-developers.com/showthread.php?t=1017817 Easiest way I have ever seen to root a phone.
Hello everyone, Sorry for my english.
*
Here I wanted to be clever , but somehow I think I've made mistakes and I will need to have your help to know if my TF201 and dead or not . (Obviously longer under warranty ... )
*
So I was in the final version of the Asus Rom 4.1.1 JB .
*
I unlocked my TF201 using this method : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
but I stopped before nvflahs manipulation .
*
I installed CM 10.1 here: download.cyanogenmod.org/?device=tf201&type=nightly
the latest and it worked
*
I finally wanted to change the flatline by CMW recovery or TWRP only by the above method and just renaming the flatline ... but it did not work , so I wanted to restart the recovery flatline the original file via usb mode, but I was too far and I clicked on flight + wipe data .
*
Since my TF201 reboot only the first white asus logo and bottom powered by nvidia .
*
Top I have unlocked device .
*
But impossible to get 4 icons RCK android usb and wipe by pressing power + vol - it only reboot the asus seems impossible to extinguish.
*
When I plug in usb it is no longer recognized by Windows unless I reboot in power + vol+ the screen is black on the TF201 it seems off and is recognized by APX windows seven .
*
I kept this folder :
AndroidRoot :
blob.bin
blob.log
bootloader.ebt
create.bct
pt_patch.log
pt_restore.log
recovery.bct
and after when my tf201 is bricked i have made on APX with nvflash but it seems too late :
bricksafe.img
factory-config.img
unlock-token.img
*
*
*
Do you think I can do something to at least regain access to recovery or install a new one .
*
I tested the hard reset with the small hole but nothing.
I tested the above method of flatline in APX but it indicates wainting for device.
I placed this file as an attachment and the cm10.1 rom on my sd card in the external keyboard but I do not know how to start all this .
*
Thank you for your help.
Code:
#include
/*
* Your warranty is now void.
*
* 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER ..AND UR WARRANTY WILL BE VOID
THIS RECOVERY IS ONLY FOR THE GALAXY A7 [SM-A700FD] [QCOM] RUNNING LOLLIPOP
THIS RECOVERY HAS BEEN TESTED AND EVERYTHING SEEMS TO BE WORKING FINE .. CHECK THE BUGS SECTIONS
Why twrp ? Why not a pre-rooted firmware which will not void warranty?
Ans : TWRP has many more functionality than stock recovery ! Rooting means to playing around with your device.If some thing goes wrong it you have to flash the whole firmware again instead,backup your ROM through CWM and if something goes wrong restore your backup AS SIMPLE AS THAT !
All you have to do is follow my instructions :
STEP 1 :
-Download and setup ADB drivers for your device
can be found here Drivers !
STEP 2 :
-Download the recovery from --->
TWRP
-Download odin 3 Link
-Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7logo
-Press vol up to confirm
STEP 3 :
-Now that you are in odin mode connect your device via usb cable !
-Now open Odin3 3.09 that you have downloaded.
-If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
-Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it
MAKE SURE U UNTICK THE AUTO-REBOOT BUTTON
-Click Start
ONCE IT SAYS PASS ... BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON
HOW TO ROOT THE DEVICE :
-Download SuperSu (obviously the latest one) from here ------> Click here !
-Copy that to internal sd card or external sd
-Power off your device and press vol up + power + home button (all at once)
-Select install zip from sdcard --->choose zip from sdcard ---> scroll down and flash UPDATE-SuperSU-v2.xx.zip
Done ! And you are ready to go
BUGS
You tell me!
YOU TELL ME
NOTE : IF ANY OPTION DOESNT WORK FOR U ... TURN OFF UR PHONE AND THEN BOOT INTO RECOVERY
SOURCES
DEVICE TREE
KERNEL(PREBUILT ... THANX TO SAMSUNG ... AVAILABLE IN THE DEVICE TREE)
CREDITS
TWRP TEAM
@govind.madhu93 for testing
CHANGELOG :-
BUILD 2
Fixed Recovery reboot loop
BUILD 1
Initial Build
Thanks a lot!!
Can i try this method for A700FQ if i can flash twrp i can root my A7
I had installed a kitkat twrp on my a700fd that was developed for a700h and it worked.
Sent from my SM-A700FD using XDA Free mobile app
help
system force close after flashing recovery. only status bar is visible
PS: everything working fine now. cleared cache and restarted it. thanks a lot. backup restore also working
Hey are you also thinking to develop any custom rom for galaxy a7 ?
if you start i am ready to help.
govind.madhu93 said:
I had installed a kitkat twrp on my a700fd that was developed for a700h and it worked.
Sent from my SM-A700FD using XDA Free mobile app
Click to expand...
Click to collapse
It work with A700H kitkat my friend?
is this working on russian lollipop version of A700FD?
palimatix said:
is this working on russian lollipop version of A700FD?
Click to expand...
Click to collapse
yes
Hello
How about the SM-A700F would it work on that device too?
Great job. Now we just need an AOSP ROM.
I noticed that backups made with this TWRP have wrong date in their names (half a year earlier).
New build is up !!
Changelog
Fix Recovery reboot loop
Download - http://dl.rutvikrajagopal.com/a7lte/twrp
Will we see any development for the A700F [Exynos] ?
Hello! I've installed the second version of TWRP - all works, but backup folder name has invalid date - today it made backup with folder name 2015-03-25..
jazzzzy said:
Hello! I've installed the second version of TWRP - all works, but backup folder name has invalid date - today it made backup with folder name 2015-03-25..
Click to expand...
Click to collapse
I'll look into the issue soon
RVR said:
Code:
#include
/*
* Your warranty is now void.
*
* 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER ..AND UR WARRANTY WILL BE VOID
THIS RECOVERY IS ONLY FOR THE GALAXY A7 [SM-A700FD] [QCOM] RUNNING LOLLIPOP
THIS RECOVERY HAS BEEN TESTED AND EVERYTHING SEEMS TO BE WORKING FINE .. CHECK THE BUGS SECTIONS
Why twrp ? Why not a pre-rooted firmware which will not void warranty?
Ans : TWRP has many more functionality than stock recovery ! Rooting means to playing around with your device.If some thing goes wrong it you have to flash the whole firmware again instead,backup your ROM through CWM and if something goes wrong restore your backup AS SIMPLE AS THAT !
All you have to do is follow my instructions :
STEP 1 :
-Download and setup ADB drivers for your device
can be found here Drivers !
STEP 2 :
-Download the recovery from --->
TWRP
-Download odin 3 Link
-Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7logo
-Press vol up to confirm
STEP 3 :
-Now that you are in odin mode connect your device via usb cable !
-Now open Odin3 3.09 that you have downloaded.
-If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
-Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it
MAKE SURE U UNTICK THE AUTO-REBOOT BUTTON
-Click Start
ONCE IT SAYS PASS ... BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON
HOW TO ROOT THE DEVICE :
-Download SuperSu (obviously the latest one) from here ------> Click here !
-Copy that to internal sd card or external sd
-Power off your device and press vol up + power + home button (all at once)
-Select install zip from sdcard --->choose zip from sdcard ---> scroll down and flash UPDATE-SuperSU-v2.xx.zip
Done ! And you are ready to go
BUGS
You tell me!
YOU TELL ME
NOTE : IF ANY OPTION DOESNT WORK FOR U ... TURN OFF UR PHONE AND THEN BOOT INTO RECOVERY
SOURCES
DEVICE TREE
KERNEL(PREBUILT ... THANX TO SAMSUNG ... AVAILABLE IN THE DEVICE TREE)
CREDITS
TWRP TEAM
@govind.madhu93 for testing
Click to expand...
Click to collapse
hello, you can create a recovery for Galaxy A7 (SM-A700F Lollipop)? I looked everywhere but there:laugh::laugh:
nino64 said:
hello, you can create a recovery for Galaxy A7 (SM-A700F Lollipop)? I looked everywhere but there:laugh::laugh:
Click to expand...
Click to collapse
I would like that too if possible, our Sm-A700f dosnt get much love :crying:
After installed the build 2 I am still having reboot loop.
Unbrick your ASUS ROG Phone 3 for free!!
Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself.
I noticed some people in the community charging upto 50$ for the firmware which should've been free from the start.
Code:
#include <std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* I'm not gonna tell you how to install drivers and other things and only[COLOR="RoyalBlue"][/COLOR]
* proceed with this if you know what you're doing and please do some
* research first. YOU are choosing to make these modifications, and if you
* point the finger at me for messing up your device, I will laugh at you.
*/
NOTE - In case it's a Hard / Soft Brick
• For Hard Brick - Hard brick is when your device can only enter EDL mode and shows up as Qualcomm HS-USB QDLoader 9008 in device manager.
- Just follow from Step 1 to 3 to fix your device.
• For Soft Brick - Soft brick is when the system fails to boot but you can access fastboot mode.
- Just follow Step 3 to fix your device.
Prerequisites ►
• Windows PC
• Device fastboot drivers
• Qualcomm EDL drivers
• a bricked ROG 3 duh
Downloads ►
• EDL Unbrick tool - ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z
• RAW ROG 3 Firmware - Check the second post below
Instructions ►
Make sure you have device manager opened up to see if the device is connected.
1] Extract the EDL firmware
- Use the side port and connect device to PC
- Then run the file named 1ROG3_VFLASH_EDL.cmd
2] After you get an EDL SUCCESS message let the device boot within a minute or two into bootloader, use the device manager to
check if it's in EDL and if it's still there after a minute, press Power key + Volume down for about 12-13 seconds until
you don't see it in Device Manager, keep it plugged in and let it boot or try to power it on so it gets into the bootloader.
3] Once it's in bootloader flash any of the RAW firmware linked above depending on the device that you have, if its Tencent then flash CN, for global it's WW.
- Extract the RAW firmware and run the file zs661ks_raw_flashall.bat , have some patience and do not disconnect the device as this will take some time.
• That's all folks.
ROG 2/3 Telegram Groups & Channels ►
Global Discussion Group
Updates Channel
GCam Discussion
List of RAW firmware (latest at the top)
— Android 11 RAWs —
18.0410.2108.158 : WW
18.0410.2106.138 : WW
18.0410.2105.133 : WW
— Android 10 RAWs —
17.0823.2104.147 : WW
17.0823.2102.143 : WW
17.0823.2012.131 : WW
17.0823.2012.122 : WW
17.0823.2009.99/100 : WW | CN
17.0823.2009.98 : WW | CN
17.0823.2008.78 : WW | CN
17.0823.2007.58 : WW | CN
17.0823.2007.47/48 : WW | CN
17.0823.2007.32 : WW | CN
does it work for imei repair
tolgahan33 said:
does it work for imei repair
Click to expand...
Click to collapse
NO
deadlyindian said:
Unbrick your ASUS ROG Phone 3 for free!!
Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself.
I noticed some people in the community charging upto 50$ for the firmware which should've been free from the start.
NOTE
If your device can only enter EDL mode and shows up as Qualcomm HS-USB QDLoader 9008 in device manager then this is for you.
I'm not gonna tell you how to install drivers and other things, you should only proceed with this if you know what you're doing.
Prerequisites ►
• Windows PC
• Device fastboot drivers
• Qualcomm EDL drivers
• a bricked ROG 3 duh
Downloads ►
• EDL Firmware - ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z
• RAW ROG 3 Firmware - WW RAW | CN RAW | Mirror [17.0823.2007.32]
Instructions ►
Make sure you have device manager opened up to see if the device is connected.
• Extract the EDL firmware
- Use the side port and connect device to PC
- Then run the file named 1ROG3_VFLASH_EDL.cmd
• After you get an EDL SUCCESS message let the device boot within a minute or two into bootloader, use the device manager to
check if it's in EDL and if it's still there after a minute, press Power key + Volume down for about 12-13 seconds until
you don't see it in Device Manager, keep it plugged in and let it boot or try to power it on so it gets into the bootloader.
• Once it's in bootloader flash any of the RAW firmware linked above depending on the device that you have, if its Tencent then flash CN, for global it's WW.
- Extract the RAW firmware and run the file zs661ks_raw_flashall.bat , have some patience and do not disconnect the device as this will take some time.
• That's all folks.
Click to expand...
Click to collapse
what cable did you use?
takoyaki17 said:
what cable did you use?
Click to expand...
Click to collapse
You can use the deep flash cable if you can't get your device into EDL mode
Also don't quote the whole thing, just tag the user next time.
sorry,first time using this XDA lab app.thanks btw
Is it possible to unlock bootloader via EDL ?
Reserved Thanks
Do we need to keep PC in Test Mode?
Sorry I used Unbrick Toll of Oneplus earlier in that we need to put PC in test mode, that's why I'm asking.
sendme2pop said:
Do we need to keep PC in Test Mode?
Sorry I used Unbrick Toll of Oneplus earlier in that we need to put PC in test mode, that's why I'm asking.
Click to expand...
Click to collapse
When drivers lack a valid driver signature Windows prevents them from being installed and that's where test mode and disabling Driver Signature Enforcement comes in, if you have driver's with valid signature then you don't need to do this
Moha1155 said:
Is it possible to unlock bootloader via EDL ?
Click to expand...
Click to collapse
If you find a solution to this problem, please write. I also cannot unlock the bootloader on my Tencent version
Thanks for making this thread. This is my 1st Asus device and I confirmed that this tool is working 100%. I got my bricked device back with this tool. Now waiting for other development for Dirty Flash.
Warning Guys please dont use this tool
Unless the issue been rectified
This unbrick tool damage system partition
And persist as well
Need to fixed as early as possible
It also boot in asus rog 2 boot animation
Asus ROG Phone 3 (I003D)
можете помочь пытался прошить с китайской на глобальную Asus ROG Phone 3 ни чего не получается может есть человек мне нужна помощь
Please update the RAW files man thanks
Qtr1st said:
Warning Guys please dont use this tool
Unless the issue been rectified
This unbrick tool damage system partition
And persist as well
Need to fixed as early as possible
It also boot in asus rog 2 boot animation
Click to expand...
Click to collapse
Can you please explore more how its damaging the partition?
Have you tried it or its your guess?
I wouldnt say if i didnt try .. i flashed when i forced my phone to edl
And then tried edl mode .. the phone could not boot anymore .. system partition was damaged and couldnt be flashed using fastboot even when i re unlocked my phone by a help of chinese guy .. and then got system partition solved and also persist was fixed
deadlyindian said:
Latest at the top
17.0823.2007.58 : WW | CN
17.0823.2007.47/48 : WW | CN
17.0823.2007.32 : WW | CN
Click to expand...
Click to collapse
update
sendme2pop said:
update
Click to expand...
Click to collapse
How about you do it yourself? Ever hear of google? Geez.
Hi!
I tried to update my Mi Pad 4 Wifi to latest twrp 3.5.2.9 but I ended with a half-brick...
I cannot access TWRP anymore (no way to access it with power+volume up). Power menu (I am using arrowos) or adb reboot recovery, they just show me a brief twrp loader image than goes black and I need to power cycle.
Worse even, I can launch fastboot, fastboot devices responds but I cannot boot/flash, or whatever from fastboot.
I suspect I had somehow hosed some boot/persistent or other device partition.
I tried to reboot to EDL but it's not responding ...
System is working but I fell I am in an unsafe position....
Any clue on how to restore fastboot twrp funcionality or I lost my Mi Pad?
not sure if your issue but I needed to goto to fastbook devices, fastboot flash default boot.img. I couldn't get TWRP to work natively as boot - I needed to use Fastboot boot boot.img to temporarily boot into TWRP. This was over a year ago however so definitely not 3.5.2.9
p.s. somehow I managed to get 3.3.1 working - this is what is on my MiPad currently
p.p.s. if your fastboot comes onscreen but jumping straight to black screen with "press any key to shutdown" as soon as you plug in the USB then try this. I needed to
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd For some Windows 10 users (like me), it seems impossible to unlock the bootloader of their Xiaomi devices. Because every time they run MiFlashUnlock and connect...
forum.xda-developers.com
I've also now just installed this. I flashed from TWRP and it worked
[RECOVERY][UNOFFICIAL] Pitch Black Recovery Project [v3.x.x][2021/03/30]
/* *Disclaimer * * Your warranty is now void. * * We're 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...
forum.xda-developers.com
Last message - promise. Seems that it worked for me initially because I used 3.3.1.
Long-standing and known issues with later versions and suggested fix here >
PSA - The Latest TWRP Release (3.5.0_9-0) is Bugged
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it. I experienced the following when updating TWRP to 3.5.0_90: - long loading time: takes ~20s to finish initialization -...
forum.xda-developers.com