Related
UPDATE: Do not flash cm-11 roms with the current stable version (2.6.3.0) of TWRP. It won't work. I will create new builds for the I9195 and the I-9190 after someone this issue.
Hi!
I've compiled a TWRP 2.6.3.0 for the Samsung Galaxy S4 Mini LTE (GT-I9195) with crypto support. I've attached a screencapture during an installation of an cyanogenmod update from my encrypted /data partition using goomanager. So i thought, maybe someone can use this because i didn't find any build for the device yet.
I'm not sure if you can use it with encrypted stock samsung roms (I've included some samsung libs, but i couldn't test it), but for cm it should work. And any unencrypted devices..
Should work for the GT-I9190 and GT-I9192 as well, as written on page 4.
Installation as usual (Odin (tar.md5.zip - needs to be unzipped) or Heimdall (.img)):
For Odin:
Download the recovery-twrp-2.6.3.0-serranoltexx.tar.md5.zip and unzip it
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up
Start Odin, uncheck "F. Reset Time" and "Auto Reboot", and then click AP button.
Select extracted "recovery.tar.md5" file and press Start button.
A blue transfer bar will appear on the device showing the recovery being transferred. Check the Message Window in Odin for: "All threads completed. (succeeded 1 / failed 0). The transfer has successfully completed.
Long press the power botton to turn it off.
Hold volume up, home button and power buttons simultaneously to boot into recovery mode.
Sorry, i couldn't post in the Developer Forum and no direct links (< 10 Post for me). And a special thanks to @Dees_Troy for helping me getting the right crypto options.
I hope the image works, first time building a TWRP for me. At least it won't brick your device
_____________
Edit 18.09.2013. (Already Fixed) If the screen locks in the recovery after a few minutes idle (without userinput), the screen gets greyish after the unlock, but the recovery still seems to work properly (see post #4 for image). I've asked in the twrp channel on freenode and tried a fix, that didn't help. . So, it seems more cosmetic. I wonder if someone else gets this, because they said in the channel, they've never seen something like that before.
_____________
Edit 19.09.2013: Sourcecode with my modifications here: https://github.com/johanneszab
Its mainly the BoardConfigCommon.mk and recovery.fstab for TWRP and enryption in the msm8930-common repo and the crypto libs in the recovery directory in the serranoltexx repo.
_____________
Edit 20.09.2013: New recovery.img without Screentimeout, so no more messed up screen after screenlock.
_____________
Edit 28.09.2013: Added SELinux and exfat and removed USB-OTG Support. Recovery should be ready for Android 4.3 with this settings. You won't lose SELinux contexts if you should ever make a backup and then restore it. Thanks to @Dees_Troy for the SELinux informations!
_____________
Edit 19.10.2013: Recreated, reuploaded and tested .tar.md5.zip file with odin since i somehow completely ****ed it up (post #12 and so forth). I'm so sorry for all those broken files without testing and thanks for the Info!
Code:
$ md5sum recovery-twrp-2.6.3.0-serranoltexx.img
9262c28bf81632c66ff1133d6078c8c6 recovery-twrp-2.6.3.0-serranoltexx.img
$ md5sum recovery-twrp-2.6.3.0-serranoltexx.tar.md5.zip
e5014d5e230a5bb1103771b30dd2a159 recovery-twrp-2.6.3.0-serranoltexx.tar.md5.zip
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Whosat said:
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Click to expand...
Click to collapse
Yap, I think that should work. I've read that heimdall is just an open source replacement for odin and i used heimdall because i've followed the cyanogenmod install instruction for the serranoltexx. They flashed the cwm-recovery with heimdall and it worked. So, i think, it will do it
Its my first samsung device, i've just got it 2 weeks ago, and for my old N1 there wasn't much flashing lately.. so many changes for me
Whosat said:
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Click to expand...
Click to collapse
in odin it is not possible to select an .img file fpr flashing. i found this thread that discribes how to convert a .img to an odin flashable file
edit: i converted the file and flashed it successfully with odin. recovery works. i did a backup => ok
two issues / questions:
1) the graphic gets messed after the screen goes off ( i cant supply a screenshot right now)
2) backups going to the internal sdcard. is it possible to change the backup path to the external sdcard? - found it myself
finally i took a screenshot can you please check this
ratelutz said:
edit: i converted the file and flashed it successfully with odin. recovery works. i did a backup => ok
two issues / questions:
1) the graphic gets messed after the screen goes off ( i cant supply a screenshot right now)
2) backups going to the internal sdcard. is it possible to change the backup path to the external sdcard? - found it myself
finally i took a screenshot can you please check this
Click to expand...
Click to collapse
Ah, thanks for clarifying odin for me
Okay, since i'm not the only one with that screentimeout issue, i've modified the image and completely disabled it for now. I think it's anyways not really necessary in a recovery. Well, as it seems to only happen with the S4 mini and happened to you as well, it's maybe driver/chipset related and would take some more time to fix. And i'm not so much into that code..
I reuploaded the image in my first post. Works fine for me now.
Iirc, Mobile Odin is capable flashing .img files? Going to test it after i switch roms and report back.
E: Ah, silly me, should've known our device is not supported by Chainfire
labbe- said:
Iirc, Mobile Odin is capable flashing .img files? Going to test it after i switch roms and report back.
E: Ah, silly me, should've known our device is not supported by Chainfire
Click to expand...
Click to collapse
Okay, i used these simple 3 steps to make that .zip into a .tar.md5 and attached it in my first post:
Code:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
Hope that file works with Odin now.
yeah i used that method as well
Sent from my GT-I9195 using Tapatalk 2
Can I flash CyanogenMod with this?
My question is that can I flash CyanogenMod with this recovery as in the installation of CyanogenMod it says only install with
"Use ClockworkMod Recovery.
Warning: Only use this recovery to flash CM-10.2. Otherwise, you risk bricking your phone!"
I just wanted to clarify.
It should work
This is very interesting when I try to flash it via odin, odin stops responding and I have to close it.
Nevermind used heimdall and flashed it. The long awaited twrp is here. I made several post asking for this and I love it. Finnaly a real useful recovery
Whosat said:
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Click to expand...
Click to collapse
Yes you can confirm that this build of TWRP is an alternative to CWM through Odin BUT the provided .tar.md5 crash Odin everytime !
The solution i've found is : (Linux required...)
-> download the .img file attached to this post and rename it to recovery.img
-> then create the .tar.md5 from the previous file using this code :
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Code which has already been given by @johanneszab on his post !
I have then an Odin flashable & working TWRP build ... i can attach it to this post if anybody wants to I've tested it a little bit : partitions successfully seen, wiped cache & dalvik and finally backed up stock SAMSUNG ROM OK :thumbup:
Have a nice day
Tapatalked from my TF300T
PS : Great work @johanneszab :thumbup:
ne0zone75 said:
Yes you can confirm that this build of TWRP is an alternative to CWM through Odin BUT the provided .tar.md5 crash Odin everytime !
The solution i've found is : (Linux required...)
-> download the .img file attached to this post and rename it to recovery.img
-> then create the .tar.md5 from the previous file using this code :
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Code which has already been given by @johanneszab on his post !
I have then an Odin flashable & working TWRP build ... i can attach it to this post if anybody wants to I've tested it a little bit : partitions successfully seen, wiped cache & dalvik and finally backed up stock SAMSUNG ROM OK :thumbup:
Have a nice day
Tapatalked from my TF300T
PS : Great work @johanneszab :thumbup:
Click to expand...
Click to collapse
Did you also a restore from backup. Worked the phone well after restore?
ladislav.heller said:
Did you also a restore from backup. Worked the phone well after restore?
Click to expand...
Click to collapse
Not yet... I'll give it a try today
Tapatalked from my GT-I9195
Is it possible to flash recovery-twrp-2.6.3.0-serranoltexx.img via dd command directly from Terminal Emulator?
Anybody tried?
The command should be something like this:
dd if=/sdcard/recovery-twrp-2.6.3.0-serranoltexx.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=512
But I am not sure whether the above is correct.
ne0zone75 said:
[..] BUT the provided .tar.md5 crash Odin everytime !
Click to expand...
Click to collapse
hmm, strange stuff . Thanks for that info! I had even checked md5sums and the command history for the file. Didn't test it with odin though, still haven't it installed. So, i recreated the file, maybe this time it works, ..
johanneszab said:
hmm, strange stuff . Thanks for that info! I had even checked md5sums and the command history for the file. Didn't test it with odin though, still haven't it installed. So, i recreated the file, maybe this time it works, ..
Click to expand...
Click to collapse
Odin still craches right afther you hit "start"....
EDIT:
Installed the recovery using heimdall, but I'm still not able to mount the USB-OTG....
Does anyone have the same problem, have the same with CWM-recovery?
Keon91 said:
Odin still craches right afther you hit "start"....
EDIT:
Installed the recovery using heimdall, but I'm still not able to mount the USB-OTG....
Does anyone have the same problem, have the same with CWM-recovery?
Click to expand...
Click to collapse
I'm so sorry for those crap odin files . I'm going to install odin now, make a third new image and flash it once to make sure it works. This is so strange because those 3 commands are no brainer . Maybe ubuntu messed up their tar .. i don't know :/.
I've turned off USB-OTG in the build, because i thought that the S4 Mini doesn't support it (and it depends on some hardware?!). I've no clue about USB-OTG, but i've read in the forums here in some posts that the S4 Mini doesn't support it and i couldn't try it in my first builds that included USB-OTG, because i don't have any hardware for it, ..
johanneszab said:
I'm so sorry for those crap odin files . I'm going to install odin now, make a third new image and flash it once to make sure it works. This is so strange because those 3 commands are no brainer . Maybe ubuntu messed up their tar .. i don't know :/.
I've turned off USB-OTG in the build, because i thought that the S4 Mini doesn't support it (and it depends on some hardware?!). I've no clue about USB-OTG, but i've read in the forums here in some posts that the S4 Mini doesn't support it and i couldn't try it in my first builds that included USB-OTG, because i don't have any hardware for it, ..
Click to expand...
Click to collapse
As i posted above, i've created successfully a flashable Odin file using your IMG one AND i used Ubuntu 12.04.3 x64 to perform this so Ubuntu is not involved in the difficulties you're facing for creating a working TAR.MD5; i'd like to suggest that those difficulties are maybe caused by the filename you give to the input / output of your shell commands ... in my experience they have to be the same and short (only filename extension differs of course).
That said you did a really great job with your TWRP build :thumbup: ... i know this is a difficult task to build one
PS : I still do not have tested the restore process of my device's nandroid backup i made earlier this week using your TWRP build ...
Tapatalked from my TF300T
I'm sorry , I don't mean usb-otg but how can I Mount my storage sdcard and / or internal storage to my pc, trough USB?
Sent from my GT-I9195 using xda app-developers app
****** I DO NOT TAKE ANY RESPONSIBILITY FOR ANY BRICKS/BOOT LOOPS/Mi LOGO BRICK. I AM SHARING THE STEPS THAT I HAVE USED AND YOU USE THESE STEPS AT YOUR OWN RISK ******
Use Android Image Kitchen to decompress and Recompress.
Unzip the whole Kitchen and ROM files through 7 Zip * mode.
Copy the "boot.img" to the Android Kitchen Unzipped Folder.
Follow the following steps:
Step 1. Decompress the boot.img file through Android Image Kitchen (unpackimg.bat)
Step 2. Open the file "fstab.qcom" via notepad / notepad++.
Step 3. Remove the ".verify" from it and save the file. Do not change the file extension. (Though it should not ask/or do). (This unlocks bootloader over server).
Step 4. Open default.prop via notepad / notepad++.
Step 5. Change "ro.secureboot.devicelock=1" to "ro.secureboot.devicelock=0" (This unlocks the bootloader).
- Additional Amendments if you want, like enabling adb, debug, etc, then do Step 6, else go to Step 7. STep 6 somehow seems to have some error on WiFi access. In case you do not want that, do not perform Step 6. a. and 6.b.,.
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.adb.secure=0"
These enable OEM Unlock over Server and over Developer mode.
c. "ro.debuggable=0" to "ro.debuggable=1".
This turns on USB Debug.
d. "persist.sys.usb.config=none" to "persist.sys.usb.config=adb"
This turns on ADB mode.
e. "persist.sys.timezone=Asia/Shanghai" to "persist.sys.timezone=Asia/XXX".
One can set the default locale from here. (This does not seem to work on Beta ROM's, as the server denies setting locale). (Though it should not ask/or do).
- Save the file. Do not change the file extension.
Step 7. Recompress these files back through repackimg.bat."
A new file "image-new.img" will be created. Rename the file to "boot.img" and replace the same to the unzipped folder of the ROM.
You now have a cooked/modded boot.img within the ROM, and your device is bootloader unlocked. Now Flash the ROM through MIFlash.
Also note: Rename the TWRP/Custom Recovery image to "recovery.img" and replace it with the Stock Recovery within the ROM. Now you have Custom Recovery ROM.
These steps take no more then 5-6 minutes, and are pretty easy.
Happy Flashing.
N.B.: I have attached the Android Kitchen File here.
Is this equivalent to unofficial unlock or the official one?
BlueJeans said:
Is this equivalent to unofficial unlock or the official one?
Click to expand...
Click to collapse
Actually None. I mean not the official, nor the unofficial one.
I am on unlocked bootloader myself.
These are the steps I did to unlock my bootloader.
I have even rooted my RN3QC within 10 days from purchase.
I just wanted to unlock and have even custom TWRP 3.0.2-2.
can miflash just flash the boot.img?
meangreenie said:
can miflash just flash the boot.img?
Click to expand...
Click to collapse
Nope, I tried, and it went to bootloop once and second time to mi logo.
The easiest way to install the boot.img and the recovery.img are:
If you want TWRP to be your recovery and that too after flashing the ROM, I will ask you to replace the default recovery file within the unzipped ROM with the TWRP Recovery File. The default recovery path is within the images folder and called recovery.img.
Just rename the TWRP Recovery image file to recovery.img and replace it in images folder, and flash through MIFlash. Done.
And if you want to flash boot.img, then flash through TWRP. That is the easiest method.
Safe and no bricks.
N.B.: FYI: Few Stable ROM's have a verity check on even after official unlock. That just means that the server has not yet updated their unlock, and if it is not done manually, then it will remain locked on server.
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
NVDX11 said:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
Click to expand...
Click to collapse
Hope that moderator is not here too.
vdbhb59 said:
Hope that moderator is not here too.
Click to expand...
Click to collapse
Haha , yep :laugh:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
kraatus90 said:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
Click to expand...
Click to collapse
R3S it should not work, and as you confirmed it does not work.
Yes I am thr guy whose post got deleted, and the Mod is still adamant on saying it does not unlock bootloader.
They have changed the method to unlock on MM, so this apparently is only for LP.
vdbhb59 said:
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.secure=0"
These enable OEM Unlock over Server and over Developer mode.
Click to expand...
Click to collapse
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
abihary said:
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
Click to expand...
Click to collapse
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
vdbhb59 said:
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
Click to expand...
Click to collapse
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
abihary said:
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
Click to expand...
Click to collapse
Any day welcome.
For kenzo or hennessy?
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
For kenzo
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
Kenzo and unfortunately currently limited to LP.
Searching for MM and N pattern to unlock.
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
MiripRedmoon said:
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
Click to expand...
Click to collapse
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
vdbhb59 said:
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
Click to expand...
Click to collapse
So you are back to a locked bootloader when you moved to 6.9.9?
And for doing that you just flashed the fastboot tgz file in edl mode?
Btw, overall comment -> u mean to say .. using this process there is no need to replace/ flash the modded emmc_appsboot.mbn file?
This will restore your Indian variant Honor 7x back to stock, in case you have rooted or flashed TWRP before. After this you can get OTA updates and they will flash fine. If you want to manually flash OTA updates, you can continue to next video after watching this
I suggest you to watch it carefully and do same as I did to prevent any damages.
Downloads:
https://goo.gl/8TKYoT
Password for the zip is shared in telegram group:
MOD EDIT: LINK REMOVED
Also files access will be granted in the group for now, later they will be made public.
Text guide coming soon.
Watch on YouTube (not monetized)
Sudeep Duhoon said:
This will restore your Indian variant Honor 7x back to stock, in case you have rooted or flashed TWRP before. After this you can get OTA updates and they will flash fine. If you want to manually flash OTA updates, you can continue to next video after watching this
I suggest you to watch it carefully and do same as I did to prevent any damages.
Downloads:
https://goo.gl/8TKYoT
Password for the zip is shared in telegram group:
MOD EDIT: LINK REMOVED
Also files access will be granted in the group for now, later they will be made public.
Text guide coming soon.
Click to expand...
Click to collapse
Thanks for the helpfull information.
I have the files for BND-L24 uploaded and want to share same method of restore , for US version. As the method is the same.
Would it be ok to link to your thread from a new thread with L24 files attached , or add the backup here and just change the title?
mrmazak said:
Thanks for the helpfull information.
I have the files for BND-L24 uploaded and want to share same method of restore , for US version. As the method is the same.
Would it be ok to link to your thread from a new thread with L24 files attached , or add the backup here and just change the title?
Click to expand...
Click to collapse
Do as you like, I am good with anything.
Sudeep Duhoon said:
Do as you like, I am good with anything.
Click to expand...
Click to collapse
Ok. I like to keep thing simple. And to not complicate things as much as possible.
I will put this link to the L24 backed up images here.
File host folder with ==>BND-L24C567B140<== files
mrmazak said:
Ok. I like to keep thing simple. And to not complicate things as much as possible.
I will put this link to the L24 backed up images here.
File host folder with ==>BND-L24C567B140<== files
Click to expand...
Click to collapse
Thank you so much!! I've been looking for this all day yesterday!!
Will i have to flash all this file by twrp?
mrmazak said:
Ok. I like to keep thing simple. And to not complicate things as much as possible.
I will put this link to the L24 backed up images here.
File host folder with
Click to expand...
Click to collapse
Will i have to flash all this files by twrp? Liie flashing system.zip as system and flashing other images in partition? And if yes then there is other zip file 482 Mb how to flash it? Also in system ?
Will i be able to go to Emui 6 from Emui 8? I had manually flashed oreo.
Thanks
suryaxcharel said:
Will i have to flash all this files by twrp? Liie flashing system.zip as system and flashing other images in partition? And if yes then there is other zip file 482 Mb how to flash it? Also in system ?
Will i be able to go to Emui 6 from Emui 8? I had manually flashed oreo.
Thanks
Click to expand...
Click to collapse
All the post I see about manually flashing Oreo say you CAN NOT return to emui 5. So I would believe no
**EDIT**
I see now on firmware finder there are roll-back to emui 5.1 full-ota packages.
right now only for
BND-AL00
BND-AL10
BND-TL10
but perhaps after flashing that full ota to get partition table back , then follow this method from here to get correct regional specific parts back.
All still untested at this point
Suppose if I install Other rom first like AOSP or RR?
mrmazak said:
All the post I see about manually flashing Oreo say you CAN NOT return to emui 5. So I would believe no
Click to expand...
Click to collapse
Suppose if i install other rom RR or Aosp from Emui.and then can i ftry this method?
Thanks
suryaxcharel said:
Suppose if i install other rom RR or Aosp from Emui.and then can i ftry this method?
Thanks
Click to expand...
Click to collapse
I have no first hand information. Just that for RR you need to first update to Oreo, so same as before, the information at this point is, NO , roll-back is not able.
need help please
suryaxcharel said:
Will i have to flash all this files by twrp? Liie flashing system.zip as system and flashing other images in partition? And if yes then there is other zip file 482 Mb how to flash it? Also in system ?
Will i be able to go to Emui 6 from Emui 8? I had manually flashed oreo.
Thanks
Click to expand...
Click to collapse
What if you used recovery and went to stock but you don't have system updater and when you try to update firmware it keeps failing is there anyway to fix this on my bnd-l24?
P.S no longer have twrp
Can I try it on my Honor 7X BND-AL10 variant.??Please reply
riteshnaik77 said:
Can I try it on my Honor 7X BND-AL10 variant.??Please reply
Click to expand...
Click to collapse
Your other post show you are on Oreo. This method, files linked are Android nougat.
You need to replace twrp with stock recovery, then wipe cache from there. This should fix your bootloop ,caused by wipeimg cache in twrp. Unless there is more to the story than you tell.
mrmazak said:
Your other post show you are on Oreo. This method, files linked are Android nougat.
You need to replace twrp with stock recovery, then wipe cache from there. This should fix your bootloop ,caused by wipeimg cache in twrp. Unless there is more to the story than you tell.
Click to expand...
Click to collapse
OHHHHH!!!!..Thank you!
This is what I actually did so far.
1)I am on BND AL10 Oreo.
2)Unlocked the bootloader & rooted device.
3)Tried to flash Xposed using Magisk,Then my phone went to bootloop.
4)I tried to flash RR rom using fastboot mode.Then my phone gone mad, Now I can access TWRP ,But only for 10 sec.
5)PLEASE GUIDE ME TO A COMPLETE GUIDE WHERE I CAN FRESH START.
----------------------------------------------------------------------------------------------------------------------
riteshnaik77 said:
OHHHHH!!!!..Thank you!
This is what I actually did so far.
1)I am on BND AL10 Oreo.
2)Unlocked the bootloader & rooted device.
3)Tried to flash Xposed using Magisk,Then my phone went to bootloop.
4)I tried to flash RR rom using fastboot mode.Then my phone gone mad, Now I can access TWRP ,But only for 10 sec.
5)PLEASE GUIDE ME TO A COMPLETE GUIDE WHERE I CAN FRESH START.
----------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Well it twrp is not staying on, then fastboot will have to be the method to recover
Hope this will work
fastboot format cache
fastboot format userdata
If those not work, or not allowed try
fastboot -w
mrmazak said:
Well it twrp is not staying on, then fastboot will have to be the method to recover
Hope this will work
fastboot format cache
fastboot format userdata
If those not work, or not allowed try
fastboot -w
Click to expand...
Click to collapse
Thanks alot for your quick reply.Lemme try the method you have shared.
I did the steps in post. Was successfully able to downgrade from Oreon to Naugat. But Ota failed and phone into boot loop. Any suggestion
kavena78 said:
I did the steps in post. Was successfully able to downgrade from Oreon to Naugat. But Ota failed and phone into boot loop. Any suggestion
Click to expand...
Click to collapse
the downgrade is tricky , if not done with full downgrade files. It is pretty much a half full update, then restore a backup. There are many things that could cause trouble with this.
Did you try to factory reset after failed OTA?
mrmazak said:
the downgrade is tricky , if not done with full downgrade files. It is pretty much a half full update, then restore a backup. There are many things that could cause trouble with this.
Did you try to factory reset after failed OTA?
Click to expand...
Click to collapse
Unfortunately I do not have backup (can you share it pls if you have) after factory reset also same issue.
kavena78 said:
Unfortunately I do not have backup (can you share it pls if you have) after factory reset also same issue.
Click to expand...
Click to collapse
backup files are linked in the op
mrmazak said:
backup files are linked in the op
Click to expand...
Click to collapse
Op is that 1st post? It has link to update files in rar format
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......
Hello all !
I followed this tutorial on how to root my Galaxy S10+ : https://www.thecustomdroid.com/samsung-galaxy-s10-root-guide/ but there are 2 problem:
1st: At the Step6, the file name isn't exactly magisk_patched.tar but magisk_patched-25200_xLm0q.tar. Is this a problem ?
2nd: at Step 10, when I want to exit the Download Mode (Volume Down and Power button for over 7s), the phone get in a boot-loop (which I found online that it means the phone can't find a proper OS to boot on)
How can I know what I'm doing wrong ? I have a doubt on the stock firmware I found on Frija:
my phone is a G975F-DS and there is no "G975F-DS" but only "G975F"
I can't use Phone Info Sam because the link is broken/the app doesn't exist anymore ? When I type *#1234# the CSC code is G975FOXMGHWA3. I searched OXM but couldn't find anything on Frija so I search and I've read that OXM is not the correct CSC Code so I went to Software INFO and in the Service provider software version it's written ...SM-G975F_OXM_XSP... so I chose the XSP firmware and did the root with it until the phone boot-looped.
My service provider now in KT in Korea, does it make a difference ?
Thank you for reading me
Edit: I found Phone INFO ★SAM★ 3.8.5 By vndnguyen on APK Mirror and it says " Firmare's CSC Code: XEF" and "Active CSC Codes: XSP". Which one is correct ?
Reflash the stock firmware, then flash TWRP and flash Magisk in TWRP.
First Flash Offical firmware (BL,AP,CP,CSC)
Then Patch AP file by magisk
windows4droid said:
First Flash Offical firmware (BL,AP,CP,CSC)
Then Patch AP file by magisk
Click to expand...
Click to collapse
Isn't it the same as Step 6 from the tutorial ?
V0latyle said:
Reflash the stock firmware, then flash TWRP and flash Magisk in TWRP.
Click to expand...
Click to collapse
May I ask a trustful tutorial on how to do it please ?
Constantine1711 said:
Isn't it the same as Step 6 from the tutorial ?
May I ask a trustful tutorial on how to do it please ?
Click to expand...
Click to collapse
The firmware must be flashed first
Then you make a patch from the AP file
The baseband of the device must be identical to the firmware from which the root file is made
windows4droid said:
The firmware must be flashed first
Then you make a patch from the AP file
The baseband of the device must be identical to the firmware from which the root file is made
Click to expand...
Click to collapse
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
V0latyle said:
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
Click to expand...
Click to collapse
Yes, you can try twrp
[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea) Disclaimer I am not responsible for bricked devices, dead SD...
forum.xda-developers.com
Edit: see below
V0latyle said:
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
Click to expand...
Click to collapse
I did that and now my Phone Status is Custom but Root Checker says Root access is not properly installed.
Constantine1711 said:
I did that and now my Phone Status is Custom but Root Checker says Root access is not properly installed.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?
V0latyle said:
What version of Magisk are you using and where did you download it from?
Click to expand...
Click to collapse
I got the v25.2 from magiskmanager.com/
Constantine1711 said:
I got the v25.2 from magiskmanager.com/
Click to expand...
Click to collapse
NEVER download Magisk from anywhere but the official Magisk repo. That is the ONLY trustworthy source; any other source is not affiliated with the project and may be malware.
V0latyle said:
NEVER download Magisk from anywhere but the official Magisk repo. That is the ONLY trustworthy source; any other source is not affiliated with the project and may be malware.
Click to expand...
Click to collapse
Oops ... what's the risk ? Should I reset my phone again ?
Constantine1711 said:
Oops ... what's the risk ? Should I reset my phone again ?
Click to expand...
Click to collapse
The risk is malware, like a virus. If you've had questionable apps with root access, I would absolutely recommend you perform a clean factory flash.
V0latyle said:
The risk is malware, like a virus. If you've had questionable apps with root access, I would absolutely recommend you perform a clean factory flash.
Click to expand...
Click to collapse
Is it possible to check if an apk is different from the github one ? Like a code checker or something. I'm so tired of reseting my phone it's been a week I try to root it ...
Otherwise, maybe I'll try with an other tutorial.
The Proper Way to root your S10 (10+,10e) Device and get it Right! Tipps & Tricks
Hi Guys :cowboy: Today I want to bring some simple and effektive Insights on proper Device & Software Management and also about Mistakes on the Way and Solutions! :good: ;) So make yourself comfortable and check this out! It will really help...
forum.xda-developers.com
Is this one a good one ?
Is it just me getting older or rooting a device got much more complicated than before ? (I use to root PSP/playstation2 and 3 in the past)
I missed having full control of my device so I thought to root my phone but it's seems so complicated for so little reward
Edit: I tried to follow the official Magisk tutorial but I failed so I'm just gonna stop trying here. Sorry for wasting your time guys !