Related
I been trying for days to get my HTC Flyer with Honeycomb rooted via the GUIDE but I am stuck at step 1.
"If you are not on an appropriate gingerbread version, eg. if you have upgraded to honeycomb then downgrade by using an appropriate RUU; to identify your RUU see: here"
(downgrade to Gingerbread) but I get stuck at the "Fastboot getvar cid" stage to find out which RUU I have. When I have the Flyer in Fastboot mode and connect the cable, I get an error when it trys to install the "Android 1.0" driver.
I have uninstalled, rebooted, reinstalled, repeatedly. I just tried another link that suggested to try installing PDANet for Android to get around this problem. Now when I run Fastboot, rather than just "waiting for connection", I get an error that says "getvar:cid FAILED (status malformed (1 bytes)) finished.
*** Update***
I just tried a different HP Laptop with Windows 7 installed & I had the exact same error regarding the Android 1.0 driver as soon as I plugged in the Flyer when it was in Fastboot mode. Is there some other setting other than Fastboot off I need to do on the Flyer itself? Any other suggestions would be GREATLY appreciated.
Please help!! I am at my wits end here.
thanks,
sPk
still need help
I am still struggling here.
By pointing the Android 1.0 driver installer to the PDANet directory, it found a ADB driver and installed it. But I still get the "malformed error" when I try to use "Fastboot getvar cid" command to find RUU version. Is there another way to get the RUU version??
I think the driver is communicating with the Flyer as I was able to get Flyer to respond to the serialno command.
I have OTA update and want to root/Rom with HBoot 1.11.00011.
If I can't get the RUU version, is there a most likely suspected RUU for a WiFi only Flyer that I just got from Buy.com for US market.
thanks in advance for your help.
sPk
You have the android sdk installed right?
Andriod SDK
Gumby63 said:
You have the android sdk installed right?
Click to expand...
Click to collapse
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
windsurfsail said:
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
Click to expand...
Click to collapse
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
SDK
Gumby63 said:
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
Click to expand...
Click to collapse
I was able to get the Android SDK & Java installed properly. I uninstalled the driver in the Device Manager and then pointed the driver install to Android SDK/Tools and it indicated that the driver was already installed. I tried Fastboot command for the zilllionth time and still got the same malformed error. So I uninstalled driver & deleted it this time and tried to re-install but now it doesn't find the driver files (because I deleted them). I can re-install SDK or just point it to the PDANet directory again.
Is the correct driver for Fastboot the the Android ADB? It is the only one I have been able to get to load when I plug in the Flyer in Fastboot mode.
thanks,
sPk
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
hboot & fastboot confusion
globatron said:
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
Click to expand...
Click to collapse
DOH!
Globatron, thanks for the clarification. In all my reading of threads, I never saw any definition of hboot & fastboot. Since it wasn't working, I installed the other drivers in an effort to fix what was apparently a driver issue.
Is "fastboot mode" just having the "Fast boot" box checked under the Power settings?
thanks again!
sPk
Fastboot mode
After searching in the forums for a while, I found a description on how to get into "fastboot mode". I have added below in case someone else is new enough not to know.
I ran the command & it finally worked. Being in the right mode was key.
sooo, I now have the cidnum= BS_US001 but looking through the list of the RUU's files, I still don't see any reference to this CID. Another stupid question: How do I find which of the list of 25 RUU files is correct for my WiFi Flyer?
UPDATE: Found out how to find RUU file from link.
http://forum.xda-developers.com/showpost.php?p=18508220&postcount=2
modelid: PG4140000 (Wifi Flyer)
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001
cidnum: HTC__055
sPk
----------------------------------------------------------
You need to be in fastboot mode. Two ways to get there.
Get into boot then select fastboot
Or
While booted in android connect to PC then enter "adb reboot bootloader" (assuming you know adb a little)
Once in fastboot you need to enter the commands in a cmd terminal on your PC just like adb
What I learned, that may help you...
I had a surprisingly difficult time getting my OTA Honeycomb US WiFi Flyer S-Off'ed, Rooted & uploading a new ROM. I did get it done but there were some basic things I should have known or done. Thanks to Globatron & all who post on this board.
1: Before you start, make sure your PC's drivers are 100% working. I had Windows driver problems that caused other problems. Make sure that your tablet is properly recognized by the PC when the tablet is in Fastboot/Hboot modes, and in regular Android mode.
2: I didn't understand the difference between Hboot & Fastboot. This small thing made all the difference and was one of my major issues. Because I had the tablet in Hboot not Fastboot, the Fastboot commands didn't work and I couldn't get my RUU version
3: Pay attention to the phone's settings. Especially USB Debug mode, Fastboot mode.
4: After I had finally downgraded to Gingerbread. I couldn't figure out why Revolutionary wouldn't recognize my tablet. The simple answer was when I had downgraded to Gingerbread, all my phone settings were back to stock also so I had go in and change the USB Debug and Fastboot modes. It would be helpful to add a reminder in the GUIDE to make sure that these settings are changed before running Revolutionary.
5: Not really related but I had a problem when I wanted to backup my newly Rooted/ROM'ed phone. I had previously purchased the Titanium Backup Pro and I installed it on the Flyer but it wasn't listed in the Apps menu but was listed in the Manage Apps. Because Google-Play/Android Marketplace only copied over the paid apps to my newly upgraded Flyer, it didn't copy the free version of Titanium Backup. You must load both the free version & the paid Pro version for it to work.
I hope this helps someone who runs into any of the same issues I had.
thanks,
sPk
Hello, first post and fisrst tutorial here.
So here I want to show you how you can restore completely died LG p760(or his brothers p765/p768/p769) showing nothing or just LG Logo and so well known "Security Error", or boot loop problems.
The goal is to flash stock recovery, x-loader and u-boot and to unlock the bootloader(u-boot), so it can boot Clockworkmod or TWRP recovery.
First of all you'll need a computer(preferably Win7/8), an died phone , some drivers on the computer and fastboot on the phone. Let's start.
I'm not responsible for any damage to your device made during this guide. You can continue at YOUR OWN RISK.
Please READ IT before taking any actions on your phone!
1. Get fastboot on the phone. How? You can see here and here, or search the internet. There is a driver package, install them following the instructions.
2. After you inserted phone, installed drivers, etc. start the fastboot loader script(I prefer Lelus's one, i'ts more option-rich), and select one option for ICS x-loader and u-boot for your phone. Follow the instructions, it may take 2 or 3 tries before the drivers are correctly installed. Start again if the drivers are not correctly installed.
3. Copy the bin folder that is inside the fastboot files folder in C:, press winkey+R, type cmd and press OK.
Then copy everything from v20c_00 folder inside the C:\bin\ folder, it's in attachments in the end.
Here is the time to say that this files are for p760 only, you can find x-loader, u-boot and stock recovery for you model from internet, or here in the forums. I flashed also the boot.img, but don't think it's necessary for the completion of the process. You can also extract the .img files from stock .KDZ rom with this tool here, thanks to user kuma82. In the archive is the tutorial how to make x-loader.img, it's easy.
Let's continue.
Type in:
Code:
cd C:\bin
Check if the phone is in fastboot mode with this command:
Code:
fastboot devices
It must show something like:
Code:
1234567890 fastboot
If not, check that you are in the correct folder(C:\bin\), go and check drivers(no yellow marks or unknown devices), read the instructions again.
Then after you copied the files from archive, or files that you extracted from your stock rom, type in, or copy and paste into the cmd window:
Code:
fastboot erase x-loader
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash x-loader 0-x-loader.img
fastboot flash u-boot 1-u-boot.img
fastboot flash boot 2-boot.img
fastboot flash recovery 3-recovery.img
You must be fast, because after 30-60 seconds(don't know exactly) of inactivity, the phone will exit the service mode it is in and try to boot. Nothing bad happened, just load fastboot again and repeat the above fastboot commands.
After all the commands are completed without any errors, plug out usb, plug out battery, put the battery in, start the phone. The "Security Error" message MUST be gone. If it's not, probably your recovery is wrong, flash recovery again, if not, try with other recovery. This is working on P760, at least on mine. Here the S/W Update mode must also work like a charm, and you can try with some KDZ updaters, but that's not for this tutorial.
4. Now for step 4 we will need the phone in Recovery Mode. With phone turned off and battery inserted, press VOL_UP+HOME+POWER, when LG logo shows, release POWER and hold other two while the LG Recovery Mode show up. The phone must go straight into recovery, not bootlooping or showing "Security Error". If this happens, probably you recovery or u-boot is wrong.
Now put the usb into the phone and install the drivers from usb_drv_windows folder that is in the fastboot archive.
5. Type into cmd window:
Code:
adb devices
It must show something like:
Code:
1234567890 recovery
If not, you know..
Then we will unlock the bootloader with this command:
Code:
adb oem-unlock
The phone will restart, don't touch nothing. You'll see screen with info on what to do. Guess what..? We must press the VOL_UP button to confirm that we want to UNLOCK the bootloader, so it can load unsigned recoveries like CWM or TWRP and not to show the annoying "Security Error".
6. The phone will go into fastboot mode itself, you must install the drivers, again from the folder in the archive.
Now we'll flash CWM recovery with the help of fastboot. Copy the recovery-clockwork-6.0.2.9-p760 or recovery that is for your model to C:\bin\ folder.
Write:
Code:
fastboot flash recovery recovery-clockwork-6.0.2.9-p760.img
fastboot reboot
The phone will reboot, and hopefully you will not see "Security Error" error message. Now try to boot into recovery - pull the battery out, the usb cable, put battery in, and hold down VOL_UP+HOME+POWER, you know..
7. If everything is successfull you phone will load the recovery and you will be able to load nandroid backup or stock update.zip or CyanogenMod on your phone. Don't forget to wipe cache/data and dalvik's cache. From here you can backup your data or do whatever you want.
If your phone is not totally bricked, and if you are lucky enough you can continue from step 4(if you have recovery in your phone and it's still loading).
DOWNLOAD
I want to attach them here to the forum, but I can't for now, so here is Google Drive folder.
https://drive.google.com/folderview?id=0B9wMsz4X38L2aE5VdGFZcWczcEk
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
zhekozhekov said:
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
Click to expand...
Click to collapse
If your PC Is not seeing device in fastboot. It may be you need to update your fastboot.exe
In my case there was two possibilities. In Windows 10 I gave myself higher
admin rights clicking right in the folder of my fastboot programm. I tried a little bit, but there is no big thing to get a positive answer writing (before of course I switch on under developer settings usb debugging and gave answer in phone screen) :
fastboot devices
Better and easier is it on Linux, because writing sudo in front of fastboot and ready is it:
sudo fastboot devices
sudo fastboot flashing unlock
or
sudo fastboot flashing unlock_critical
:good:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I am still waiting for someone to give detailed instructions of rooting it.
Did you flash and use TWRP or flashed the patched boot.img straight? Cheers.
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
just got my phone bro. would you be kind in sharing the method you used to root your armor x5.. thanks.
I have the some problem.
In other device, fastboot are work alright.
I try to edit (repack) Zip Rom with replace boot_verified.img with img from magisk, and instal with SP multi port from official site, its error' on boot.img....
Any idea to verify signature boot_verified.img from magisk.???
Sorry for my bad English..
A Solution
Hi, popping in to say I had the same exact problem. After you enter fastboot through the command "adb reboot bootloader", go into device manager and look for Armor X5, right-click update drivers, and then select search for drivers online. It should automatically update with the adb driver.
( I also found the code at the end of the romprovider tutorial titled "How to create a prerooted patched boot.img with magisk" useful, although fair warning it did wipe my device clean )
My input
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Hi, on my side I am stuck in the same way because I found several versions:
- mt6762
- mt6763
i feel all twrp and magisk are for 6763.
Can you confirm which version you have?
Sorry but I'm stuck months too and I really need to root my phone ;-(
Pachacouti said:
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Click to expand...
Click to collapse
error for me too
you are win?
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Pachacouti said:
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Click to expand...
Click to collapse
Hello, I have the same phone, any news about rooting etc.. ?
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
bjlabuk said:
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
Click to expand...
Click to collapse
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Deleted link to unofficial twrp site
maxxvd said:
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Click to expand...
Click to collapse
You dont have same fone, you have mt6762, I have mt6765
This worked for me (am using a mac so my terminal lingo may be different)
Device: Ulefone X5 2019
Chipset MT6763
Processor: arm64-v8a, A-only system partition
Reset device
Enable developer options, USB debugging, and OEM unlock, then in terminal, do:
adb device
adb reboot bootloader
fastboot flashing unlock_critical
Device is now unlocked and reboots (unlocked warning now appears on reboot screen)
——
Then I installed TWRP & Magisk:
Re-enable developer options, USB debugging, and OEM unlock
To flash the TWRP recovery.img: Copy the TWRP recovery.img into the platform-tools folder, and from that folder, do:
adb reboot bootloader
fastboot flash recovery recovery.img
Then once finished, hold down the power and volume up buttons until it shuts down and restarts (restarts in TWRP recovery)
——
• Download the latest Magisk installer file and put it in the ADB (platform-tools) tools folder (or in your device storage)
• Inside TWRP, go to Advanced > ADB Sideload, then do adb sideload Magisk.zip (replace Magisk.zip with the Magisk zip filename )
Swipe the slider to install Magisk
Tap Reboot System
can anyone pls help with how to root the Lenovo TB-x306f
i already unlocked the bootloader but that's as far as i was able to go with it.
i want to also like to install a recovery to flash the evolutionx rom if someone can pls help me and others that needs the same help.
GOD BLESS
I second that. There's nothing out there.
What I tried was to download the original ROM patch the boot.img with magical, replace in LMSA download folder and start a rescue. Didn't help. Got boot loop.
Ok, maybe a bit more details on what I tried already:
1. Enabled developer options. Good.
2. OEM unlocked. ADB connected. Good.
3. Boot to bootloader working. Good.
4. fastboot not listing the device after fastboot devices. Not good.
5. Googling around, found an universal root method with Magisk. Good.
6. Donwloaded, installed and ran RSA (Lenovo Rescue and Smart Assistant). Connected to device. Good.
7. Entered Rescue and using that downloaded the original ROM. Good.
C:\ProgramData\LMSA\Download\RomFiles\TB_X306F_S100134_210120_BMP
8. Copied boot.img to device, installed MagiskManager, patched image with magisk, downloaded the image to PC, replaced the original boot image with the patched one. Good.
9. Started the Rescue procedure in RSA. Rom flased. Good.
10. Bootloop. Bad.
No idea why would that not work, any help, pointers, ideas appreciated.
EDIT: There's a new ROM version now: TB_X306F_S100152_210205_BMP
For a preface, I have the same Tablet as OP. I tried to unlock the bootloader, following seemingly every guide out there but, no success so far. I've enabled debugging, activated OEM unlock and, adb detects my device but, after I send it to fastboot (adb reboot bootloader), no more commands work. I've updated the driver in Manager as one guide suggested but, still nothing.
I used command (fastboot OEM unlock) to continue but nothing. What am I doing wrong?
So just a tip for those that are looking for a guide to do a complete bootloader unlock for TB-X306F, there isn't one. I found a bunch of different ways to go about unlocking the bootloader from different Lenovo devices. First thing is that you need Minimal ABD Fastboot v1.4.3 if Platform Tools or LeTools doesn't work. Use CMD with admin rights, not PowerShell.
Everything else to unlock it is the same from all the guides out there. Make sure to use "fastboot flashing unlock" when unlocking instead of "fastboot oem unlock" or "fastboot oem unlock-go" if they dont work.
Second tip is for root when installing the Magisk patched boot image. While you're getting the boot.img, make sure to also grab the vbmeta.img from the ROM folder and place it in the Minimal ADB Fastboot folder where you will be using CMD. Do all the steps to get the patched boot image. Once you got the boot.img patched, enter fastboot then enter the command "fastboot --disable-verification flash vbmeta vbmeta.img" This will disable verification needed to boot correctly. After that, enter the command "fastboot flash boot <name of .img>" like normal to flash the patched boot.img from magisk. Then fastboot reboot.
This is what I did to get my TB-X306F unlocked and rooted. YMMV.
Different threads that I read to get to where I got, credit goes to them:
LENOVO Tab M10 Plus
After receiving my LENOVO Tab M10 Plus TB-X606F I tried to root my tablet. my Firmware version is TB-X606F_RF01_200103 - loaded the Lenovo Rescue and Smart Assistant (V5.0.0.25) - enabled OEM unlock - downloaded magisk - installed ADB now my...
forum.xda-developers.com
Lenovo M10 HD 2nd Gen X306F boot loop if boot.img is patched - android 10 · Issue #3832 · topjohnwu/Magisk
I recently installed magisk manager and extracted the boot.img from tb-x306f_rf01_200926 upon doing a fastboot flash boot magisk_patched.img , the machine goes into a boot loop. Am I doing somethin...
github.com
TWRP for LENOVO Tab M10 FHD - TB-X606F?
Hello, Possessing two tablets of this brand, I was wondering if a custom recovery existed for this one, I can look everywhere on all the forums, Russian, English, etc ... But, I do not find. If anyone can create one with this SOURCE CODE from...
forum.xda-developers.com
Lenovo tab m8
Hello, Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer.. Thanks :) :)
forum.xda-developers.com
By any chance can u pls.... Make a video on the steps u explained including on where to get that file needed. Pls thank u and GOD BLESS YOU. If u can find the time to do it .
I apologize for asking for so much help on this.
I too would very much care to see a video of the process but, I have no problem trying it first hand to myself. This tablet is just weird. It can be detected but, as soon as I boot into fastboot, it can't pick it up anymore even though, I had grabbed all of the recommended tools so far such as the fast Boot and the bundle.
A detailed guide would be good enough too
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
I don't get around to checking my email as often as I used to so I just now got around to seeing this but, I will try this after I get home from work in 10 hours plus time. If I can get this to successfully work, I will be flat out amazed. I had gotten to the point where I had just given up any and all hope that I would get it to work.
Show
Chairos said:
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
Click to expand...
Click to collapse
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
* I have the TB-X306F***
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
I got it for free for online classes but that's not the problem twrp is out for this device unofficialy but many say that it works, anyways good luck on u mate I gave up on rooting this device I can't do it anymore I've been trying for 4 months but nothing still if I had the Chance and the correct guide I would definitely do it
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
Make sure you have the latest MTK usb drivers.
Hello Everyone,
I apologize for the delay but I didn't get notified of your replies.
I also got the waiting for device problem, but as @Yahoo Mike says, it's the MTK USB drivers that are used to communicate with the device in fastboot mode. Latest drivers should do.
Let me know if you're still experiencing the problem after installing the latest MTK drivers, since it depends on which motherboard the tablet has but all models should use mediatek.
Worked like a charm! Thanks.
Can anyone please confirm if there is a TWRP even unofficial IMG out there? And if any kind soul could share the file too I would be so grateful thanks
worked beautifully ...
just the installation of the latest MTK drivers is not very typical. however, you can follow this guide to install MTKL drivers and disable the driver signature enforcement
Download MTK USB Drivers for Windows 11, 10 - Driver Easy
To flash files to your MediaTek chipset phones, you need to have the latest MediaTek drivers installed. We'll show you how to install the MTK driver easily.
www.drivereasy.com
When you Restart: go to Advanced Options to find the Driver Signature Disablement option
I received yesterday my TB-X306X, with Android 10 and with software version S100184_210325_BMP. First thing to do was to unlock and root the tablet, without any issue, thanks to clear indications found on this thread.
Has anybody been able to find working TWRP for this tablet ?