Related
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:1. You should be on SU2-3.3 (Blur 19.6.3) or SU2-3-15 (Blur 19.5.3) rooted and have SafeStrap installed!
2. You have never flashed SU4.21 (Blur 21.11.21) Android version 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
Let's do it and enjoy fully rooted 4.4.4!1 I've done 2 ZIP-files, download one, you prefer:
full rooted stock 4.4.4 SU4.21 with hosts-file ADBLOCK trick.
Download 4.4.4_full here
full rooted Debloated stock 4.4.4 SU4.21, with Touchless Control, Active Display, NFC, Wireless Monitor (inc. Cromecast)
Download 4.4.4_debloated here
Debloated ROM develompent was stopped, due to my smartphone physical damage. Im' sorry.
Regards, Dmitry.
2. Copy downloaded zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select ZIP, you prefer.
5. For locked bootloader: when installation will finish, reboot you device in to bootloader and flash stock kernel from SU4.21
you could take it here or from ZIP-file.
6. After flashing boot.img just reboot you smartphone and enjoy 4.4.4 with root and writable /system
For unlocked bootloader - all done, just reboot your device .
DO NOT PERFORM ANY WIPES!
If something happend with you phone, you can revert to SU2-3-15 (Blur 19.5.3) via RSDLite, get root, install SafeStrap
If you need to clean bloatware, use my Custom Recovery compatibility scripts, could be downloaded in this topic
If you found any features, you need, missing, please, pm me.
i am BL Unlocked, so no need for this for me... but if this is the case and it works then great find my man!!
Given the recent vulnerability published by Dan Rosenberg, I'm hesitant to update to 4.4.4, as it may patch this vulnerability - keeping the bootloader locked indefinitely. I would just keep this in mind if considering this update.
EDIT: Got my information wrong. The date on the OTA is before the date the vulnerability was published. 4.4.4. seems good to go in that case.
has anyone tried this yet?
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
rdenova said:
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
Click to expand...
Click to collapse
Settings>About Phone>Build number
summer.cat said:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
Click to expand...
Click to collapse
This, I see under Build Number.
summer.cat said:
2. You have boot.img from SU4-21, you can download it below
Click to expand...
Click to collapse
This, I do not see any place and is why I asked.
Wait so is this a fully write protection off?
mrwinkle said:
has anyone tried this yet?
Click to expand...
Click to collapse
Looks like this fella did...
http://forum.xda-developers.com/droid-ultra/general/update-19-5-3-obake-t2845903
ceelos218 said:
Wait so is this a fully write protection off?
Click to expand...
Click to collapse
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
summer.cat said:
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
Click to expand...
Click to collapse
Instead of using the SU for identifying builds, you should probably the system version number as that is more frequently used. 19.5.3, 19.6.3, 21.11.21
summer.cat said:
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
You have never flashed 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
2. You have downloaded boot.img from SU4-21
can be downloaded here https://drive.google.com/file/d/0B_kAWkXp3XK9VmpnSGNaVUZtTDQ/edit?usp=sharing
Let's do it!
1. Download 4.4.4_rooted.zip here
https://drive.google.com/file/d/0B_kAWkXp3XK9amVwNjJKUjk4QmM/edit?usp=sharing
2. Copy 4.4.4_rooted.zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select 4.4.4_rooted.zip
5. After flashing reboot to bootloader and flash via fastboot tools boot.img file from point 2 above
Code:
fastboot flash boot boot.img
6. Reboot after flashing boot.img
7. Enjoy 4.4.4 with root and writable /system
If something happend with you phone, you can revert to SU2-3.15 via RSDLite, get root, install SafeStrap
PS: You flashing clean from bloatware system! As clean as possible, but everything works fine!
Click to expand...
Click to collapse
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
thebenshow said:
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
Click to expand...
Click to collapse
i mean, you can use 4.4.4 without write protection
I'm about to try this out to n my xt1080 on 4.4.4... I will update when I'm finished
Can this be used for the droid mini?
I should have read closer I got too excited about about getting root... I already took 4.4.4 OTA... I need root
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
BriCo84 said:
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
Click to expand...
Click to collapse
I am too lol. Been refreshing this thread ever since I ran across it.
Anyone try this?
He is talking about using safestrap on a 4.4 ROM. If you EVER updated to 4.4.4, this will never work for you as you will never be able to disable write-protect to be able to install safestrap.
OP: perhaps you should make this more clear in the original post. Specifically that it will not work if you ever updated to 4.4.4 (Actually, the OP DOES say this...), AND that you're not actually running the 4.4.4 rom, but rather a 4.4.4 stock-based, safestrap-compatible ROM. If you are using this successfully, your bootloader AND your partition table are still on 4.4, which allows you to retain WP-off, safestrap, and root.
But yeah...this will absolutely work if you never updated past 4.4. We have known about this for a long time...I'm surprised a guide was just recently put out about this.
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Adarsh balu said:
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Click to expand...
Click to collapse
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
EDIT - I understand you're desperate for help resolving this, please don't post the same thing in 3 places if you can.
echo92 said:
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
Click to expand...
Click to collapse
Here it is
I did not use kernel
Oem done
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
All steps are followed until flashing of supersu..The error comes there..is there any xt 1643 users who could suggest a correct reliable and error free method for this
Adarsh balu said:
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
Click to expand...
Click to collapse
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
echo92 said:
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
Click to expand...
Click to collapse
Thanks..let me test it....
Any way thnq for the suggestions...:good:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Adarsh balu said:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Click to expand...
Click to collapse
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
echo92 said:
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
Click to expand...
Click to collapse
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Adarsh balu said:
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Click to expand...
Click to collapse
Again, Android O hasn't been formally announced yet...
I see you've already gotten an answer from tywinlannister regarding this question https://forum.xda-developers.com/showpost.php?p=71265934&postcount=249
I don't see much to add to his well thought out reply except if you're staying with stock (assuming you're using temporary TWRP):
1) Unroot completely using the SuperSU settings panel or follow the unrooting instructions for your superuser app.
2) Reboot into temporary TWRP, restore your boot.img (if you flashed ElementalX kernel) from within TWRP (if I recall, it's Restore >Select image and then assign it as a boot image). If you did not make a backup of your boot.img, there are images around (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/1643-indian-version-stock-boot-modem-t3460615 - i don't know if this is for nougat or marshmallow - download and extract the rar file, copy the extracted boot.img to your device and boot into temporary TWRP, then flash the boot.img).
3) Reboot and you should be fully stock - with stock kernel/boot.img, recovery and no root.
1a) As tywinlannister linked, you could just reflash the latest fastboot image which would remove root and give you a stock boot, which would be the best for reliability (which as of this post is this: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Thus, when/if Android O does arrive, you should be able to update via OTA. It's gonna be at least 6-12 months away for the update, if previous Android updates have been anything to go by.
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
itcanbdone said:
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
Click to expand...
Click to collapse
What firmware? 7.0 or 8.1? If you are on 8.1 it's as safe as it ever is to flash a custom ROM.
If you're still on 7.0 you should update first and in any case make a full nandroid backup incl. Persist and EFS before you flash anything.
Sent from my Moto G5 Plus using XDA Labs
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
itcanbdone said:
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
Click to expand...
Click to collapse
Yes. If you can update via OTA that should be the way to go. If you can't flash full Motorola signed fastboot 8.1 firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Unlock the BL on Motorola website, boot to or flash TWRP and make a full nandroid incl. persist.
After that you shoud be good to go and flash custom ROMS. Check whether the selected ROM needs 7.0 or 8.1 as base, almost all of them need stock Oreo.
Sent from my Moto G5 Plus using XDA Labs
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
itcanbdone said:
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
Click to expand...
Click to collapse
You wrote you're on the retus channel and model is 1687. Here are the firmwares for your device, the second one ( OPS28.85-17-6-2) is the latest and last build, flash that one and everything should be fine:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETUS/
You still know how to fastboot flash? Unzip firmware to ADB/Fastboot folder etc.?
Here's a post I made for someone else, it includes a link to a flashall.bat, put in in there too so you don't have to manually flash all partitions, just double-click it and it'll run all the commands for you.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
itcanbdone said:
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
Click to expand...
Click to collapse
I'm not sure that I understand everything. After flashing (official) TWRP and making a nandroid you weren't able to boot to system, only to bootloader?
Have you updated to 8.1 stock Oreo before?
Havoc needs that definitely:
https://forum.xda-developers.com/g5-plus/development/rom-havoc-os-v2-2-t3906282/post79018816
It won't make any sense to revert to stock and root it because after flashing havoc root will be lost anyway. What do you mean with "the two su & Magisk aren't cuttin it in TWRP"? (English is not my native language)
Why two? There should be magisk only to flash.
So the goal seems to be making TWRP work correctly when running havoc to be able to flash magisk.zip and boot to system.
Can you post a recovery log after the attempt to flash magisk from TWRP (the function is in TWRP/ advanced/log.)
Can you boot to havoc directly now?
Are you able to reach TWRP?
I need the error message that appears when you try to flash magisk, should be in the log.
And what is it about two things, su AND magisk?
Magisk.zip is the su binary.
Please provide some more information and sorry if it's me who don't understand something.
Sent from my Moto G5 Plus using XDA Labs
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
itcanbdone said:
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
Click to expand...
Click to collapse
Never use SuperSU alongside with magisk but I think you know that now.
To remove encryption: It's not enough to wipe data in TWRP, you have to format it (the option where you have to confirm with "Yes" and not just wipe). That will wipe your internal storage too.
Only formatting data in TWRP will remove the encryption and the Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip will keep it decrypted. Make sure usb debugging is enabled.
Boot to TWRP and flash ROM and Gapps (both in one action without a reboot in between).
Now flash the no verity-force encryption.zip.
You can reboot to system now but you can also flash the magisk.zip directly afterwards, it helps to keep the data partition encrypted too.
I flash everything in a row.
Check that thread: https://forum.xda-developers.com/g5-plus/how-to/guide-how-to-remove-device-encryption-t3863586
(page 2)
Sent from my Moto G5 Plus using XDA Labs
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
itcanbdone said:
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
Click to expand...
Click to collapse
I decrypt my device, for example to have access to /data in case of a bootloop because of a magisk module. I don't like the idea of not physically seeing parts of my partitions or even not being able to edit it.
From the sight of security it's better to encrypt naturally. It depends a bit how old your device is and what you want to do with it.
I never lost my device or it was getting stolen so as long it's in my pocket I don't need encryption.
But that's just my personal opinion.
Sent from my Moto G5 Plus using XDA Labs
Hey so I found a really cool way to decrypt but ROM after it's already been encrypted and you have all your stuff in it, I figured it out on accident. What I did was simply did a backup through TWRP and formatted the drive. When I restored the drive it was decrypted! And all this time everyone ever told me that you cannot decrypt. Pretty cool. Actually found this out by switching to a ROM and then going back anyway maybe people should know this? Hope it helps thanks for all the pointers
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......