Database Users

[RECOVERY][KANG] TWRP 3.0.2 recovery for u8800pro/u8860

Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOGS
Changelogs can be found from TeamWin site TeamWin - TWRP
BUGS:
- No off mode charging, boots straight in to recovery.
INFORMATION:
- Supports the f2fs file system.
2016-05-10
- TWRP version 3.0.2-0
2016-02-06
- TWRP version 3.0.0-1
2015-12-10
- TWRP version 2.8.7.0
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #18.
DOWNLOAD:
For u8800pro
Stable:
TWRP_2.8.1.0-20141026-u8800pro.zip
Unstable:
TWRP_3.0.2-0-u8800pro.zip
TWRP_3.0.0-1-u8800pro.zip
TWRP_2.8.7.0-20151210-u8800pro.zip
For u8860
TWRP_2.8.1.0-20141026-u8860.zip
Looking for the u8800 version?
It can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800.
Big thanks to @Dees_Troy, @bigbiff and @Captain_Throwback. Also I want to thank you @desalesouche from his help.

Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!

CrysisLTU said:
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
Click to expand...
Click to collapse
Thanks and thanks to you and other dev's who was part of this forum, you have made a job which can't be forgotten!

Great. This must be a record. Not so famous device, still getting superb support from devs. Lets see what happens to Android L.

It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work

Greekguy74 said:
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Click to expand...
Click to collapse
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.

Lihis said:
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Click to expand...
Click to collapse
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.

Greekguy74 said:
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Click to expand...
Click to collapse
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.

Lihis said:
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Click to expand...
Click to collapse
I tried those instructions and they don't seem to work.
If I attempt it from the normal recovery screen I get a
Code:
update package;s ext name error
E:ota_pre_update error
Maybe will try to flash everything ie reinstall B928 as well and not just try to unlock the pink screen.
Will keep you posted.

Greekguy74 said:
I tried those instructions and they don't seem to work.
Click to expand...
Click to collapse
What is the error? No, you cannot flash the update.app via recovery.

Lihis said:
What is the error? No, you cannot flash the update.app via recovery.
Click to expand...
Click to collapse
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss

Greekguy74 said:
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Click to expand...
Click to collapse
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?

Lihis said:
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Click to expand...
Click to collapse
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.

Greekguy74 said:
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Click to expand...
Click to collapse
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image

Lihis said:
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Click to expand...
Click to collapse
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:

Greekguy74 said:
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Click to expand...
Click to collapse
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?

Lihis said:
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Click to expand...
Click to collapse
adb is not accessible but fastboot seems that it is. even though I cannot flash anything since they are locked.

Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.

Lihis said:
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Click to expand...
Click to collapse
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.

mohammad.afaneh said:
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
Click to expand...
Click to collapse
Thanks! Are you working a F2FS enabled rom?

[ROOT][Recovery]Wileyfox Storm

## Disclaimer and acknowledgements
All your actions with your phone are at your own risk;
## Intro
Hey,
I propose a tutorial to root Wileyfox Storm with lastest SuperSu Binary, but you can flash zips too ^^
Wileyfox storm's stock recovery has a signature verification, so you can't flash SuperSu 2.46, but with long work i got custom cyanogen recovery with no signature verification ;D
## Tutorial
Step 1 : Unlock bootloader !!!! It will erase All Data So backup first !!!!
- Go to settings>about phone and tap a few times on build number to unlock dev options
- Go to Dev options and check OEM Unlock and reboot bootloader (volume +)
- Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y
Step 2 : Flash Custom Recovery
- Reboot Bootloader
- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img"
- Wait the flash process and reboot recovery (volume -)
- Now Flash SuperSu-2.46.zip
Step 3 : Enjoy !!
## Download
Super Su : SuperSu-v2.46_signed.zip
Custom Recovery : kipper-custom-recovery.img

Corrected link to recovery?
Hi,
The custom recovery link is to the supersu file as well. Can you post the corrected link?
Thanks

Sorry xD

Thanks, I haven't had time to try compiling the Cyanogen Recovery for the Storm myself yet.
The above recovery image worked for me using fastboot boot xxx thus leaving the stock recovery intact.
F:\downloads\kipper>fastboot boot kipper-custom-recovery.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
OKAY [ 3.082s]
finished. total time: 3.758s
Wileyfox Storm (Kipper) - 12.1-YOG4PAS3MG
SuperSu and Busybox successfully installed.
Thanks.

No prob i'm happy, i've done it myself ^^

Phone wont boot pasted the Cyanogen logo
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
bobslesbricoleurs said:
## Tutorial
Step 1 : Unlock bootloader !!!! It will erase All Data So backup first !!!!
- Go to settings>about phone and tap a few times on build number to unlock dev options
- Go to Dev options and check OEM Unlock and reboot bootloader (volume +)
- Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y
Step 2 : Flash Custom Recovery
- Reboot Bootloader
- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img"
- Wait the flash process and reboot recovery (volume -)
- Now Flash SuperSu-2.46.zip
Step 3 : Enjoy !!
Click to expand...
Click to collapse
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!

codeclinic said:
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
Click to expand...
Click to collapse
The first boot after wiping takes a few minutes so do be sure that you are waiting long enough, otherwise sounds like something borked.
Are you able to boot back to recovery by holding volume down while powering up?
If so you should try clearing cache and wiping.
You can also try restoring to stock CyanogenOS images : https://cyngn.com/support
If just installing the stock recovery the image can be extracted from the fastboot zip.
There is now also a CyanogenMod nightly build, you can try flashing the recovery from there instead (there is also the nightly Cyanogen build if you are feeling brave): https://download.cyanogenmod.org/?device=kipper
There is a separate download for the recovery image.
Flashing su is not required to boot after flashing the custom recovery.
However to flash it, first copy the SuperSu zip onto the phone (for simplicity use the main memory not the SD card), either download directly onto phone, copy from computer when connected as a usb device or transfer using adb. From the custom recovery you can then select Apply Update and browse to the SuperSu zip file.

codeclinic said:
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
Click to expand...
Click to collapse
Did you unlocked bootloader before?
Envoyé de mon Wileyfox Storm avec XDA Forums

bobslesbricoleurs said:
Did you unlocked bootloader before?
Envoyé de mon Wileyfox Storm avec XDA Forums
Click to expand...
Click to collapse
Yes, i followed all the instructions. I even tried doing it with the 'fastboot boot' method. But still no luck.
In the end I did a factory reset from the recovery and rebooted. I'm now able to get into android normally.
However, if i go back to recovery and try to flash the su binaries, it fails with the output sayings something about the signature of the package.
Any ideas?

codeclinic said:
Yes, i followed all the instructions. I even tried doing it with the 'fastboot boot' method. But still no luck.
In the end I did a factory reset from the recovery and rebooted. I'm now able to get into android normally.
However, if i go back to recovery and try to flash the su binaries, it fails with the output sayings something about the signature of the package.
Any ideas?
Click to expand...
Click to collapse
If you are getting messages about the signature then you are probably running the stock recovery again,
Go back to the bootloader and use fastboot to boot or flash the customer recovery above or cyanogen recovery again.
You can also grab an unsigned version of SuperSu from the developer : https://download.chainfire.eu/696/supersu/

miSAKe said:
If you are getting messages about the signature then you are probably running the stock recovery again,
Go back to the bootloader and use fastboot to boot or flash the customer recovery above or cyanogen recovery again.
Click to expand...
Click to collapse
I figured / hoped that was the case. I'll give it another shot tonight.
miSAKe said:
You can also grab an unsigned version of SuperSu from the developer
Click to expand...
Click to collapse
Are there any pros/cons of using the unsigned version over the signed one? If not, is it not better to use the unsigned version and not bother with the flashing of the recovery?
Thanks

Maybe i'll try later to port philz to this phone ^^

Is it possible to relock the bootloader again?

