Related
Hi, I am a happy owner of the HP Slate 7 Extreme which is basically the same device as you guys are using.I am still on the 4.2 Jelly bean since HP are not pushing over the air updates with our devices.I want to use the script from the development forum "[Script] [Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root", I want to know if anyone has tried to use it with the Slate Extreme or if it simply should work on the Jelly Bean aswell. Thanks guys.
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
mofared said:
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
Click to expand...
Click to collapse
What about the 4.3+ ?
crazyhacker202 said:
What about the 4.3+ ?
Click to expand...
Click to collapse
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
mofared said:
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
Click to expand...
Click to collapse
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
There was an individual who has received the 4.4.2 update from HP on his Slate Extreme over at the HP forums. I believe he stated he received 20 units donated directly from HP and was wondering why only 1 of them received the update. I believe the reason stated is that he most likely received a non-retail unit by accident. Not sure if he ever dumped the ROM or even knows how. I don't know either otherwise I'd try to contact him to get him to do so.
Re-write recovery partition?
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Belmichel said:
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893
What am I supposed to open updater-script with?
---------- Post added at 03:47 AM ---------- Previous post was at 03:31 AM ----------
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
---------- Post added at 04:25 AM ---------- Previous post was at 03:47 AM ----------
I downloaded a script editor and deleted the first three lines of updater script but it still fails to flash.
Finally success!
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I have the 4450 extreme and one the things that was a little different- is that I had put the update zip on the sd card prior and it did the update on its own... WEIRD but acceptable! rooted and on 4.4.2- thanks man!
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot (previously this): This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk (Previously this): The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip (previously this): A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt (previously this): A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
It Worked! But...
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
I was able to unlock my bootloader using the above method and it worked. My s7e rebooted and everything was working normally. I loaded the bootloader again to go in and do a cache wipe and my 3 year old bumped into me as I was holding down the volume+ and power buttons. Now I'm stuck in ADX mode (black screen but recognized by my pc, have tried connecting to charger, volume+ and power, volume - and power, nothing works) . I've read that Advent has released adx files for the Vega Note 7 and you can use Tegra Note 7 Super Tools to restore the Nvidia Note 7. I'm wondering if I can use the update.zip file and the nvflash files from Nvidia to restore my tablet from ADX mode.
Any suggestions?
Mike-S, Thanks for the in depth how-to. I tried to sell my Extreme 4450 and the guy that I sold it to said when he received it was in boot loop. I got it back and it is indeed the one I sent him, however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling. I almost seems like the recovery was wiped... I can get to uploading from SD and have tried using your info to accomplish with no success. Any suggestions? I hate to smash it or try and sell if I can fix it.
Thank you in advance for anyone's help
som1special2 said:
however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling.
Click to expand...
Click to collapse
Damn, I'm sorry to say that I'm unsure if i'll be able to help much or at all. All i can suggest is look and see if there is any pre-boot subsystem that connects to your pc via usb, similar to the mediatek "preboot mt65xx" which can sort of provide a last gasp chance of recovery.
help with ROM
Hi there,
Need desperate help. I followed the instructions here but ended up with no OS in the s7e. I kept on trying to install a signed ROM via ADB, it reaches 100% senidng but always failed inside TWRP. Not succesful even with CWM. I even tried installing from SD card but no success. Please help, thank you.
Anyone still around here?
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
MGrad92 said:
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
Click to expand...
Click to collapse
Get your device drivers right (try androidsdk if it's still not getting recognised) and fastboot the stock system images (fastboot is not root dependent). By the way why were you trying those weird rooting methods ??? Just flash supersu from cwm/twrp and be done with it.
Thanks ... I'll try androidsdk. I actually am a root n00b and so I was trying to figure out the simplest way to go. I guess I guessed wrong! But of course before I can get that working I need the right drivers ... So I'll try that first. I was thinking the drivers were OK since my PC recognized the S7E when Android loaded (before it crashed to the white screen).
Couldn't get androidsdk to work
Hello again... I never could get androidsdk to work. My computer never recognized the tablet to be able to fastboot. *sigh* As much as I hate to give up, I don't know what else to do.... I might try another PC?
Looking for update.zip for S7E
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
Hey Mike, you wouldn't still happen to have that signed update.zip since you've don't have it on Dropbox anymore?
There's a painful brick story behind this, and I'll share those details if needed, but let me start with my current situation.
I've got a D800 (AT&T). I can boot to Android (almost stock D80030f, rooted), but I can't get to recovery. I've tried AutoRec to install TWRP, but when I reboot to recovery, it takes me to fastboot mode instead. I would try to flash recovery from fastboot, but the only fastboot command that ever returns is getvar, and it comes back empty for most variables. Anything else I've tried just hangs (erase, flash, reboot). I see the command printed on the phone's screen, but nothing happens after that. This is the same as it was while I was bricked and stuck in fastboot mode. I've tried from Linux, from Windows in a VM, and from a Windows host.
I can get to download mode, but I can't flash anything there, either. The drivers are installed and everything is set up correctly according to all the guides, but when I try to flash, I get an error that the version doesn't match (or something, I can get the exact error message if needed). I suspect this is related to the fastboot problem, because it shows version strings that are either empty or null, I don't remember which. I get the same behavior from both my Windows VM and my Windows host. Both are Windows 7 64-bit.
It would be nice to get fastboot and download mode working, but what I really care about is TWRP, of course. Is there anything I can do to get this working while booted to Android?
I've already short circuited this thing once, and that's how I got this far. I dd'ed every partition (from http://downloads.codefi.re/autoprime/LG/LG_G2/D800/Stock_Firmware/30f_partitions) except for modem and dbi, and a TWRP image for the recovery partition. So if I have to short circuit again, I'm not afraid to.
Edit:
I'm not sure if this is in any way indicative of the problem, but I just noticed that my GPS isn't working. Honestly, I'd be happy to start with a fresh TOT if I could just get it to flash.
*******DISCLAIMER**********...... neither myself or xda takes any responsibility for damage caused to you or your tablet if you choose to follow this guide!
It is for MARSHMALLOW and so far only tested on 4GB versions.
Your tablet must be able to enter DNX Mode. power on with both volume buttons pressed until it says DNX mode on screen.
This guide expects that you have probably already rooted your tablet and have some level of competence. just ask if you are stuck.
This guide can simply reflash factory image to YT3-X90L version. (LTE)
With a few more steps It can also fix YT3-X90F (wifi version) , however you also need to have a full TWRP backup for this one.
If you are reading this chances are you have stuffed up your tablet!! i managed to completely screw mine while messing around in the bios trying to get windows to boot on my YT3-X90F. Big mistake! no way to access BIOS to fix my errors. no recovery! no OS! just intel logo then reboot and repeat!!!
So after some internet digging was able to find aMarshmallow factory image for the YT3-X90L
Instructions.
1) Download factory image, do not unzip or extract.
[url]https://yadi.sk/d/GaiYOUqF3GXmmY&xid=17259,1500004,15700022,15700124,15700149,15700168,15700173,15700186,15700201&usg=ALkJrhjdbFsiXatmDp31rYS2ch3l42eJ3Q[/URL]
Or
[url]https://mega.nz/#!RUtznJYS!gjeS7Qqw956MsFMdCSlrFYVHMwnxsURn59jZ4ynx0UQ[/URL]
2) Download Intel platform flash tool lite (availiable for Windows, Ubuntu, Fedora and Mac) i think to install on windows you will have to disable driver signature enforcement. [url]https://windowsreport.com/driver-signature-enforcement-windows-10/[/URL]
[url]https://01.org/android-ia/downloads/intel-platform-flash-tool-lite[/URL]
3) Open flash tools and connect your tablet to your pc in DNX mode ( hold volume up and down together while turning on tablet) using a usb cable. you will know you are in DNX mode as it will say it on your tablet screen and show up in intel flash tool.
4) In Intel Platform Flash tool lite select browse in the top right corner then locate the factory firmware zip file you downloaded in first step. wait while the flash tool loads the firmware then select the Flash option next to your loaded tablet.
5) wait for flash to finish, provided there are no errors your tablet should be back working.
(I had some errors, probably because of how stuffed my tablet was!!! i selected configure above my tablet in flash tool and set it to "user2user" and then it flashed)
*********The next steps are only needed for the YT3-x90F!!!!!!!!! if you are still reading you have this device.**********
As we have flashed the wrong firmware we may find some problems with our device. mine would reboot on first setup, allow me to complete on second boot but after power down back at setup and reboot.!
6) complete setup after second boot, you can skip everything, no need for google setup, wifi etc, we just need to get to the Android OS.
7) once booted, go to settings and scroll to the bottom select about tablet. then click the info about "build number" 7 times, you are now a developer! go back to settings and you will see a new option here "developer options" open this and enable OEM unlocking.
8) Restart tablet in fastboot mode (power on while holding volume up) then issue command from your pc "fastboot flashing unlock"
9) download and extract twrp from first post here https://forum.xda-developers.com/th...a-tab-3-pro-root-thread-instructions-t3319666 and issue the command "fastboot boot twrp.img"
10) Tablet will boot to twrp. restore your precious backup you saved when rooting your tablet that got you into this mess!!! restore all partitions.
I did this on my YT3-X90F and it worked out fine, back in business.
Good luck.
Here is a full TWRP backup for the YT3-X90F ONLY!!!, if you flash this to L variant you will lose LTE data connection. Up to date as of 07/04/2018.
[url]https://mega.nz/#F!kBUmEbaD!PvF_W9uBZQlBdPGocHqC_Q[/URL]
Do you think I can restore the TWRP backup without doing the other steps? My X90F is working fine but it doesn't have the latest OTA.
mletchworth said:
Do you think I can restore the TWRP backup without doing the other steps? My X90F is working fine but it doesn't have the latest OTA.
Click to expand...
Click to collapse
Yes it is just standard twrp backup.
If you are hoping to preserve your data, make sure to make a backup of your data partition to either external sd or usb otg.
Copy the twrp backup, unencryption zip and twrp data enabled img from root instructions thread to your external sd or usb otg.
Restore backup from this thread then Flash unecyption zip and twrp data enabled img.
Reboot to bootloader , from pc issue "fastboot format data" then reboot to recovery.
Restore data.
Should work.
Possibly just restore twrp and flash the data ununcryption zip, not sure if this will work but it might. As you have made a data backup you may as well try this method first.
Thanks so much. It was even simpler than you thought.
I made a full TWRP backup, restored your TWRP backup (without wiping anything), installed the flashed the unencryption zip, and rebooted. All my data was still there. Only some of the system settings had changed.
mletchworth said:
Thanks so much. It was even simpler than you thought.
I made a full TWRP backup, restored your TWRP backup (without wiping anything), installed the flashed the unencryption zip, and rebooted. All my data was still there. Only some of the system settings had changed.
Click to expand...
Click to collapse
Good to know. Thanks for sharing.
joesnose said:
*******DISCLAIMER**********...... neither myself or xda takes any responsibility for damage caused to you or your tablet if you choose to follow this guide!
It is for MARSHMALLOW and so far only tested on 4GB versions.
Your tablet must be able to enter DNX Mode. power on with both volume buttons pressed until it says DNX mode on screen.
This guide expects that you have probably already rooted your tablet and have some level of competence. just ask if you are stuck.
This guide can simply reflash factory image to YT3-X90L version. (LTE)
With a few more steps It can also fix YT3-X90F (wifi version) , however you also need to have a full TWRP backup for this one.
If you are reading this chances are you have stuffed up your tablet!! i managed to completely screw mine while messing around in the bios trying to get windows to boot on my YT3-X90F. Big mistake! no way to access BIOS to fix my errors. no recovery! no OS! just intel logo then reboot and repeat!!!
So after some internet digging was able to find aMarshmallow factory image for the YT3-X90L
Instructions.
1) Download factory image, do not unzip or extract.
[url]https://yadi.sk/d/GaiYOUqF3GXmmY&xid=17259,1500004,15700022,15700124,15700149,15700168,15700173,15700186,15700201&usg=ALkJrhjdbFsiXatmDp31rYS2ch3l42eJ3Q[/URL]
Or
[url]https://mega.nz/#!RUtznJYS!gjeS7Qqw956MsFMdCSlrFYVHMwnxsURn59jZ4ynx0UQ[/URL]
2) Download Intel platform flash tool lite (availiable for Windows, Ubuntu, Fedora and Mac) i think to install on windows you will have to disable driver signature enforcement. [url]https://windowsreport.com/driver-signature-enforcement-windows-10/[/URL]
[url]https://01.org/android-ia/downloads/intel-platform-flash-tool-lite[/URL]
3) Open flash tools and connect your tablet to your pc in DNX mode ( hold volume up and down together while turning on tablet) using a usb cable. you will know you are in DNX mode as it will say it on your tablet screen and show up in intel flash tool.
4) In Intel Platform Flash tool lite select browse in the top right corner then locate the factory firmware zip file you downloaded in first step. wait while the flash tool loads the firmware then select the Flash option next to your loaded tablet.
5) wait for flash to finish, provided there are no errors your tablet should be back working.
(I had some errors, probably because of how stuffed my tablet was!!! i selected configure above my tablet in flash tool and set it to "user2user" and then it flashed)
*********The next steps are only needed for the YT3-x90F!!!!!!!!! if you are still reading you have this device.**********
As we have flashed the wrong firmware we may find some problems with our device. mine would reboot on first setup, allow me to complete on second boot but after power down back at setup and reboot.!
6) complete setup after second boot, you can skip everything, no need for google setup, wifi etc, we just need to get to the Android OS.
7) once booted, go to settings and scroll to the bottom select about tablet. then click the info about "build number" 7 times, you are now a developer! go back to settings and you will see a new option here "developer options" open this and enable OEM unlocking.
8) Restart tablet in fastboot mode (power on while holding volume up) then issue command from your pc "fastboot flashing unlock"
9) download and extract twrp from first post here https://forum.xda-developers.com/th...a-tab-3-pro-root-thread-instructions-t3319666 and issue the command "fastboot boot twrp.img"
10) Tablet will boot to twrp. restore your precious backup you saved when rooting your tablet that got you into this mess!!! restore all partitions.
I did this on my YT3-X90F and it worked out fine, back in business.
Good luck.
Here is a full TWRP backup for the YT3-X90F ONLY!!!, if you flash this to L variant you will lose LTE data connection. Up to date as of 07/04/2018.
[url]https://mega.nz/#F!kBUmEbaD!PvF_W9uBZQlBdPGocHqC_Q[/URL]
Click to expand...
Click to collapse
Can i downgrade to Android Lollipop 5.0 using this same method ? Im struggling so much with this device at the current update on Marshmallow.I own a 2GB model and its really slow and sluggish.Tried restoring a TWRP Backup from an earlier update but i totally hate marshmallow update on this device.I have currently issues loading apps like zynga poker in my device.It opens and spins and never get pas that screen.This is not the reason i want to go back but the overall perfomance.
dibranoice said:
Can i downgrade to Android Lollipop 5.0 using this same method ? Im struggling so much with this device at the current update on Marshmallow.I own a 2GB model and its really slow and sluggish.Tried restoring a TWRP Backup from an earlier update but i totally hate marshmallow update on this device.I have currently issues loading apps like zynga poker in my device.It opens and spins and never get pas that screen.This is not the reason i want to go back but the overall perfomance.
Click to expand...
Click to collapse
Are you running unencrypted? That is the biggest help to stopping this tablet suck.
I have not heard of anyone downgrading successfully . However i have only heard of people trying to restore their lollipop twrp backup over marshmallow, i gather this does not work.
There is factory images of lollipop floating around and it may work but i dont actually know.
Try running tablet unencrypted, difference is like night and day. **it does delete all user data, make sure you backup anything important first**
Hi everyone,
I ran into some problems with my tablet (YT3-X90F | 6.0, 4GB) and I believe I found the latest firmware for it here.
Original TWRP backup was displaying the firmware version in the name: YT3-X90F_USR_S200322_1706140050_WW17_BP_ROW
All firmware I've seen are old (YT3-X90L_S200219_170323) or for other devices (X90L), like in this in this thread.
The link above is YT3-X90F_USR_S200322_1706140050_WW17_BP_ROW.zip
My question is, by using this zip & following the instructions, Can I just be done in #5?
I also wanted to post this here to hopefully help others in my situation.
Update:
I tried to flash the firmware I found but Intel Flash tool is not detecting my device.
I believe I'm able to boot into DNX, this is what I see:
{
"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"
}
When I connect the tablet to the computer (windows) I am getting the sound that it is detected but Flash tool shows nothing.
Output doesn't show any errors of missing drivers or else. What am I doing wrong?
Update:
Reinstalled drivers & Intel Flash tools and I was able to flash firmware.
It had an error while writing /data. It was showing something about encryption (can't remember what exactly), I skipped it and got my tablet up & running again. But this error seems to be carried , I can not write to /data in TWRP. When I tried to install Magisk it ended in an error, I gained root nevertheless but when I tried to disable encryption TWRP fails to intall it saying: Unable to mount storage. Any ideas, anyone?
Thank you joesnose for the instructions!
OscarBrito said:
Update:
Reinstalled drivers & Intel Flash tools and I was able to flash firmware.
It had an error while writing /data. It was showing something about encryption (can't remember what exactly), I skipped it and got my tablet up & running again. But this error seems to be carried , I can not write to /data in TWRP. When I tried to install Magisk it ended in an error, I gained root nevertheless but when I tried to disable encryption TWRP fails to intall it saying: Unable to mount storage. Any ideas, anyone?
Thank you joesnose for the instructions!
Click to expand...
Click to collapse
Sorry only just saw this, did you get it sorted?
joesnose said:
Sorry only just saw this, did you get it sorted?
Click to expand...
Click to collapse
Yes I did, thank you.
I've posted the firmare used and I can confirm it works perfectly, in case it is of use to someone else.
problems by using this manual
i have download all tools and roms for this thread. thanks for this manual.
ich use the intel platform flash tool 5.8.4. 0, after "Start Flash" the program has an Error Code:
1. ERROR : [Port 2/3] "Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\fastboot.exe" "-s" "YOGAA8DC2034" "flashing" unlock"` failed"
2. ERROR : [Port 2/3] Flash failed (Command type: Fastboot)
I have "Developer Optiosn" enabled an "USB debugging" enabled.
Same Problem, any ideas for this problem?
thanks!
pcircle said:
i have download all tools and roms for this thread. thanks for this manual.
ich use the intel platform flash tool 5.8.4. 0, after "Start Flash" the program has an Error Code:
1. ERROR : [Port 2/3] "Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\fastboot.exe" "-s" "YOGAA8DC2034" "flashing" unlock"` failed"
2. ERROR : [Port 2/3] Flash failed (Command type: Fastboot)
I have "Developer Optiosn" enabled an "USB debugging" enabled.
Same Problem, any ideas for this problem?
thanks!
Click to expand...
Click to collapse
Have you got fastboot drivers properly installed on your pc?
Thanks a ton, friend! I was able to get my unlocked, rooted, stuffed lenovo YT3-X90L back to stock in order to sell it with warranty! It even updated to the latest version after I flashed your image, with no issues! You're the man! :highfive:
joesnose said:
Your tablet must be able to enter DNX Mode. power on with both volume buttons pressed until it says DNX mode on screen.
Click to expand...
Click to collapse
Hi joesnose,
Ive exact same isse like you had. Messed with bios to boot Windows, but bricked YT instead. Since then my Yoga is laying around in silence. Just read your successful attempt and wish to revive mine, too.
Ive issues in entering DNX mode as my YT is stucked in uncharged state and wont charge normally on cable. Its like blinks of seconds I have to put it in this state and than have fastly to switch cable to computer.
Did you had a similar problem ? How to proceed ? Is there a way to flash it fully switched off ?
Thanks in advance !
EDIT: With some fast finger combos and cable switching I managed to get into DNX mode. However trying to flash it finally gave me same error as pcircle:
ERROR : [Port 0/2] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\fastboot.exe" "-s" "YOGA3D76EBF0" "flashing" "unlock"` failed
ERROR : [Port 0/2] Flash failed (Command type: Fastboot)
Used the command fastboot getvar all:
unlocked: no
secure: yes
device-state: locked
boot-state: ORANGE
secureboot: no
This surprised me a lot. I never relocked my tablet. So why it is locked again ? I tried to unlock it with fastboot flashing unlock: FAILED (remote: Unlocking device not allowed)
Tried to boot TWRP: FAILED (remote: command not allowed in locked state)
Also tried format userdata and format cache, also tried directly to flash recovery or other image files, all same errors, not allowed in locked state.
So Im quite frustrated, as Ive no clue why Im in locked state and also how to flash stock firmware on my tablet now. Any help would be appreciated.
Zladimir said:
Hi joesnose,
Ive exact same isse like you had. Messed with bios to boot Windows, but bricked YT instead. Since then my Yoga is laying around in silence. Just read your successful attempt and wish to revive mine, too.
Ive issues in entering DNX mode as my YT is stucked in uncharged state and wont charge normally on cable. Its like blinks of seconds I have to put it in this state and than have fastly to switch cable to computer.
Did you had a similar problem ? How to proceed ? Is there a way to flash it fully switched off ?
Thanks in advance !
EDIT: With some fast finger combos and cable switching I managed to get into DNX mode. However trying to flash it finally gave me same error as pcircle:
ERROR : [Port 0/2] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\fastboot.exe" "-s" "YOGA3D76EBF0" "flashing" "unlock"` failed
ERROR : [Port 0/2] Flash failed (Command type: Fastboot)
Used the command fastboot getvar all:
unlocked: no
secure: yes
device-state: locked
boot-state: ORANGE
secureboot: no
This surprised me a lot. I never relocked my tablet. So why it is locked again ? I tried to unlock it with fastboot flashing unlock: FAILED (remote: Unlocking device not allowed)
Tried to boot TWRP: FAILED (remote: command not allowed in locked state)
Also tried format userdata and format cache, also tried directly to flash recovery or other image files, all same errors, not allowed in locked state.
So Im quite frustrated, as Ive no clue why Im in locked state and also how to flash stock firmware on my tablet now. Any help would be appreciated.
Click to expand...
Click to collapse
Hi Zlad,
Have you tried other options under configure in intel platform tools? I seem to remember there was a recovery option or something. Not sure if it will work but worth a try maybe.
Sent from my Lenovo YT3-X90F using Tapatalk
Hi Jose,
thank you for your fast response. Could kiss you right now. Like u described in your first post, user2user configuration did the trick. I do not know how, but this configuration enforced an unlock state. After that I could flash straight away. Like you I had a lot of errors during this process and the whole procedure took like 3 hours, but in the end he succeeded the flash and I could charge and boot up my device first time for almost two years, yehaa!
Thank you for that.
Also had the problems regarding Launcher3 and wrong time zone, the least I fixed as described. Launcher3 suggested fix didnt work for me, so I exchanged it by another Launcher just. Anyway I didnt like it much.
Also need to mention, Ive the 2GB version of YT3-X90L but flashed your 4GB stock firmware version. So I can confirm it works compatible without flaws. Updated everything, rooted and unecrypted.
Maybe by time I ll try a liveboot from a pendrive with Win10, instead of trying to install it. Haha.
With new Win10arm and Win10S maybe there are new options on this tablet.
How faw you ever came with the try to install Win10, Jose ?
I used your method and it worked.
Thanks a lot!
Zladimir said:
Hi Jose,
thank you for your fast response. Could kiss you right now. Like u described in your first post, user2user configuration did the trick. I do not know how, but this configuration enforced an unlock state. After that I could flash straight away. Like you I had a lot of errors during this process and the whole procedure took like 3 hours, but in the end he succeeded the flash and I could charge and boot up my device first time for almost two years, yehaa!
Thank you for that.
Also had the problems regarding Launcher3 and wrong time zone, the least I fixed as described. Launcher3 suggested fix didnt work for me, so I exchanged it by another Launcher just. Anyway I didnt like it much.
Also need to mention, Ive the 2GB version of YT3-X90L but flashed your 4GB stock firmware version. So I can confirm it works compatible without flaws. Updated everything, rooted and unecrypted.
Maybe by time I ll try a liveboot from a pendrive with Win10, instead of trying to install it. Haha.
With new Win10arm and Win10S maybe there are new options on this tablet.
How faw you ever came with the try to install Win10, Jose ?
Click to expand...
Click to collapse
i am not sure how you even got the installer to boot, i always get acpi bios error, for installer and win2go. How did you get past it?
I think the only two options left are...
bios edit- to enable OS id option....
or dsdt edit loaded from grub2 to boot windows.
Bothe these options are beyond me.
Well, as every good person was trying to get root access from my device and all the tutorials I was seeing told me that it would be necessary to unlock the bootloader so that I could install a superior room, android 8, and unlock the cell phone - so I followed my walk and I was trying various tutorials, I could list the links here, but it would not work.
Well, what was the game change was this:
https://eusouandroid.co/voltar-zenfone-3-para-o-android-marshmallow-6-0/
Which is basically based on running a flash recovery and a flash boot. After the procedure the cell decided to stay a reboot loop, that is, it loaded the android screen, loaded the asus screen and rebooted.
Searching in the forums I saw that it would be necessary to perform an update via recovery mode, so I downloaded the version correctly for my boot and recovery, I passed the data to the memory card and went to access my recovery mode, however, Access keys to recovery mode is the same as doing nothing.
The cell phone has decided that it will no longer open recovery mode and I do not know how to solve it.
In the middle of the way I realized one:
fastboot erase cache
fastboot erase recovery
fastboot erase boot
And without wanting a fastboot erase system.
I think my solution starts by putting the system files back into the phone and following this tutorial here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
I created the files and would perform the procedure as described, however by the time I should open the recovery mode saint nothing happens while holding the keys and I do not know what options I have anymore.
Does anyone know of any way to regain access to recovery?
I already tried to flash the twrp indicated for the device in the tutorials, but the recovery still does not open.
At the moment I have an electronic block that sheer lack of knowledge has arrived in this state.
At the moment I only have access to fastboot
Thanks in advance!
EDIT: It looks like I was sabotaging myself, the model of the device is zc553kl. I still could not figure it out, but I was headed in the wrong direction.
EDIT: I was using the incorrect version of the device to flash the information, after updating the post with the version of the device I was able to find the correct information on how to recover the cell and perform the root.
Thank you very much.
Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).
Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate
unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself