1.
I unlocked the bootloader following the Russians tutorial at http://lenovo-forums.ru/topic/22665-lenovo-phab-2-pro-razblokirovka-bootloader-by-sevenmaxs/
YOU DO NOT NEED TO DISABLE SECURE BOOT, only do the step in that tutorial about how to unlock the bootloader.
Google translate does a good enough job with that page, ask here if stuck.
See post below for English translation on how to unlock the Bootloader.
2
After unlocking bootloader you can load TWRP without actually installing it with fastboot, see https://forum.fairphone.com/t/howto-use-twrp-without-flashing-it-e-g-for-backup/23747
Get TWRP https://drive.google.com/open?id=0B4WxcwjxK2VnZ0tWSl9wUTVoaTg
When you are in this temporary recovery you need to wipe data, this REMOVES ENCRYPTION! yay! :good:
(DO NOT REBOOT! Rebooting would just generate a new encryption key and you would have to repeat this step.)
Then in the same recovery you will be able to mount internal storage, put the SuperSU.zip file on your device and flash it in TWRP.
Congratulations, you are rooted!
3.
To install then TWRP permanently just usual fastboot flash recovery twrp.img
You are done! :highfive:
Get QPST Flash tool, install the Lenovo and Qualcomm USB drives that come with it aswell.
https://drive.google.com/open?id=0B4WxcwjxK2VnM2pvRDk0VzZLVWs
Download the PB2-690M unlock attachmet from this post and unpack it to the root of your drive, aka directly in C:\PB2-690M unlock
Connect your phone by USB, make sure USB debugging is on and your pc is authorised.
Now run the QFIL tool from step 1, in the upper left corner select flat build
In the Select Programmer line, click on the Browse button and specify the path to the unpacked file \ PB2-690M_unlock_7M \ img \ prog_emmc_firehose_8976.mbn
Click on the Load XML button and select rawprogram0.xml first, and then patch0.xml
Run Reboot_QDLoader.bat .
In Windows device manager you should see a device "Qualcomm HS-USB QDLoader 9008" under COM Ports if all is good.
In QFIL click "Download" to execute, should say Download Suceed, Finish Download if it all went well.
Now disconnect the USB cable, power on the device (might have to hold power for a bit) and re enable USB debugging and allow OEM Unlock if needed.
Connect cable again, allow your PC for USB debugging on the device, and run Unlock_Bootloader.bat
The device should reboot to bootloader, and then reboot again to a screen with the Android robot, THIS WIPES YOUR DATA!
That's it, you have unlocked your bootloader! Congratulations!
Yes. Good job.
Mhhh... If something goes wrong, how can we restore the stock firmware? I can't found the last version.
Lenovo often disable the server of ota (i saw that on lenovo's forum).
Maybe a guide for restore can be useful too.
Anyway thank you very much.
vespino75 said:
how can we restore the stock firmware? I can't found the last version.
Click to expand...
Click to collapse
At the moment you need go to russian forum here http://lenovo-forums.ru/topic/23342-proshivka-phab-2-pro-pb2-690m_s200100_170228_row_qpst/ and here https://cloud.mail.ru/public/2B9M/3uV5oLdB1
Sorry. You must know russian or wait/ask for translate.
Elemy said:
At the moment you need go to russian forum here http://lenovo-forums.ru/topic/23342-proshivka-phab-2-pro-pb2-690m_s200100_170228_row_qpst/ and here https://cloud.mail.ru/public/2B9M/3uV5oLdB1
Sorry. You must know russian or wait/ask for translate.
Click to expand...
Click to collapse
Sorry, i am an idiot. This is the last firmware version.
Sorry.
Exelios said:
RESERVED
I will translate the russian tutorial and add a more step by step guide as soon as I have time, this for now should let advanced users do their thing.
Click to expand...
Click to collapse
Pardon. Is it actual?
Can someone who didn't unlock the bootloader yet try step 2? Can you fastboot boot twrp.img with locked bootloader?
I'm really curious
Exelios said:
Can someone who didn't unlock the bootloader yet try step 2? Can you fastboot boot twrp.img with locked bootloader?
I'm really curious
Click to expand...
Click to collapse
Code:
C:\Users\Administrator\Downloads\PB2-690M_unlock_7M\tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4072000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xceb7fbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) serialno:c9a7e83e
(bootloader) kernel:lk
(bootloader) product:MSM8952
all:
finished. total time: 0.016s
I assume because of "(bootloader) secure:yes" that my bootloader is locked.
Tried to boot "twrp-lenovo-tango.img" from your post#1 section 2
Code:
C:\Users\Administrator\Downloads>PB2-690M_unlock_7M\tools\fastboot.exe boot twrp-lenovo-tango.img
downloading 'boot.img'...
OKAY [ 0.563s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.563s
So i guess bootloader unlock is inevitable.
google translate of h**p://lenovo-forums.ru/topic/22665-lenovo-phab-2-pro-razblokirovka-bootloader-by-sevenmaxs/
[russian]->[german] = horrible
[russian]->[english] = somehow understandable
but this is the result of my testing:
Code:
Programmer Path:C:\PB2-690M_unlock_7M\img\prog_emmc_firehose_8976.mbn
Image Search Path: C:\PB2-690M_unlock_7M\img
RAWPROGRAM file path: C:\PB2-690M_unlock_7M\img\rawprogram0.xml
PATCH file path:C:\PB2-690M_unlock_7M\img\patch0.xml
Start Download
Program Path:C:\PB2-690M_unlock_7M\img\prog_emmc_firehose_8976.mbn
Download Fail:Sahara Fail:QSaharaServer Fail:Der Verzeichnisname ist ungültig
Finish Download
SaharaServer Fail... at this point i have absolutely no **** clue what i'm doing
and i violate the rule set in the second sentence of the russian guide:
"You must understand what you are doing! "
i hope you find the time to write an foolproof guide, since i found only wrong and misleading information about rooting my phone...
Greetz
oRG4ZMo
----------------------------------------------------------------------
edit:
after reviewing all steps i've found the solution for my QFIL error.
In the russian thread is an older version linked:
QPST_&_Drivers.7z
contains QFIL 2.0.0.4 not 2.0.0.5 like on the provided screenshots.
Now i'm stuck at the same step like "pancx 0" from post #6 in the russian thread. :/
i finally got my bootloader unlocked and magisk installed after hours of studying lenovo-forums.ru
this is what i did:
switch from a Windows 2016 Server Workstation to a fresh installed Win 7 x64 on another PC
driver install order:
- phone factory reset
- enable usb debugging
- LenovoUsbDriver_autorun_1.1.33_user.exe from the emulated CD-Drive of the Phab2Pro
- installed newest QPST.2.7.460.zip
EFS Backup described here:
h**p://lenovo-forums.ru/tutorials/article/989-efs-%D0%BD%D0%B0-qualcomm-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0%D1%85-%D1%80%D0%B5%D0%B7%D0%B5%D1%80%D0%B2%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B2%D0%BE%D1%81%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5/
this seems to fix my error "System cannot find the file specified"
with patched boot partition works the command "fastboot oem device-info" (works now even on my other workstation without changing anything)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after that it is possible to boot TWRP Recovery img without flashing it "fastboot boot twrp-lenovo-tango.img" like described in your link - no problems.
and so on ...
sorry it's late again.
Greetz
oRG4ZMo
oRG4ZMo said:
i finally got my bootloader unlocked and magisk installed after hours of studying lenovo-forums.ru
this is what i did:
switch from a Windows 2016 Server Workstation to a fresh installed Win 7 x64 on another PC
driver install order:
- phone factory reset
- enable usb debugging
- LenovoUsbDriver_autorun_1.1.33_user.exe from the emulated CD-Drive of the Phab2Pro
- installed newest QPST.2.7.460.zip
EFS Backup described here:
h**p://lenovo-forums.ru/tutorials/article/989-efs-%D0%BD%D0%B0-qualcomm-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0%D1%85-%D1%80%D0%B5%D0%B7%D0%B5%D1%80%D0%B2%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B2%D0%BE%D1%81%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5/
this seems to fix my error "System cannot find the file specified"
with patched boot partition works the command "fastboot oem device-info" (works now even on my other workstation without changing anything)
after that it is possible to boot TWRP Recovery img without flashing it "fastboot boot twrp-lenovo-tango.img" like described in your link - no problems.
and so on ...
sorry it's late again.
Greetz
oRG4ZMo
Click to expand...
Click to collapse
I have one on the way and hopefully what you posted will help me get it rooted.
Do you have the 690m or the 690y?
You who? I have the 690m
ddubz said:
Do you have the 690m or the 690y?
Click to expand...
Click to collapse
Making a proper translation of the russian post today, sorry for the delay, working on 6 devices atm.
PS, Translation done, feel free to suggest edits if anything can make it easier.
Devs complaining English uncommented code is hard to understand
Me be like, hold my beer
Exelios said:
Get QPST Flash tool, install the Lenovo and Qualcomm USB drives that come with it aswell.
https://drive.google.com/open?id=0B4WxcwjxK2VnM2pvRDk0VzZLVWs
Download the PB2-690M unlock attachmet from this post and unpack it to the root of your drive, aka directly in C:\PB2-690M unlock
Connect your phone by USB, make sure USB debugging is on and your pc is authorised.
Now run the QFIL tool from step 1, in the upper left corner select flat build
In the Select Programmer line, click on the Browse button and specify the path to the unpacked file \ PB2-690M_unlock_7M \ img \ prog_emmc_firehose_8976.mbn
Click on the Load XML button and select rawprogram0.xml first, and then patch0.xml
Run Reboot_QDLoader.bat .
In Windows device manager you should see a device "Qualcomm HS-USB QDLoader 9008" under COM Ports if all is good.
In QFIL click "Download" to execute, should say Download Suceed, Finish Download if it all went well.
Now disconnect the USB cable, power on the device (might have to hold power for a bit) and re enable USB debugging and allow OEM Unlock if needed.
Connect cable again, allow your PC for USB debugging on the device, and run Unlock_Bootloader.bat
The device should reboot to bootloader, and then reboot again to a screen with the Android robot, THIS WIPES YOUR DATA!
That's it, you have unlocked your bootloader! Congratulations!
Click to expand...
Click to collapse
I think I am getting lost somewhere during line 10. My phone reboots and (I assume is in it's fastboot mode) I can do fastboot commands at the screen, it DOES NOT make it to the android robot screen. I let it set for a few minutes and nothing happens. It just stays on the Lenovo boot screen.
I did manage to do this and get it to say OK instead of FAILED. I did fastboot flash recovery instead of fastboot boot.
Thank you for your time.
Is support for exfat file system in this twrp?
I tried to backup to my exfat flash drive, but flash drive is unvisible.
Is support for exfat file system in this twrp?
finally! after 3 years with Galaxy Note 3,i got phab 2 pro and successfully rooted,i try to root it from yesterday..today i did it!
hello guys.
1. could someone create a new topic with clear steps and software needed for the bootloader unlock and root of our device?
2. are there any custom roms available for our device? audio lag in videos and some other staff are pretty annoying!!!
@Exelios: it would be much more user friendly if bootloader unlocking, rooting and installing twrp were in seperate topics so users with specific problems could find more direct help. just a suggestion
I finally got TWRP on the 690Y. After following the instructions in post #2, you'll need to do this. After doing the Windows-specific stuff, I rebooted back to Ubuntu, and installed the android-tools-adb and fastboot packages:
Code:
adb reboot bootloader
(wait a few seconds)
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
Note: the above commands might wipe your system and reboot again, in which case you have to go through the Lenovo setup, enable dev mode, enable USB debugging, etc all over again. I'm not sure that fastboot flashing unlock_critical is necessary.
After the reboot:
Code:
adb reboot bootloader
(wait a few seconds)
fastboot flash recovery twrp-lenovo-tango.img
fastboot flash recovery twrp-lenovo-tango.img
(I don't know if doing it twice actually matters)
Hold down power until it turns off
Contrary to the above posts, the correct combo to get into TWRP is Volume Up-Power. Once the phone vibrates, you can let go of Power, but keep holding Volume Up until the TWRP screen appears. Also, the very first thing you should do is hit the Select Language button and choose English, otherwise you're going to have a bad time!
Well, I was not smart and didn't back up first, but I got lucky. Thought I'd bricked it, but the problem was SuperSU. I got the "latest" from the internet, but that one is old. You must use this one: UPDATE-SuperSU-v2.79.zip
Related
<[???]> COMPATABILITY CHECK <[???]>{[>TWRP & OS<]}< Please Read & Comment!!!
Having problems with getting good files that are specific to my DEVICE, and my DEVICE SOFTWARE/VERSION..... Someone please help me understand what I'm doing wrong..?!?
:good::angel:THANKS VERY MUCH!!!:angel::good:
My Details As Follows;
Ok So I'm editing this post since I have had help with the first part, and I didnt want to flood the forums with a bunch of "noob" posts's. But I am not going to guess or assume I know what I'm doing. Especially considering the abundance of resources and knowledge everyone one these forums has already been kind enough to share with me... Ok so one or two more questions...
My Current Status
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3892mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Ok so I'm understanding that the "Recovery" Tools/Interfaces and the MD5sum are important to understand. What exactly am I Checking with the MD5sum?? Is there anything SPECIFIC I need to know about that in comparison to my "GETVAR ALL" Details? How am I able to tell if one or another is going to be COMPATIBLE with my SPECIFIC phone, or not?? Why so Many different Choices?
Then Im understanding the the "ROM/RUU" and the "Firmware" is what I'm going to execute AFTER the ^^recovery tools^^.... So if I'm understanding this right, once again How am I able to tell if one or another is going to be COMPATIBLE with my SPECIFIC phone, or not?? Why so Many different Choices?
My Main Concern is, I Don't want to FLASH/OVERWRITE anything on my phone with something that May OR May Not be compatible... Also I want to just confirm that I'm understading the order of operations, and the difference between RECOVERY and BACKUP as compared to OS/FIRMWARE/ROM/RUU... Theres so many different versions of everything I could download.. How do I know if it's going to work with my phone specifics.. And am I understanding the ORDER of the "operations" that I am trying to execute.
poolproj said:
Phone won't boot, cant mount sd card, cant access files for recovery, just all around TORTURE.. Now I feel like I shattered an already broken phone... Beyone Repair... Please help me understand.
I was able to get my phone to read **UNLOCKED**
I started the "recovery" part of his thread and started experiencing problems...
1) twrp seems to not work
2)flash recovery cannot load
PLEASE HELP!
Click to expand...
Click to collapse
Which version of TWRP did you try to flash?
Did you use the fastboot erase cache command right after you flashed the recovery?
Can you post a fastboot getvar all except remove your imei and serialno?
---------- Post added at 11:19 AM ---------- Previous post was at 11:07 AM ----------
poolproj said:
PLEASE HELP!
Click to expand...
Click to collapse
Did you check the MD5 of the TWRP file you downloaded? Based on your other post, it said it did not load. It may have been a corrupt download!
majmoz said:
Which version of TWRP did you try to flash?
Did you use the fastboot erase cache command right after you flashed the recovery?
Can you post a fastboot getvar all except remove your imei and serialno?
Click to expand...
Click to collapse
FASTBOOT GETVAR ALL
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3849mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
TWRP VERSION
4.18.502.7_ATT-WWE_FULL_STOCK.zip
After I tried the TWRP (I wasn't 100% confident that it had even installed) I then immediately wiped the cache. At that point my phone froze.. And So Did this Whole Process.
Now my CPU wont recognize my phone, and my CMD Prompt wont locate it when I use ADB. Although when I'm in fastboot mode it does work but it doesnt function in any way. I can hear my CPU alert when I connect and disconnect my phone, but the drivers dont install properly and I cant see my phone in the Device Manager.
I got through the unlock process fairly easily but now I'm stuck. I have downloaded so many diff things too... Just haven't tried anything crazy because I dont want to guess.
EXTRA/NECCESSARY?!? DOWNLOADS (Everything I have downloaded as of now)
Java Development Kit
Android Studio Bundle
HTC Sync Manager
HTCDriver_4.8.0.002 (not even sure if its real OR if I should even mess with it)
ADB
ADB Drivers
Fastboot
Unlock Code.bin
Not Sure What the MD5 File is? I see HDR and NB0
Thanks in Advance for your Time and Help. I hope I can figure this out.
poolproj said:
FASTBOOT GETVAR ALL
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3849mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
TWRP VERSION
4.18.502.7_ATT-WWE_FULL_STOCK.zip
After I tried the TWRP (I wasn't 100% confident that it had even installed) I then immediately wiped the cache. At that point my phone froze.. And So Did this Whole Process.
Now my CPU wont recognize my phone, and my CMD Prompt wont locate it when I use ADB. Although when I'm in fastboot mode it does work but it doesnt function in any way. I can hear my CPU alert when I connect and disconnect my phone, but the drivers dont install properly and I cant see my phone in the Device Manager.
I got through the unlock process fairly easily but now I'm stuck. I have downloaded so many diff things too... Just haven't tried anything crazy because I dont want to guess.
Click to expand...
Click to collapse
I don't think you flashed the recovery what you flashed is the firmware for an older version of your firmware. And if you erased the cache after that then you don't have a recovery installed or it is corrupted.
EXTRA/NECCESSARY?!? DOWNLOADS (Everything I have downloaded as of now)
Java Development Kit
Android Studio Bundle
HTC Sync Manager
HTCDriver_4.8.0.002 (not even sure if its real OR if I should even mess with it)
ADB
ADB Drivers
Fastboot
Unlock Code.bin
Thanks in Advance for your Time and Help. I hope I can figure this out.
Click to expand...
Click to collapse
Let's try this procedure to get you back up and running follow each step and when it is completed then move on to the next. :
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone any ways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didn't install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
majmoz said:
I don't think you flashed the recovery what you flashed is the firmware for an older version of your firmware. And if you erased the cache after that then you don't have a recovery installed or it is corrupted. Let's try this procedure to get you back up and running follow each step and when it is completed then move on to the next. :
Click to expand...
Click to collapse
Do I want to download the Drivers to the same folder as TWRP, Fastboot, ADB ...??
poolproj said:
Do I want to download the Drivers to the same folder as TWRP, Fastboot, ADB ...??
Click to expand...
Click to collapse
You can if you want, the drivers will be loaded directed to your PC.
majmoz said:
You can if you want, the drivers will be loaded directed to your PC.
Click to expand...
Click to collapse
Ok I got the drivers and everything working. My phone now appears in the device manager and CMD prompt.
The TWRP is just a recovery interface right?
How do I "CHECK" the MD5... What am I checking/comparing it to? Also should I download the MD5sum aswell?
So after I get it and flash it to my phone (assuming everything works that easily.. lol)
I would still need to download a Firmware or a SuperSU?!
Or what exactly will happen once I have this TWRP Recovery Installed & flashed to my phone...?
poolproj said:
Ok I got the drivers and everything working. My phone now appears in the device manager and CMD prompt.
The TWRP is just a recovery interface right?
How do I "CHECK" the MD5... What am I checking/comparing it to? Also should I download the MD5sum aswell?
So after I get it and flash it to my phone (assuming everything works that easily.. lol)
I would still need to download a Firmware or a SuperSU?!
Or what exactly will happen once I have this TWRP Recovery Installed & flashed to my phone...?
Click to expand...
Click to collapse
This post explains MD5: http://www.droidviews.com/check-md5sum-of-a-file-on-windows-mac-and-linux/
Firmware should already be installed on your phone
You can download and install SuperSU to give you "root"
With the custom recovery install you can flash custom roms and themes
If anyone knows anything about something please tell me everything.
I'm Still Having Issues, Any Feedback or Input would be greatly appreciated. I need the specific versions that are compatible with my phone and the software thats currently not working on my device.
Thanks!:angel:
poolproj said:
If anyone knows anything about something please tell me everything.
I'm Still Having Issues, Any Feedback or Input would be greatly appreciated. I need the specific versions that are compatible with my phone and the software thats currently not working on my device.
Thanks!:angel:
Click to expand...
Click to collapse
What are you trying to accomplish? Custom Rom? Custom Recovery? Root? Unlock Bootloader?
You have an AT&T phone with what I believe is the latest software, so what do you want to put on the phone or what do you want the phone to do that you can not do already?
What issues are you having that can be addressed?
majmoz said:
What are you trying to accomplish? Custom Rom? Custom Recovery? Root? Unlock Bootloader?
You have an AT&T phone with what I believe is the latest software, so what do you want to put on the phone or what do you want the phone to do that you can not do already?
What issues are you having that can be addressed?
Click to expand...
Click to collapse
I have the TWRP and It is unlocked, but it wont boot.. I see the HTC startup screen then after that it just turns black.. I just want it to work like an Android Phone, doesn't have to be custom, but I just want it to turn on and load up so I can place calls, use data, and message... I guess I need the android software? or what... ?!? I couldn't get the SuperSU to flash, but I'm not even sure if I need that... I dont believe I'm trying to "root"... I think I'm just trying to actually Have ANY OPERATING SYSTEM?? It's confusing and wearing me out already.. Lol
Thanks So Much For Your Time! :good::good:
poolproj said:
I have the TWRP and It is unlocked, but it wont boot.. I see the HTC startup screen then after that it just turns black.. I just want it to work like an Android Phone, doesn't have to be custom, but I just want it to turn on and load up so I can place calls, use data, and message... I guess I need the android software? or what... ?!? I couldn't get the SuperSU to flash, but I'm not even sure if I need that... I dont believe I'm trying to "root"... I think I'm just trying to actually Have ANY OPERATING SYSTEM?? It's confusing and wearing me out already.. Lol
Thanks So Much For Your Time! :good::good:
Click to expand...
Click to collapse
Install TWRP 2.6.3.3, if not already
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Download and flash in TWRP Guru Reset 5.12.502.2. Follow the instructions in the OP.
This will put you back at stock if you choose to install the stock recovery.
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
EDIT - I sort of solved it myself in post #7
sminki said:
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
Click to expand...
Click to collapse
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
piskr said:
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
Click to expand...
Click to collapse
Not on these. That the first thing I tried. That gives
Code:
FAILED (remote: Command not allowed)
Which is essentially "command not found", as you can pass it any garbage and that's what it gives back.
As I see it, you can't install updates with an unlocked bootloader (unless I'm wrong, or there is something desperately wrong with my phone). With no custom roms (at the moment) this is all we have
EDIT:
Looks like I was wrong about updates on unlocked bootloader. I went back to B100 (UK) then back up to B121
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
t-ph said:
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
Click to expand...
Click to collapse
I haven't retried yet. I was still in my 14 day return period and was undecided if I was going to keep the phone
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried it on B100?
Have you tried it on B140?
Have you tried "oem lock" instead of "oem relock"?
Note: Always mention your model number in your thread title and description. Not all different models behave the same and not all updates give the same error message.
Thank you for opening this thread. We hope to read your answers on the above questions to help you.
kenshiwara said:
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried "oem lock" instead of "oem relock"?
Click to expand...
Click to collapse
I have the EU Version PLK-L01 16GB
..and yes I had, see my second post - lock doesn't seem to be a valid Huawei boot-loader command.
I've had a busy and incredibly boring time trying to sort this out.. Somehow, I re-locked :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unfortunately from the point of view of returning the device to Huawei, Re-locked is not the same as Locked, but it's all I have found.
After TWRP format:
Code:
sudo fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: images signature check fail)[/COLOR][/B]
finished. total time: 1.048s
After B100 Downgrade:
Code:
fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: root type is risk)[/COLOR][/B]
finished. total time: 0.970s
I re-flashed the UserData image from B100, after booting up I got this:
After UserDate Wipe:
Code:
fastboot oem relock 1111111111111111
...
OKAY [ 1.985s]
finished. total time: 1.985s
fastboot oem get-bootinfo
...
(bootloader) [COLOR="Green"]relocked[/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
So basically, I re-locked with a completely fresh, untouched system and a "factory" wiped data partition.
Obviously I have unlocked again and gone back to B140. If someone else want to experiment, feel free to post your results. I'm done with this :silly:
Re-lock your bootloader successfully
Re-lock your Honor 7(PLK-L01)'s bootloader successfully
No matter on which version you are and on which recovery, follow the steps:
1. Extract the B100 "UPDATE.APP" using this tool. Credit goes to its maker. If you wanna make flashable zip from "UPDATE.APP" then use the attached "Profiles.xml" file for HuaweiUpdate Extractor, me and @kenshiwara has added Honor 7 in the list.
2. Now flash "boot.img", "recovery.img", "cache.img", "cust.img", "system.img", "userdata.img" from the extracted B100 "UPDATE.APP" by executing following commands in "Command Prompt"
Make sure you are in the same folder where all these files are then "Right click" inside the folder by holding down "Shift", then select "Open command window here".
For "boot.img"
Code:
fastboot flash boot boot.img
For "recovery.img"
Code:
fastboot flash recovery recovery.img
For "system.img"
Code:
fastboot flash system system.img
For "cache.img"
Code:
fastboot flash cache cache.img
For "cust.img"
Code:
fastboot flash cust cust.img
For "userdata.img"
Code:
fastboot flash userdata userdata.img
Now reboot your device by executing this command
Code:
fastboot reboot
3. Setup your device, then place B100's "UPDATE.APP" in your external SDCARD in "/dload" folder.
4. Now, switch off your device and press the three button combo to flash the B100 "UPDATE.APP", the three button combo is "Vol. Up", "Vol. Down" and "Power Button" press these three simultaneously to flash the B100 "UPDATE.APP".
5. After your device reboots and after you are done setting it up, go to "Settings > Backup & Reset", then select "Factory data reset", tick "Internal Storage" and press "Reset Phone".
6. Again after rebooting, switch off your device then by pressing "Vol. Down" button connect your device with PC.
7. Now, you'll be in "Fastboot&RescueMode" and your device status will be "Phone Unlocked".
8. Execute the following command to relock your device.
Code:
fastboot oem relock *16 digit unlock code*
9. Now, you'll see that your device status is changed to "Phone relocked".
So, you just relocked your Honor 7.
So basically what I said then
sminki said:
So basically what I said then
Click to expand...
Click to collapse
I think you just flashed "userdata.img" of B100 which is not good as it broke your "/userdata" partition, but yea basically that
DigiGoon said:
8. Execute the following command to relock your device.
Code:
fastboot relock *16 digit unlock code*
Click to expand...
Click to collapse
are you sure? i thaught it was
Code:
fastboot [B]oem[/B] relock *16 digit unlock code*
non-toxic said:
are you sure? i thaught it was
Code:
fastboot relock [B]oem[/B] *16 digit unlock code*
Click to expand...
Click to collapse
Thank you for pointing that out.
speaking as the man who has, you're both incorrect
Code:
fastboot oem relock *16 digit unlock code*
sminki said:
speaking as the man who has, you're both incorrect [emoji14]
Code:
fastboot oem relock *16 digit unlock code*
Click to expand...
Click to collapse
You should've checked my answer before stating that I'm incorrect too. And yeah check its last edit too, its not edited after your reply.
Sent from my PLK-L01 using Tapatalk
i'm not well
my humble apologies @DigiGoon
I have try "fastboot oem relock *my code*" and it works. But i had changed nothing on my phone. it was just unlocked.
no root; no TWRP; no other updates
maybe this was the reason why.
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Hello,
i can`t relocked my phone.
FAILED (remote: root type is risk).
My Honor 7 has the Firmware B330.
I think i tried everything but i always have the same error.
What can is the newest solution?
what's the point of relocking the bootloader?
hachuwaka said:
what's the point of relocking the bootloader?
Click to expand...
Click to collapse
I want to know too. Is there any risk to keep unlocked the bootloader on non rooted device?? Except guarantee
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Sandnes74 said:
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Click to expand...
Click to collapse
You will receive updates but do not install them!!!! If you don't listen to me your device will be caught in bootloop
Sent from my PLK-L01 using XDA-Developers mobile app
If you connect your phone to the pc and see something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for you
What you will need:
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)
2. Windows
3. The device defined somehow Device Manager
4. The latest version of MiFlash
5. MIUI firmware developer for fastboot here
6. Adb and fastboot installer here
Theory:
If the primary boot loader (placed directly on the SoC - unkilled) can't pass control to the secondary and applied loader, the interface starts to restoration device: 9006 or 9008 mode. They differ in that the 9006 mode if the device gets lost only access to the application Loader (what we call the fastboot). It all sections of the devices are mounted in the OS and we can edit files on them or record RAW data.
In 9008 mode, you can get into if partition and entire chain bootloader (secondary and applied loader) is dead. From it anything useful we can not do: just go back to the 9006 mode (in fact in this case, have access to a low-level operations, but to describe them does not make sense). For this purpose, the device is sent to the programmer (MPRG8974.mbn) flash secondary loader (8974_msimage.mbn), after which the smartphone reboot in 9006 mode.
Restore stock partion
Add a flash-all.bat line
Code:
fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
just before
Code:
fastboot% * flash tz% ~ dp0images \ tz.mbn
and flash device via fastboot.
Then u can flash again but w/o fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
If device hangs on Mi logo and cant flash via fastboot / problems after re-partition / defined as QHSUSB_BULK
If you touched anything from the name of the spoiler and the previous instruction does not help, then our task will be to move into 9006 mode (if your smartphone is already defined as QHSUSB_BULK, you can go directly to the firmware).
On a device located in fastboot write in the console:
Code:
fastboot erase aboot
fastboot reboot
View attachment 3590163
Phone will remain a black screen in the Device Manager, the new device will be Qualcomm HS-USB Diagnostics 9006/9008, and Windows about 7 new flash devices. Simply close all offers their formatting. Reboot the PC (required on Windows 10, or sections will not be able to unmount when flash).
MiFlash Run as Administrator, click the button "Refresh", this will be a new device like this
View attachment 3590164
Choose the folder with the firmware, click the button "Flash". After ~ 160 seconds, the firmware is completed, to restart, hold the power button.
View attachment 3590165
If in MiFlash nothing appeared
1. Make sure that the device appears in the Device Manager, if not:
1) Connect the USB cable to the motherboard (ie "behind")
2) Put the device on charge for at least two hours and try again
Device in 9008 mode
Here things can be a little tricky, but it depends only on your particular case.
It may be necessary short-circuit test points
Possible errors in MiFlash
EE: Access is denied. (0x80070005: Dismount volume ...)
AA: Restart your laptop, connect the device to a different usb port
EE: Reached the end of the file. (0x80070026: Receiving hello packet)
AA: Need a short-circuit of the test-points, change the cable, use a different computer
Contributor
nikitaklsnkv2000
Original source
4pda
Thanks for the tip ramm...
Dr. Ramm said:
If you connect your phone to the pc and see something like this
View attachment 3590142View attachment 3590143
This guide is for you
What you will need:
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)
2. Windows
3. The device defined somehow Device Manager
4. The latest version of MiFlash
5. MIUI firmware developer for fastboot here
6. Adb and fastboot installer here
Theory:
If the primary boot loader (placed directly on the SoC - unkilled) can't pass control to the secondary and applied loader, the interface starts to restoration device: 9006 or 9008 mode. They differ in that the 9006 mode if the device gets lost only access to the application Loader (what we call the fastboot). It all sections of the devices are mounted in the OS and we can edit files on them or record RAW data.
In 9008 mode, you can get into if partition and entire chain bootloader (secondary and applied loader) is dead. From it anything useful we can not do: just go back to the 9006 mode (in fact in this case, have access to a low-level operations, but to describe them does not make sense). For this purpose, the device is sent to the programmer (MPRG8974.mbn) flash secondary loader (8974_msimage.mbn), after which the smartphone reboot in 9006 mode.
Restore stock partion
Add a flash-all.bat line
Code:
fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
just before
Code:
fastboot% * flash tz% ~ dp0images \ tz.mbn
View attachment 3590159
and flash device via fastboot.
Then u can flash again but w/o fastboot% * flash partition% ~ dp0images \ gpt_both0.bin
If device hangs on Mi logo and cant flash via fastboot / problems after re-partition / defined as QHSUSB_BULK
If you touched anything from the name of the spoiler and the previous instruction does not help, then our task will be to move into 9006 mode (if your smartphone is already defined as QHSUSB_BULK, you can go directly to the firmware).
On a device located in fastboot write in the console:
Code:
fastboot erase aboot
fastboot reboot
View attachment 3590163
Phone will remain a black screen in the Device Manager, the new device will be Qualcomm HS-USB Diagnostics 9006/9008, and Windows about 7 new flash devices. Simply close all offers their formatting. Reboot the PC (required on Windows 10, or sections will not be able to unmount when flash).
MiFlash Run as Administrator, click the button "Refresh", this will be a new device like this
View attachment 3590164
Choose the folder with the firmware, click the button "Flash". After ~ 160 seconds, the firmware is completed, to restart, hold the power button.
View attachment 3590165
If in MiFlash nothing appeared
1. Make sure that the device appears in the Device Manager, if not:
1) Connect the USB cable to the motherboard (ie "behind")
2) Put the device on charge for at least two hours and try again
Device in 9008 mode
Here things can be a little tricky, but it depends only on your particular case.
It may be necessary short-circuit test points
Possible errors in MiFlash
EE: Access is denied. (0x80070005: Dismount volume ...)
AA: Restart your laptop, connect the device to a different usb port
EE: Reached the end of the file. (0x80070026: Receiving hello packet)
AA: Need a short-circuit of the test-points, change the cable, use a different computer
Contributor
nikitaklsnkv2000
Original source
4pda
Click to expand...
Click to collapse
Thanks man u are truly
Savior of mine MI4
Thanks a lot
Tell me how to flash fastboot rom on extended partition... My device got bricked when I tried to flash miui7 mm on extended using twrp....plz help
Nice share bro. Thanks
mad-extrem said:
Tell me how to flash fastboot rom on extended partition... My device got bricked when I tried to flash miui7 mm on extended using twrp....plz help
Click to expand...
Click to collapse
There is no difference between stock or extended partition, in flashing fastboot rom using MiFlash! It will recreate whole partition table!
Just follow steps in OP
Inviato dal mio D6633 utilizzando Tapatalk
mad-extrem said:
Tell me how to flash fastboot rom on extended partition.
Click to expand...
Click to collapse
U mean MM merged partition? IDK, which error show MiFlash?
If error: 0x80004005: FAILED (remote partition table doesn't exist).
then use this tutorial
Bricked my Mi3 and seeing lots of drive when connected to PC. trying to follow this guide.But link to download "MiFlash" not working. any Mirrors ?
EDIT : Solved it using this Guide.. Thanx a lot !!!!
It worked, thanks allot
Sir, I have bricked my mi3. I am not actually understanding how to follow this tutorial..Please give me some help...
vaski123 said:
Sir, I have bricked my mi3. I am not actually understanding how to follow this tutorial..Please give me some help...
Click to expand...
Click to collapse
What do you not understand?
You have to flash a fastboot rom, with MiFlash, that will re-build partition table
Inviato dal mio D6633 utilizzando Tapatalk
That will erase internal stoarge (sd card too). I lost everything on stored on it.. ?
i have my mi4 stuck on fastboot mode, and every time i try to flash a rom with miflash it shows the message "remote partition table doesn´t exist" y have tryed your method but it didnt fix the problem. Do you know why?
marlo125 said:
i have my mi4 stuck on fastboot mode, and every time i try to flash a rom with miflash it shows the message "remote partition table doesn´t exist" y have tryed your method but it didnt fix the problem. Do you know why?
Click to expand...
Click to collapse
Check post #7, if you read all (just less than 2 pages) you could find the solution by yourself.
Inviato dal mio D6633 utilizzando Tapatalk
Thank you for you sharing your knowledge I am very grateful I ran into this post and was able to repair my mi3. :good:
thanks sir, you saved ma life,thanks once again
You are my saviour
thanks for tutorial
a.broken.star said:
Bricked my Mi3 and seeing lots of drive when connected to PC. trying to follow this guide.But link to download "MiFlash" not working. any Mirrors ?
EDIT : Solved it using this Guide.. Thanx a lot !!!!
Click to expand...
Click to collapse
hey could you or anyone else help me with this...i bricked my phone and not able to boot into recovery and fastboot mode..its just completly dead...i am downloading miflash and fastboot room for my device[mi3]...plz help
Sir I Have followed your instructions because my problem is having having a Partition does not exist error in mi flash. i was already in the MiFlash step when suddenly the there was an error Access Denied and i keep receiving an error saying USB not recognized. Please help me any workaround Sir my mi3 no longer turns on and it no longer detected to a computer
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Nice find!
No DRM crap or anything that would cause some features to be lost (stopped working) after unlocking bootloader?
I'm Sony user btw and had already lost DRM and some of its features, including camera that didn't work on older ROM version XD
Thanks, I just ordered the phone because of this post.... Though I should probably have waited for the U20
Still, ive been jonesing for an HTC fix . I need this.
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Doesn't work for me... (Solution)
Mick_Rinelander said:
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Click to expand...
Click to collapse
Know it's working!
Don't use fastmode/Fastmoded Mode, it has to be done with CMD and bootloader startet!
Hello, friends on the fifth floor
Before using FastBoot flash unlock, you need to open OEM lock in developer mode now. You can try my way and give me a reply on how to unlock normally. I am looking forward to your reply
Mick_Rinelander said:
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Click to expand...
Click to collapse
Start CMD: adb reboot bootloader
then run
fastboot flashing unlock (for devices above 2015 y.)
If you still have this error, make sure if you have Correctly driver installed (must be Android bootloader interface) !!!!!!!!!!
Enjoy!!!
wpride77 said:
Start CMD: adb reboot bootloader
then run
fastboot flashing unlock (for devices above 2015 y.)
If you still have this error, make sure if you have Correctly driver installed (must be Android bootloader interface) !!!!!!!!!!
Enjoy!!!
Click to expand...
Click to collapse
Were you able to flash any GSI roms on your unlocked HTC Desire 20 Pro?
otack said:
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Click to expand...
Click to collapse
Were you able to flash any GSI roms on your unlocked HTC Desire 20 Pro?
i have one and im thinking of unlocking it
C:\Users\mypc>fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
Getting this error on my Itel A48 (L6006) running on android Q.......fastboot and adb drivers are installed and fastboot recognize my device
is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader can now be easily unlocked.Older get_identifier_token command is no more needed.
Instructions
Download HTC_Driver_v4.17.0.001 and install the package.
Download Google USB Driver. ( For installation information, read Install a USB Driver) .
To install the Android USB driver on Windows 10/11 for the first time, do the following:
Connect your Android device to your computer's USB port.
From Windows Explorer ( Search ), open Computer Management.
In the Computer Management left pane, select Device Manager.
In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
Right-click the name of the device you connected, and then select Update Driver Software.
In the Hardware Update wizard, select Browse my computer for driver software and click Next.
Click Browse and then locate the Google USB driver folder.
Click to expand...
Click to collapse
Connect your device to your computer and Backup device
( Get a complete backup of your contacts, messages, apps, and internal storage. Now usually, Enabling OEM unlock won’t erase the data on the device. But obviously, the eventual step after OEM unlock is bootloader unlocking, and that will wipe away everything on your device )
Download ADB. ( How to Install ADB on Windows, macOS, and Linux )
Enable OEM Unlocking
Open the settings on your phone.
Find the section that says “Developer options” and tap on it.
Scroll down till you find the option “OEM unlock”
Tap on it to turn the toggle on, and you are done.
Then simply run below command.
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
D:\android\Bat\com>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I've experienced error messages like this. OEM is unlocked in the developer mode, and the device is in bootloader also. Am I missed something?
elimiriel said:
D:\android\Bat\com>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I've experienced error messages like this. OEM is unlocked in the developer mode, and the device is in bootloader also. Am I missed something?
Click to expand...
Click to collapse
Yes you have problems with fastboot on your PC.
Btw OEM unlock wiped my data just to heads up.
otack said:
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Click to expand...
Click to collapse
Thanks mate!
I can confirm same strategy for the new Desire 21 pro 5G.
ToM
how unlock bootloader spd 9863a Android ver.11 realme c11
Hello, I need HELP! When I get to the "Google USB Driver" section I cannot proceed any further. When I open the update hardware wizard, I choose the folder that the Google drivers are in, and sadly, the drivers do not get installed to the device. The error reads "The best drivers for your device are already installed", preventing it from getting installed. I am using a Samsung Galaxy S21 that has an IMEI of a bunch of zeros (0).
Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?