I've successfully managed to install the custom Cyanogen recovery, and CyanogenMod on my WF Storm this afternoon. I largely did this by following the instructions posted previously - unlocking bootloader, installing CM recovery image with fastboot, then installing CM12.1-kipper from recovery.
I did encounter some problems - namely that the nightly version of the CM recovery (cm-12.1-20151120-NIGHTLY-kipper-recovery.img ) just did not seem to work, despite reportedly being installed OK - Whenever I tried to install anything in recovery mode, it came up with "failed to verify whole-file signature" or similar errors. Strangely I was able to overcome this by using fastboot to boot from the image of it downloaded to my PC, and installing the CM ROM that way; initially it came up with an error about filesystems being incompatible, but after erasing all data, it seemed to go on OK.
I installed the openGAPPS aroma version (allows you to choose which GApps to install interactively) and used the ARM-64 version. Initially, I had the problem with the recovery and couldn't install it, so finally decided to install the cyanogen recovery linked to above in one of the first posts (kipper-custom-recovery.img) rather than from the nightlys. This seemed to solve the problem, about signature errors and I tried to install GApps. The first time I tried this (after going through and selecting what to install from the huge list), it seemed to start OK then said there was not enough space on the device - which seemed very odd indeed. I rebooted and tried again, this time with a few less GApps selected, and it seemed to work fine. I think it was just some kind of a glitch the first time, because there is plenty of space left.
During the first boot after installing the GApps, the systemUI crashed, the screen went black and it was not looking good. Following another reboot though, it seemed to be OK, and I am very happily now using the Storm with CyanogenMOD and root access. I've now installed the dozens of extra apps I use, from the play store, and so far, everything is working well.
Of course, I haven't checked evreything yet, but the camera, phone, 4G LTE, tethering, google account etc. all seem to be working very well.
I hope this info might be of help to anyone looking to get CM12.1 going on their WFStorm. If you get signature errors, just make sure you try installing a different CM recovery!
A huge thanks to earlier posters, and everyone who's worked on getting a version of CM for the Storm. Peace-out,
Neon

nsam1 said:
I've successfully managed to install the custom Cyanogen recovery, and CyanogenMod on my WF Storm this afternoon. I largely did this by following the instructions posted previously - unlocking bootloader, installing CM recovery image with fastboot, then installing CM12.1-kipper from recovery.
I did encounter some problems - namely that the nightly version of the CM recovery (cm-12.1-20151120-NIGHTLY-kipper-recovery.img ) just did not seem to work, despite reportedly being installed OK - Whenever I tried to install anything in recovery mode, it came up with "failed to verify whole-file signature" or similar errors. Strangely I was able to overcome this by using fastboot to boot from the image of it downloaded to my PC, and installing the CM ROM that way; initially it came up with an error about filesystems being incompatible, but after erasing all data, it seemed to go on OK.
I installed the openGAPPS aroma version (allows you to choose which GApps to install interactively) and used the ARM-64 version. Initially, I had the problem with the recovery and couldn't install it, so finally decided to install the cyanogen recovery linked to above in one of the first posts (kipper-custom-recovery.img) rather than from the nightlys. This seemed to solve the problem, about signature errors and I tried to install GApps. The first time I tried this (after going through and selecting what to install from the huge list), it seemed to start OK then said there was not enough space on the device - which seemed very odd indeed. I rebooted and tried again, this time with a few less GApps selected, and it seemed to work fine. I think it was just some kind of a glitch the first time, because there is plenty of space left.
During the first boot after installing the GApps, the systemUI crashed, the screen went black and it was not looking good. Following another reboot though, it seemed to be OK, and I am very happily now using the Storm with CyanogenMOD and root access. I've now installed the dozens of extra apps I use, from the play store, and so far, everything is working well.
Of course, I haven't checked evreything yet, but the camera, phone, 4G LTE, tethering, google account etc. all seem to be working very well.
I hope this info might be of help to anyone looking to get CM12.1 going on their WFStorm. If you get signature errors, just make sure you try installing a different CM recovery!
A huge thanks to earlier posters, and everyone who's worked on getting a version of CM for the Storm. Peace-out,
Neon
Click to expand...
Click to collapse
Wich open gapps you need ? mini, micro, full ?

Hi,
I used the aroma version of GApps, which has the interactive graphical installer so you can choose whichever apps you want. I am sure Nano and Pico etc. are all fine, I just wanted to install a lot of GApps.
I downloaded from here: http://opengapps.org/?api=5.1&variant=nano
It is set to nano by default but I chose aroma. Make sure you select the correct architecture (ARM64) and android 5.1 (if you are using kipper).
Best of luck,
Nsam

