Greetings!
I'd like to present a TWRP recovery for the Xperia X Compact. This release should work on Xperia X single and dual-SIM variant of the device. I am an owner of Xperia X, but some users reported that my recovery works just fine on its smaller brother.
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-kugo-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds, you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Thank you for sharing.
thanks
Thanks for sharing brother
Working ⚒ perfectly on stock 7.0
no problem
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
XperienceD said:
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
Click to expand...
Click to collapse
That shouldn't work anyway. I can enable these flags if you want.
eagleeyetom said:
That shouldn't work anyway. I can enable these flags if you want.
Click to expand...
Click to collapse
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
XperienceD said:
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
Click to expand...
Click to collapse
It didn't work for me on X. I can enable them in the next version.
realtuxen said:
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Click to expand...
Click to collapse
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
trewelu said:
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
Click to expand...
Click to collapse
Exactly. I know hotbooting is not the best description, but you understood anyway.
Strange, I am not a flashophile so I usually just booted twrp this way after a upgrade with flashtool. When the phone was connected to the pc anyway.
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
I see you are still on MM, I have been on N since it came out and if I remember correctly I backed up ta just before N came out (exploit and N came out very close to each other), took the ota, and unlocked BL. So I performed all the 'fastboots' (better word? heh) on that and 7.1.1. Perhaps the bootloader changed someway? I have no idea.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
---------- Post added at 20:00 ---------- Previous post was at 19:58 ----------
kekistaneerefugee said:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
Click to expand...
Click to collapse
MTP works absolutely fine here..
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
eagleeyetom said:
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
Click to expand...
Click to collapse
Is this in response to something functional, or just general cosmetics info? Doesn't the sony screen origin from the bootloader? How should a official twrp look while booting it? I get the sony boot and led then the TWRP boot image, isn't that normal when booting fotakernel replaced by TWRP? ie. the bootloader handles it when turning the phone on while holding vol down.
An official version would sure be nice. I more than appreciate what you already done. So just take your time.
realtuxen said:
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
Click to expand...
Click to collapse
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
trewelu said:
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
Click to expand...
Click to collapse
Why are you running it through both ta_poc and Tobias rootkernel with drm fix?
Either you use ta_poc to mount your ta backup from before the bootloader was unlocked thereby bringing the whole trim area back including drm.
Or you use Tobias rootkernel to fix or 'emulate" drm.
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
If you for example run a boot.img with drm fix through ta_poc it will remove the drm fix first. So I imagine things could go wrong of you apply drm fix again (if that is what you're doing) after using ta_poc.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
Click to expand...
Click to collapse
Lol I hate it general too, it can come in handy when only twrp is booted though. I am not sure I have any drivers installed either. Regardless I can access a drive resembling my phone labeled 'mtp device' in 'my computer' when I boot twrp.
Edit: sorry for sidetracking the thread a bit.
eagleeyetom said:
NEEDS TESTING
USB-OTG
Click to expand...
Click to collapse
Thanks! and i can confirm that USB OTG works well.
Working on Sony Nougat
This is the only TWRP I can decrypt my data with on Sony Nougat Stock ROM, Thanks !
realtuxen said:
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
Click to expand...
Click to collapse
Using both tools stems from users reporting they had to to get Magisk to work.
XperienceD said:
Using both tools stems from users reporting they had to to get Magisk to work.
Click to expand...
Click to collapse
There was an info in one of threads, that you should get the stock kernel first through TA_POC and then through kernel repack tool. If you did not, it would work, but occassionally reboots. I am now on 7.1.1 build 206 with Genesis Kernel 1.05 (no_DRM patch version) and it works ok.
As for TWRP, thanks for this! It works ok. Can not fastboot it, must be flashed in recovery parition, but no deal for me. Only thing that I wonder, there are options to backup system, data etc, but not Internal SD (/data/data). Why?
Hi I have a question, I have N 7.1.1, and i want to root it, so i need the twrp, if I flash this twrp, its okay? Ty!
Related
Mount USB storage does not work with CWM. Will sort out soon... maybe...
First thing.
Question | Answer
Click to expand...
Click to collapse
Users:
Q: Why not make 2 separate posts?
A1: Normally I'd say "I Didn't feel like it", but its more like "I didn't see the need to."
A2: You all should be adult enough to say which you're using if problems arise.
Q: Why label beta.
A: Cause testing is really needed and I don't count myself as a test.
Q: What works?
A: Flashing, USB mount, wiping.... you know recovery stuff....
Developers:
Q: We've been trying and havent been able to get usb mounting to work... How did you?
A1: I didnt really... I figured the problem didnt come from any of the setup used to build the recovery... but the recovery kernel itself.
A2: I used the stable CWM5504, pulled the kernel from that and used the prebuilt kernel in place of building from source. Hopefully a real genius *cough*kornyone*cough* hits the nail *IF* he ever has spare time. PS thanks to xmcwildchild's stable.
Now your toys!
Click to expand...
Click to collapse
Clockworkmod 6.0.4.6 (MD5: 9d37a1029b9f5e79bbef8cb55632e7d7)
Team Win Recovery Project 2.6.3.0 (MD5: 2a227d0607e10892e7d5e15d0d3a4625)
Team Win Recovery Project 2.6.3.0 w/ DumLock (MD5: f3af450c43c03d790f8e1241a60d6efc)
TWRP Update info @ http://teamw.in/project/twrp2
Backups (there are some changes in future roms that made it problematic to flash with older recoveries, noobie kieranmenor reported a problem not being able to flash older roms with the current TWRP.)
Clockworkmod 6.0.3.6
Team Win Recovery Project 2.6.3.0
Team Win Recovery Project 2.6.3.0 w/ DumLock
Typical disclaimers apply. Good luck.
Downloading twrp now. Any difference between this and riyals version?
mattlowry said:
Downloading twrp now. Any difference between this and riyals version?
Click to expand...
Click to collapse
Aside from being the latest, I dont think so. I didnt even remember about Riyal's until you mentioned it otherwise I may have just not done it at all.
ahh yes thanks for making these! i contacted riyal about twrp 2.3, he said he didn't know it was out of beta and that he would look into it (and then i think his phone died?) and now you picked it up! will test and let you know how it goes.
btw does it have offline charging? i remember riyal made an offline charging version of his twrp
---------- Post added at 02:29 PM ---------- Previous post was at 02:23 PM ----------
for those who want to flash this but don't know how, here are instructions (from an old recovery thread by xmc_wildchild22
From Terminal Emulator
su
dd if=/sdcard/RECOVERY.img of=/dev/block/mmcblk0p21
reboot recovery
From ADB
adb reboot bootloader
fastboot flash recovery RECOVERY.img
fastboot reboot
where "RECOVERY.img" is the respective name of the recovery you want to flash
anitgandhi said:
ahh yes thanks for making these! i contacted riyal about twrp 2.3, he said he didn't know it was out of beta and that he would look into it (and then i think his phone died?) and now you picked it up! will test and let you know how it goes.
btw does it have offline charging? i remember riyal made an offline charging version of his twrp
Click to expand...
Click to collapse
No, it does what the phone normally does. Orange blinking light where you cant do squat til you take it off the charger.
I also dont know how he did it, and... may not be able to add it myself. :/
SilverL said:
First thing.
Users:
Q: Why not make 2 separate posts?
A1: Normally I'd say "I Didn't feel like it", but its more like "I didn't see the need to."
A2: You all should be adult enough to say which you're using if problems arise.
Q: Why label beta.
A: Cause testing is really needed and I don't count myself as a test.
Q: What works?
A: Flashing, USB mount, wiping.... you know recovery stuff....
Developers:
Q: We've been trying and havent been able to get usb mounting to work... How did you?
A1: I didnt really... I figured the problem didnt come from any of the setup used to build the recovery... but the recovery kernel itself.
A2: I used the stable CWM5504, pulled the kernel from that and used the prebuilt kernel in place of building from source. Hopefully a real genius *cough*kornyone*cough* hits the nail *IF* he ever has spare time.
Clockworkmod 6.0.2.7
Team Win Recovery Project 2.3.3.0
Typical disclaimers apply. Good luck.
Click to expand...
Click to collapse
What are the technical benefits/detractions (pluses/minuses) of these compared to CWM 5.5.0.4 or 5.0.2.7?
Fuzi0719 said:
What are the technical benefits/detractions (pluses/minuses) of these compared to CWM 5.5.0.4 or 5.0.2.7?
Click to expand...
Click to collapse
Aside from reading somewhere that the newer versions of android(4.2+) will require a recovery update.
Also saw it here too.
Both of these recoveries have installing from sideload, ability to delete backups from within the recovery, higher version numbers(always means better -_-) and some other minor things.
TWRP you can name backups immediately. Full touch interface, extremely theme-able. Works well with GooManager. Queue multiple zips.
CWM has another backup type option dedupe(not a fan of it). Looks better...
Essentially about as technical as going from ICS to JB and JB to new JB. -_-
post the boardconfig.mk you used with this, let me see if you're missing any flags
xmc wildchild22 said:
post the boardconfig.mk you used with this, let me see if you're missing any flags
Click to expand...
Click to collapse
Its the default one on TeamDS. Minor changes because I had to use that prebuild kernel. Its currently a mess. What do you think would be missing? Have you encountered any problems?
SilverL said:
Its the default one on TeamDS. Minor changes because I had to use that prebuild kernel. Its currently a mess. What do you think would be missing? Have you encountered any problems?
Click to expand...
Click to collapse
When I turned on the theme prom and the emulate processes or something like that in twrp I had problems flaking a rom I even rebooted the recovery so I turned that option off then my roms flash again
Sent from my MyTouch 4G Slide using xda premium
butch87402 said:
When I turned on the theme prom and the emulate processes or something like that in twrp I had problems flaking a rom I even rebooted the recovery so I turned that option off then my roms flash again
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Exact options would be helpful...
Anyway. If you turned on a theme and the simulate actions for theme testing.
Then I assume the simulate options is what caused the not problem you had.
Before you start creating a custom theme, you should tap on settings and tap the checkbox for "Simulate most actions for theme testing" to enable simualation mode. This setting will cause TWRP to simulate most actions including installing zips, backup, restore, partitioning sdcards, etc. In this mode you can safely test a theme without wearing out the memory chips on your device. There's also a checkbox for simulating failure that will appear on the settings page when you turn on simulation mode. This checkbox will cause TWRP to report a failure for all simulated actions instead of success so that you can provide the appropriate message on the screen. Don't forget to disable simulation mode when you're done!
Click to expand...
Click to collapse
- Source
SilverL said:
Aside from reading somewhere that the newer versions of android(4.2+) will require a recovery update.
Also saw it here too.
Both of these recoveries have installing from sideload, ability to delete backups from within the recovery, higher version numbers(always means better -_-) and some other minor things.
TWRP you can name backups immediately. Full touch interface, extremely theme-able. Works well with GooManager. Queue multiple zips.
CWM has another backup type option dedupe(not a fan of it). Looks better...
Essentially about as technical as going from ICS to JB and JB to new JB. -_-
Click to expand...
Click to collapse
Is the new CWM or TWRP compatible with the backups done with CWM 5.5.0.4/5.0.2.7? All of my nandroid backups are done with 5.5.0.4.
Fuzi0719 said:
Is the new CWM or TWRP compatible with the backups done with CWM 5.5.0.4/5.0.2.7? All of my nandroid backups are done with 5.5.0.4.
Click to expand...
Click to collapse
TWRP is not compatible with CWM and vice versa. The CWM backups should still be compatible. One way to test is to flash, see what happens if it doesnt work... go back? Doesnt kill. I did it when testing and swapped between TWRP and CWM and back to old 5.5.0.4 then back to these again. Now I'm on TWRP, hopefully permanently.
Flashed TWRP and immediately backed up my CM9 nightly without a problem. Mounted USB storage and transferred over a new ROM, went back and forth to bootloader since I'm S-ON, no problem. This recovery doesn't feel beta to me, in a good way. I haven't tried restoring from my backup yet but I'm not worried. I got spoiled using 4EXT on my old phone and going back to CWM never felt right. This TWRP is definitely a step in the right direction. Being able to boot into bootloader from recovery is awesome from a S-ON standpoint. No more waiting to power off and then restart holding buttons or screwing it up and having to remove my case for a batpull. Full touch support speaks for itself.
Thanks so much for getting us a new recovery option. This is the biggest update for our device in a while :good:
aawillma said:
Flashed TWRP and immediately backed up my CM9 nightly without a problem. Mounted USB storage and transferred over a new ROM, went back and forth to bootloader since I'm S-ON, no problem. This recovery doesn't feel beta to me, in a good way. I haven't tried restoring from my backup yet but I'm not worried. I got spoiled using 4EXT on my old phone and going back to CWM never felt right. This TWRP is definitely a step in the right direction. Being able to boot into bootloader from recovery is awesome from a S-ON standpoint. No more waiting to power off and then restart holding buttons or screwing it up and having to remove my case for a batpull. Full touch support speaks for itself.
Thanks so much for getting us a new recovery option. This is the biggest update for our device in a while :good:
Click to expand...
Click to collapse
Overall they should be stable, I listed them as beta because I cannot account my successes as testing. I would like to see a few more pages before classifying as stable.
I'd also like to possibly build them completely from source at some point too.
@SilverL
I just noticed your thread and I'm glad you saved me time updating my TWRP recovery. I lost all the source code of my previous twrp and was frustrated porting it again from scratch Downloading it now...
By the way the offline charging version of my TWRP is here
http://forum.xda-developers.com/attachment.php?attachmentid=1374782&d=1349346744
just extract the ramdisk and you should see the workaround I made. There's no additional binary added. The offline charging I made is just pure shell script and edits on the rc files so it should be pretty easy for you.
Regarding a full compile use a CM7 kernel and add the doubleshot board files and drivers and you should be good to go. Also I used the boardconfig of MT4G(non slide).
Anyways the boardconfig isn't the issue but the kernel. The USB driver of ICS isn't compatible with twrp and that's the issue. Even Dees_Troy couldn't even make a build with fully working USB on CM9
Riyal said:
@SilverL
I just noticed your thread and I'm glad you saved me time updating my TWRP recovery. I lost all the source code of my previous twrp and was frustrated porting it again from scratch Downloading it now...
By the way the offline charging version of my TWRP is here
http://forum.xda-developers.com/attachment.php?attachmentid=1374782&d=1349346744
just extract the ramdisk and you should see the workaround I made. There's no additional binary added. The offline charging I made is just pure shell script and edits on the rc files so it should be pretty easy for you.
Regarding a full compile use a CM7 kernel and add the doubleshot board files and drivers and you should be good to go. Also I used the boardconfig of MT4G(non slide).
Anyways the boardconfig isn't the issue but the kernel. The USB driver of ICS isn't compatible with twrp and that's the issue. Even Dees_Troy couldn't even make a build with fully working USB on CM9
Click to expand...
Click to collapse
Thanks, I figured it needed a gb kernel to do its thing. Especially after I realize the android usb kernel driver is also responsible for adb(which didnt work either). Also its not just with twrp, it affects cwm as well. Both of these use the exact same kernel.
If getting an old kernel if required then I wont even worry about it. I'll just keep my CM10 build environment the way it is just in case I have to update these in the future. I will also check out the shell script and the rc edit. Thanks, if you want to take twrp back its all yours.
to be more specific it's this one
init.rc
service detect_charge /sbin/detect_charge
oneshot
Click to expand...
Click to collapse
and on
/sbin/detect_charge
#!/sbin/sh
if [ `cat /sys/class/power_supply/battery/charging_enabled` = '1' ]
then
start offmode_charging
else
start recovery
fi
kill -9 $$
Click to expand...
Click to collapse
Can't do anything as of the moment since I don't have any working MT4GS at hand. Also I have lots of different projects planned so I might leave twrp to you as it is here.
Riyal said:
to be more specific it's this one
init.rc
and on
/sbin/detect_charge
Can't do anything as of the moment since I don't have any working MT4GS at hand. Also I have lots of different projects planned so I might leave twrp to you as it is here.
Click to expand...
Click to collapse
I'll try to throw this in for the guys that want it....
And since no one has complained(except for that one guy who couldnt flash because he put his phone in the 'feature' to simulate those events rather than actually do them) or died. I'll consider these stable.
Might also have to add my usual, "I am a jerk. Will laugh at you if you do something dumb, etc." disclaimer to this as well since.... most people dont know that I am. -_-
Flashed CWM 6!!!
everything is fine
however, transfering titanium backup files from pc to microsd class 10 is kinda of slow when i mounted it as usb storage inside the recovery
and
thank you for your good work. What's next? CWM touch?
Removed
Reserved for Links and Firmwares
It turns out a permissive Kernel helps with the Storage Problems. I will edit the Guide later with a Link
Nice guide brother, this works also on xperia 1 i think ?
Sorry for my guide, i have no time to update it anymore so thats why its kinda outdated and i found those files on a chinese site in my guide so i shared it only
Xperia
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Pandemic said:
Nice guide brother, this works also on xperia 1 i think ?
Sorry for my guide, i have no time to update it anymore so thats why its kinda outdated and i found those files on a chinese site in my guide so i shared it only
Click to expand...
Click to collapse
Same Steps, different Files like You can imagine. I made two Folders on Google Drive to keep them seperated. :angel:
I was wondering if we can use the TWRP Installer Zips from like for example the Pixel 2 XL which is almost the same as what we flash actually. Our TWRP is actually from a One Plus 2 or so, while using an old Lazy Flasher with old Magisk Boot File. While the newer TWRP Installers are using a Magisk kind of Installer to do the Ramdisk changes. Only thing i wonder is if the included ramdisk cpio is Device specific or a general thing which shares between different devices!? I'm really about to just try a flash on risk but i would like to here if You know that...
@MartinX3 can hopefully look at this
The ramdisk also contains device specific files
I put the twrp 1/5 on my to-do list
Pandemic said:
@MartinX3 can hopefully look at this
Click to expand...
Click to collapse
MartinX3 said:
The ramdisk also contains device specific files
I put the twrp 1/5 on my to-do list
Click to expand...
Click to collapse
We found together @Pandemic just asked @MartinX3 some Hours ago if he can invite us to the Xperia TWRP Family on his XZ2 Thread, and You mentition him over to this Thread. Funny
It's really no fun actually to recover my Xperia after Bootloops with Fastboot instead of TWRP. Really throw my Hat in the air once we get a working Recovery. If i can help in any way, let Me know Martin!
Wish You a good Start in the coming Week Guys! :fingers-crossed:
Miustone said:
We found together @Pandemic just asked @MartinX3 some Hours ago if he can invite us to the Xperia TWRP Family on his XZ2 Thread, and You mentition him over to this Thread. Funny
It's really no fun actually to recover my Xperia after Bootloops with Fastboot instead of TWRP. Really throw my Hat in the air once we get a working Recovery. If i can help in any way, let Me know Martin!
Wish You a good Start in the coming Week Guys! :fingers-crossed:
Click to expand...
Click to collapse
Yeah haha and i spoke him also in private
I honestly cant wait to see what lineage looks like on the Xperia 5. The stock UI is good but it feels out of place compared to my other Xperia phones
Does this require unlocked bootloader?
BuyXRPnow! said:
Does this require unlocked bootloader?
Click to expand...
Click to collapse
Yes
TWRP freezes when i try step 18, until i hard reboot. I also can't mount the storage to put the zips on my phone. Don't know what else to do. Also my touchscreen has stopped working in android, but still works on twrp.
Joran95 said:
TWRP freezes when i try step 18, until i hard reboot. I also can't mount the storage to put the zips on my phone. Don't know what else to do. Also my touchscreen has stopped working in android, but still works on twrp.
Click to expand...
Click to collapse
Please try : "fastboot flash boot_a ..." instead of just "fastboot flash boot ..." and repeat with "fastboot flash boot_b ...". This will flash the Recovery to both booth Slots. after that do "fastboot -w" which will format Your Device. Reboot into the Recovery and repeat Step 18 if possible. Would be nice to hear from You again!
Edit: You need to pass Step 18 to use Your Storage. After flashing the Zips will Your System start to work normally again. (Touch and everything else)
VIdeo Guides coming this Weekend! Stay tuned!
Miustone said:
Please try : "fastboot flash boot_a ..." instead of just "fastboot flash boot ..." and repeat with "fastboot flash boot_b ...". This will flash the Recovery to both booth Slots. after that do "fastboot -w" which will format Your Device. Reboot into the Recovery and repeat Step 18 if possible. Would be nice to hear from You again!
Edit: You need to pass Step 18 to use Your Storage. After flashing the Zips will Your System start to work normally again. (Touch and everything else)
Click to expand...
Click to collapse
Thank you for the advice! I actually got my phone working with (just) magisk with your other tutorial, that also had the a and b slots. I'll edit it to see if this works too!
Also thank you for supporting a lesser known phone!
edit-
I've tried your new steps, but the phone still freezes when formatting it. Am I doing something stupid?
Joran95 said:
Thank you for the advice! I actually got my phone working with (just) magisk with your other tutorial, that also had the a and b slots. I'll edit it to see if this works too!
Also thank you for supporting a lesser known phone!
edit-
I've tried your new steps, but the phone still freezes when formatting it. Am I doing something stupid?
Click to expand...
Click to collapse
Just a clue, did You Set TWRP to English before doing the Format? That caused Problems for Me...
Miustone said:
Just a clue, did You Set TWRP to English before doing the Format? That caused Problems for Me...
Click to expand...
Click to collapse
Oh.. that might be it. I will try again this weekend.
Joran95 said:
Oh.. that might be it. I will try again this weekend.
Click to expand...
Click to collapse
Good luck, i will investigate some time in this to figure out whats going on... But that might be it :fingers-crossed:
First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.
Your first link doesn't work for me. The Adaway link works. FYI.
RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.
eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.
Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.
iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??
egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.
Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance
Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
TWRP Recovery Project for the Samsung Galaxy A41 [Only for Android 11 Devices, will be upgraded soon.]
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the SM-A415F.
I am not responsible for any bricked imei, when flashing TWRP backup the EFS & NVRAM partitions to be safe, do not root until having an actually good working backup, if you signal goes restore your backup, if you didn't have a previous backup I got a fix for you , flash your firmware as always but on the CP slot in Odin Flash Tool get the CP slot from a CUD4 firmware corresponding your CSC code.
Click to expand...
Click to collapse
A mantainer is required for this device, I just revived the project but someone with the device needs to mantain it.
Download - You'll always find the latest release in here: https://github.com/Galaxy-MT6768/android_device_samsung_a41xx/releasesKnown Issues / Report Issues - https://github.com/Galaxy-MT6768/android_device_samsung_a31nsxx/issuesTelegram support group - http://t.me/a31nsxx
How to install
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
Flashing Disabled vbmeta (To boot a modified system)
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/Galaxy-MT6768/android_device_samsung_a41xx
Note: The device tree should be compatible with SHRP too
Click to expand...
Click to collapse
Special thanks to:
TeamWin for the Recovery Project.
Akhil1999 for his kernel.
Zillion for re-doing Akhil's lost device tree.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?
Catoplepas said:
I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?
Click to expand...
Click to collapse
Yeah, just reflash stock firmware via Odin.
Also I should update this build, the latest isn't actually the latest.
Wait until v1.2.0 gets released
Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop
LolUnis said:
Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop
Click to expand...
Click to collapse
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis
Zillion said:
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis
Click to expand...
Click to collapse
Doesn't work the phone still goes into bootloop
LolUnis said:
Doesn't work the phone still goes into bootloop
Click to expand...
Click to collapse
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.
Zillion said:
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.
Click to expand...
Click to collapse
Where can I find the link of the Telegram group?
LolUnis said:
Where can I find the link of the Telegram group?
Click to expand...
Click to collapse
It's a public group
Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.
bestnugnification said:
Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.
Click to expand...
Click to collapse
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.
Zillion said:
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.
Click to expand...
Click to collapse
I guess I'll just repair the screen even if It's not actually worth it. Thanks though.
Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.
abcuky said:
Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.
Click to expand...
Click to collapse
The latest version works on both Android versions