Related
All About Redmi 3 Family
If you are satisfied with my work please make a donation
Bitcoin : 169cZB6dmrbFZBwJpS4gjawUQdhhxZpWNz
U can ROOT them and U can flash XPOSED !
Roms For Redmi 3/Pro and Redmi 3S/3X(MIUI 7&8)[Official/Unofficial Global ROM]
For both Locked and Unlocked bootloaders
Please report the bugs For Redmi 3/Pro HERE
Please report the bugs For Redmi 3S HERE
Please report the bugs For Redmi 3X HERE
I am not responsible for any damage you may cause So
Do it at your own RISK
Code:
[SIZE="3"][CENTER][B][COLOR="red"]***If you dont wanna unlock your bootloader but need Root and TWRP Please flash SpaceX ROM***
**Remember by flashing SpaceX U cant Unlock your bootloader(it will stop at 50%) till you reflash Stock China Dev ROM**
*I recommend U Flash the least China Dev ROM and Unlock your Bootloader first
and flash xiaomi.eu ROMs (anyway as you wish!)
[If You are running SpaceX ROM and wanna unlock your bootloader check section "How to Unlock bootloader" ]
[/COLOR][/B][/CENTER][/SIZE]
Xiaomi Redmi 3 Pro - Bend test, Scratch test, Burn test - Durability video : Be Proud of your phone
Its better than Mi5 !!!!
Video Link
Download ROMs :
Redmi 3/Pro
Redmi 3/Pro Locked Bootloader: [SpaceX][MIUI7][Stable][6.5.12] Link
Redmi 3/Pro Locked Bootloader: [SpaceX][MIUI8][Weekly][6.7.7] Link
Redmi 3/Pro Unlocked Bootloader: [xiaomi.eu][MIUI7][6.5.25] Link [Please Download HM3]
Redmi 3/Pro Unlocked Bootloader: [xiaomi.eu][MIUI7.5][Stable] Link [Please Download HM3]
Redmi 3/Pro Unlocked Bootloader: [xiaomi.eu][MIUI8][Stable] Link [Please Download HM3]
Redmi 3/Pro Unlocked Bootloader: [xiaomi.eu][MIUI8][Weekly] Link [Please Download HM3]
Redmi 3/Pro Unlocked Bootloader: [Thunder ROM][MIUI8][Weekly] Link
Redmi 3S/3X
Redmi 3S/3X Locked Bootloader : [SpaceX][MIUI8][Weekly]
Redmi 3S/3X Locked Bootloader : [Stock][MIUI7.5][Stable][Global] Link
Redmi 3S/3X Unlocked Bootloader: [xiaomi.eu][MIUI8][Weekly] Link [Please Download HM3SHM3X]
Redmi 3S/3X Unlocked Bootloader: [xiaomi.eu][MIUI 7.5][Stable] Link [Please Download HM3SHM3X]
How to Update SpaceX ROM with Locked Bootloader [Redmi3/Pro]?
As far as U know its not possible to update the Space X via OTA so I bring u a way to update your ROM to least version of MIUI8 even with LockedBootloader(Do it at your OWN RISK)
According to reports :
Anybody Who flashed SpaceX 6.7.7 with Locked Bootloader can update to least MIUI 8 !
For safety matters (for example: Quadroot Vulnerability) and more features its logical to do it !
Description and Download Link : LINK1 &LINK2
Please tell me about it
Push Thanks If You liked it :good::good:
How to Unlock the Bootloader?
1. (Important) Backup your data and store them out of the phone
2. (Very Important) Download and flash the least China Dev ROM Here >>> Flashing Guide
*( before downloading , think about the way you wanna flash it ! )
3. And read this (*ignore note 3 ! its the same method for Redmi3)
*** If You are running SpaceX and Try to Unlock the bootloader it will stop at 50% but I solve it > here we go:
1. Download the least FASTBOOT China Dev ROM here
File name : Redmi 3 Latest China Developer Version Fastboot File Download
2. Download Adb/Fastboot and install it on Windows 7 (64bit recommended ) link
3. Download MiFlash ( MiPhone20151028.exe) Link and install it on the Windows 7 (Allow all the Drivers instillation)
4. Reboot the PC
5. at Phone :Go to Developer options and Enable "Enable OEM unlock" , "USB debugging" and "Fastboot mode"
6.at Windows : Extract the FASTBOOT China Dev ROM in a newfolder and extract the contained file with 7-zip app
in the extraction area u got to see some files and a folder named : "image(s)"
7. Run Miphone and select extraction area folder (not images folder)
8. Turnoff the phone and hold vol- and press power button till u see the FASTBOOT logo
9. Plug USB cable to the phone and let windows detect the phone after that refresh the Miphone and it has to detect your device make sure that are address the folder correctly
and select "Flash all" in MiFlash then press flash and sit tight [ never ever disconnect the phone during flashing or you may lose it for ever better to use a laptop for power disconnection matters ]
when flashing is done the phone reboots itself and takes around 10 minute to boot up
after that login to your Mi account and do this (*ignore note 3 ! its the same method for Redmi3)
How to Flash Recovery [Redmi 3/Pro] ( TWRP )?
You need to unlock the bootloader first (see section "How to Unlock the Bootloader")
[f you are running China Dev ROM skip this part](Very Important) Download and flash the least China Dev ROM Here >>> Flashing Guide
*( before downloading , think about the way you wanna flash it ! )
.
.
***Check the Bootloader status ***
Code:
fastboot oem device-info
If its relocked dont worry Just Unlock it with the Miflash Unlock tool !
.
.
1. Download the least Version of TWRP here
2. Download Adb/Fastboot and install it on Windows 7 (64bit recommended ) link
3. Download MiFlash ( MiPhone20151028.exe) Link and install it on the Windows 7 (Allow all the Drivers instillation)
4. Reboot the PC
5. In order not to end up with bootloop you got to active China Dev ROM root @ Security app > Permissions > Root (you need internet connection for that) Phone phone reboots and takes 10 minute to bootup
6. Go to Developer options and Enable "Enable OEM unlock" , "USB debugging" and "Fastboot mode"
7. Connect your phone to the PC with USB cable and Run CMD (as administrator) (serach CMD in windows 7 Start)
8.At CMD type
Code:
adb root
and wait a while
then type
Code:
adb disable-verity
almost done !
9. Turn off the phone and turn it on while you are holding both POWER and VOL(-)[down] together it has go to FASTBOOT
10. Rename the downloaded recovery to "twrp.img" and Create a new folder in desktop and move the twrp.img in to it
11. At the new folder Hold SHIFT button of keyboard and press Right key of mouse (a menu pops out) select "Open command window here"
12. at the command window type
Code:
fastboot devices
13. if you see any registered device(if not do step 2&3 again or try on another windows)go for final step type
Code:
fastboot flash recovery twrp.img
wait a while then type
Code:
fastboot boot twrp.img
after that u will find yourself at TWRP!
U can do what ever u want now!
14. It's DONE !!! U got 2 options to go to the recovery
First > (Setting>About phone> System updates > upper right 3-dots menu > "Reboot to Recovery mode")
Second > (Hold Power and vol+ together while the phone is off)
:good::good:Press thanks if it was awesome! :good::good:
How to Flash Recovery [Redmi 3S/3X] ( TWRP )?
1. Unlock your bootloader ( see section"How to Unlock the Bootloader" )
2. Download Adb/Fastboot and install it on Windows 7 (64bit recommended ) link
3. Download MiFlash ( MiPhone20151028.exe) Link and install it on the Windows 7 (Allow all the Drivers instillation)
4. Reboot the PC
5. Install TWRP Recovery with TWRP Installer Tool: Here
6. Phone will automatically boot into recovery mode.
Swipe to allow modifications.
Browse to Advanced setting and Disable dm-verity. (If You dont do that the phone ends up with bootloop)
How to Unbrick Redmi 3 ?
for all of possible conditions you need these stuffs so bring them up before you start unbricking the phone
1. Download Adb/Fastboot and install it on Windows 7 (64bit recommended )
2. Download MiFlash ( MiPhone20151028.exe) Link and install it on the Windows 7 (Allow all the Drivers instillation)
3. Reboot the PC
We have a different scenarios:
a) The phone boots up and stock in MI logo (softbrick)
a2) The phone boots up and stock in MI logo and android animation (softbrick)
a3) The phone boots up and reboot itself (softbrick)
a4) The phone does not boot up but it respond while plugging charger (softbrick or hardbrick)
b) The phone does not boot up and its not respond while plugging charger (hardbrick)
For Scenario( a & a2 & a3 & a4 )
*** If you have unlocked bootloader try to flash TWRP and reflash a stable rom (like xiaomi.eu)
*** For lockedbootloader :
Hold power button till phone restarts as quick as possible hold vo(+) so that phone can go to bootloader Try to reflash the ROM in download mode
Watch the video
What you need :
1. ROM Download
2. MiFlash
3. Do what exactly the Video says
For Scenario B (Hard Brick! ):
first of all make sure your battery has enough charge
1. Download the least FASTBOOT China Dev ROM here
File name : Redmi 3 Latest China Developer Version Fastboot File Download
2. Download Adb/Fastboot and install it on Windows 7 (64bit recommended ) Link
3. Download MiFlash ( MiPhone20151028.exe) Download and install it on the Windows 7 (Allow all the Drivers instillation)
4. Download and install THIS1 & THIS2 then Reboot the PC
5.at Windows : Extract the FASTBOOT China Dev ROM in a newfolder and extract the contained file with 7-zip app
in the extraction area u got to see some files and a folder named : "image(s)"
Now be ready for the phone...
Keep press vol(+) and vol(-) together (make sure U do it !! press harder dont worry!!!! ) (dont leave them ! )and then press power button till U see a blank page,The phone is on ... U can see the background LED lights (THE PHONE IS IN THE FACTORY PROGRAMMABLE MODE)
now
7.Run MiPhone (or MIflash) Plug USB cable to the phone and let windows detect the phone after that refresh the Miphone and it has to detect your device (U see the phone is detected ... if not do part 3 and 4 another time or try on another win7 64bit) and select extraction area folder and select (images folder)
and select "Flash all" in MiFlash then press flash and sit tight [ never ever disconnect the phone during flashing or you may lose it for ever better to use a laptop for power disconnection matters ]
If u got an error (TELL ME ABOUT THE ERROR)dont worry
8.Run Miphone and select extraction area folder (not the images folder this time select the root folder! )
and select "Flash all" in MiFlash then press flash and sit tight [ never ever disconnect the phone during flashing or you may lose it for ever better to use a laptop for power disconnection matters ]
It takes around 300-400 s to flash
When its done press power key for seconds and it resets
U are ok now ! ( wait around 20 min to see the least MIUI8 )
Please Keep me Update!
How to use semi-QuickCharge ?
Caution :
Redmi 3/Pro stock kernel do not support QC but it can use maximum 1.6 A of 2.0 A .
but why is that ?
according to battery safety policy it cant be so warm during charging so PMU will decrease the current in order to make the battery cooler. it s kinda related to PMU parameters ( some kernels can modify that unfortunately Redmi 3/pro stock kernel do not support PMU modification )
so how could I reach 1.6A ? ( in normal operation you may reach to 0.8 A)
***flash the least version of MIUI 8 first***
1. Install ampere app
2.Turn on Airplane mode
3.Force stop all background app
4.Run Ampere and plug the charger
5.Use the stock adapter (5V @2A) and stock cable
6.Try to cool it down while its charging ! ( I used Ice pack for that) (dont cool it so much keep it around 20 Celsius degree or you may damage the battery )
7.Then you reach 1.6A current (in the optimum situation)
*** Simply ! Try to keep the phone cool while its charging ! ***According to sciences You cant charge the phone [0 to 100] less than 160 Minutes!
So dont blame the phone!
Try to create a new kernel !
Dont Forget to Thanks :good::good::good:
Root:
*First of all You need to Unlock your bootloader and flash TWRP
(See section "How to Unlock bootloader" and "How to Flash Recovery")
1. Download Stable or the least Super su "link"
2.Store the downloaded zip file into phone
3.Reboot to recovery (Setting>About phone> System updates > upper right 3-dots menu > "Reboot to Recovery mode")
@ Recovery :
1. Allow system modification
2. Install Supersu zip
3. Reboot
4. Now You have access to Super su features
Xposed For MIUI 8 (SDK22) Arm64[Both Locked and unlocked BL] :
***First Flash the least version of Supersu with TWRP *** "[Link]"
1.Download XposedInstaller_3.0-alpha4 and install it [Link]
2.Download Xposed For MIUI 8 (SDK22) Arm64 and move it to SD [Link]
2*.Download Xposed Uninstaller and move it to SD [Link]
3.Reboot to recovery (Setting>About phone> System updates > upper right 3-dots menu > "Reboot to Recovery mode")
then Flash Xposed For MIUI 8 with TWRP
4.Reboot (may takes time to boot up)
5.If anything goes wrong Flash Xposed Uninstaller and reboot
Screenshots:
COMING SOON ...
Tweaks (More Battery and Performance) :
I've Started New Project (BT4A)
Check it out LINK [UPDATED] [/B]
Bugs:
- No LTE for some users NOT FIXED YET!
- Brightness changes to its default value by cleaning the recent apps
Temp FIX: Turn on reader mode and choose "Selected apps" . but don't select any app in it ... DONE !
How to Flash the ROM ?
(you may lose your data storing on internal storage after flashing so back up your data first and keep them out of phone !)
Locked Bootloader:
Watch the video
What you need :
1. ROM ( You got from Download section)
2. MiFlash (Download MiPhone20151028.exe) Link
3. Do what exactly the Video says
Unlock bootloader:
1.Move the Downloaded ROM to SD
2.Do a factory reset
3.Do a clean Flash of the Downloaded file with TWRP Recovery
Remember First Boot takes time please be patient
Don't Forget to
push Thanks bottom
:good: :good: :good: :good:
XDA:DevDB Information
ROMs For Redmi3/Pro/S/X, ROM for the Xiaomi Redmi 3
Contributors
adblocker
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Stable
Current Stable Version: 8.0.2
Stable Release Date: 2016-09-01
Current Beta Version: 6.10.27
Beta Release Date: 2016-10-28
Created 2016-06-28
Last Updated 2016-10-28
thanks dude for ur work. i wanna ask u something, what is the difffrent about your rom with xiaomi.eu build. look like its have same feature? correct me if im wrong. thanks in advice
sorry for my bad english
So far this is the cleanest rom I've used, liking it.:good:
tpetran said:
So far this is the cleanest rom I've used, liking it.:good:
Click to expand...
Click to collapse
what about fingerprint?
Mahut said:
what about fingerprint?
Click to expand...
Click to collapse
don't know, I have plain Redmi 3
Mahut said:
what about fingerprint?
Click to expand...
Click to collapse
Working
check the bug section
iModStyle said:
thanks dude for ur work. i wanna ask u something, what is the difffrent about your rom with xiaomi.eu build. look like its have same feature? correct me if im wrong. thanks in advice
sorry for my bad english
Click to expand...
Click to collapse
Please check the feature section
thanks for providing this rom since i got bootstuck after flashing twrp. it saved my phone
btw how to activate lte on this rom? i already changed through *#*#4636#*#* lte only but no changes, still stuck at wcdma preferred.
any help would be appreciated
thanks
I'll use this rom if lte issues solved.. Thx
28/06/2016
23:05: Flashing ...
23:25: Flashed, booted, configured - now testing
00:30: Everything looks so far so good. I am currently not using any SIM Card. Wifi is stable, translations are good, ROM is fast and responsible. FM Radio is working great.
00:35: I compared the Stock ROM NON-HLOS.bin with the NON-HLOS.bin of this build. They are identical. I hope to get a Indian NON-HLOS.bin to compare with my stock rom version to figure out how to enable LTE Band 20, which is very important for germany. Any hint is very welcome!
08:00: Flashed SuperSU latest build with TWRP, working great here.
Conclusion so far:
- ROM is very stable (out of the box), no crashes so far
- ROM is very fast. Booting is a lot faster than any other ROM before and feels very smooth. Congrats!
GoodSoul said:
28/06/2016
23:05: Flashing ...
23:25: Flashed, booted, configured - now testing
- Looking great so far.
Question(s):
- When I boot to recovery and allow "modifications", is my system then broken (bcs. I am on a unlocked bootloader)?
Click to expand...
Click to collapse
i think not cz before installing this rom my stock dev rom is broken then i flash this rom and it works great for me unless the lte
papazz23 said:
i think not cz before installing this rom my stock dev rom is broken then i flash this rom and it works great for me unless the lte
Click to expand...
Click to collapse
Did you have LTE before flashing this ROM? Bcs. NON-HLOS.bin is the same as on the Stock ROM.
adblocker said:
Please check the feature section
Click to expand...
Click to collapse
ok may i was wrong, but when i check link for unlock it show build from xiaomi.eu sir. sorry if im wrong (again) i wanna taste ur rom and report the result here hehe. thanks for answering.
iModStyle said:
ok may i was wrong, but when i check link for unlock it show build from xiaomi.eu sir. sorry if im wrong (again) i wanna taste ur rom and report the result here hehe. thanks for answering.
Click to expand...
Click to collapse
The unlocked bootloader is the same as .eu
New Bug (maybe) :
Have U guys notice any thing wrong about Auto Brightness ?
Sometimes it freezes on 20 % till u lock and reopen the phone !
Please tell me about Any weird thing in the Rom
GoodSoul said:
28/06/2016
23:05: Flashing ...
23:25: Flashed, booted, configured - now testing
Question(s):
- When I boot to recovery and allow "modifications", is my system then broken (bcs. I am on a unlocked bootloader)?
Click to expand...
Click to collapse
When I boot to recovery and allow "modifications", is my system then broken (bcs. I am on a unlocked bootloader)?
No , Its functional
Flash Super su with that (link in description)
adblocker said:
No , Its functional
Flash Super su with that (link in description)
Click to expand...
Click to collapse
It is working, thnx. But for Xposed I still needed a unlocked BL, correct?
adblocker said:
New Bug (maybe) :
Have U guys notice any thing wrong about Auto Brightness ?
Sometimes it freezes on 20 % till u lock and reopen the phone !
Please tell me about Any weird thing in the Rom
Click to expand...
Click to collapse
i thin it's from the miui 8 itself cz i used to face it when in stock dev miui 8. if you can fix it would be awesome
GoodSoul said:
Did you have LTE before flashing this ROM? Bcs. NON-HLOS.bin is the same as on the Stock ROM.
Click to expand...
Click to collapse
lte on the previous stock dev rom works well. it's weird that i can't lock it to lte, but the others are good 'wcdma only' and 'gsm only'.
adblocker said:
The unlocked bootloader is the same as .eu
Click to expand...
Click to collapse
oh i see, thanks sir for ur answer
iModStyle said:
thanks dude for ur work. i wanna ask u something, what is the difffrent about your rom with xiaomi.eu build. look like its have same feature? correct me if im wrong. thanks in advice sorry for my bad english
Click to expand...
Click to collapse
The made by ManhIT does not require you to unlock your bootloader, has no Chinese apps, etc. Check this post and the whole thread.
tpetran said:
So far this is the cleanest rom I've used, liking it.:good:
Click to expand...
Click to collapse
True that, if you probably exclude CM, because this one still holds MI account and other few similar things (which I never user for instance).
iModStyle said:
ok may i was wrong, but when i check link for unlock it show build from xiaomi.eu sir. sorry if im wrong (again) i wanna taste ur rom and report the result here hehe. thanks for answering.
Click to expand...
Click to collapse
You should go for the ManhIT build for sure. It is build after the xiaomi.eu but it is tweked a bit.
adblocker said:
The unlocked bootloader is the same as .eu
Click to expand...
Click to collapse
Not sure what you mean but I can confirm that my bootloader is locked even with the ManhIT version, which is not an official build like the one found at xiaomi.eu
BTW the OP for the SpaceX by ManhIT is http://choimobile.vn/threads/locked...-6-23-khong-can-unlock-booloader-26-06.66360/
The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1
<disclaimer> I take no credit for anything in this guide. A BIG Thanks goes out to @tennear, @Unjustified Dev, @DrakenFX and @Starvirus. They are the ones who figured out the process described below and provided the excellent LineageOS 14.1 ROM. I just wrote this all-in-one-guide because I think the information is way too cluttered and spread over these forums.</disclamer>
<disclaimer> If you're not 100% sure what you're about to do, please first scroll down to the bottom of this post to see a list of DON'T's, a few things you SHOULD ABSOLUTELY NOT DO if you want to keep using your device.</disclaimer>
After having had quite some phones (Moto Defy +, Oneplus One, Nexus 5x,...) and having flashed a lot of ROMs on them, I thought I had quite some experience in these matters. Alas. Unlike Oneplus, ZTE would rather not have users fiddling with their devices. There are also three versions of the Axon 7 called the A2017 (China), A2017G (Global) and A2017U (USA), each with some minute differences from the others. This makes unlocking BL, flashing a custom recovery and installing custom ROMs not so easy on this device.
The following guide describes how to go from a stock, not rooted, locked bootloader A2017G on Marshmallow Firmwares (B03 to B10) to an unlocked bootloader TWRP recovery LineageOS 14.1 A2017G. A2017U users, this guide should work for you too, but I hear there's an alternative, easier process exclusively for A2017U users. A2017 users do not proceed, this guide won't work for you. Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first. Even A2017G or A2017U Marshmallow users must proceed with caution. There's always a tiny chance this process bricks your device. By following this guide, you will lose all your data on your internal memory. Please backup before proceeding. The data on your SD card should be safe.
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4UVMBVpYdVwcnlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
15) Type "Fastboot oem unlock" and hit enter
16) Follow the instructions on your phone and use the volume and power buttons to confirm you want to unlock your bootloader
17) Boot into TWRP by holding both power and volume up button
18) Type "Wipe" and choose "Format Data"
NOTE: If you get a permissions denied issue, try doing these steps while your device is in TWRP.
C) Update bootstack, Install LineageOS 14.1 and update your TWRP to latest version
Q: Why do I need Lineage OS 14.1?
A: It's a custom ROM that's a lot smoother than any available stock rom for any of the Axon 7 versions. Aside from an audio bug (the speakers make a rattling noise when the volume is turned higher than 80-90%) it's perfect. You can however find quite some other decent ROMS here.
Q: Why do I need the latest TWRP?
A: Tenfar's signed TWRP version is the only one that will be accepted by a locked phone, so you need to flash that version first to unlock your bootloader. You should however not use it for backing up and restoring, since it contains fatal flaws that can lead to bricking your phone. Update it using the steps below.
1) Download the latest unofficial Lineage OS 14.1 ROM from here: https://www.androidfilehost.com/?fid=457095661767134540
2) Download the A2017G Nougat bootstack from here: https://www.androidfilehost.com/?fid=673368273298930583 (A2017U users: your bootstack is here
3) Download the latest TWRP .img from here: https://build.nethunter.com/twrp/zte/twrp-3.0.4-1-ailsa_ii.img
4) Download a Google Apps version from here: http://opengapps.org/?arch=arm64&api=7.1/ .You must use an ARM64 file since that is the type of the CPU in the Axon 7. You must use 7.1 Gapps since that's the android version Lineage OS 14.1. is based on. Which one you choose is up to you, the "smaller" you go the less google apps will be installed as stock. You can always download the ones you miss via the play store after having installed LineageOS
5) Put the bootstack, the LineageOS and the chosen Gapps zips on your MicroSD card. Also put the TWRP.img on there
6) Flash the A2017G Nougat bootstack: Flash -> select the bootstack file on the microSD card
7) Flash LineageOS 14.1, then flash the Gapps zip file (again via TWRP)
8) Update your TWRP recovery by choosing "Install" and then clicking "Install Image" (bottom right) and selecting the TWRP .img file
9) Wipe dalvik, cache and data
10) Reboot
11) Enjoy your phone
In the unlikely case that you're greeted by a screen that asks you for a password because your system is somehow encrypted, reboot to TWRP and format your data partition to ext4 instead of f2fs (wipe -> advanced)
If your phone doesn't pop up as QUSB_BULK in EDL, you probably installed the driver that came with the phone. The device will pop up below Ports (COM & LPT) on Device Manager as Qualcomm something-something USB device. Uninstall that driver and reinstall winUSB drivers through Zadig.
If axon7tool fails with a what() and STD-exception and whatnot - if you installed the Zadig driver
Go to Device Manager, right click QUSB__BULK and Uninstall, then use the "adb reboot edl" command. Install the winUSB driver via Zadig. Reboot the phone by holding the power button about 10 seconds. Enter the command adb reboot edl again. Enter "axon7tool -r gpt boot recovery" in command.
If LOS refuses to install and you get the error axon7.verify_trustzone, install the universal bootloader (A2017X_B15_UniversalBootloader) before the N Modem.
So, the steps after you get access to TWRO are: 1) Install univ. BL (A2017X_B15_... .zip); 2) Install A2017G_N_modem.zip; 3) Install LOS14.1 zip; 4) Optionally, install Gapps; 5) Flash TWRP img
DON'T's:
- DO NOT use the signed TWRP (3.0.2) to backup or restore, it might brick your device
- DO NOT use this guide when you're on locked stock nougat, you need to downgrade to Marshmallow first
- DO NOT flash the wrong N bootstack. There's a different version for G and U devices
- DO NOT use this guide if you're on an A2017 (Chinese) device
- DO NOT unplug your cable from your PC or Axon while axon7tool is doing it's magic
- DO NOT make a mistake or typo, it can be fatal
- DO NOT try flashing random zips or files or formatting this and that when your device doesn't act according to the guide, post your issue instead
- DO NOT wipe anything else than Data, Dalvik and Cache in TWRP
ADDITIONAL STEPS:
- You can opt to root your device by flashing the latest SuperSU zip file
- You can opt to upgrade your unofficial LineageOS to the latest official version to receive weekly OTA updates
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
PsyJoe said:
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
Click to expand...
Click to collapse
Both the aboot.img and the TWRP.img come from A2017U versions. For the moment, we do not know if there is any difference in the aboot file between A2017U and A2017G, but it's highly unlikely. @tennear sent me a tool to read the partitions on my A2017G and the result showed the partitions were the same as those in the A2017U model.
For the moment, there's only one TWRP version, made for A2017U, but it seems to work on all models. I quote tennear here:
tennear said:
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
Click to expand...
Click to collapse
I suspect nearly all bricks on A2017G devices happen when A2017G users use tenfar's tool to unlock the BL. There's a lot of margin for error, for example with the whole COM ports shizzle. I advise not to go down that route. I also advise against trying to flash a rooted image through TWRP without unlocking your bootloader. Especially the command "axon7root.exe -p 4 -b -r" (flashing both boot.img and recovery.img at the same time) seems to kill specifically A2017G devices, that seem to have an extra "DFU" mode, which the A2017 and A2017U devices don't seem to have. A2017G devices get stuck in that mode and there's no way to get them out again.
TL;DR I think the risk isn't in flashing TWRP, but in flashing both boot and recovery at the same time, in the axon7root tool and in flashing a rooted stock rom without unlocking BL.
Thank you for this one thread guide. Should make it a lot easier.
Maybe you can add a few words and links to the B03 files that allow a downgrade from higher versions.
You have a typo in step 14), should be adb not ab
Controllerboy said:
30) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
Click to expand...
Click to collapse
Hi,
So, the backup can be restored, even if we cancel the password? Isn't the backup encrypted than?
Also, when we do swipe to agree to modify the system partition, is flashing SuperSU enough to gain root?
I'm not so much interested in installing a custom ROM (yet) but do want a safe way to gain root.
Thanks for your time and efford,
Edit: And all this is safe (step A) when on B08?
Cheers,
/Cacti
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Znuf said:
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Click to expand...
Click to collapse
Hi,
Thanks Znuf, I'll give it a go then.
Cheerz,
/Cacti
Controllerboy said:
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QDL_BULK"
16) In command, type "axon7tool -r gpt" and hit enter
Click to expand...
Click to collapse
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
le_cactus said:
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
Click to expand...
Click to collapse
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Controllerboy said:
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Click to expand...
Click to collapse
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
le_cactus said:
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
Click to expand...
Click to collapse
I give up. Or at least at this computer.
Just to be sure, the QDL_BULK/QUSB__BULK, shoild it be an unknown device, one with a yellow exclamation mark? Or should I install a driver for it, and if so where do i find it? Google didn't help me out today
I'll try another pc, see if that does work.
Cheers,
/Cacti
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Hi,
i unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Thanks in advance
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Killerdog said:
I unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Click to expand...
Click to collapse
Here's the file from DrakenFX: http://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Flash bootstack only once, then flash BO6 stock ZIP. In my experience it doesn't replace TWRP with stock recovery, even when you're not rooted.
DeJe63 said:
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Click to expand...
Click to collapse
Thanks for the tricks. I didn't know you could do all three commands at once. I'll update my guide.
Will this work for B08 or should I go all the way back to "B03 (or others)" ??
Tutorial looks good and simple, big thanks!
In general it works.
For some reason I was not able to update from DragenFX B06 to OTA B08. So I flashed stock recovery, stock B06, OTA B08 and just flashed back TWRP with axon7tool...and it worked. But it may be that I make some mistakes on the way to B08.
I was at BL unlock before.
Controllerboy said:
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Click to expand...
Click to collapse
Hi,
That worked flawlessly on my Win7 box, but I have general USB problems on that device. Got timeouts a few times during the axon7tool -r commands, so I don't dare doing a axon7tool -w command on that machine. So I stepped over to my Win10 x64 machine, but that machine it keeps identifying it as a "Qualcomm HS-USB QDLoader 9008 (COM3) device." :crying: axon7tool -r gives my a "Failed to connect"
Thanks for the help though, much appreciated.
Cheers,
/Cacti
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Controllerboy said:
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Click to expand...
Click to collapse
Thanks for the tips. I'll let you know how things work out.
Cheers,
/cacti
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Edit: thanks for the answers, when I buy this phone an root it I can let you know how it went.
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
there is no problem to root xiaomi device,because it can unlock BL
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
Hello , You can unlock bootloader then root your device easily with magisk , xiaomi devices are root friendly if you need any help lemme know i will do as much as i can
I would love a step-by-step, hold my hand type of tutorial. If some of you have spare time to do something good for the less capable brothers here, it will be great.
Yeah step by step Link would bei very helpful
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "fastboot devices" your phone should appear
Method 1 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 booting in TWRP (not recommended on this device, may cause bootloop)
pros: original recovery wont be replaced
cons: loads temporary recovery, once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
GoldenWarriorM said:
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "adb devices" your phone should appear
Method 1 booting in TWRP
pros: original recovery wont be replaced
cons: loads temp recovery once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery)
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Click to expand...
Click to collapse
Just confirming: in the TWRP page, the 12T Pro is not listed as a compatible device (https://twrp.me/Devices/Xiaomi/).
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Just did as instructed and it works. Only bummer is that twrp is in Chinese. I did google a youtube video and followed instructions to change language. So far all good.
Do OTA updates still work after rooting? Or what is the process to upgrading once rooted?
GoldenWarriorM said:
7) type "adb devices" your phone should appear
Click to expand...
Click to collapse
You mean "fastboot devices", as it is already in fastboot
booting to recovery ended in error for me " FAILED (Status read failed (Too many links))" which led to bootloop.
I reflashed original ROM and I will try flashing.
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
HValenti said:
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
Click to expand...
Click to collapse
I didn't tried to boot without installing, I think there is a problem with A/B slots. On devices without B slot booting in TWRP should work as intended.
JF_Derzi said:
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Click to expand...
Click to collapse
Provided version works on my device (Mi 12T Pro, Global ROM). Hardbrick is impossible if flashing TWRP in recovery partition.
I didn't found compatible Orangefox recovery
There are 3 versions of TWRP:
BOOT:
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
REC:
Update with existing TWRP.
gold
CMD
fastboot flash recovery_ab twrp.img***
powershell
./fastboot flash recovery_ab twrp.img***
BOOT REC:
Both methods
On this thread the proposed version is REC.
***Remove lock screen security and reboot to decrypt data then install TWRP.
Reboot with the buttons combination and not with a fastboot command
Update REC
twrp-3.7.0_12-v6.5_A12-diting-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Spoiler: Change languages
{
"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"
}
Then reboot TWRP
No need TWRP for Rooting
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Xiaomi 12T Pro
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
Pass SafetyNet without Magisk Hide Props Config and
How to Hide Root from Apps via Magisk DenyList [Android 13]
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Try island app on Google play
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
NOSS8 said:
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
Click to expand...
Click to collapse
Yes I have done all of this. Links have been fixed.
tavocabe said:
Try island app on Google play
Click to expand...
Click to collapse
I don't think I can isolate Google Pay/Wallet, but I will try it.