https://youtu.be/b6XUFmHoY4U
I upload it just wait 1 Hr

bobslesbricoleurs said:
https://youtu.be/b6XUFmHoY4U
I upload it just wait 1 Hr
Click to expand...
Click to collapse
All looks good I seem to have a slight problem with one bluetooth device, but I need to look in to it more before I say it is a problem with kipper. Other bluetooth devices work fine
keep up the good work
Nsam

Hei it has been the second day running nightly built of CM12.1, and so far its been great never had serious issues. I just noticed that the proximity sensor distance when call is engage is set to very near like 1cm. If the phone goes further the screen lights on and gets activated.

Nightly most of time runs well, apart from "Not Responding" whatsapp every once in a while. Battery life is average almost the same stock CM. Call gets cut/muted at the middle of the conversation, not sure if the network or the phone has it. Hopefully there will be a TWRP soon for the device as NANDroid backup is very important when using nightly. Thanks for all the devs.

[ GUIDE ] [ Marshmallow Firmware Upgrade ROM install including ViperOneM9 4.x.x ]

Dummy friendly guide how to upgrade, flash and install the latest Marshmallow Firmware and the latest ROM’s such as the ViperOne ROM 4.x.x, this guide is intended for those who are already slightly familiar with the flashing process and have previously managed to flash a ROM on their HTC One M9 device…
CHECKLIST BEFORE STARTING:
1) Phone is S-OFF
2) Unlocked Bootloader
3) Rooted
4) Latest TWRP recovery
5) SUPER CID changed to 11111111
6) External SD Card
7) NANDROID Backup and any or every other form of backup
8) Device drivers, Android SDK Platform Tools including ADB & FASTBOOT.
9) USB Debugging enabled.
10) BACK UP OF ALL YOUR DATA !!!
Before we begin make sure you back up all your data on both the internal and external SD card.
For the purpose of this tutorial we will be installing the latest ViperOneM9 ROM…
a) Downloaded and place the latest ViperOne ROM - ViperOneM9_4.x.x.zip on your External SD card,
Main Thread by j to the 4n is found here:
http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Latest ViperOne ROM for download is here:
http://venomroms.com/htc-one-m9/
b) If you are currently on ViperOneM9 3.5.0 or older and wish to upgrade to the latest 4.x.x than the latest Marshmallow firmware is required (3.35.401.12 or 3.35.617.12 firmware)… This can be found here and within Sneakyghost original thread.
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Now download the latest version of either:
NO WIPE ZIP
or
FULL STOCK WIPE ZIP
For this tutorial we will use the FULL STOCK WIPE ZIP (to archive a clean install – this will wipe everything on your phone excluding the External SD card)
c) Place the downloaded M9_3.35.401.12_FullStock_wipe.zip into your Android SDK Platform Tools Folder (for example C:\Android\ if this is where all your tools are found)
d) Download the latest version of TWRP recovery from
http://www.teamw.in/devices/htconem9.html
Place the downloaded twrp-2.8.7.0-hima.img in your Android SDK Platform Tools Folder
e) Once you are 101% ready to begin the process start by connecting your device and launching the command window (hold shift, right click in window with all the required ADB/FASTBOOT aps and select "open command window here) once the black terminal window appears start by typing in
adb devices
if your phone appears in the list we can continue by typing:
adb reboot download
wait a few seconds for the screen to appear and type:
fastboot oem rebootRUU
your phone should now be in the RUU mode with a silver HTC logo, now type
(if you renamed the original file type its current name, by default it is as follows)
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
f) you will most likely receive something like this towards the end after running the above command...
FAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device...
just type the above command again and phone will flash the update again and hopefully it will take at least a minute or more to complete, hopefully there will be no more errors, just in case repeat the above command... Just in case you do see errors try looking them on Sneakyghost's thread found here
g) Once this is done and everything passed than we have successfully upgraded our firmware to Marshmallow... Since we selected the FULL STOCK WIPE option we need to flash TWRP once again (as it was wiped) and don't bother resetting or hoping for the phone to boot normally as it won’t...
(if you renamed the original file type its current name, by default it is as follows)
Type:
fastboot flash recovery twrp-2.8.7.0-hima.img
and once it’s done
adb reboot-bootloader
*if for any reason you need to reset your phone and gain access to the bootloader menu, download mode, recovery etc. you can always do this manually by holding vol up, vol down and power buttons at the same time for a few seconds to reset the device, to get into the bootloader, recovery, download mode etc. After the phone resets continue holding the vol down and power button until you reach the bootloader menu.
*if you type adb devices and you see multiple devices or emulators that prevent the commands from working I suggest running the following:
adb kill-server
adb devices
Now only your connected device should appear…
h) It is now time to enter our recently flashed recovery to finally install our latest ROM.
Enter the recovery manually or by typing
adb reboot recovery
From there you may select the wipe option (swipe to factory Reset) and proceed to the Install section, browse for your ROM file and select it.
i) Within Aroma installer select all your preferred options and begin to install, once the flashing completes your device should reboot and now you keep your fingers crossed and wait (will take several minutes so just be patient…. And DONE!!! You now have the latest Marshmallow firmware and ViperOneM9 ROM installed.
#Please note that I’m no expert when it comes to these matters, this guide is here to help anyone who is unsure what to do, I tried to write it up the best way possible (sorry that there are no fancy pictures) if there any errors or issues with my methods please feel free to correct them but so far they worked for me and hopefully will also work for you. (This guide will also help you flash other ROM's) If you need more help please feel free to ask, there is always someone here on xda who knows the answers 

Excellent write up !!
Many thanks !!!....g

glad i could help

GODSPD said:
glad i could help
Click to expand...
Click to collapse
Very nice writeup. Just got an M9 for the wife. I've been around the block so I get everything, but I've been away from HTC since the One X...well, there's the N9 but it's a nexus. What are the RUU mode and Download mode. If I remember correctly there was only the bootloader to go to on the One X. If it's complicated is there somewhere I can read about the modes?

Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk

Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.

CrazyRom said:
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
Click to expand...
Click to collapse
PM sent, hope it helps.

zrzhu said:
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...

GODSPD said:
PM sent, hope it helps.
Click to expand...
Click to collapse
Also try the following as error 22 was not covered in the error handling section...
http://forum.xda-developers.com/showpost.php?p=59783531&postcount=3
Download 7zip, open the zip inside of the program, right click on the Android text file and open within. Change the mid to yours hit save. It will ask if you want to update the zip, hit yes. Then try and flash.
SneakyGhosts post explains this:
Error 22 is new to me too but the string is kind of self explanatory: every archive has a header where the archive-program finds info about what type of archive and what compression. If the error says anything about this header, the logical conclusion is either a corrupted, broken archive or an unsupported archive type.
I suspect the latter simply due to the fact that the zip was unpacked and repacked, which then easily creates an incompatible zip.

GODSPD said:
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
Click to expand...
Click to collapse
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk

zrzhu said:
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.

GODSPD said:
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
Click to expand...
Click to collapse
Thanks. Hopefully ATT will release Marshmallow soon then.

Hi guys i dont have anymore pc. Can i flash new firmware without pc? Plz help

Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder

BLEK0TA said:
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
Click to expand...
Click to collapse
which exact files are you after, the android sdk?

thanks bro!! nice collection!

zrzhu said:
Thanks. Hopefully ATT will release Marshmallow soon then.
Click to expand...
Click to collapse
I'm still kind of "fuzzy" on this whole firmware thing.... IF I don't want to wait (on ATT) and IF I go S-OFF, which firmware can I/should I use for Marshmallow?

Delete

HI, can you please tel me how long does the firmware flash take as mine has been at it for over 2 hours? Not sure if it is stuck?

I am on sprint. How do i get the new firmware? It isnt on the list. Thank you

Lemfo lem5 custom recovery - twrp

Was able to port twrp recovery of blitz smartwatch after unpacking and replacing the kernel file with the lemfo lem5's stock kernel file extracted from unpacking stock recovery of lemfo lem5 and then repacking and flashing it to lemfo lem5. The recovery got successfully installed and all features are working except the recovery screen is flipped / inverted but not the touch response. The touch inputs are the same as non inverted screen and using the touch is pain in the a**s. If the touch input field is at 45 degrees then to access it, need to tap at 225 degrees and on the same radius distance. Can anyone let me know how to flip the recovery screen without affecting the touch fields or is there a similar custom recovery for mtk6580 lollipop smartwatch with flipped screen.

I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.

geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... For wipe
There is not enough space to backup or restore and i think only root is all you need
Click to expand...
Click to collapse
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?

Gautam_Gundap said:
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Click to expand...
Click to collapse
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
Click to expand...
Click to collapse

Gautam_Gundap said:
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
Click to expand...
Click to collapse
I have with chainfire but never had any problem to recover
Thanks

Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )

