Database Info

Rooting/Recovery Install for the S4... on a Mac!

I have searched high and low for an easy, clear guide to rooting/installing a custom recovery for your Galaxy S4 via Mac OSX... I couldn't find what I was looking for, so I decided to write this. I tried the Motochopper method on my Canadian S4 and it doesn't work at all (I believe that is due to an OTA breaking its functionality, similar to Sprint models).
Just to clarify - I tested and confirmed this method on the Rogers Samsung Galaxy S4 using a Mac that runs OSX Mavericks. It should work on any version of Mac OSX... and realistically this should work on any GS4 Model with an Unlocked Bootloader... the TWRP Recovery file should be the only variable.
Warning... I'm obviously not responsible for anything that happens if you test this... but I can tell you that the risk level is fairly low. It's by no means a "one-click" method but it shouldn't be very difficult if you have any experience with Flashing ROMS/Recoveries at all.
Here are the steps:
Run the Uninstaller for Samsung Kies.
Download and fully install Heimdall (will require a restart).
Download correct version of TWRP for your device (with the .img extension)
Place recovery on your desktop for easy access.
Rename recovery(for easy command line entry - named mine recovery.img)
Put your device into Download Mode (hold Volume Down, Home, Power) and plug in to your Mac.
Open Terminal on your Mac.
Verify device is connected... type “heimdall detect” into terminal then press "Enter". It should say "Device Detected".
Install the recovery using the command “heimdall flash --RECOVERY /users/”you”/desktop/recovery.img --no-reboot"
It is important that your device does not reboot. Rebooting will overwrite this recovery with the stock recovery.
You now have a custom recovery installed.
Now...
Hold "Volume Up, Home & Power"
Your device should have booted into Recovery Mode running Team Win Recovery Project (TWRP).
Now that you are in TWRP, you can simply press "Reboot" and it will provide you with a warning stating that the SU Binaries weren't found (something like that). It will then tell you to "Swipe to Install" which will root your device, retaining your custom recovery and rooting your stock ROM.
Happy Flashing.
NB

