XT1096 - System update 23.16.5.en.US - X 2014 General

My new Moto X 2014 (rooted, unlocked BL) just received this file:
Blur_Version.23.16.3.victara_verizon.verizon.en.US.zip - about 2.88Mb
VZW says it is to update to system 23.16.5.en.US
Since my phone is rooted and has TWRP installed it won't install. I have attached for others who might find it of value. Per VZW it is a security update, probably for one of the Stagefright exploits.
If someone creates a TWRP installable ZIP it would be greatly appreciated.
Thanks in advance,
Don S.

donslade said:
My new Moto X 2014 (rooted, unlocked BL) just received this file:
Blur_Version.23.16.3.victara_verizon.verizon.en.US.zip - about 2.88Mb
VZW says it is to update to system 23.16.5.en.US
Since my phone is rooted and has TWRP installed it won't install. I have attached for others who might find it of value. Per VZW it is a security update, probably for one of the Stagefright exploits.
If someone creates a TWRP installable ZIP it would be greatly appreciated.
Thanks in advance,
Don S.
Click to expand...
Click to collapse
This is the Stagefright update.
If you remove root, you should be able to flash the zip using TWRP (unless you have done more than root.) Then you can re-root after the update is flashed.
Another option is in this post: http://forum.xda-developers.com/showpost.php?p=62785699&postcount=781
Or use the info/files toward the bottom of this post: http://forum.xda-developers.com/showpost.php?p=63326136&postcount=885

Yes, I realized that after I posted. I followed the directions in that post and updated my phone.
Thank you, and thank you the images you created.

so I take it there is no ROOT method for this firmware?
is there a full fastboot package that I can use to flush the system?
I have a Verizon Moto X 23.16.5 verizon and it's STUCK in DEMO mode... anyone have any suggestions?

solidus636 said:
so I take it there is no ROOT method for this firmware?
is there a full fastboot package that I can use to flush the system?
I have a Verizon Moto X 23.16.5 verizon and it's STUCK in DEMO mode... anyone have any suggestions?
Click to expand...
Click to collapse
There is no root method yet for the firmware you have.
Try this:
Turn the phone off
Enter the bootloader/fastboot mode.
Volume down to highlight recovery, volume up to select.
In recovery, volume down to select Factory reset.
If it asks for a password, use: demomodeexit

mikeoswego said:
There is no root method yet for the firmware you have.
Try this:
Turn the phone off
Enter the bootloader/fastboot mode.
Volume down to highlight recovery, volume up to select.
In recovery, volume down to select Factory reset.
If it asks for a password, use: demomodeexit
Click to expand...
Click to collapse
looks like it worked. didn't ask me for a password....but it worked.
for anyone lookin for an answer...
also; when recovery first boots, and you see "no command" screen. must hold "power" then while holding, press vol + , then release power.
should bring up usual recovery menu, wipe data, good to go !

donslade, can you tell what you did to update it.
I took the file you provided in the OP and opened up the update script and removed the references to recovery and apps I removed from system. I then tried to flash it in TWRP but receive the following error:
Package expects build fingerprints of motorola/victara_verison/victara:5.0/LXE22.46-11/11:user/release-keys or motorola/victara_verison/victara:5.1/LPE23.32-25-3/10:user/releases-keys: this devices has motorola/omnivictara/victara:4.4.4/KTU84P/2:eng/testkeys
Do I need to remove the version check that causes the error? Or is it something else that I missed?

To apply this update the phone has to be essentially 100% stock including the recovery. The phone cannot be rooted and must have the correct Motorala recovery to match the installed software.
If your phone is bootloader unlocked and you have TWRP installed it is MUCH easier to just install one of mikeoswego's 5.1 system ROMs. Go here for the thread:
http://forum.xda-developers.com/moto-x-2014/development/img-xt1096-victara-mofo-image-root-t3100145
This will make your phone up to date in one step (or a few simple steps) and is much quicker than returning the phone to stock to receive an OTA update.

OK, thanks for the quick reply. I got all of his stuff downloaded but wanted to see if I could modify the patch package myself. I'll be flashing later today.

Related

[HOW TO] Easy root a stock Android 4.4.2 - 4.4.4

Ok, assuming your bootloader is already unlocked, the easiest way to root your device if you want to keep the stock firmware (including recovery partition) is to flash a special modified boot.img called "Superboot r2" that installs su binaries and SuperSU on your device. It's nothing new, this workaround was originally developed by PaulOBrien, founder of MoDaCo, several months ago. People started to complain since 4.4.2 release saying this method doesn't work anymore... false! They just don't know the trick! I successfully rooted even the 4.4.4:good:
You just need to:
1) have your stock or official firmware flashed
2) clear cache partition through recovery before to flash
3) flash boot.superboot.img using the standard fastboot, not the mfastboot
4) your phone will crash with a disappearing android logo, just press the power button for few second to reboot it
5) if you don't find SuperSu in your drawer just try again
This method doesn't compromises your phone from receive OTA updates, fully tested.
I already re-packed it for you, just run the batch file.
DOWNLOAD
All credits to PaulOBrien.
Clarification
So all one needs to do is run the batch file if the bootloader is already unlocked?
chaserblack said:
So all one needs to do is run the batch file if the bootloader is already unlocked?
Click to expand...
Click to collapse
Yeah, clear cache and run the batch while you're in fasboot mode.:good:
Worked.
1st try, thanks man.

[REF][How To] Return to STOCK Recovery (IF rooted) and sideload OTA

By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.
Good work KidJoe :laugh::good:
I guess this will be more relevant as Soaks start heading out for the 2013 X...
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
there any way to make a dump the stock recovery in Lollipop, without the need root?
ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.
Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.
upload the stock recovery lollipop please!!!!
Good work, love your detailed explanations always .

Updating To MM from LP (Moto X Pure)

So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment

Fire TV 3 (needle/stark): TWRP

Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.
Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.
Confirmed, it works on the cube (stark) as well...
That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.
Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.
2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.
How may I get the "su". It said, I don't have permision.
eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?
eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work
Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.
moving it to the right place.
anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?

[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......

Categories

Resources