cassettesgoboom said:
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
Click to expand...
Click to collapse
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.

To use pc for full rom backup and restore and many other features use cracked version of miracle box v2. 27A. Mtk Droid tools and SP flash tools do not support this watch, so don't waste time trying with it.

Xposed framework installed successfully!

Anyone need full power button menu for lemfo lem5 install advance power menu app from playstore. It works well. Once you long press the power button you get options for power off, reboot, download, recovery, UI restart , screen shot, soft reboot and safe mode reboot. Select floating mode from settings. looks and works nice on smart watch display

Gautam_Gundap said:
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
Click to expand...
Click to collapse
Very cool - seems straightforward enough. I'll see if I can find something to fix up or workaround to get the rotation back while I'm at it. First thing's first is to give this a shot though. Need to get a windows machine so I'll get it going at work tomorrow!
Will update again soon. Thanks so much for the steps!

Hi guys.. root + twrp ok.. but there are Custom ROM with full smartwatch function (not only standalone)? Or the only one solution (partial solution) is M2D?

Well done! :laugh: I've configured Lem5 TWRP how u can see here:
https://forum.xda-developers.com/smartwatch/other-smartwatches/twrp-lemfo-lem-5-twrp-t3544569
I think/hope i've solved recovery flipped screen issue, because X5 TWRP haven't this problem.
X5 TWRP + Lem5 kernel = solution? I hope so!
If someone want try, please post the result. Thanx at all...!
Sent from my S7 Edge using XDA Labs