and realistically this [I said:
should[/I] work on any GS4 Model... the TWRP Recovery file should be the only variable.
Click to expand...
Click to collapse
Thanks for the right up.
Just a clarification though...you mention this should work on any GS4 model.
I don't think this will work on a GS4 with a locked bootloader, correct (such as the ATT MF3 bootloader)?

rayburne said:
Thanks for the right up.
Just a clarification though...you mention this should work on any GS4 model.
I don't think this will work on a GS4 with a locked bootloader, correct (such as the ATT MF3 bootloader)?
Click to expand...
Click to collapse
correct. at least not on the MF3 build of the AT&T S4's. that should be stated somewhere as flashing a custom recovery to an MF3 variant will result in problems. MF3 users should stick to @jortex guide right now.

rayburne said:
Thanks for the right up.
Just a clarification though...you mention this should work on any GS4 model.
I don't think this will work on a GS4 with a locked bootloader, correct (such as the ATT MF3 bootloader)?
Click to expand...
Click to collapse
100% Right. Will edit the post. I forgot that us Canadians are spoiled with our unlocked bootloaders.

In the steps, You say "run the uninstaller for Samsung Kies"
Is that a program to download or should I uninstall kies?
Sorry Noob to this stuff
Also this should work with my Galaxy S4 Sprint right?

twistmycap said:
In the steps, You say "run the uninstaller for Samsung Kies"
Is that a program to download or should I uninstall kies?
Sorry Noob to this stuff
Also this should work with my Galaxy S4 Sprint right?
Click to expand...
Click to collapse
On a Mac just drag it to trash, that's what I did and never use it. I am mdl build though

Tried to root, failed, total noon here.

Hey guys, today I tried to root my t-mobile s7 from a random YouTube video I found. After flashing a file from Odin, my phone got stuck in a boot loop.
I did a factory reset from recovery and the phone started up fine.
Now here's my problem, after doing a reset, the first thing I noticed was that while I was booting up the phone. It showed the usual Samsung Galaxy S7, followed by an unlocked padlock with the words "Custom" under it.
2nd issue. My phone just looks a lot different than when I originally bought it. It is also very sluggish, experiencing a lot of lag.
I've looked up how to go back to stock firmware but I'm not sure which one to use.
Any help would be appreciated.
I'm currently on the PG1 firmware.

It appears you still have the eng kernal... You can just re-run the root.bat and install SuperSu, or if you want complete stock follow the steps below:
*Also Before you try this turn it off and let it charge for 45 min-1 hour or so...*
1. Volume Down + Power + Home to put it in download mode
2. Then press Volume Up to continue past the warning screen even if nothing is displayed.
3. Grab The Latest Version of Odin here
4. Then Download The Stock Firmware, in this case you will need whichever version you have (if you do not remember you can just download the latest available firmware) Download Firmware and then extract it. (If you have 5 different files in the zip go to step 8)
5. Then install Samsung device drivers(if not already).
6. Start Odin, Plug in the S7, Load in the tar.md5 in the AP/PDA and uncheck Auto Reboot and Repartition.
7. Let the phone restart... VIOLA!!!
8. Alternatively if the zip has 5 files... They should all start with the corresponding buttons in Odin For Example:
AP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
BL_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
After they are entered into Odin you hit start and after a few minutes ... It should be fixed....
Let me know if you have any further questions or issues...

The custom is normal since you flashed a modified kernel.
Follow this instructions here for rooting / unrooting.
Most of these applies to Tmobile S7, expect specific ones mentioned for Verizon.
http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039

Thanks man, I'm gonna try to finish rooting. I thought my phone was just screwing up and the first part of the rooting process failed, since the bootloader.
I also tried sammobile and the download won't start.
If I were to download an earlier firmware, would I be able to update it to the most recent one?

Is it possible to revert to stock without wiping data?

Can I flash a custom kernel with flashfire?
Sent from my SM-G930T using XDA-Developers mobile app

xda23 said:
Can I flash a custom kernel with flashfire?
Click to expand...
Click to collapse
No you cannot. Or rather, science threw bootloader is still locked, your phone will not boot if you try.

KillerClaw321 said:
It appears you still have the eng kernal... You can just re-run the root.bat and install SuperSu, or if you want complete stock follow the steps below:
*Also Before you try this turn it off and let it charge for 45 min-1 hour or so...*
1. Volume Down + Power + Home to put it in download mode
2. Then press Volume Up to continue past the warning screen even if nothing is displayed.
3. Grab The Latest Version of Odin here
4. Then Download The Stock Firmware, in this case you will need whichever version you have (if you do not remember you can just download the latest available firmware) Download Firmware and then extract it. (If you have 5 different files in the zip go to step 8)
5. Then install Samsung device drivers(if not already).
6. Start Odin, Plug in the S7, Load in the tar.md5 in the AP/PDA and uncheck Auto Reboot and Repartition.
7. Let the phone restart... VIOLA!!!
8. Alternatively if the zip has 5 files... They should all start with the corresponding buttons in Odin For Example:
AP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
BL_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930TUVS3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G930TTMB3APD8_CL7856276_QB9546176_REV02_user_low_ship_MULTI_CERT.tar.md5
After they are entered into Odin you hit start and after a few minutes ... It should be fixed....
Let me know if you have any further questions or issues...
Click to expand...
Click to collapse
New to samsung here, quick question. I soft bricked with an xposed app and have to restore.
What is the difference between the csc and the home csc files and which is the correct one. I don't see a home tab in odin
Sorry for the noob question, My first Samsung device

kc6wke said:
New to samsung here, quick question. I soft bricked with an xposed app and have to restore.
What is the difference between the csc and the home csc files and which is the correct one. I don't see a home tab in odin
Sorry for the noob question, My first Samsung device
Click to expand...
Click to collapse
You can just use CSC and not the CSC Home.

Quick question, I bought a used s7 edge off Craigslist and when it's asking me to log in with another guys email. I tried contacting the guy I bought it from but he hasn't texted me back yet. Can I root it and install another rom on it to bypass the lollipop lock? Thanks guys.

Palatis3 said:
Quick question, I bought a used s7 edge off Craigslist and when it's asking me to log in with another guys email. I tried contacting the guy I bought it from but he hasn't texted me back yet. Can I root it and install another rom on it to bypass the lollipop lock? Thanks guys.
Click to expand...
Click to collapse
I don't know if this will work, but try this:
---------- Post added at 02:09 AM ---------- Previous post was at 02:07 AM ----------
Palatis3 said:
Quick question, I bought a used s7 edge off Craigslist and when it's asking me to log in with another guys email. I tried contacting the guy I bought it from but he hasn't texted me back yet. Can I root it and install another rom on it to bypass the lollipop lock? Thanks guys.
Click to expand...
Click to collapse
Wait did you try rooting the s7 or s7 edge... (Or is the s7 edge completely unrelated to the brick)

Play pokemon go and any safetynet protected app with root switch new method (cant be

PLAY POKEMON GO WITH ROOT SWITCH NEW METHOD (CANT BE PATCHED)
i did this on my samsung s7 edge g935f and have not tested on anything else but should apply across the board realy
before we get started
u will need to have your phone at stock with no root and pokemon go working on that stock rom
(been trying on lots of note 7 port roms with no look hopefuly crack that one day)
IF U ARE NOT DOING THIS ON A SAMSUNG INSTALL TWRP ON YOUR DEVICE AND START AT STEP 5 IT WILL WORK
AND I MANAGED TO GET THIS TO WORK WITH EVERY COUSTEM ROM TO IF ANYONE WOULD LIKE ME TO ADD SUPORT FOR THAT PLZ LET ME KNOW
STEP ONE
download all files
no-verity-opt-encrypt-2.1.zip
https://drive.google.com/file/d/0B6bGIsDu5O5pV3JkX2JUV290MEU/view
systemless super su
https://drive.google.com/file/d/0B6bGIsDu5O5pbWNHSFJEQjhLY2s/view
coppy them two to a micro sd card and put in your phone
samsung smart switch for pc
http://www.samsung.com/uk/smart-switch/samsung-desktop-app.html
twrp for g935f ONLY
download the one for your device
https://drive.google.com/file/d/0B6bGIsDu5O5pMnRfRmxUYThWZ1E/view
odin
https://drive.google.com/file/d/0B6bGIsDu5O5pbGlobkVTZWFkYmM/view
for use on pc
STEP TWO
on your phone go to settings/about phone/software info/ and tap the biuld number 5 times to unlock developer options
and and go into developer options turn on usb debuging and and oem unlock
STEP THERE
install smart switch (only used for the phones drivers) and extract odin and run it click on the ap tab and load the twrp and click start
and instal twrp and w8 for reboot and boot stright to twrp (vol-up and power and home)
STEP FOUR
insatl no-verity-opt-encrypt-2.1.zip in twrp from the instal tab and reboot after and instal pokemon go and test it (if working carry on)
STEP FIVE
boot into twrp again and go to the backup tab. untick everythin but boot(40mb) select storage as sd card and swipe to back up then reboot
on your phone go to myfile and go to sd/twrp and find your backup it will begin with a date and rename that folder to stock
STEP SIX
boot back into twrp and install super su system less DONT reboot.
go back and backup boot only again then reboot
go to myfile again and go to sd/twrp and find your backup it will begin with a date again and rename that folder to root
not u can switch between stock and root just b flashing tho boot files and takes seconds
i have been useing this for days now and u can istall as mennt root apps as u like aslong as u flash the stock boot it will allways let u use any app thats blocks root
thank you this is the fist time i have releced my of work due to not being able to read and wright

Got it working on the note 7 port Rom

I'm on a Note 5 and going to give this a try using my version of TWRP. Will edit this post and report findings!
Able to boot after flashing the first .zip. Always got boot loop previous after flashing TWRP but not flashing root! Thanks for the solution!
Basically the minimum I want is the ability to remove my boot sound and update my hosts file. This lets me do that but otherwise be stock. Good enough. Wish I had xposed, root, but still Android Pay and PGO without reboots but that's ok.

henderjr said:
I'm on a Note 5 and going to give this a try using my version of TWRP. Will edit this post and report findings!
Able to boot after flashing the first .zip. Always got boot loop previous after flashing TWRP but not flashing root! Thanks for the solution!
Basically the minimum I want is the ability to remove my boot sound and update my hosts file. This lets me do that but otherwise be stock. Good enough. Wish I had xposed, root, but still Android Pay and PGO without reboots but that's ok.
Click to expand...
Click to collapse
If u need a hand let me know

I can not install "no-verity-opt-encrypt-2.1.zip" it says :
"Error: Unpacking boot image failed!"
I am using Note 4 (N910c)
Update : so i have learned that i dont need no-verity-opt-encrypt-2.1.zip
my phone dos not have encryption so i basically skipped that step and *bang* i am rooted and can play pokemon. Thanks much

Is this working on android nougat?
Thx

psxcis said:
Is this working on android nougat?
Thx
Click to expand...
Click to collapse
Anyone tried this yet? im itching to root my pixel xl but cant live without pokemon go and snapchat

Souler19 said:
Anyone tried this yet? im itching to root my pixel xl but cant live without pokemon go and snapchat
Click to expand...
Click to collapse
works fine if the root u use is systemless
Tut for pixel and pixel xl
http://www.androidpolice.com/2016/10/29/chainfire-releases-systemless-root-method-pixel-pixel-xl/

TLEAF-TOM-LEE said:
works fine if the root u use is systemless
Tut for pixel and pixel xl
http://www.androidpolice.com/2016/10/29/chainfire-releases-systemless-root-method-pixel-pixel-xl/
Click to expand...
Click to collapse
Can anybody confirm that this is true for me? I haven't seen anyone else mention this.

Hello, I would like your help.
First of all, sorry for my poor English.
I installed the Root Switch to use Pokemon Go, but my phone crashed and rebooted while I played. After that, I was not able to activate root again, including the SuperSU app says my cell does not have Root.
Does anyone know how I should proceed? Would redoing root solve my case?
Thank you.

Alison.Souza said:
Hello, I would like your help.
First of all, sorry for my poor English.
I installed the Root Switch to use Pokemon Go, but my phone crashed and rebooted while I played. After that, I was not able to activate root again, including the SuperSU app says my cell does not have Root.
Does anyone know how I should proceed? Would redoing root solve my case?
Thank you.
Click to expand...
Click to collapse
Yeah, just reroot and you will be fine
Sent from my SPH-L720 using Tapatalk

mattzeller said:
Yeah, just reroot and you will be fine
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks mattzeller! It worked!

Just to clarify, this requires an unlocked bootloader correct? I am on the g930v with is locked.

Wetzel402 said:
Just to clarify, this requires an unlocked bootloader correct? I am on the g930v with is locked.
Click to expand...
Click to collapse
Yes that's correct

It looks like the Root Switch has stopped working, at least here on my S4 I9505 with Android 5.0.1.
Anyone else going through this?

Root Switch never work on my G900T S5 with Lollipop 5.1.1

There was a safetynet update last week that breaks RootSwitch. Had to go the Magisk route but now can use Android Pay along with PoGo

Moto One 5G Ace Rooted with TWRP using stock Firmware

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.

[RECOVERY] TWRP for Samsung Galaxy A41 [SM-A415F] [BINARY 1 & 2]

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/releases​Known Issues / Report Issues - https://github.com/Galaxy-MT6768/android_device_samsung_a31nsxx/issues​Telegram 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