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
So I was trying to get into making a rom and realize how difficult it was so with me being impatient I tried installing the android q gsi straight from google and it works! well kinda Its only showing the android booting screen can anyone get passed it? Im ssure its vey possible
All you need to do is
Flashing the GSI
Reboot to your device’s bootloader using either a button combination or by issuing the command:
adb reboot bootloader
Next, we need to disable Android Verified Boot (AVB). You can do this by entering the following command:
fastboot flash vbmeta vbmeta.img
Next, let’s wipe the system partition:
fastboot erase system (might be easier to do this in twrp)
Boot into twrp:
fastboot boot <img file name>, e.g. fastboot boot twrp.img (use the latest build)
Then drag and drop the system image from zip and twrp image onto the phone and flash the system.img for system and twrp for recovery using twrp
reboot in recovery flash again and wipe data!
done
Gsi Download
https://developer.android.com/preview/gsi-release-notes#downloads * I used the gsm but I dont think it really matters out of the two arms64 I tested both and got the same results
Twrp Download
https://twrp.me/oneplus/oneplus6t.html
NOT trying to click bait i just dont know how to change the title my bad guys
Edit. U also have the VB disable command wrong. What u are saying just flashing the vbmeta. --disable-verification is in there too..
Yeah everyone got that far bud. There is no booting past logo.. we posted about it in a thread last month
fullofhell said:
Edit. U also have the VB disable command wrong. What u are saying just flashing the vbmeta. --disable-verification is in there too..
Yeah everyone got that far bud. There is no booting past logo.. we posted about it in a thread last month
Click to expand...
Click to collapse
Actually I saw on erfran's telegram chat for q gsi someone posted screenshots fully booted into the q gsi that was right away when he first released it too. The guy hasn't respond as to how or what he did differently but if u search for 6t in the chat and scroll all the way up you'll see what I mean. So it's possible hell if theyre getting into the 5 I don't know why we're not able to get in too... Although I'd prefer an official alpha Dev leaked whatever from OnePlus I'd settle for some aosp Google Q
gigilie said:
Actually I saw on erfran's telegram chat for q gsi someone posted screenshots fully booted into the q gsi that was right away when he first released it too. The guy hasn't respond as to how or what he did differently but if u search for 6t in the chat and scroll all the way up you'll see what I mean. So it's possible hell if theyre getting into the 5 I don't know why we're not able to get in too... Although I'd prefer an official alpha Dev leaked whatever from OnePlus I'd settle for some aosp Google Q
Click to expand...
Click to collapse
I have flashed every single gsi he posts on his server. Nothing works on our phone. Non ab stuff has q booting all day. I have even ported his stuff and they still don't boot. Miui is the only thing that works.
@ayjays but the ROM Q beta GSI, work on op6t?
Thanks
@iaio72 yes to a certain extent maybe go off the one plus 6 build I've seen around on the internet I've tried flashing it and it seems to be stuck on the screen before the bootloader but when you check twrp folders have been created like download and music so maybe there's something to it ??*
And @gigilie hopefully he can just boot into twrp, backup, and be generous enough to share ?
So the ROM booted, but don't started? Correct?
I followed your instructions, but the phone doesn't boot
iaio72 said:
So the ROM booted, but don't started? Correct?
Click to expand...
Click to collapse
It has a bootlogo, and that's it.. he never said it went past that. Hence my whole input as stated above. . It doesn't work for us bro. Everyone in tg tried this a month ago. All same results. I managed to port some of it to our stock system img and got a different boot logo...and also the command to disable VB is not the same as flashing the image
It is: fastboot flash --disable-verification vbmeta vbmeta.img
(for the Q gsi the install instructions are to use their vbmeta.img.)
Fastboot flash vbmeta vbmeta.img just flashes vbmeta. U must disable ours and flash theirs. One command
@iaio72 yes it boots but only till you reach Android bootlogo I've tried everything I can't think of anything else that's why I was hoping our talented friends can fix this and @fullofhell I understand this was already brought up I just quickly posted this without doing any further research because I thought I already seen all there was but I'm sure there's a way to make it boots I'm almost certain maybe someone can port with treble or port the boot.img from a pixel build I'm not really an expert just suggesting no reason on giving up cuz someone told me to
ayjays said:
So I was trying to get into making a rom and realize how difficult it was so with me being impatient I tried installing the android q gsi straight from google and it works! well kinda Its only showing the android booting screen can anyone get passed it? Im ssure its vey possible
All you need to do is
Flashing the GSI
Reboot to your device’s bootloader using either a button combination or by issuing the command:
adb reboot bootloader
Next, we need to disable Android Verified Boot (AVB). You can do this by entering the following command:
fastboot flash vbmeta vbmeta.img
Next, let’s wipe the system partition:
fastboot erase system (might be easier to do this in twrp)
Boot into twrp:
fastboot boot <img file name>, e.g. fastboot boot twrp.img (use the latest build)
Then drag and drop the system image from zip and twrp image onto the phone and flash the system.img for system and twrp for recovery using twrp
reboot in recovery flash again and wipe data!
done
Gsi Download
https://developer.android.com/preview/gsi-release-notes#downloads * I used the gsm but I dont think it really matters out of the two arms64 I tested both and got the same results
Twrp Download
https://twrp.me/oneplus/oneplus6t.html
Click to expand...
Click to collapse
Check out this thread. https://forum.xda-developers.com/oneplus-6/development/rom-pixel-3-xl-port-oneplus-6-t3856031
@ayjays this guide can help us to install ANdroid Q DP GSI?
https://forum.xda-developers.com/oneplus-6t/how-to/guide-gsi-flashing-tutorial-one-plus-6t-t3891655
Your a god ??? @sangiman thanks!!
Bit of you guys lol @iaio72
https://forum.xda-developers.com/showpost.php?p=79360784&postcount=286 I think he has found our solution
ayjays said:
https://forum.xda-developers.com/showpost.php?p=79360784&postcount=286 I think he has found our solution
Click to expand...
Click to collapse
Did it boot?
_Masked_ said:
Did it boot?
Click to expand...
Click to collapse
yes it did just make sure you flash international oos 9.0.11 first and oem unlock again then follow his guild for the oneplus 6t its pretty buggy and the wifi doesnt work might not recommend daily use but people can use this to make a rom im sure.. maybe lol
BUT yes its running Q oneplus 6t thank you guys
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.
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?.
Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!
You should just be able to install matiek form my understanding
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.
peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.
holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!
I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW