<[???]> 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.
Related
Hello!
So since I had a sensation before the Amaze, I remembered that once we got S-Off, a next step was to obtain SuperCID on the phone. Basically, having SuperCID allows you to flash any ROM, regardless of which carrier it is for. Pretty handy if you have your phone SIM unlocked and wanted to use your Amaze on Wind Mobile or something. Anyway, the steps are from this thread (http://forum.xda-developers.com/showthread.php?t=1192300) and original credit goes to "xl VipeR lx" for the Sensation write up.
The usual warning goes here. I'm not responsible for what you do, use this at your own risk!
Required - You MUST have your phone S-Off from Juopunutbear's method first! Go here for that: http://forum.xda-developers.com/showthread.php?t=1611977
Also, if you've upgraded to ICS, the 1.93.0002 SHP Hboot is required to SuperCID!
--------------------------------------
ATTENTION:
It appears that the ICS update changes the firmware of the phone a bit. This means that using any bootloader other than SHP 1.93.0002 will remove your ability to write SuperCID to your device. This includes the ENG bootloader. It makes no different if you're locked/unlocked and S-OFF, the command doesn't work without being on the proper HBoot. Unfortunately, being on 1.93.0002 also removes your ability to flash partitions directly in Fastboot (ie. fastboot flash recovery, fastboot flash radio, etc) and you must revert to ENG 1.90.2005 in order to use fastboot flash commands.
--------------------------------------
The process is very simple and exactly the same as the Sensation and most S-Off HTC devices:
1. Command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
2. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings)
3. Enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
4. Enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
IF it doesn't you can Manually put the phone in the bootloader/hboot mode
Navigate to fastboot by pressing volume down and pressing power button to select (power off > vol down + power on)
It will take you to the fastboot bootloader screen on your phone
Connect your phone via USB
Your Screen should now read fastboot USB
5. Enter the command "fastboot oem writecid 11111111"
6. Enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
7. Enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
8. Enter the command "fastboot reboot"
9. You can now flash any ROM you like.
{
"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"
}
To remove SuperCID and return to stock CID:
1. Follow steps 1-4 for SuperCID
2. Enter the command "fastboot oem writecid __________" <--- Here you will put either T-MOB010 (T-Mobile), TELUS001 (Telus), GLOBA001 (Wind Mobile Canada)
3. Enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
4. Enter the command "fastboot getvar cid" [it should confirm your CID has changed]
5. Enter the command "fastboot reboot"
6. You are now back on stock CID (for your carrier)
****If you like the automated route, benjamminzIs has provided two batch files, one for SuperCID (for all devices) and one for reverting to stock (T-Mobile only). Place them in your SDK/tools folder and run them!****
I'll write two .bat scripts for you soon
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
I'll write two .bat scripts for you soon
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
If you are on another operator such as wind, you might want to do a "fastboot getvar cid" and take note of what your cid is, or even post it on here as a reference just in case anyone wants to revert.
hhilton said:
If you are on another operator such as wind, you might want to do a "fastboot getvar cid" and take note of what your cid is, or even post it on here as a reference just in case anyone wants to revert.
Click to expand...
Click to collapse
Thanks, updated. If anyone has a Wind device and knows what the CID is, I'll add it for reference.
benjamminzIS said:
done...
here: DOWNLOAD
place these in SDK/tools folder and run them...
Click to expand...
Click to collapse
Thanks, attached to main post with credit
Here are my scripts. No need to put it in the SDK folder. Just extract and run it!
electronicrice said:
Thanks, attached to main post with credit
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
benjamminzIS said:
use this version instead: http://www.mediafire.com/?igjxm0t3xv1u9y7 updated and now no need to extract to a certain folder, different method than hasoon's though as far as the script goes...
Click to expand...
Click to collapse
Basically the same. You just push the .CID rather than writing them.
hasoon2000 said:
Basically the same. You just push the .CID rather than writing them.
Click to expand...
Click to collapse
Drag n Drop SuperCID - UPDATED HERE!
benjamminzIS said:
use this version instead: http://www.mediafire.com/?igjxm0t3xv1u9y7 updated and now no need to extract to a certain folder, different method than hasoon's though as far as the script goes...
Click to expand...
Click to collapse
That's okay, I'm just using your original batch files with a couple prompt edits, and bundling it with ADB. Should work fine for the majority of people. Otherwise, people can use the other method you have linked as far as automation goes. The manual commands will always work.
electronicrice said:
That's okay, I'm just using your original batch files with a couple prompt edits, and bundling it with ADB. Should work fine for the majority of people. Otherwise, people can use the other method you have linked as far as automation goes. The manual commands will always work.
Click to expand...
Click to collapse
hey, it's your thread, I just figured since I had been making some drag and drop scripts for the splash screen, I may as well make this one just as simple... heh... I wasn't trying to step on anyones toes...
benjamminzIS said:
hey, it's your thread, I just figured since I had been making some drag and drop scripts for the splash screen, I may as well make this one just as simple... heh... I wasn't trying to step on anyones toes...
Click to expand...
Click to collapse
no not at all. everything's great here. we have s-off. mood couldn't be better. =]
Thanks for this post. Just for understanding - what does SuperCID do for the Amaze, that couldn't be done before?
Thanks, for reference
Code:
cid: TELUS001
For reference as well, Wind Mobile Canada
Code:
cid: GLOBA001
Worked like a charm Thanks
Opentang said:
Thanks for this post. Just for understanding - what does SuperCID do for the Amaze, that couldn't be done before?
Click to expand...
Click to collapse
Yeah it's in the OP but basically it allows you to flash to any carrier's official ROM for the Amaze. So if you have a T-Mobile Amaze and you wanted to flash the RUU for Telus or Wind, you can with SuperCID.
In the past, the RUU has to be hacked to allow a flash on a non-carrier specific device, and this allows you to bypass that entirely.
MentalDeath said:
Thanks, for reference
Code:
cid: TELUS001
Click to expand...
Click to collapse
idaggerpwn said:
For reference as well, Wind Mobile Canada
Code:
cid: GLOBA001
Click to expand...
Click to collapse
Great, thanks guys, updated the OP
updated the DnD_SuperCID here: DOWNLOAD. (PLEASE DON'T QUOTE THIS POST!!!)
This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
{
"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"
}
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here http://forums.team-nocturnal.com/showthread.php/3162
One more for future use
XsMagical said:
One more for future use
Click to expand...
Click to collapse
Appreciate your contrbution
Do this only if you want to change the partition 19 cid. We do not know why HTC has a cid there and we do not know why getprop ro cid shows it.
Right now there is no reason for it.
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
Worked perfect! Thank you sir. So I can go over to the Sprint forums and grab ViperRom per se and flash it to my AT&T version no problem?
Sent from my HTC One using xda app-developers app
Do we reckon this will work on HTC sensation xe??
Sent from my HTC Sensation Z715e using xda app-developers app
Does not work on my AT&T HTC one.....
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
hyelton said:
Does not work on my AT&T HTC one.....
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Click to expand...
Click to collapse
If your S-OFF all I did was boot to the bootloader
plug in phone usb wait for fastboot USB
then from PC where you have fastboot shift/right click cmd window here then run - fastboot oem writecid 11111111
reboot bootloader to see the change.
if you want to revert back to your carrier CID theirs a list of them here -> http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
clsA said:
If your S-OFF all I did was boot to the bootloader
plug in phone usb wait for fastboot USB
then from PC where you have fastboot shift/right click cmd window here then run - fastboot oem writecid 11111111
reboot bootloader to see the change.
if you want to revert back to your carrier CID theirs a list of them here -> http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
Click to expand...
Click to collapse
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
hyelton said:
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
Click to expand...
Click to collapse
this is what I used - I'm at&t
http://forum.xda-developers.com/showthread.php?t=2314582
I have already returned my CID to AT&T stock as I have no intentions of flashing a RUU anytime soon ..just waiting on ARHD 10.2 now
hyelton said:
Well here is my issue.... I just seen that it says for S-Off devices I swear it did NOT say that before.... How do I S-Off???? There is NO guide for the AT&T version just the international one.
Click to expand...
Click to collapse
The revone method works flawlessly with the AT&T version, that's what I used. Didn't try the other method so I don't know but revone definitely works.
barondebxl said:
The revone method works flawlessly with the AT&T version, that's what I used. Didn't try the other method so I don't know but revone definitely works.
Click to expand...
Click to collapse
Thats what I have been trying for the past HOUR!!!!
It fails everytime!
C:\sdk>adb push revone /data/local/tm
3413 KB/s (646704 bytes in 0.185s)
C:\sdk>cd /data/local/tmp
The system cannot find the path speci
C:\sdk>adb shell
[email protected]:/ # su
su
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod
chmod 755 revone
[email protected]:/data/local/tmp # ./revo
./revone -P
Failed (please reboot and try again!)
revone failed (error code = -6
250|[email protected]:/data/local/tmp #
hyelton said:
Thats what I have been trying for the past HOUR!!!!
I cant get past step 1... I can do ADB shell, Then ADB devices to make sure the device is there and it SHOWS UP, Then I do adb push revone /data/local/tmp/ and BAM no devices found...
SO now what??
Click to expand...
Click to collapse
Here is a video tutorial. Its not the best video around as the guy was trying to do it for the first time as well but it will help you. Make sure you make the youtube video 720p or 1080p full screen otherwise you wont see sh*t. Do the same hing as he does and pause the video when you need to. If you have more question you can pm me.
http://www.youtube.com/watch?v=YYb_Cz5rPIU
hyelton said:
Thats what I have been trying for the past HOUR!!!!
Click to expand...
Click to collapse
are you on a stock kernel ? you can also do it from the device itself
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
hyelton said:
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
Click to expand...
Click to collapse
error -6 means your not on stock kernel ?
hyelton said:
Well not really needing a tutorial I know how to read how to do it haha, but I`m doing exactly what its saying and it just asks to reboot and do it all over aginn
Click to expand...
Click to collapse
Keep trying, the tutorial says if it doesn't go through reboot and keep trying. Worked for the 1st attempt for me but others had to try several times.
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
hyelton said:
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
Click to expand...
Click to collapse
Are you SuperCID ?
did you use this script or the fastboot commands ?
hyelton said:
GOT IT!! Used another PC and rebooted phone, Not sure why my Beast Rig was causing issues. (Prob Windows 7) haha.
Click to expand...
Click to collapse
Congrats! Now get Super CID.
Hello,
I need the help of the XDA community. I'm very new to Android and Ive gotten myself in quite a bit of trouble.
I rooted my phone recently and decided to unroot the phone in order to trade with another user. In the process, my phone is wiped clean, and attempting to use RUU has left me relocked with S-On. I currently have no OS on the device. Attempting to run RUU gets no results, as I am met with Error 155 before I get any progress when the phone starts the "Sending" process. My phone will go into bootloader and it is recognized as a fastboot device by my PC, but not as an ADB device. I have the info from my bootloader menu below.
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
OS-5.12.502.2
My phone is an AT&T HTC ONE M7, 32 GB. I am at a loss and I've tried researching. Any help would be greatly appreciated.
Thanks
Juice Jones said:
Hello,
I need the help of the XDA community. I'm very new to Android and Ive gotten myself in quite a bit of trouble.
I rooted my phone recently and decided to unroot the phone in order to trade with another user. In the process, my phone is wiped clean, and attempting to use RUU has left me relocked with S-On. I currently have no OS on the device. Attempting to run RUU gets no results, as I am met with Error 155 before I get any progress when the phone starts the "Sending" process. My phone will go into bootloader and it is recognized as a fastboot device by my PC, but not as an ADB device. I have the info from my bootloader menu below.
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
OS-5.12.502.2
My phone is an AT&T HTC ONE M7, 32 GB. I am at a loss and I've tried researching. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
My guess you tried to run a RUU of a lower version than what is on your phone that is why you got the error 155. ADB does not work if there is no OS because it needs USB Debugging enabled in the OS but it works with a custom recovery like TWRP. Download the Guru Reset 5.12.502.2 and push it to your phone with the following procedure:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
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 anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt 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
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
majmoz said:
My guess you tried to run a RUU of a lower version than what is on your phone that is why you got the error 155. ADB does not work if there is no OS because it needs USB Debugging enabled in the OS but it works with a custom recovery like TWRP. Download the Guru Reset 5.12.502.2 and push it to your phone with the following procedure:
Click to expand...
Click to collapse
So I attempted to follow your instructions, got my bootloader unlocked and TWRP installed. Got the Guru Reset pushed onto my phone storage. Now I'm getting an error when trying to install. "Error Flashing zip" "E: Unable to mount '/cache' " "E: Unable to mount '/data/ " "E:Unable to mount storage. "
Not sure where to go from here.
Juice Jones said:
So I attempted to follow your instructions, got my bootloader unlocked and TWRP installed. Got the Guru Reset pushed onto my phone storage. Now I'm getting an error when trying to install. "Error Flashing zip" "E: Unable to mount '/cache' " "E: Unable to mount '/data/ " "E:Unable to mount storage. "
Not sure where to go from here.
Click to expand...
Click to collapse
Are you using TWRP 2.6.3.3? If not, flash it first.
In TWRP under Wipe, there’s an Advanced Wipe menu. Go there and select Data, format the partition. Downside you will have to push the Guru Reset back to the phone.
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
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?