[TOOL] MiTool Xelar & gdetra
Hi guys, today i want to show you a tool that i have written with a friend (@xelar25 ).
It is Called MiTool and it allow you to change roms and to install recoveries on your xiaomi phone and use a Material Design GUI.
This tool is very easy to use. You have to choose your device and after this you can choose what to do.
It supports a lot of Xiaomi device but there is a very important thing: YOU CAN USE THIS TOOL ONLY IF YOU HAVE UNLOCKED THE BOOTLOADER OF YOUR DEVICE.
This tool support italian and english ( if there is words that aren't translate, please contact me )
Internet connection is required for download (but if you have already downloaded a rom you can flash it)
The latest version of this tool is downloadable at this link : DOWNLOAD MITOOL
In this version you can:
-Download and install OTA updates for this tool
-Install necessary fastboot and adb drivers (if you have problems with kedacom drivers you can use )
-Flash fastboot rom
-Download the latest version of selected category(China stable, China dev, Global stable, Global dev)
-Flash TWRP
-Download the latest TWRP for your device and install it
-When is required you can connect the phone in fastboot mode to flash roms and recoveries
-See the percentage of flash and download
MiTool Version 1.3.0
CHANGELOG:
-Fixes and optimization
-Added english changelog
-Fixed a bug with recognize of fastboot devices
-Started develop of Flash Rom with locked bootloader (NOT ACCESSIBLE)
-Started develop of Flash Rom Xiaomi.eu (NOT ACCESSIBLE)
You can download OTA update or you can download the installer from:
For any question you can contact me on telegram. We think that your feedback can be usefull.
My username is @gdetra
Visit our Web Site. You can see supported devices and If you want you can support us you can donate :
WEB SITE
THANK YOU!
XDA:DevDB Information
MITool, Tool/Utility for the Xiaomi Redmi Note 4
Contributors
gaab1998
Version Information
Status: Stable
Current Stable Version: 1.3.0
Stable Release Date: 2017-09-28
Created 2017-09-16
Last Updated 2017-09-29
Nice tool buddy
Thank you for this tool
ahaa...thats good bro just installed it, wish i can use after i (which i know i cant) unlock my damn boot-loader (rn4x)
rahul.trivedi1994 said:
ahaa...thats good bro just installed it, wish i can use after i (which i know i cant) unlock my damn boot-loader (rn4x)
Click to expand...
Click to collapse
lol why cant u unlock bootllader? flash dev rom, and wait for max 10 days, definitely it will allow you to unlock BL
Now it is different, you have to wait 3 days after the xiaomi message with permission
feherneoh said:
Yeah, I still have like 70 hours left....
Click to expand...
Click to collapse
Now se are developing a way to flash with locked bootloader also
feherneoh said:
Yeah, I still have like 70 hours left....
Click to expand...
Click to collapse
I'm waiting too... I wanna use this excellent tool... Thanks to the Dev! :good:
Flashed twrp and booted on twrp or it seems like so. Click on reboot and...
...my phone is soft bricked. Could not even switch off the beast.
looking for mitools folder here what i found in a log file :
target reported max download size of 536870912 bytes
sending 'recovery' (26812 KB)...
OKAY [ 0.591s]
writing 'recovery'...
OKAY [ 0.685s]
finished. total time: 1.276s
downloading 'boot.img'...
OKAY [ 0.591s]
booting...
OKAY [ 0.654s]
finished. total time: 1.246s
:
I finally flashed with the official develloper image with the official xiaomi tools. I'm done with this stuff.
This thread smell like $£*&@.
w1nst0n sm1th said:
Flashed twrp and booted on twrp or it seems like so. Click on reboot and...
...my phone is soft bricked. Could not even switch off the beast.
looking for mitools folder here what i found in a log file :
target reported max download size of 536870912 bytes
sending 'recovery' (26812 KB)...
OKAY [ 0.591s]
writing 'recovery'...
OKAY [ 0.685s]
finished. total time: 1.276s
downloading 'boot.img'...
OKAY [ 0.591s]
booting...
OKAY [ 0.654s]
finished. total time: 1.246s
:
I finally flashed with the official develloper image with the official xiaomi tools. I'm done with this stuff.
This thread smell like $£*&@.
Click to expand...
Click to collapse
Hi sorry but only today i have had the time to write to you. You have to flash no verity zip file that there is in mitool folder in c
Can i flash custom rom with this tool.
abhi91ar said:
Can i flash custom rom with this tool.
Click to expand...
Click to collapse
No at the moment, Sorry.
Related
Hi there,
I'm new to all this (first post) but I've just received a Zuk z1 which came with ZUI 0.9.096 installed.
I first followed the instructions on cyanogenmod dot org and later found the Tool All in One one here but I seem to run into the same problem on both.
When I attempt to flash TWRP recovery it fails, example error message:
target reported max download size of 1610612736 bytes
sending 'recovery' (10252 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: Invalid data)
finished. total time: 0.470s
this is the error I get with TWRP 2.8.7 but the error is consistent no matter what version I use.
Anyone have any idea what I can do?
The phone isn't really usable to me without flashing as there doesn't seem to be an app store on it (at least not in English).
Thanks in Advance
Eric
Sgt_Stubby said:
Hi there,
I'm new to all this (first post) but I've just received a Zuk z1 which came with ZUI 0.9.096 installed.
I first followed the instructions on cyanogenmod dot org and later found the Tool All in One one here but I seem to run into the same problem on both.
When I attempt to flash TWRP recovery it fails, example error message:
target reported max download size of 1610612736 bytes
sending 'recovery' (10252 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: Invalid data)
finished. total time: 0.470s
this is the error I get with TWRP 2.8.7 but the error is consistent no matter what version I use.
Anyone have any idea what I can do?
The phone isn't really usable to me without flashing as there doesn't seem to be an app store on it (at least not in English).
Thanks in Advance
Eric
Click to expand...
Click to collapse
Use dd command to flash recovery or use flashify app, of course first you need to have root rights but there's kingoroot to help although isn't a clean solution might do the trick for you.
Enviado desde mi A0001 mediante Tapatalk
Did you unlock the bootloader?
Hello,
I have the same problem,
I have the same Zui version, ZUI 0.9.096
I unlocked the bootloader, but I'm unable to flash TWRP
KingRoot is not working either, keeps failing
I got my OnePlus 5 back from the OnePlus support people the other day (I'll provide background for that if requested, I don't want this to get too long), and just yesterday sat down to install TWRP and root it. I unlocked the bootloader with no issues, but then when it came time to install TWRP, I ran into the issue. So I'll be in fastboot, and will enter in the command prompt:
"fastboot flash recovery [the recovery file]"
Which will return the following:
"target reported max download size of 536870912 bytes
sending 'recovery' (25860 KB)...
OKAY [ 0.557s]
writing 'recovery'...
OKAY [ 0.007s]
finished. total time: 0.566s"
Which seems to indicate that everything works, right? But when I then enter the command:
"fastboot boot [recovery name]"
It returns:
"downloading 'boot.img'...
OKAY [ 0.530s]
booting...
OKAY [ 10.104s]
finished. total time: 10.638s"
and boots back into fastboot mode.
I have tried this on both my HP laptop which is running Window 8.1 and my Dell laptop which is running the most recent version of Debian (I used sudo), and to the same results. I have tried multiple tool kits such as the one mentioned in this thread:
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
and the one mentioned here:
https://www.teamandroid.com/2017/07/12/download-oneplus-5-toolkit/
which (to the best of my knowledge) only seem to enter the same commands I do.
I have also tried unplugging the phone after flashing the recovery and using the button combos to enter the recovery. It always takes me to the default recovery instead of TWRP.
Some miscellaneous details:
The phone is unlocked.
I have developer options enabled and OEM unlocking is enabled.
I have done no modifications besides unlocking the phone.
I checked to make sure the phone is fully updated. It is.
I have no problem with erasing everything on the phone if need be.
I apologize in advance for any weird grammar usage, spelling mistakes, and/or formatting issues. Any and all help is much appreciated. I really have no clue what's going wrong here.
What TWRP are you trying to use?
I tried using version 3.2.2.0. I grabbed it from here: https: // twrp.me / oneplus / oneplus5. html
Nunna the Insane Gerbil said:
I tried using version 3.2.2.0. I grabbed it from here: https: // twrp.me / oneplus / oneplus5. html
Click to expand...
Click to collapse
It's not a good version. It's broken, in fact.
I'd recommend codeworkx 3.2.1-0
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
It works, thank you so much!
Nunna the Insane Gerbil said:
It works, thank you so much!
Click to expand...
Click to collapse
You're welcome. :good:
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
UselessIdiot said:
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
Click to expand...
Click to collapse
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
It says "Getting package info failed"
My internet connection should be ok.
But I didn't try factory reset yet.
Shall I try?
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Download b560 fullota-MF-PV !!!
Flash it using twrp open Kirin edition the one here on the forums
First flash the update zip and then the second file with it
U will be back to stock & receive updates
If anything happens & the system ask for reset simply erase data and redo the process and that's it {I did this many times since I always brick my phone with testing & always worked}
ceriqdesign said:
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
Click to expand...
Click to collapse
The Bootloader is unlocked but TWRP isn't installed.
UselessIdiot said:
The Bootloader is unlocked but TWRP isn't installed.
Click to expand...
Click to collapse
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
>fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.626s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.637s
OEM-Unlock is not Enabled
And I cant relock the bootloader.
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
UselessIdiot said:
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
Click to expand...
Click to collapse
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
ceriqdesign said:
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
Click to expand...
Click to collapse
I can't transfer Gboard from another phone, bacause my phone is stuck in the establishment phase.
I can't give my PC access to my files.
So i cant fill in my google account and because the FRP is still active i cant bypass the google protection. xD
Done! My mobile phone works again XD
But I would like to get away from the test keys.
UselessIdiot said:
Done! My mobile phone works again XD
But I would like to get away from the test keys.
Click to expand...
Click to collapse
did you already tried HuRUpdater method?
ceriqdesign said:
did you already tried HuRUpdater method?
Click to expand...
Click to collapse
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
UselessIdiot said:
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
Click to expand...
Click to collapse
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
ceriqdesign said:
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
Click to expand...
Click to collapse
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
UselessIdiot said:
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
ceriqdesign said:
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
Click to expand...
Click to collapse
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
UselessIdiot said:
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
Click to expand...
Click to collapse
sorry..but have you renamed twrp to recovery.img?
if it showed FRP Lock in bootloader with green font it's mean that the bypassed is not successful..did you try both method in the video?
Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Code:
[email protected]:~/Downloads/ota/output$ ./fastboot update images.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e5a9f9c
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (64 MB) to disk... took 0.187s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.032s]
Writing 'boot_a' OKAY [ 0.333s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.052s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.001s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2860 MB) to disk... took 12.379s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/6 (513608 KB) OKAY [ 16.216s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 2/6 (514145 KB) OKAY [ 18.289s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 3/6 (515013 KB) OKAY [ 18.389s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 4/6 (515534 KB) OKAY [ 18.281s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 5/6 (510919 KB) OKAY [ 18.317s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 6/6 (184768 KB) OKAY [ 8.139s]
Writing 'system_a' OKAY [ 0.001s]
archive does not contain 'system_ext.img'
archive does not contain 'system_other.img'
extracting vendor.img (1024 MB) to disk... took 4.095s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Sending sparse 'vendor' 1/2 (511135 KB) OKAY [ 16.211s]
Writing 'vendor' OKAY [ 0.001s]
Sending sparse 'vendor' 2/2 (389097 KB) OKAY [ 15.169s]
Writing 'vendor' OKAY [ 0.001s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 10.729s]
Finished. Total time: 165.761s
mudlee said:
Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Click to expand...
Click to collapse
Can you Reboot to Fastboot? If so then load up TWRP via Fastboot Boot. Once in TWRP, flash OOS ZIP and TWRP Installer. Once that's done, Reboot to Recovery and Again flash OOS ZIP and TWRP Installer. Then Format Data by going to Wipe -> Format Data. Once that's done, Reboot to OOS and skip the Initial Setup. Transfer the LOS ROM and TWRP Installer as well as Gapps to Phone Storage and Reboot your phone to Recovery. Once there, go to Install and Flash LOS and TWRP Installer. Once that finishes, Reboot to TWRP and flash Gapps. After flashing Gapps, Format Data again and Reboot. Hopefully you boot into LOS. Also, if you are trying to install LOS 16, Use OOS 9.0.17 ZIP and if you're trying to Install LOS 17, Use OOS 10.3.0
thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.
mudlee said:
thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.
Click to expand...
Click to collapse
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.
DarthVader said:
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.
Click to expand...
Click to collapse
:-O I have to grab a windows pc then.
mudlee said:
:-O I have to grab a windows pc then.
Click to expand...
Click to collapse
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.
DarthVader said:
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.
Click to expand...
Click to collapse
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS
mudlee said:
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS
Click to expand...
Click to collapse
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran
Code:
fastboot flash boot twrp.img
then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg
mudlee said:
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg
Click to expand...
Click to collapse
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?
DarthVader said:
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?
Click to expand...
Click to collapse
- As I said, I tried multiple twrp versions. Currently I'm trying out this one: https://eu.dl.twrp.me/fajita/twrp-3.3.1-1-fajita.img.html
- OOS: 10.3.0
- Android: 10
Maybe the problem is that I flashed last time too new OOS and that's why twrp does not work?
The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.
mudlee said:
The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.
Click to expand...
Click to collapse
Are you trying to install LOS 17 or 16?
DarthVader said:
Are you trying to install LOS 17 or 16?
Click to expand...
Click to collapse
I installed LOS 16 in the end, I might try the unofficial 17 as well, will see if I have time. I'm getting used to this flashing this and that here and there stuff
Thank you for your really valuable help!
eellogofusciouhipoppokunurious
Quote:
Originally Posted by OhioYJ
Appreciate it. This step maybe the key. I was using the TWRP installer, that maybe where I was going wrong. I'll have to give it another try.
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
(CUSTOM ROM)
lineage-17.1-20200115_153235-UNOFFICIAL-fajita
(TWRP WITH SUCESSFULL DECRYPTION OF BASE STOCK ROM / CUSTOM ROM STORAGE)
twrp 3.3.1-30 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - arm64-10.0-pico-20200116-BETA
(Latest)
RadioactiveKernel _ V10.2.0_CUSTOM_OnePlus6-6T
(Latest)
NanoDroid - 22.5.1.20200102
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE/WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MY)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
Last edited by Johndoesmoked; 18th January 2020 at 07:13 AM. Reason: i dont know
Michelsup
19th January 2020, 08:55 AM |#743
Member91 posts Thanks: 133
Quote:
Originally Posted by OhioYJ
You were able to install TWRP? A lot of us cant install TWRP anymore, only boot it. If this has changed it would be nice to have a recovery
There was a bug on the first 17.1. With the last builds you can update like you always did; lineage.zip, twrp.zip, reboot to twrp, gapps.zip, magisk.zip, reboot and profit.
Of course you obviously had to update /vendor, as stated on Luk's post.
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson
speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.
A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...