I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."

dimex said:
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
Click to expand...
Click to collapse
if your bootloader is locked, it will not allow you to flash twrp recovery via fastboot . Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.

Gautam_Gundap said:
if your bootloader is locked, it will not allow you to flash twrp recovery. Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Click to expand...
Click to collapse
Did you read my update? It's bootlooping TWRP.

dimex said:
Did you read my update? It's bootlooping TWRP.
Click to expand...
Click to collapse
If you are unable to reboot to system, then you need to re flash complete stock rom. You can do this using cracked miracle software. I have already uploaded full stock rom for flashing via cracked miracle box software except data/userdata partition . you can find it in one of the lemfo lem5 threads here. After re flash you can use the steps explained earlier to flash twrp recovery

I just released a fully working TWRP 3.0.2 recovery for X5+ and LEM5 here:
http://roundandroidwatches.proboards.com/thread/1016/twrp-recovery-port-x5-lem5
Don't forget to read all the instructions.

[ROOT][TB-X505X] Rooting Lenovo Tab M10 TB-X505X

This guide is now obsolete. Please check my new guide. It has a custom recovery for this device as well as a rooting guide. Refer to this guide only for installing adb and unlocking bootloader.
This rooting guide is for the Lenovo Tab M10 X505X only.
I plan to work on a custom recovery for this tab as well and probably a custom rom in the future.
So please consider donating so that I can keep up the work.
Donations
Google Pay
This will work only on the version "TB-X505X_S001037_200718_ROW". Check it in the Settings > System > About Tablet > Build Number. If it is the newer "X505X_S001038_200819_ROW", do a factory reset and make sure it is the "TB-X505X_S001037_200718_ROW" before proceeding.
Once a custom recovery is made, OTA updates can be applied without losing root. So do not update the tablet until a custom recovery is developed for the device. I plan to develop a custom recovery for it as soon as possible, so please support me.
Anything that goes wrong in this tutorial is not my responsibilty. Proceed at your own risk.
Downloads
patched_boot.img
Step 1. ADB and Fastboot Installation [If adb and fastboot are already installed, skip to Step 2]1. Download the platform tools for your OS from this link.
2. Extract the zip file and place the contents in a folder "platform-tools".
3. To confirm if adb is working, open a command prompt "platform-tools" and run the following command.
Code:
adb version
If it returns the adb version, its done.
Step 2. Unlocking BootloaderWe have to unlock the bootloader inorder to root the device.
Warning: Unlocking bootloader wipes data on the device. It is recommended to backup your data. Proceed at your own risk.
1. Now in the tab, goto Settings > System > About Tablet. Multiple tap the "Build Number" till the developer options are enabled.
2. Goto the developer options and turn on the "OEM unlocking".​3. Power off the device.
4. Turn it on by holding Power Button + Volume Down. Once the screen turns on. leave the power button but continue holding the Volume Down button until the fastboot mode is shown.
5. Now open a command prompt in "platform-tools" and now run the following command:
Code:
fastboot oem unlock-go
Your Bootloader is now succesfully unlocked.​Step 3. RootingNow to root the tab, download the "patched_boot.img" from the top of this post. Copy the file to the "platform-tools" folder.
Make sure the tab is still in the fastboot mode. Otherwise go back into the fastboot mode as instructed before.
Now run the following command:
Code:
fastboot flash boot patched_boot.img
Congratulations, you have rooted your tab.:highfive:
To complete the process, run the following command.
Code:
fastboot reboot
Once the tab turns on, goto this link and download the latest version of Magisk apk and install it. It is required to control the root privileges for other apps.​That's all. You now have a rooted tab.:victory:
If this helped you, hit the thanks button.
And keep tuned for new stuff that are to come for this device.

