Related
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
So as I woke up I had just seen that omg Android 10 is finally being released, the stable version. I just downloaded the OTA and flashed it and wow am i impressed. The first thing I did was do an antutu benchmark and I got 354802 which I thought was pretty impressive. Then I saw that it said that my device was rooted, which was odd, because I just updated the rom. I checked magisk manager and it showed that magisk was not installed. I tried the usual way to get into recovery by using fastboot boot twrp.img but it just didnt work.
Is this a bug or something else?
AmonRatMC said:
So as I woke up I had just seen that omg Android 10 is finally being released, the stable version. I just downloaded the OTA and flashed it and wow am i impressed. The first thing I did was do an antutu benchmark and I got 354802 which I thought was pretty impressive. Then I saw that it said that my device was rooted, which was odd, because I just updated the rom. I checked magisk manager and it showed that magisk was not installed. I tried the usual way to get into recovery by using fastboot boot twrp.img but it just didnt work.
Is this a bug or something else?
Click to expand...
Click to collapse
Well, it's expected behaviour for A10. fastboot boot is currently disabled by OnePlus devs.
Try Fastboot flash boot magisk_patched.img(or whatever you named the file)
I did this and it was flashing the TWRP as boot.img. After that my OP6T didn't get out of the locked screen or showed the Qualcomm CrashDumb.
After several times pressing the power button, finally the bootloader showed up again and I was able to flash the original boot.img again
Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....
boot img
tom1807 said:
I did this and it was flashing the TWRP as boot.img. After that my OP6T didn't get out of the locked screen or showed the Qualcomm CrashDumb.
After several times pressing the power button, finally the bootloader showed up again and I was able to flash the original boot.img again
Click to expand...
Click to collapse
hey man,
can I ask you where I can find the original boot.img, I have your same problem but I can't find the recovery image and then I can't restart the phone with android 10.
Thanks
dbarrett480 said:
Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....
Click to expand...
Click to collapse
Is it still true?
BesoC said:
Is it still true?
Click to expand...
Click to collapse
Fastboot flash boot twrp.img woks for me.
After that manualy reboot to recovery and flash twrp.zip.
fress said:
Fastboot flash boot twrp.img woks for me.
After that manualy reboot to recovery and flash twrp.zip.
Click to expand...
Click to collapse
Now it's booting only to TWRP lol
paolo.pise said:
hey man,
can I ask you where I can find the original boot.img, I have your same problem but I can't find the recovery image and then I can't restart the phone with android 10.
Thanks
Click to expand...
Click to collapse
Sorry, I didn't get notification. I downloaded the complete zip file and extracted from payload.bin all images with payload_dumper-win64.
Cheers
Tom
I'm having the same problem. Did anybody manage to get the fastboot boot twrp.img command working?
Darshan A S said:
I'm having the same problem. Did anybody manage to get the fastboot boot twrp.img command working?
Click to expand...
Click to collapse
It depends upon the context. If you are already in A10 and If you are using Twrp which is for Android Q, it should.
If you're on OOS 10.3.0 it should work as is
In other cases try 'fastboot flash boot twrp img'
Numerous posts about that
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
How do I get Magisk 21.0 to install through Magisk Manager?
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
CraigHardy said:
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
Click to expand...
Click to collapse
This is what I am getting after following your directions to a T!
I also flashed to both partitions. Please see attachments. I sent 2 screenshots.
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
CraigHardy said:
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
Click to expand...
Click to collapse
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Doesn't work. Download the patched image, put it on the phone, use magisk canary manager to patch it again, transfer it off your phone, then boot into Fastboot and flash it.
It has to be patched in the phone it will be installed to otherwise it will not work.
akinkoff85 said:
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Click to expand...
Click to collapse
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Here is the exact size.
Problem uploading image
I am a little confused now... I uninstalled root for a few days and now have the second release of android 11... I am in fastboot mode doing fastboot flash boot... then the file name and all it says is waiting for device?? Any help??
dladz said:
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Click to expand...
Click to collapse
Indeed, using the beta version worked for me! Thanks for the tip!
imval said:
Indeed, using the beta version worked for me! Thanks for the tip!
Click to expand...
Click to collapse
No worries man, glad you're sorted
CraigHardy said:
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
Click to expand...
Click to collapse
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
rodken said:
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
akinkoff85 said:
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Click to expand...
Click to collapse
Watch this video it helped me out allot
dladz said:
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
Click to expand...
Click to collapse
I did not know that one can just boot a magisk_patched.img instead of flashing.
rodken said:
I did not know that one can just boot a magisk_patched.img instead of flashing.
Click to expand...
Click to collapse
It's preferable.
There are some things to note.
1st. You are only booting it, meaning if you reboot; you will start using the installed / flashed image and the booted image will be lost.
2nd. For the above reason. If you want to make root permanent you have to open magisk after opening and then click install - install directly.
As magisk will already have root access, it will be able to accomplish patching, if you tried this whilst unrooted it would fail, or not be an option.
3rd. By booting you avoid the potential bootloop problems you can and almost will have at some point if you always flash, bad images are pretty rife for a number of reasons.
I've got a large guide for rooting in the guides section which covers all the bases and their shortcomings /benefits.
Attached with this post are :
+ Stock boot of OOS12 ( C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Magisk patched boot of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Modded stock recovery of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007) with ADB enabled, security disabled, ability to debug enabled and allow mock location by default.
Just flash in Fastboot mode as usual!
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
bookofjoshua said:
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
Click to expand...
Click to collapse
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
LinhBT said:
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
Click to expand...
Click to collapse
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
bookofjoshua said:
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
Click to expand...
Click to collapse
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
kevinco1 said:
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
Click to expand...
Click to collapse
True, if you are on OOS12 C41 ( TMO ) to be specific, then u can use the magisk patched boot image from my post to root your device using normal fastboot commands as mentioned!
LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
bookofjoshua said:
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
Click to expand...
Click to collapse
There's a guide to enable 5G and/or VoLTE for KB2007 also in our forum. But since u did it, congrats
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
works beautifully
heyChristo said:
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
Click to expand...
Click to collapse
not bad so far just more security . disabled pinch out hidden menu.. had to create code and use dialer to access hidden menu. i fastbooted this and now rooted have not tried recovery yet im afraid actually
So I converted mine to the EU version and then to the global version and updated to 12 via OTA. However I could not find the file prior to flashing so I couldn't pull it to the PC. Obviously I lose root on that full update. Can I flash this boot image to restore root or will that brick the device?
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Hey. Thanks for all your work. I'm rooted on stock kb2007. My OTA update to 41 is not working. Would flashing these before asking the system to update fix it, or are these for after you unroot and allow the update. I think the unroot is where I'm having trouble. I uninstalled Magsik and wiped cache for google play. The OTA still won't work. I'm sure there is every note on XDA about this, but I thought I'd ask here because I think I'm so close.
droidgreg said:
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Click to expand...
Click to collapse
you wouldnt have the last android modem img for android? thx in advance. i forgot to safe modem via msm tool before i converted to global smh
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
kevinco1 said:
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
Click to expand...
Click to collapse
There is no 100% confirmation that C42 was released as a full update and not incremental on C41.
If I'm already on Android 12, C41 unrooted than I don't need to do any other flashing except the magisk patched boot image from the post to root my device using normal fastboot?
What is the purpose of the modded stock recovery?
MustangLife03 said:
What is the purpose of the modded stock recovery?
Click to expand...
Click to collapse
The main reason is enabled adb access.
Having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
Though there is unofficial TWRP for A12 which makes stock adb enabled a bit obsolete in this case.
But anyway thanks for LinhBT for compiling it.
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