I was wondering if there is a way to install a customer Recovery such as TWRP withtou ODIN? I dont have a computer (only Ipad) and I really dont have time to go use my friends.
I tried to use Goomanager to install TWRP and got a bunch of errors.
I really dont want to brick my device so is ODIN the only way?
Yes, if goomanager isn't working for you, you'll have to use odin. There is a mobile odin app also but it's kinda hit or miss.
bnd10706 said:
I was wondering if there is a way to install a customer Recovery such as TWRP withtou ODIN? I dont have a computer (only Ipad) and I really dont have time to go use my friends.
I tried to use Goomanager to install TWRP and got a bunch of errors.
I really dont want to brick my device so is ODIN the only way?
Click to expand...
Click to collapse
if you are rooted, download the recovery.img from twrp or cwr or whatever, put it on your internal storage. Download Android terminal emulator and type:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(hit enter after su, grant it su permissions, type the dd command and hit enter, and you win.)
Btw dont goof the dd command up.
You can always try Flashify.
Here is the description from Play Store:
Flash your boot.img, recovery.img and zip files right away using Flashify!
Be safe and backup everything either to local storage or cloud storage with automatic syncing!
If you don't know where to get your recovery files, just download directly from this app!
Features:
1 - Flash boot and recovery .img without even needing to go to recovery.
2 - Flash zip files. Option to wipe cache, dalvik and data when using TWRP or Philz recovery.
3 - Download and flash CWM, Philz, TWRP, Gapps, Franco Kernel, Stock Nexus Kernel (premium), and Stock Nexus Recovery (premium).
4 - Automatic Loki Patch when needed.
5 - Full nandroid backups/restores when using TWRP or Philz recovery.
6 - Backup/Restore kernel and recovery using Sdcard or cloud (Dropbox, Box (premium) or Google Drive (premium)).
7 - Automatic cloud synchronisation of backups between devices and desktops.
8 - Keep track of recently flashed items.
9 - Flash multiple files and build your flash queue.
11 - Flash from anywhere! Do you want to flash from your favorite File Explorer or Email app? No biggie, that also works together with Flashify.
This app is free but has a limit of 3 flashes per day. You can unlock the limit with a quick in-app payment.
ShinySide said:
if you are rooted, download the recovery.img from twrp or cwr or whatever, put it on your internal storage. Download Android terminal emulator and type:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(hit enter after su, grant it su permissions, type the dd command and hit enter, and you win.)
Btw dont goof the dd command up.
Click to expand...
Click to collapse
Thread moved to proper forum
Another vote for Flashify. Used it for TWRP without any issues for my S5 and the girlfriend's also without any issues.
Related
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
rogsoccerman said:
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
Click to expand...
Click to collapse
Use odin.... thats what i done worked perfect!
Sent from my SAMSUNG-SGH-I717 using xda premium
How do I Odin a recovery image? I thought you need a tar file.
rogsoccerman said:
How do I Odin a recovery image? I thought you need a tar file.
Click to expand...
Click to collapse
Scroll on down this thread and u will find the tar file for odin and it will fix ur problems
Sent from my SAMSUNG-SGH-I717 using xda premium
rogsoccerman said:
How do I Odin a recovery image? I thought you need a tar file.
Click to expand...
Click to collapse
Its a little bit farther down someone already made the same thread ur file is there hope it helps let me know
Sent from my SAMSUNG-SGH-I717 using xda premium
Link please I can't find what you are talking about, all I can find is the old version by braway.
Thank you
rogsoccerman said:
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
Click to expand...
Click to collapse
I get the same problem as root in terminal:
flash_image recovery /mnt/sdcard/recovery.img
error scanning partitions: no such file or directory
- ROM Manager won't work; the "flash touch recovery" says "not supported" on this phone. The recovery download also doesn't work; the Galaxy Note is not listed, despite it being on the clockworkmod website!
- ODIN won't work as it needs a tar file or md5, or similar.
- There is no tar file in this thread or anywhere else I can find. If anyone knows exactly where this can be found, that would be helpful!
Basically, if I could find an easy way to "tar" up the recovery.img, it might work with ODIN. This might work, as past tars had only the one file within, but I need a UNIX OS to use the tar command. Drat!
UPDATE: I tarred it in the terminal and will now try ODIN. I hope it works....
UPDATE #2 - yep, it works!
How to install
Odin (this will increase the flash counter)
- put your phone into download mode
- in odin choose pda, and select the .tar.md5 file and flash
http://forum.xda-developers.com/showthread.php?t=1584576
[Recovery] ClockworkMod Based Touch Recovery - 04/14/12
works without any issue.....
Here's how I installed/upgraded CWM to 5.8.4.3 this is an A in Q&A
I was on the April version of CWM and was fat and happy, then I thought I'd try ICS, and didn't much care for what I was finding, then I read about another one I thought I'd try, but it (apparently) required a newer version of CWM, 5.8.4.3 i think.
So ROM Manager from the play store wouldn't do the upgrade for me, kept giving errors.
I'd used odin to install the april .tar, but this new version comes in an .img file.
I downloaded the .img file and placed it on my phone in sdcard (/mnt/sdcard)
searched high and low for a few hours, found a semi-cogent post about how to install it using adb from your PC, i guess.
adb is in the SDK which you can get from here:
http://developer.android.com/sdk/index.html
I installed this and I located adb here: C:\androidsdk\android-sdk-windows\platform-tools
on my PC from the command line (start, run, cmd, ENTER) I changed directories to that directory.
I executed, still on the command line: adb shell
:
This presented me the the octothorpe (hashtag if you must) prompt:#
at the # prompt I entered WITHOUT the double quote, ditto marks (")
"dd if=/sdcard/recovery-clockwork-touch-5.8.4.3-quincyatt.img of=/dev/block/mmcblk0p22"
so it looked like this:
#dd if=/sdcard/recovery-clockwork-touch-5.8.4.3-quincyatt.img of=/dev/block/mmcblk0p22
I pressed enter and it ran pretty quickly and returned to the (apparent) adb prompt # then I typed exit and it dumped me to the C: prompt and I exited that too (so there!), Then I rebooted the phone into recovery mode using one of many nifty reboot apps in the play store, so I don't have to have my fingers holding this slick and slippery buttons.
I verified I was in the new version of CWM, and rebooted to make sure my phone was still breathing... it was so I bailed back into recovery and am now running a backup... then I'll try to install the new ICS ROM, although it looks way too small to me.
I've gathered that the # prompt is the root prompt in adb, so either I'm very lucky and it does this by default, or adb detected my rooted phone... if you've read this far your guess is as good as mine.
I hope this helped someone from having to google for hours and hours into the night, and then not oversleep, not be late to work, not get fired, not go on unemployment, etc.
or not.
if you are running an unsecured kernel, adb should start with root rights of I'm not mistaken...also when you were done moving the recovery file instead of exiting the adb session and the c prompt altogether
You could have simply used the command:
Adb reboot recovery
And in fact..That's all those apps do.
Also of you copy the files in your android sdk platform-tools folder:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
Into your main Windows folder, you no longer have to cd to the platform-tools folder, you can use adb as a global command.
bigjoe2675 said:
How to install
Odin (this will increase the flash counter)
- put your phone into download mode
- in odin choose pda, and select the .tar.md5 file and flash
http://forum.xda-developers.com/showthread.php?t=1584576
[Recovery] ClockworkMod Based Touch Recovery - 04/14/12
works without any issue.....
Click to expand...
Click to collapse
That's an older version of cwm touch which is not compatible with some newer rooms.
VoluntaryMan said:
That's an older version of cwm touch which is not compatible with some newer rooms.
Click to expand...
Click to collapse
Really...cus i have been using it since i got the note and have flashed just about every ROM, lol works great for me sir, maybe my phone likes me idk, and yes just about every ROM....k
But hey i could be wrong..., so which ever works...use it, thanks
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I had the same problems... Ended up flashing twrp 2.2.1. But this link will work for you.
http://forum.xda-developers.com/showthread.php?p=28932726
Sent from my SAMSUNG-SGH-I717 using xda premium
CWM Touch [Solved, again]
I got it working very easily...
Heres how.
Got my .img file from http://www.clockworkmod.com/rommanager. Scroll to find Samsung Galaxy Note(ATT)
Changed the name of the file from "recovery.whatever.whatever.quincyatt.img" to "recovery.img"(minus quotes) using es file explorer(root needed)
Moved the file to root of /sdcard = /sdcard/recovery.img
Opened terminal emulator
typed
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
quit
then backed out to home screen and rebooted into my newest CWM Touch recovery.
Hope this helps anyone who needs it
EDIT: Just performed backup and succeeded. saved backup to /sdcard/clockworkmod/backup/
Moving prior braway recovery backups there to see if they are manageable within ROMmanager
This worked for me, thanks!
tyler79durdan said:
I got it working very easily...
Click to expand...
Click to collapse
I know this is old but better late than never...
ClockworkMod Touch Recovery 5.8.4.3 for SGH-I717 .tar file
http://forum.xda-developers.com/showthread.php?p=39037837
your welcome, enjoy
tyler79durdan said:
typed
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
quit
Click to expand...
Click to collapse
I did this, but instead of quit, I wrote "reboot recovery". I'm not sure if that did it, or if it was something else I did wrong, but the phone won't come back up. I checksummed the img I downloaded with another copy of "recovery-clockwork-touch-6.0.4.3-quincyatt.img" that I downloaded, and they matched:
e70ee18c0d63ee18d325c94e2af7a683
Shrug.
Edit: I just flashed it through odin and it worked. To build the tar.md5 I did the following in cygwin:
Code:
mv recovery-clockwork-touch-6.0.4.3-quincyatt.img recovery.img
tar -H gnu -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
eastwood1 said:
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
Click to expand...
Click to collapse
Someone with more knowledge will need to chime in, but I I'd bet the build we are using isn't official, and probably can't be installed through Rom Manager. Give it some time, eventually things will work as normal
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Click to expand...
Click to collapse
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
eastwood1 said:
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
Click to expand...
Click to collapse
To all,
I couldn't be bothered with learning ADB, but wanted a custom recovery on my SIII ... maybe you can relate?
Here's the easiest way to do it -- and you don't even need a computer!!! You do, however, already need to be rooted before you can use this method ...
Download your recovery of choice (.. as of this writing, I think there are two: CWM and TWRP ..) and make sure you place a copy in the root drive of your sdcard. Rename it recovery.img, if you want to follow the terminal directions listed below ...
Then, download a terminal emulator onto your device (I use Better Terminal Emulator Pro, which is a paid app) and fire it up.
Once in the terminal emulator, type the following commands one line at a time, waiting after each line for the appropriate prompt:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Your device should then boot into the custom recovery, which serves as immediate confirmation that you did things correctly.
I just used this method to install birdman's twrp8.img to my SIII and it worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1764398
I dont think that will work. Notice the command says sdcard.
The internal memory on the sgsiii is labeled sdcard for whatever reason. The external sdcard slot is under mnt/extsdcard in root explorer if that helps.
Sent from my SGH-T999 using xda premium
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
You need to be rooted and have a "su" command. Typical "rooted" roms include supersu , or equivalent, and busybox (which provides the basic Linux commands). I would install super super and busybox from Google play and try again.
You need the SU command to switch to root user in the shell to have the rights to use dd to overwrite the recovery partition.
I can confirm that the dd command works as that is how I loaded cwm on my s3.
Sent from my SGH-I747M using xda app-developers app
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
See if this helps.
http://forum.xda-developers.com/showthread.php?t=1739426
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Pompsy said:
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Click to expand...
Click to collapse
There's no official CWM Recovery for any US versions of the GS3, Sprint included. The only official GS3 recovery available is for the international version. The one we're all using right now (I believe) was built by Team Epic. They're historically Sprint devs and so they built it for the Sprint version; however, as you know it works on more than just the Sprint version. Eventually, I'm sure there will be official recoveries direct from Koush.
Personally, I prefer TWRP (bettery touch control layout and options such as compression to save space), but that too is a work in progress.
So what I am trying to do is get my feet wet with doing some dev work and basically I'm trying to figure out how to (without flashing anything, i want to remove the stuff myself):
De-bloat the stock sense rom and/or just remove all of the HTC garbage and use a different launcher all together without if affecting the system (Im not too sure what is acceptable to remove and what needs to stay in the /system/app/ dir)
Remove the annoying WiFi in the status bar
any and all help is much appreciated and even just pointing me in the right direction
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
.torrented said:
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
Click to expand...
Click to collapse
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
yearn2burn said:
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
Click to expand...
Click to collapse
While all of this is very very helpful, I failed to mention that this isn't my first rodeo, While I have firm understanding of ADB and rooting and flashing, my approach was more of the "behind the scenes" kind of stuff like what goes on inside of the ROM (tweaking files and what not) I'm at the stage where im trying to learn how to cook a rom(i guess some would say). I've already done so with CM10.1 for my Nexus 7(compiled from sauce), im farily comfortable with linux and my way around the OS. I've got the kitchen setup as well as apktool and what Im trying to learn is how to use these tools to their full extent.
like to make the boot.img unsecure, create a "flashable signed zip", remove non essential apps, the starter stuff
A little bit of background about me: I love computers, im going to school for a Computer Science degree, this kind of work has always interested me and I cant seem to get enough of it, ever since ive discovered this site i cant keep away and i love this communty, I've always wanted to just do more than flash someone else's work, i want to give back and start being able to do things.
Like i said before thanks to everyone for any information its all much appreciated!
A the title says, i'd like to know if there's a way/flashable zip for a 6.0.4.3+ recovery. I've been trying to upgrade mine for a few days now, and havent been able to do so.
nicoleitor said:
A the title says, i'd like to know if there's a way/flashable zip for a 6.0.4.3+ recovery. I've been trying to upgrade mine for a few days now, and havent been able to do so.
Click to expand...
Click to collapse
Have you tried replacing recovery.img inside a flashable internal recovery zip file (e.g., flashable_CWM_6.0.2.9.zip from Succulent's repo http://goo.im/devs/succulent/acclaim/recovery) with 6.0.4.3+ (renamed to recovery.img before inserted into the zip file), then flashing the resulting zip file with SD-based recovery?
Yes, i tried that, and after i did, CWM would not load. I had to then use the Nook Tablet Recovery Flasher app that has been around this for a while, to revert the changes back to 5.0.x.x (since thats the default version installed by that app). Any other suggestions? Thanks for the answer tho.
Others have reported same problem with loading CWM v6.0.4.3, but found that TWRP v2.6.3.1 works (http://forum.xda-developers.com/showpost.php?p=47688848&postcount=19). You can obtain a copy of TWRP v2.6.3.1 .img binary for the NT from http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.6.3.1-acclaim.img and should be able to flash it the same way I had described above.
There is a way to flash the recovery img file from within a terminal on the nook itself. I did that 2 days ago with the most recent TWRP (well, most recent I could find).
Save it to your /sdcard (name it cwm.img for this example)
Open a terminal emulator (download one if you don't have one) and type su <enter> then enter the following (make sure you enter it exactly, especially the last part or you'll end up flashing to the wrong partition and hosing your nook):
Code:
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p3
Hit enter, let it do its thing (should be fast), then reboot.
Note: I take no responsibility if this hoses your nook. If you're uncomfortable doing it, take the advice given above and replace the img file inside a working recovery zip.
liquidzoo said:
There is a way to flash the recovery img file from within a terminal on the nook itself. I did that 2 days ago with the most recent TWRP (well, most recent I could find).
Save it to your /sdcard (name it cwm.img for this example)
Open a terminal emulator (download one if you don't have one) and type su <enter> then enter the following (make sure you enter it exactly, especially the last part or you'll end up flashing to the wrong partition and hosing your nook):
Code:
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p3
Hit enter, let it do its thing (should be fast), then reboot.
Note: I take no responsibility if this hoses your nook. If you're uncomfortable doing it, take the advice given above and replace the img file inside a working recovery zip.
Click to expand...
Click to collapse
Worked like a charm.
Sent from my SM-N900T using XDA Premium 4 mobile app
Below you'll find an unofficial semi-bootleg version of TWRP for the Mate 20 X. I say bootleg because I took @Pretoriano80's P10 lite build and modified it for our devices.
Credits: teamwin, @Pretoriano80, @ante0
Testers: @cflynt
Download: Download TWRP for Mate 20 X
Installation guide:
Welcome to the TWRP installation guide for the Mate 20 X. Keep in mind that installing this REQUIRES you to format your data and remove encryption in order for TWRP to read your /data partition and be able to create backups, so backing up your internal storage is recommended if you want to keep anything from it. This will factory reset your device as well.
Flashing TWRP to the eRecovery ramdisk partition is recommended as it allows you to have both Magisk root and TWRP simultaneously. Otherwise, you can flash between Magisk and TWRP when you need it by flashing this image to recovery_ramdisk. This guide will focus on eRecovery installation.
Magisk root and ADB/a terminal app is REQUIRED for the installation of TWRP as fastboot does not allow flashing of erecovery_ramdisk partition.
Backing up your original eRecovery:
The easiest way to accomplish this is to download "partitions backup & restore" from the google play store, and using that app to back up "erecovery_ramdisk." However, you can also accomplish this with adb by running the command "dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/sdcard/erecovery_ramdisk_stock.img" with your device hooked up to a computer. If you are backing up your internal storage, do it after creating this backup. Otherwise, copy this backup to a safe location on your computer.
Booting to TWRP: Booting into TWRP requires a different button combination.
-Booting to TWRP is as simple as getting to the standard boot splash "corruption" screen. When you see this, it will be followed by instructions to hold volume UP for three seconds. Doing this will boot you into TWRP or eRecovery, depending on which one you have installed. With the phone connected to a power source, USB or AC, reboot/boot the phone holding volume UP. Once the standard corruption screen is displayed, release and hold the volume UP key again.
Booting to Magisk root:
-Booting to Magisk root requires the same volume UP key combination, but the phone must NOT be connected to a power source (USB or AC), OR you must use the "adb reboot recovery" command. Reboot/boot the device holding volume UP. This will display the standart boot splash "corruption" screen but will NOT show the standard instructions for booting into eRecovery. It will simply show a "your device is booting" message under the "corruption" message.
Booting to Magisk root from TWRP: the Reboot>Recovery option in TWRP does NOT reboot the device back into TWRP. This is used to boot Magisk root.
-From TWRP, tap the Reboot button followed by Recovery. Normally, the device would boot back into TWRP, but since TWRP is installed to the eRecovery partition and Magisk is installed to the normal recovery partition, it reboots to Magisk root instead.
Booting back into TWRP from TWRP: Using the Reboot>System option in TWRP will get you back to the standard corruption boot splash screen where you can use the "Booting into TWRP" instructions above to get back into TWRP.
-From TWRP, tap the Reboot button followed by System. This will reboot the device normally, giving you the standard corruption screen followed by a normal boot WITHOUT Magisk root. Use this option only if you plan on rebooting back into TWRP with the "Booting into TWRP" instructions above. Otherwise, use the Reboot>Recovery option to get you back into a rooted system.
Modifying system from TWRP: This device uses "System as root" file structure, so it's a bit different to modify system from TWRP.
-Go to the mount option in twrp and mount "System_root" From here, you'll need to browse /system_root NOT /system in order to make changes to system.
*******************INSTALLING TWRP TO ERECOVERY*******************
Flashing TWRP to eRecovery ramdisk:
-Hook your phone up to a PC.
Step 1.
Start by copying the TWRP image to your internal storage OR nm card. Rename it to "twrp.img" to make typing the next command easier.
Step 2.
Using ADB or a terminal app, gain SU access and run the following command: "dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk"
Step 3.
Reboot your phone into TWRP by following the "Booting to TWRP" instructions above.
Step 4.
Once you are in TWRP, you will need to format data, as TWRP cannot read encrypted storage on this device yet. Do this in the "wipe" "Format Data" section of TWRP.
Step 5.
Once data is formatted, copy the fstab.kirin980 file from this package to your internal storage or nm card.
Step 6.
Go to "mount" in twrp, and mount Vendor.
Step 7.
Use TWRP file manager in the "advanced" section of TWRP to copy fstab.kirin980 from your internal storage or nm card to /vendor/etc. This will overwrite the original fstab.kirin980 file and replace it with our modified one removing forced encryption so that the system won't try and re-encrypt your device on boot.
Step 8.
Reboot>Recovery to get back into a rooted system, which is now factory resetted.
DO NOT USE ANY OF THE TWRP SUGGESTIONS TO INSTALL ROOT TO YOUR SYSTEM. Disable the notice to install root by going into TWRP settings and unchecking the relevant box.
Great work! @freeza
Can you expand on step 2...
"Using ADB or a terminal app, gain SU access..."
How does one "gain" SU access? Opening a terminal app on the phone and entering SU in command prompt comes back with permission denied even though I am booted under the previous root method.
n1tro said:
Can you expand on step 2...
"Using ADB or a terminal app, gain SU access..."
How does one "gain" SU access? Opening a terminal app on the phone and entering SU in command prompt comes back with permission denied even though I am booted under the previous root method.
Click to expand...
Click to collapse
Are you sure you're booted with magisk root? If so, open the magisk manager and go to > superuser and make sure shell is allowed for root. If you're using a terminal app, then make sure that's allowed.
Sent from my EVR-AL00 using Tapatalk
freeza said:
Are you sure you're booted with magisk root? If so, open the magisk manager and go to > superuser and make sure shell is allowed for root. If you're using a terminal app, then make sure that's allowed.
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Took a few tries typing in SU before it triggered the Magisk Grant Permission prompt to come up. I granted permission. But entering in the command gives me a permission denied.
Attached screenshot
Magisk permission
n1tro said:
Attached screenshot
Click to expand...
Click to collapse
You want to use app launcher in phone manager or battery settings to turn off emui optimization of magisk manager so it'll be allowed to run in the background to prompt for su. Also try entering just su in the terminal first to get the # prompt instead of $, then enter the dd command
Sent from my EVR-AL00 using Tapatalk
freeza said:
You want to use app launcher in phone manager or battery settings to turn off emui optimization of magisk manager so it'll be allowed to run in the background to prompt for su. Also try entering just su in the terminal first to get the # prompt instead of $, then enter the dd command
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Seems not all terminal apps are created equal. Even with permissions enabled, issuing the SU command did bring it to a # prompt but kept it at $.
Downloaded and installed Material Terminal from the playstore and it works.
n1tro said:
Seems not all terminal apps are created equal. Even with permissions enabled, issuing the SU command did bring it to a # prompt but kept it at $.
Downloaded and installed Material Terminal from the playstore and it works.
Click to expand...
Click to collapse
Glad you got it sorted [emoji16]
Sent from my EVR-AL00 using Tapatalk
freeza said:
Glad you got it sorted [emoji16]
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
1 problem cleared, another one starts.
I followed the instructions wiping the data and copying the 1 file over under the vendor directory. Phone boots up in setup menu. I go through everything (skipping setting up wifi) and when I finish selecting to use gestures or nav buttons, the phone goes back to the beginning of the setup screen.
Guess, I will try to wipe everything and load the custom rom you guys made
n1tro said:
1 problem cleared, another one starts.
I followed the instructions wiping the data and copying the 1 file over under the vendor directory. Phone boots up in setup menu. I go through everything (skipping setting up wifi) and when I finish selecting to use gestures or nav buttons, the phone goes back to the beginning of the setup screen.
Guess, I will try to wipe everything and load the custom rom you guys made
Click to expand...
Click to collapse
When you wiped data, did you do it from the WIPE screen in TWRP and select Format Data? Should prompt you to type in YES when you do so. Otherwise if you are doing an ADVANCED WIPE it is only formatting data without the Media part. YOU MUST get this part right and then copy over that new fstab.kirin980 file using the TWRP File Manager. If you didn't get this right then your Data Partition will still be encrypted.
Hope that helps.
Chad
cflynt said:
When you wiped data, did you do it from the WIPE screen in TWRP and select Format Data? Should prompt you to type in YES when you do so. Otherwise if you are doing an ADVANCED WIPE it is only formatting data without the Media part. YOU MUST get this part right and then copy over that new fstab.kirin980 file using the TWRP File Manager. If you didn't get this right then your Data Partition will still be encrypted.
Hope that helps.
Chad
Click to expand...
Click to collapse
I wiped the data from the main screen and got a prompt to type YES to continue. I think the setup screen loop issue is coming from all the Huawei stuff I got rid of using the adb procedure in the other thread. Maybe I got rid of some 1st time setup file. In any rate, I got the custom ROM you guys made and installed it and everything works again.
O
n1tro said:
Attached screenshot
Click to expand...
Click to collapse
What is your dpi?? lmao
antiochasylum said:
O
What is your dpi?? lmao
Click to expand...
Click to collapse
340.
I normally have it at 320 but noticed I was making more mistakes on the shrunken keyboard.
n1tro said:
340.
I normally have it at 320 but noticed I was making more mistakes on the shrunken keyboard.
Click to expand...
Click to collapse
How did your set it? The typical lcd_density didn't trigger anything for me.
antiochasylum said:
How did your set it? The typical lcd_density didn't trigger anything for me.
Click to expand...
Click to collapse
It's in a messed up location. Go and edit the local.prop file located in /product/etc/prop pathway. That's the only thing that needs to be set. All the other files and locations are red herrings.
Guys, maybe this is a dumb question... but can i Flash SuperSU directly from the TWRP ?
filip_pine said:
Guys, maybe this is a dumb question... but can i Flash SuperSU directly from the TWRP ?
Click to expand...
Click to collapse
SuperSU is more suited for older phones and no longer being worked on so no more updates/support? https://www.androidpolice.com/2018/0...p-development/ it's also been removed from Play Store.
Magisk is used for root now https://www.xda-developers.com/magisk-vs-supersu/ and there is a thread how to install here
How can I update software?
Now 185, but 195 comming.