Thanks for this thread for the TB-X505X.
Shamil Niyas said:
I plan to work on a custom recovery for this tab as well...
I plan to develop a custom recovery for it as soon as possible...
Click to expand...
Click to collapse
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
Shamil Niyas said:
Once a custom recovery is made, OTA updates can be applied without losing root.
Click to expand...
Click to collapse
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.

Yahoo Mike said:
Thanks for this thread for the TB-X505X.
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Click to expand...
Click to collapse
I gave a look at the TWRP image. Unfortunately, X505X does not boot into the recovery image. It would have been great if it worked. I guess it is because of the different processor, as you mentioned.
It is the same for X505X as well. OTA cannot be applied without uninstalling Magisk. So I guess OTAs are a no-go until a custom recovery is developed. The latest update is also just a boot image patch. So there is no way to use magisk on that.
Thanks for the advice.

But i updated to android 10 S001122_200915
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.

Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.

ShAd0W_z0nE said:
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
Click to expand...
Click to collapse
This post has instructions for the X505F, under "How do I root my device?".

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
I'm currently working on the twrp for this device. Once it is finished it should be able to root without downgrading.

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.

Shamil Niyas said:
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Click to expand...
Click to collapse
Thanks sir. Great job and I'm also from kerala, nice to meet you

Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?

jsvenancio said:
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
Click to expand...
Click to collapse
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Twrp for x505f

Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..

tombaldwin6 said:
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
Click to expand...
Click to collapse
Check his new guide, just flash twrp and flash magisk from there

Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?

Tamiiiiiii812 said:
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Click to expand...
Click to collapse
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/

cYBER~VeTeRaN said:
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
Click to expand...
Click to collapse
OMG IT WORKED. Thank you.

Thanks bro. I found what I needed..

Shamil Niyas said:
1. Download the platform tools for your OS from this link.
Click to expand...
Click to collapse
yeah, where is the link?

Booe said:
yeah, where is the link?
Click to expand...
Click to collapse
Just search for platform tools and download it.

Guys, i tried the above mentioned method but my device is showing (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device) after performing a factory data reset the device reboots and the welcome menu shows up after 15-30 seconds the device automatically shut down and again shows the same message (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored onnn this device). this goes again and again......