Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
This is from the twrp website https://twrp.me/xiaomi/xiaomimi9t.html
Note many devices will replace your custom recovery automatically during first boot.
Click to expand...
Click to collapse
After flashing the recovery :
Code:
fastboot flash recovery twrp.img
enter the code to reboot in recovery :
Code:
fastboot oem reboot-recovery
DELLINSPIRON1958 said:
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
Click to expand...
Click to collapse
U have to flash the modified vbmeta.img in order to keep a custom recovery..
Hello ,
There is no other solution ?
DELLINSPIRON1958 said:
Hello ,
There is no other solution ?
Click to expand...
Click to collapse
Have you tried by forcing reboot to Recovery/TWRP right after flashing TWRP (answer from another user, post #2):
>>fastboot oem reboot-recovery
Are you using e.g. the official TWRP 3.4.0, and did you enter in TWRP your Android screen unlock code, for TWRP to be able to properly work with File Systems on Data and Internal memory?
I am a neophyte, can you give me precise details of the method, thanking you
DELLINSPIRON1958 said:
I am a neophyte, can you give me precise details of the method, thanking you
Click to expand...
Click to collapse
Read post #2 - if you are not familiar with Fastboot, please search by Google and read - but how else did you flash TWRP than from Fastboot.
After flashing TWRP from Fastboot (1st command), use 2nd command to force direct rebooting to TWRP - without pinpointing with Vol+&Pow buttons, etc.
But really, nothing else, just that
Search here for thread about Official TWRP 3.4.0, download and flash that TWRP for davinci
When you enter to TWRP, it will ask you for your Android screen unlock pin/password (you should know your own one you use when booting to Android and when you are unlocking the locked screen in Android), enter that one when TWRP prompts you and wait few seconds (it should report success)
There is no rocket science here to teach more about ?, you just need to follow and try
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
DELLINSPIRON1958 said:
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
Click to expand...
Click to collapse
Try as described above:
- download official TWRP for davinci
- flash from Fastboot and reboot to TWRP with the given command
- in TWRP, enter your Android screen unlock code and check does TWRP correctly read your files on Internal memory (e.g. seeing proper file names in Download, not some garbage names)
- try to reboot to recovery (by TWRP command or by using Vol+) and check if it reboots to TWRP, not to stock Recovery
Please don't waste time by further endless questions, until you first try and have concrete questions/results (can't expect that people will pay attention to answer if you at least don't even try - why should then anybody waste the time)
I can't guarantee you 100% but I always have bootable TWRP, properly reading Storage (I also have boot.img patched by Magisk, hence not 100% same environment like you)
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
thank you for your reply. while searching on the net, I noticed that there are several answers to this problem, but which one is the right one?
without the phone being out
DELLINSPIRON1958 said:
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
Click to expand...
Click to collapse
For each member you can simply judge the credibility of his posts by his 'degree' on XDA forum, for which devices and topics he mostly diiscusses about and how many people thanked his posts
E.g. if I ask how to flash Xiaomi, Mi 9T and receive a suspicious 'guide' from somebody who only participated in discussions about Nokia phones, and who even did not get Thanks there for his participation, I will probably fully ignore and not risk to brick my phone
But if I get an answer from somebody who maybe participated for a year or two in topics on Poco and Redmi Note but who got hundreds of Thanks for his posts there, I will consider that he likely very well knows about flashing Xiaomi phones, although maybe never had Mi 9T in his hands.
Moreover, if I see that two or more people guide me in the same direction.
So I would at least google myself for more info (and then ask if still something not clear), and try - specially if that what was suggested does not sound as something to potentially brick my phone
After all, this is hackers forum and everybody is responsible himself for his phone. But on the other side, nobody was born with the knowledge but learnt by searching, reading and trying things herself
Also, everybody helps for free and by his good will, and sooner or later finds useless to waste time to answer for something that was already answered by his best (what else/new to answer), but the other one did not even want to try
Of course (as also in my previous post), things work for me as you wanted but yes, I always immediately flash together the boot image patched by Magisk.
So you can try would it work with the fully stock Boot - if yes, good for you.
If not, you can consider going to root by Magisk (although, being so cautious, it would probably take much more time and many, many more new questions before ?)
Kaiwalya said:
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
Click to expand...
Click to collapse
So just tested the following on my MIUI 12.0.2 QFJEUXM, with (unofficial) TWRP 3.4.0.2 from brigudav and Canary Magisk 20424
- Booted to TWRP and flashed stock 12.0.2 eea Boot.img
- Immediately rebooted back to Recovery - that is to TWRP and (that step is also important!) entered my Android screen unlock pin to assure that TWRP 'touched' the Data
- Rebooted to Android (System), where ofc, Magisk Manager showed that Magisk was no more installed
Then rebooted to Recovery (by keeping pressed Vol+) and phone booted to TWRP, not to the stock Recovery!!!
Hence the stock Boot image did not overwrite my TWRP with stock Recovery (although without having Magisk flashed at the time), because of properly doing each and every step as above!
(At the end, flashed back my patched Boot.img from TWRP, rebooted to Android and continued to use Magisk with all previously installed modules, etc)
Btw, I have never flashed any VBMeta, decrypted storage or so
PS:
And believe me, I lost myself TWRP many times (having to reflash it from Fastboot again and again when I was uninstalling Magisk, updating MIUI from TWRP and so), before learning that every step counts?.
Related
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
Hello guys, my phone one plus 5 has stopped working when I wanted to change to a ROM called (Resurrection Remix) which does not give any problem according to the users of the forum. I have another version of (Resurrection Remix) in my ONE PLUS TWO and without any problem. The topic is the following I have done all the steps as they are indicated but at the time of restarting the phone when the installation is finished, a load loop has started and never ends. I've been searching the internet all day to unbricke the phone but it's impossible, I try to install different ROMs and I still get nothing.
Sorry for my bad English, my language is Spanish
Link video YOUTUBE : https :// w w w. youtube .com/watch?v=0prJgT2erSU Delete the spaces of the link, being a new user does not let me post links
I had this same problem, and can almost promise this will unbrick it. Unfortunately this will put your phone back to how you had it when you first unboxed it, but it will work again.
1. Download the official OOS 4.5.5 zip
2. Wipe cache/dalvik/system/data in TWRP and flash the stock zip.
3. Within TWRP, flash the stock OP recovery image. You do this the same way as a zip, but click images in the bottom right while browsing for the file. Choose recovery as the partition of course.
4. Go to TWRP power options and boot to Bootloader/fastboot
5. Hook up to your PC and run the command to lock your bootloader "fastboot oem lock" (this will wipe your device and encrypt it again. I believe at this point the stock recovery will come up, do another factory reset to be safe.
6. Start your phone, at this point it should load up like new and all you have to do is unlock bootloader again and flash TWRP through fastboot so you can root again.
I don't have an answer for why ResurrectionRemix bricked your phone, but it did for me too. I followed the decrypt instructions to the T, but the same thing happened and I spent an entire Saturday trying to get my phone running again. I would guess that ResurrectionRemix is not to blame, and any other Lineage based ROM would end in the same result.
Good luck.
ArkAngel06 said:
I had this same problem, and can almost promise this will unbrick it. Unfortunately this will put your phone back to how you had it when you first unboxed it, but it will work again.
1. Download the official OOS 4.5.5 zip[/URL]
2. Wipe cache/dalvik/system/data in TWRP and flash the stock zip.
3. Within TWRP, flash the stock OP recovery image.[/URL] You do this the same way as a zip, but click images in the bottom right while browsing for the file. Choose recovery as the partition of course.
4. Go to TWRP power options and boot to Bootloader/fastboot
5. Hook up to your PC and run the command to lock your bootloader "fastboot oem lock" (this will wipe your device and encrypt it again. I believe at this point the stock recovery will come up, do another factory reset to be safe.
6. Start your phone, at this point it should load up like new and all you have to do is unlock bootloader again and flash TWRP through fastboot so you can root again.
I don't have an answer for why ResurrectionRemix bricked your phone, but it did for me too. I followed the decrypt instructions to the T, but the same thing happened and I spent an entire Saturday trying to get my phone running again. I would guess that ResurrectionRemix is not to blame, and any other Lineage based ROM would end in the same result.
Good luck.
Click to expand...
Click to collapse
WOW Many thanks, my friend, finally my phone has revived. Again thank you very much has served me very much.:good:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
Hi all.
I am going to flash LilneageOS 15.1 on my brand new A1.
We all know it DOESN'T contain any firmware blob (I mean, the stuff that usually drives the baseband modem, the wifi, the touch screen and so on) so I'd need to be sure I am on the latest one before flashing the ROM.
I've been unable to find here a "firmware only" release, also because in a few threads the word "firmware" is used as "ROM".
Is there anyone willing to point me to the proper post?
Please, be patient with me as I'm new to the Xiaomi world, but not new at all with Android and custom ROMs and recoveries.
Thanks in advance.
Hi, I recently flashed Lineage OS 15.1(Latest version) coming from Stock 8.1 August Update.
I suggest you follow the guide on the Mi A1 Lineage OS wiki which I followed and also use GApps(this survives OTA updates or something) provided by Lineage OS maintainer in his thread + 17.x magisk.
However ok Google does not work from Google App, assistant, maps, etc but the mic works fine.
I have seen people say flashing 8.1 May Beta modem(firmware available here) fixes the issue - see attached image - although I haven't tried it myself.
Hope you have no issues with Lineage OS, it's a bit complicated to flash on this device as it is A/B partition. Ok Google hotword is the only problem I have faced which is outweighed by the many essential features Lineage provides over stock.
If you need additional help please ask, because I myself found it tough to flash initially.
Edit: Having flashed stock GApps zip I also had the issue of camera FC, which was fixed by installing this camera through Magisk, which I will recommend anyway for better photo quality.
I have just started the process with TWRP recovery by following the LineageOS wiki up to step no.5.
The device is not booting to recovery but rather to system. So I am stuck here.
Uqbar said:
I have just started the process with TWRP recovery by following the LineageOS wiki up to step no.5.
The device is not booting to recovery but rather to system. So I am stuck here.
Click to expand...
Click to collapse
Have you already done fastboot OEM unlock?
iG0tB0lts said:
Have you already done fastboot OEM unlock?
Click to expand...
Click to collapse
I am strictly following the official wiki. Could it be a problem with the A/B partitions?
Uqbar said:
I am strictly following the official wiki. Could it be a problem with the A/B partitions?
Click to expand...
Click to collapse
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
iG0tB0lts said:
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
Click to expand...
Click to collapse
Yes, I did the unlock.
What you say deviates from the original wiki.
I am now updating the system so maybe I get the latest firmware.
I will try again soon after.
iG0tB0lts said:
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
Click to expand...
Click to collapse
Nope. It doesn't reboot, even if the command line says it did.
I have found something about this problem, but am really puzzled as the official wiki isn't mentioning anything about A/B slots.
TWRP Custom Recovery for the Onn Android Tablet series
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.