Related
I was previously on CM13 rooted and unlocked. Decided to upgrade to B15 today. Everything went great and installed Beast mode rom with Magisk (hopefully to allow DTVnow app to work). Magisk showed my safetynet was still tripped so I figured I would need to lock the bootloader. Used adb to fastboot oem lock and immediately the phone rebooted. It will now flash the ZTE logo and then the red led flashes twice and it turns off.
I can get into EDL mode. I can successfully send a recovery using tenfar's tool, but I have not been able to get into any of the recoveries I have tried so far. I tried Mi Flash, but I get an error from that as well. Any ideas what I should do next? I think I need to find a stock A2017u B15 recovery, but I have not been able to find that yet.
Code:
[0.00 COM4]:[COM4]:start flash.
[2.05 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[4.61 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.17 COM4]:try to reset status.
[7.17 COM4]:Switch mode back
[7.17 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.19 COM4]:eek:bject reference not set to an instance of an object.
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
wolly6973 said:
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
Click to expand...
Click to collapse
Gotta keep that bootloader unlocked on any kind of custom software, man. Lol. Did you enable Magisk Hide in the Magisk Manager before you checked SafetyNet? That's the only reason I can think of that it wouldn't have passed, but hey, at least you were able to get everything working again.
wolly6973 said:
So shortly after I typed this I realized I could grab the recovery out of the miflash B15-NEW_FULL. Flashed that with the tenfar tool and although I still couldn't access recovery, I can now use miflash! Did the full install and things seem to be working now!
Click to expand...
Click to collapse
What is the file you were able to flash with the tenfar tool? I am stuck!
I'm completely bricked. I've even contacted ZTE support via chat.
2017U on stock B15 w/ TWRP 3.1 & SuperSU 2.69; I then flashed the stock recovery and attempted to updated to the latest 7.1.1 (I forgot to unroot). It said it was successful, however when it rebooted, the phone set up like a brand new phone (still on B15 though :/). Shortly after finishing the initial set up, I received the same OTA notification for 7.1.1. It tried to install, and never booted back up. Refuses to go to recovery or fastboot, and PC does not recognize ADB or EDL - is says it's in DFU (which ZTE support said was "Device Firmware Upgrade" mode). It just sits on a black screen with a constant red LED.
Any help at all is appreciated. I'm pretty much left with a $400 paper weight.
t2jbird said:
I'm completely bricked. I've even contacted ZTE support via chat.
2017U on stock B15 w/ TWRP 3.1 & SuperSU 2.69; I then flashed the stock recovery and attempted to updated to the latest 7.1.1 (I forgot to unroot). It said it was successful, however when it rebooted, the phone set up like a brand new phone (still on B15 though :/). Shortly after finishing the initial set up, I received the same OTA notification for 7.1.1. It tried to install, and never booted back up. Refuses to go to recovery or fastboot, and PC does not recognize ADB or EDL - is says it's in DFU (which ZTE support said was "Device Firmware Upgrade" mode). It just sits on a black screen with a constant red LED.
Any help at all is appreciated. I'm pretty much left with a $400 paper weight.
Click to expand...
Click to collapse
Have you try this:
Option 1: Zadig driver not going to work if you want to use MiFlash. Try to use in this post https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Option 2: if 1 not work, i found this http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
You can do similar using full firmware B29/B15
Tell me if it works
tamahouse02 said:
Have you try this:
Option 1: Zadig driver not going to work if you want to use MiFlash. Try to use in this post https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Option 2: if 1 not work, i found this http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
You can do similar using full firmware B29/B15
Tell me if it works
Click to expand...
Click to collapse
Option 1 does not work and in the instructions for option 2, the links to the necessary files just take me to this wheretowatch website.. so i don't know if that would work or not.
jwilensky said:
What is the file you were able to flash with the tenfar tool? I am stuck!
Click to expand...
Click to collapse
Tenfar allows you to flash a recovery. I used the stock recovery.img file from miflash. You will want to try using a recovery from whatever version you have installed.
Hi!
I need some help rooting my Nokia 6 Mobile phone
The model number is TA- 1033
I have tried all kinds of different sources as a guide, but all failed for me.
I tried several one-click root tools as well. (Kingroot, Kingo Root)
I have tried to unlock the bootloader with Fastboot and ADB for the TWRP recovery flash
I have got developer options and also enabled USB Debugging and OEM unlocking ut the procedure still fail all the time.
I've tied to flash the TWRP without unlocking the bootloader but that ailed as well.
My device is not bricked yet.
Thank you for your help
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom (https://mega.nz/#!5ccRnb4b!VsgiKQ4CjxFyjbjcxR0esjeKmHZsUTnEz0FA_FMZQbM)
(To install it, you need the phone in bootloader mode.)
If it displays an error the first time, try again until the installation is fully successful.
Once the phone is turned on, the first thing you need to do is turn off automatic software updates. Know that if you want root, you should forget about OTA updates.
Once all written above is done remains to unlock the bootloader and installing TWRP.
For that..
Enter in bootloader mode.
Use Fastboot from your PC and enter this command to allow the partitions to be changed on your phone.
(To get MD5 of your serial number, use this website: http://www.miraclesalad.com/webtools/md5.php)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Example: fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e)
After that download this bootloader(http://pc.cd/xUFrtalK) and flash it:
fastboot flash aboot D1C-emmc_appsboot.mbn
(Make sure that downloaded bootloader is located in adb/fastboot folder)[Or you can type full file path of bootloader(Example: "C:\Users\Martin\Downloads\D1C-emmc_appsboot.mbn")]
(This to flash an unlocked bootloader.)
fastboot reboot-bootloader
(This is to reboot for using new unlocked bootloader.)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Again to allow installing partitions.)
Download recovery from here: https://mega.nz/#F!K1k0gC5C!xpw3-AQvSQJ5p6VWX19gpA)
Flash it with this command:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
(Make sure that downloaded recovery is located in adb/fastboot folder)[Or you can type full file path of twrp recovery(Example: "C:\Users\Martin\Downloads\nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img")]
After that reboot to twrp recovery and flash Magisk ROOT.
All is done.
Magisk is built in recovery. You don't need to download it from internet. Flash magisk which is in recovery.
Warning: After opening magisk manager you can update app but you can't update magisk version (core). Because latest version cause bootloop on ours devices. Use 16.1 version which is in recovery build it.
I hope everything will be fine. Good luck!
Hi! I have some issues.
marto2013 said:
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom
Click to expand...
Click to collapse
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
VargaTibor1 said:
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
Click to expand...
Click to collapse
On which patch level are you?
ZeroPointMax said:
On which patch level are you?
Click to expand...
Click to collapse
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
ZeroPointMax said:
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
Click to expand...
Click to collapse
He can downgrade his bootloader using older OTA update.
=====
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
marto2013 said:
He can downgrade his bootloader using older OTA update.
=====
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
Click to expand...
Click to collapse
I thought this wouldn't work too
Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.
I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?
Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.
How do you know your bootloader is locked?
Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.
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