I installed android 4.3 ROM on this phone but it seems that it is not rooted anymore!
I cannot for the life of me figure out how to root. I clicked on the link in the AOSP thread, but my phone says it cannot open the CWM / TWRP / MobileODIN installable ZIP. Do I need a special app to open it?
Can I root it the same way I rooted my phone when it was on 4.12 or 4.22?
Jmcatch said:
I installed android 4.3 ROM on this phone but it seems that it is not rooted anymore!
I cannot for the life of me figure out how to root. I clicked on the link in the AOSP thread, but my phone says it cannot open the CWM / TWRP / MobileODIN installable ZIP. Do I need a special app to open it?
Can I root it the same way I rooted my phone when it was on 4.12 or 4.22?
Click to expand...
Click to collapse
For root with AOSP you need to flash SuperSu zip in recovery. For CM 10.2 you have to enable develiper options then select root for apps and ADB.
adfurgerson said:
For root with AOSP you need to flash SuperSu zip in recovery. For CM 10.2 you have to enable develiper options then select root for apps and ADB.
Click to expand...
Click to collapse
Thanks that clears a lot up. But I'm having trouble getting back to recovery. If I hold the volume buttons down I get this screen basically, but without the android guy https://encrypted-tbn3.gstatic.com/...VnEj5TCCm2wPaOV1fHZQa85RAmp-imzhEYbA26zTot177
If I press volume up or down it doesn't change out of fastboot. Am I missing something? I had TWRP installed and used it to flash my other ROMS but I'm having difficulty getting to it because I used to just be able to reboot directly into recovery using one of my root apps.
EDIT: Got it, just took some tinkering on the reboot. Thanks for your help!
Jmcatch said:
Thanks that clears a lot up. But I'm having trouble getting back to recovery. If I hold the volume buttons down I get this screen basically, but without the android guy https://encrypted-tbn3.gstatic.com/...VnEj5TCCm2wPaOV1fHZQa85RAmp-imzhEYbA26zTot177
If I press volume up or down it doesn't change out of fastboot. Am I missing something? I had TWRP installed and used it to flash my other ROMS but I'm having difficulty getting to it because I used to just be able to reboot directly into recovery using one of my root apps.
EDIT: Got it, just took some tinkering on the reboot. Thanks for your help!
Click to expand...
Click to collapse
On stock bootloader the banner across the top that says start in the picture you posted will not be there. For reference vloume up and power to get to fastboot screen then either volume up twice then power, or volume down twice then power will take you to recovery.
Related
Okay so im new to this and i have been working all day on trying to get my vibrant modded a little .. My earlier thread shows that i had some trouble and finally got it back to its factory settings .
Now I have upgraded to 2.2 and i rooted it using super one click rooting because I cannot root with an update.zip because I get a signature verification failure. But I realized i need to do this anyways to run a rom even using rom manager ..
So i tried to install 3e recovery installer which is suppose to override this but for some reason it fails to install. It says checking for root: and it fails.
Someone seemed to have the same problem in a different thread and said they deleted some bloatware with terminal emulator but i used termaninal backup (or something like that) to delete some bloatwares but this still did not fix the problem for me.
What is my problem? And what lag fix can i use for my vibrant when i get all this to work?
Fastest way to obtain root :
1. is to flash stock JFD rom (use AIO tools.
2. flash Clockwork recovery through Rom manager (get it from market)
3. Flash any rooted rom (with Voodoo lagfix) through CWM.
And most important thing, if you don't know what you are doing with your phone don't do anything.
Andreal said:
Fastest way to obtain root :
2. flash Clockwork recovery through Rom manager (get it from market)
Click to expand...
Click to collapse
i thought you needed root to flash recovery from rom manager...
anyways, my method of rooting is to use the recovery 3e to 2e batch (dont wanna call it an install cause it doesnt install really) and then flash a root update.zip from the 2e recovery you just flashed.
what may be happening to your 3e 2e thing is that you might of forgotten to enable usb debugging... you do this by going in the menu>applications>development>usb debugging on
make sure the phone is plugged in to the computer and debug is on and run 3e to 2e...
then get ahold of a root update.zip and rename it update.zip, put it on the root of your internal sd card (\mnt\sdcard\) and go into recovery (power phone off, hold vol up and down buttons and then hold power button at the same time until you see the vibrant boot screen. when you get into recovery, hit reinstall packages.
sorry for the wall of text; hope this helps.
younix258 said:
i thought you needed root to flash recovery from rom manager...
Click to expand...
Click to collapse
I meant install CWM, not flash.
Sorry
Andreal said:
I meant install CWM, not flash.
Sorry
Click to expand...
Click to collapse
I didnt know there was a difference... does that work then???
Sent from a cell tower to the XDA server to you.
Google z4root and then download.the.apk. its a one click root apk.. just choose permanent root n ur good to go on any stock rom
younix258 said:
i thought you needed root to flash recovery from rom manager...
Click to expand...
Click to collapse
You are right, I was rooting my device couple of months ago, I forgot that for CWM you have to obtain root first.
My memory is good but short
If my bootloader is unlocked and cwm installed can i still run the ota update? Im on the stock rom just rooted
We are in the same boat -_-
I'm currently having the same problem
even when I tried to install the update through CWM it doesn't update!
It's not 1.29.. it's just a fix for the dual mics.
Sent from my HTC One using xda app-developers app
Theres a thread in general about it. Correct...not 1.29. One confirmed fix is capacitive button fix. I believe you need to be on stock recovery to install it.
So would anyone recommend installing the new update 4.2.2 for the internatinal version instead of trying to install this update for my T-Mobile HTC One? Or the question is it even possible?
Mine is rooted and unlocked bootloader by using a toolkit.
Also in the 4.2.2 update is the sensitivity for back and home button better?
Dheia AlRadhi said:
I'm currently having the same problem
even when I tried to install the update through CWM it doesn't update!
Click to expand...
Click to collapse
How do you install it thru CWM?
PostaHTC said:
How do you install it thru CWM?
Click to expand...
Click to collapse
it won't work
but just if you want to try, when i got the update notification i downloaded the zip file then from CWM install it by selecting the zip file from download file.
Dheia AlRadhi said:
it won't work
but just if you want to try, when i got the update notification i downloaded the zip file then from CWM install it by selecting the zip file from download file.
Click to expand...
Click to collapse
Hey I just flashed back to stock with Fastboot and the update went thru then I flashed back to CWM no problems! :cyclops:
PostaHTC said:
Hey I just flashed back to stock with Fastboot and the update went thru then I flashed back to CWM no problems! :cyclops:
Click to expand...
Click to collapse
Can you provide step by step instructions on how to flash the stock recovery? Thanks!
disastar said:
Can you provide step by step instructions on how to flash the stock recovery? Thanks!
Click to expand...
Click to collapse
Use this link provided by c4b4l3 to download stock recovery
https://dl.dropboxusercontent.com/u/...k-recovery.img
1. I created a folder C: (Named it Android)
2. Rest your HTC One into Bootloader Mode
3. Highlight fastboot then press power button (you should see fastboot usb)
4. Open up Command Prompt
5. Type cd c:\Android
6. Type fastboot flash recovery htc1-stock-recovery.img
7. Let it go thru and rest your phone you should be prompted to install update if not wait for it to come back when it does go thru the motions of the installation.
(When mine went thru the installation process I had to force rest it a couple of time to make it go thru but it works like a charm now and I flashed back to TWRP)
Make sure you have all HTC Drivers installed
And believe me it works I have a Mac with VMware Fusion w/ Windows XP running and I have never had any problems!
PostaHTC said:
Use this link provided by c4b4l3 to download stock recovery
https://dl.dropboxusercontent.com/u/...k-recovery.img
1. I created a folder C: (Named it Android)
2. Rest your HTC One into Bootloader Mode
3. Highlight fastboot then press power button (you should see fastboot usb)
4. Open up Command Prompt
5. Type cd c:\Android
6. Type fastboot flash recovery htc1-stock-recovery.img
7. Let it go thru and rest your phone you should be prompted to install update if not wait for it to come back when it does go thru the motions of the installation.
(When mine went thru the installation process I had to force rest it a couple of time to make it go thru but it works like a charm now and I flashed back to TWRP)
Make sure you have all HTC Drivers installed
And believe me it works I have a Mac with VMware Fusion w/ Windows XP running and I have never had any problems!
Click to expand...
Click to collapse
Could you recheck your link to the recovery? The link was concatenated. Thanks!
Were do you put the recovery file? In the phones storage?
adezd00 said:
Were do you put the recovery file? In the phones storage?
Click to expand...
Click to collapse
No you put it in that Android folder
I was unlocked, running CWM and rooted. I'm trying what everyone is suggesting but it's just not working. I flashed the stock recovery, rebooted into OS, instructed to flash update, it reboots into stock recovery, starts flashing and hangs about 1/4 of the way through....
I eventually (30+ mins) restart by holding down power. It boots back into recovery, starts to flash the update again but this time has a red triangle at the 1/4 mark.
I reboot a second time and I'm back into the OS w/o the update.
Ideas?
disastar said:
Could you recheck your link to the recovery? The link was concatenated. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2158763&page=4
Its the second post
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
mmayhew said:
I was unlocked, running CWM and rooted. I'm trying what everyone is suggesting but it's just not working. I flashed the stock recovery, rebooted into OS, instructed to flash update, it reboots into stock recovery, starts flashing and hangs about 1/4 of the way through....
I eventually (30+ mins) restart by holding down power. It boots back into recovery, starts to flash the update again but this time has a red triangle at the 1/4 mark.
I reboot a second time and I'm back into the OS w/o the update.
Ideas?
Click to expand...
Click to collapse
Mine did the same thing I just kept resetting it and it finished
Dheia AlRadhi said:
So would anyone recommend installing the new update 4.2.2 for the internatinal version instead of trying to install this update for my T-Mobile HTC One? Or the question is it even possible?
Mine is rooted and unlocked bootloader by using a toolkit.
Also in the 4.2.2 update is the sensitivity for back and home button better?
Click to expand...
Click to collapse
I'm on Tmo and running ARHD 10.1. 4.2.2 and 1.27 firmware. It works fine. Back and home feel fine. I was running 4.1.2 with firmware 1.29 and the only problem with going back to 1.27 is the camera. It's much better on 1.29.
Got the update today. Installing it via clockworks right now .Just download it and click install later. Then reboot into recovery and found the file in the download folder
Ota-m7-ul-jb-50-tmous-1.27.531.8-1.27.531.7-release-318509-signed21cbl550vh5szzcg.zip
Wow alot to type.
Will report back when finish flashing.
xile6 said:
Got the update today. Installing it via clockworks right now .Just download it and click install later. Then reboot into recovery and found the file in the download folder
Ota-m7-ul-jb-50-tmous-1.27.531.8-1.27.531.7-release-318509-signed21cbl550vh5szzcg.zip
Wow alot to type.
Will report back when finish flashing.
Click to expand...
Click to collapse
My guess you haven't checked back because you're still stuck?...
MinimalistChris said:
My guess you haven't checked back because you're still stuck?...
Click to expand...
Click to collapse
Nah I got it working it hung but then reboot a few times and it went through.
It fixes the back and home buttons not sure what else it does since I only had the phone a few days.
Hi,
I'm a new member here, I've been reading this site for a while and I can't seem to figure out how to root my phone. It is my first time rooting a phone, so I'm not 100% sure whether I'm doing it right, but so far I've tried several things and none seems to be working.
It gets stuck in a boot loop and never goes out. Once I got it stuck on the boot and it wasn't looping, but it was stuck.
I tried CF Auto Root and UniKernel v8 and v9. With v9 it was stuck on the booting, no loop. Anything else is boot looping me. I've been trying to root my phone for quite some time but I can't get it done anyhow.
I would appreciate help on this as I really need to root my phone because an application I need to use requires root. Also I'm kinda getting scared when my phone gets stuck. I don't want to hard brick it.
Best regards,
iLikeGalaxyS6
Any information on this topic? Thanks in advance.
iLikeGalaxyS6 said:
Any information on this topic? Thanks in advance.
Click to expand...
Click to collapse
The easiest way to get root is by flashing a custom recovery through odin. After that you can root your device by installing the latest Super Su and a compatible kernel through the custom recovery. Here is link to the thread. Download the zip files to your phone first.
You need to download odin to your pc and install the latest Samsung USB drivers. Reboot your phone into download mode and then in odin select the twrp_5.1.1_edge.tar as AP and uncheck auto-reboot and then press start. When odin is finished press volume down + home + power until the screen goes off. Press volume up + home + power when the screen is off and the phone will boot into the custom recovery and there you can install the zip files found in the thread.
Good luck
Aerox912 said:
The easiest way to get root is by flashing a custom recovery through odin. After that you can root your device by installing the latest Super Su and a compatible kernel through the custom recovery. Here is link to the thread. Download the zip files to your phone first.
You need to download odin to your pc and install the latest Samsung USB drivers. Reboot your phone into download mode and then in odin select the twrp_5.1.1_edge.tar as AP and uncheck auto-reboot and then press start. When odin is finished press volume down + home + power until the screen goes off. Press volume up + home + power when the screen is off and the phone will boot into the custom recovery and there you can install the zip files found in the thread.
Good luck
Click to expand...
Click to collapse
Thanks for the suggestion. I have read the thread and I found one reply which is holding me back from doing it.
http://forum.xda-developers.com/gal...ndroid-5-1-t3144866/post61810304#post61810304
Is this going to work for my model number?
iLikeGalaxyS6 said:
Thanks for the suggestion. I have read the thread and I found one reply which is holding me back from doing it.
http://forum.xda-developers.com/gal...ndroid-5-1-t3144866/post61810304#post61810304
Is this going to work for my model number?
Click to expand...
Click to collapse
No wait it won't, i misread your title. You need twrp for the g920f. Your in the wrong forum here, this is the g925f forum but it's the same procedure. You only need the latest twrp flashable .tar package for your device here instead of the one in the post and use Unikernel found here. And than the supersu zip and that's it
Hello, I am new here and also new to using an android device. I followed instructions to root my phone and now I can access the command "su" in a local terminal. But when I go to download SuperUser it says my device is not rooted. Did I miss something? And if I did mess up and didn't install the right kernel, autoroot or whatever, how do I check my android's model number?
thakyZ said:
Hello, I am new here and also new to using an android device. I followed instructions to root my phone and now I can access the command "su" in a local terminal. But when I go to download SuperUser it says my device is not rooted. Did I miss something? And if I did mess up and didn't install the right kernel, autoroot or whatever, how do I check my android's model number?
Click to expand...
Click to collapse
On the back either on the better cover when you peel it off or under the battery it should say something like G900T or G900V depending on your carrier and type of phone I'll help if I can just need to know which model you are actually you might be able to skip my instructions below and just go to install super su and that night work but if not just follow those instructions and you'll be golden if you got any questions pm me or just click the reply button and ask and I'll do my best to answer it
Download the rom you want and kernels that go with it depending on your phones settings such as oj4 OL1 it'll say under settings and about device those versions are the last 3 characters in the field (that confused me at first just a heads up) etc etc make sure theyre all the same also don't forget to download supersu (I can't remember where to find it just go on my topic and someone posted the link there
Put them onto your SD card
Download TWRP 2.8.whatever the newest one is on your computer
Download Odin and on the AP slot or PDA click it then find the TWRP file and click that then go under options on Odin and uncheck autoreboot
Turn your phone off and put it into download mode (press the volume down button and home button and power button at the same time) then the volume up button once the confirmation screen comes on
Then flash the TWRP and once it's done it'll Stat on that screen so you have to remove the battery then put it back in and boot into recovery mode (volume up home button and power button at same time)
Now go into the install button and navigate to your SD card and find the super su and click the install or flash button I can't remember which it is and slide the slider thing and hit reboot phone
When it asks to install super su before you reboot don't click install just reboot it since you've already installed it it'll work
Then go in and you'll have supersu and be rooted
Now boot back into recovery and install/flash the rom and kernel and ignore the supersu install thing again and you'll be good to go I also highly advise making a backup if you have the space for it
Ok I have done that, but now my phone is stuck on the T-Mobile logo...
thakyZ said:
Ok I have done that, but now my phone is stuck on the T-Mobile logo...
Click to expand...
Click to collapse
hmmm did you do the whole process or just the supersu or what part did it get stuck on?
Veid71 said:
hmmm did you do the whole process or just the supersu or what part did it get stuck on?
Click to expand...
Click to collapse
It was after I chose to reboot my device so superSU could build the cache manifest with twrp
thakyZ said:
It was after I chose to reboot my device so superSU could build the cache manifest with twrp
Click to expand...
Click to collapse
okay after you slid the slider bar and click the reboot button when it asked to install supersu did you click install? or did you just click reboot and ignore it? and did you install this super su?https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip id say just redownload it and make sure it wasnt a messed up download and boot back into recovery mdoe and try it again
Veid71 said:
okay after you slid the slider bar and click the reboot button when it asked to install supersu did you click install? or did you just click reboot and ignore it? and did you install this super su?https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip id say just redownload it and make sure it wasnt a messed up download and boot back into recovery mdoe and try it again
Click to expand...
Click to collapse
Well I couldn't find that link but thanks for giving me it. I downloaded SuperSU from google play instead. But I started SuperSU and it wanted to rebuild the cache or something and it gave me the options to do it normally or with twrp so I chose twrp. It rebooted started twrp and started building it, then it started back up and was stuck on the T-Mobile screen. But I downloaded a new rom from sammobile.com and I couldn't get it to work then I renembered something about you have to use a secific Odin version, so I went from 3.10.7 to 3.09 and nothing changed, so then I cleared cache and nothing. So, I went to Odin3 3.07 and nothing so I went back up to 3.09 and it started to stop being soft bricked. And I just have to set everything back up, which will not take long, about 2 hours. So, I will download the SuperSU from that site and I will see if it works again.
Note to self: keep the stock rom, damn it's a huge file.
thakyZ said:
Well I couldn't find that link but thanks for giving me it. I downloaded SuperSU from google play instead. But I started SuperSU and it wanted to rebuild the cache or something and it gave me the options to do it normally or with twrp so I chose twrp. It rebooted started twrp and started building it, then it started back up and was stuck on the T-Mobile screen. But I downloaded a new rom from sammobile.com and I couldn't get it to work then I renembered something about you have to use a secific Odin version, so I went from 3.10.7 to 3.09 and nothing changed, so then I cleared cache and nothing. So, I went to Odin3 3.07 and nothing so I went back up to 3.09 and it started to stop being soft bricked. And I just have to set everything back up, which will not take long, about 2 hours. So, I will download the SuperSU from that site and I will see if it works again.
Note to self: keep the stock rom, damn it's a huge file.
Click to expand...
Click to collapse
No problem I figured that's what had happened and I used Odin 3.10.6 I think it was and yeah if you do it with the TWRP one it ducks it up for some reason I think it's an old supersu version or some thing and it's not compatible but I'll also post a link to download the stock rooted rom for you to flash
http://forum.xda-developers.com/tmo...t/how-to-update-to-g900tof6-5-1-1-pc-t3141404
Veid71 said:
No problem I figured that's what had happened and I used Odin 3.10.6 I think it was and yeah if you do it with the TWRP one it ducks it up for some reason I think it's an old supersu version or some thing and it's not compatible but I'll also post a link to download the stock rooted rom for you to flash
http://forum.xda-developers.com/tmo...t/how-to-update-to-g900tof6-5-1-1-pc-t3141404
Click to expand...
Click to collapse
Which one do I want to download?
thakyZ said:
Which one do I want to download?
Click to expand...
Click to collapse
Either or it really doesn't matter me personally I like deodex just because there's more customizability with it but both do the job also if you do the deodex one it'll take about 10-15minutes to come on after you flash/install it in twrp where as regular should just come on like a normal boot maybe 5 minutes
After about a month of making sure it works I have successfully rooted my phone! Thank you very much!
back up all your data before starting​
Code:
#include <std_disclaimer.h>
/*
*
* I'm not responsible for bricked devices, dead SD cards,
* before flashing it! YOU are choosing to make these modifications.
Features:
- magisk works.
- encryption/decryption doesn't work.
Install guide:
1. you are in stock rom ..
2. go to settings and remove your google accounts ...
3. reboot to stock recovery ..
4. wipe data/cache
5. reboot to boot-loader ( download mode )
6. open Odin... choose AP and select the downloaded file TWRP_3.tar
7. connect your phone to usb and click start... immediately click volume up + power button tail you are in twrp
8. if you cant open internal storage on computer... format data on twrp.
Download:
https://mega.nz/#!SWYwAQAb!bbLnex8yhT7tyBTdTMr2wIS-tzITjg5VMJ_p1msXenQ
install this decrypter .
thanks to geiti94 and Mauronofrio and Zackptg5
......
reserved
this one too
can i update to latest of magisk ?
thanks for hard work
On booting to recovery using the key combination, my phone got stuck at the TeamWin splash screen and won't go beyond it. Now it just boots to that screen when using the normal key combination as well instead of Android. Anything I did wrong or is there any other issue?
I was using Magisk with stock recovery prior to flashing this. Going to flash the stock ROM again using Odin and try this once again.
Edit: Since all reboot options now lead to the TWRP splash screen, there doesn't seem to be a way to get in to download mode. Most likely seems that I have to let the battery drain out. A word of caution for anyone else trying this out.
t3chg33k said:
On booting to recovery using the key combination, my phone got stuck at the TeamWin splash screen and won't go beyond it. Now it just boots to that screen when using the normal key combination as well instead of Android. Anything I did wrong or is there any other issue?
I was using Magisk with stock recovery prior to flashing this. Going to flash the stock ROM again using Odin and try this once again.
Edit: Since all reboot options now lead to the TWRP splash screen, there doesn't seem to be a way to get in to download mode. Most likely seems that I have to let the battery drain out. A word of caution for anyone else trying this out.
Click to expand...
Click to collapse
have you formatted data? and rebooted directly to bootloader?
when stuck on spash screen means data is encrypted.
zvox said:
have you formatted data? and rebooted directly to bootloader?
when stuck on spash screen means data is encrypted.
Click to expand...
Click to collapse
I had removed all accounts and formatted data/cache partitions before flashing the TWRP file. However, the first time I missed booting immediately in to recovery and the OS started booting instead. So, I rebooted in to recovery and it is stuck on the TWRP splash screen since then. So, did the half boot in to the OS result in encryption of the data partition once again?
Tried just about everything but still stuck on the splash screen. I don't know when the battery will run out now but do hope that I will be able to get in to download mode once it does so or otherwise I think I got myself a brick.
t3chg33k said:
I had removed all accounts and formatted data/cache partitions before flashing the TWRP file. However, the first time I missed booting immediately in to recovery and the OS started booting instead. So, I rebooted in to recovery and it is stuck on the TWRP splash screen since then. So, did the half boot in to the OS result in encryption of the data partition once again?
Tried just about everything but still stuck on the splash screen. I don't know when the battery will run out now but do hope that I will be able to get in to download mode once it does so or otherwise I think I got myself a brick.
Click to expand...
Click to collapse
no needfor battery to drain, just Press volume up + down + power with USB plugged in and when the phone turn off release power and keep pressing up/down buttons. and you'll be directed to download mode
zvox said:
no needfor battery to drain, just Press volume up + down + power with USB plugged in and when the phone turn off release power and keep pressing up/down buttons. and you'll be directed to download mode
Click to expand...
Click to collapse
Thanks, that's the combination I was looking out for. I did that combination without the USB connected and used some other combination when the USB was connected. After a fresh ODIN flash, I was able to boot in to TWRP without any issues, so great job with the recovery.
Update 1: After powering off the device, it is now only booting to stock recovery, no sign of TWRP. Selecting the 'Reboot to system' option in stock recovery results in a "cannot load android system" and "data may be corrupt" message. Selecting "factory reset" option in stock recovery booted me to Android.
Update 2: Booted to system after the factory reset and powered off. Now the phone won't go past the Samsung logo with the message "only official binaries are allowed to be flashed"
t3chg33k said:
Thanks, that's the combination I was looking out for. I did that combination without the USB connected and used some other combination when the USB was connected. After a fresh ODIN flash, I was able to boot in to TWRP without any issues, so great job with the recovery.
Update: After powering off the device, it is now only booting to stock recovery, no sign of TWRP. Selecting the 'Reboot to system' option in stock recovery results in a "cannot load android system" and "data may be corrupt" message. Selecting "factory reset" option in stock recovery booted me to Android.
Click to expand...
Click to collapse
wipe data again and reboot to bootloader and flash twrp again, once youre in twrp.. mount system... open file manager and go to system/system and rename recovery-from-boot.p to recovery-from-boot.p.bak.
i forget to mention that.
dont forget to flash the decrypter before booting.
zvox said:
no needfor battery to drain, just Press volume up + down + power with USB plugged in and when the phone turn off release power and keep pressing up/down buttons. and you'll be directed to download mode
Click to expand...
Click to collapse
zvox said:
wipe data again and reboot to bootloader and flash twrp again, once youre in twrp.. mount system... open file manager and go to system/system and rename recovery-from-boot.p to recovery-from-boot.p.bak.
i forget to mention that.
dont forget to flash the decrypter before booting.
Click to expand...
Click to collapse
I had to first boot in to the OS and check for updates to register the device with the OEM unlock option enabled once again before the "official binaries only" message disappeared. Thereafter things worked out fine as per your instructions and I have permanent TWRP. Will try out Magisk-patched TWRP later and post the results.
Would you mind attaching the kernel source?
Anyone else tried this TWRP? is this really a permanent TWRP?
zidane02 said:
Anyone else tried this TWRP? is this really a permanent TWRP?
Click to expand...
Click to collapse
TWRP is permanent but it always boots to TWRP irrespective of key combination and from there one has to reboot to System.
Also, I patched the recovery image with Magisk and it doesn't seem to work. When rebooting to recovery from TWRP the first time, it leads to a blank screen and on rebooting it gets stuck at the Samsung boot logo.
t3chg33k said:
TWRP is permanent but it always boots to TWRP irrespective of key combination and from there one has to reboot to System.
Also, I patched the recovery image with Magisk and it doesn't seem to work. When rebooting to recovery ffrom TWRP the first time, it leads to a blank screen and on rebooting it gets stuck at the Samsung boot logo.
Click to expand...
Click to collapse
I see. But what is TWRP without magisk? Nandroid is ok, but my main purpose of TWRP is magisk.
So my 2nd question is, will this work on any firmware?
zidane02 said:
I see. But what is TWRP without magisk? Nandroid is ok, but my main purpose of TWRP is magisk.
So my 2nd question is, will this work on any firmware?
Click to expand...
Click to collapse
Not much use for non-Magisk TWRP I am afraid. So I am going back to Magisk with stock recovery for now since I chiely use Titanium backup.
I am on the ASE2 firmware and since this TWRP boots it up fine, I am assuming it is the same kernel version as used in the stock version since its source code was released recently. Hence, it might not work with other firmware but I am in no position to check that out.
t3chg33k said:
Not much use for non-Magisk TWRP I am afraid. So I am going back to Magisk with stock recovery for now since I chiely use Titanium backup.
I am on the ASE2 firmware and since this TWRP boots it up fine, I am assuming it is the same kernel version as used in the stock version since its source code was released recently. Hence, it might not work with other firmware but I am in no position to check that out.
Click to expand...
Click to collapse
I see. Then I'll be preserving my knox for the mean time until a stable and Magisk-able TWRP is available.
There is magisk with stock recovery? Can you tell me where can I find this thread? Also will this method trip your knox? Thanks.
zidane02 said:
I see. Then I'll be preserving my knox for the mean time until a stable and Magisk-able TWRP is available.
There is magisk with stock recovery? Can you tell me where can I find this thread? Also will this method trip your knox? Thanks.
Click to expand...
Click to collapse
You can always install Magisk with stock recovery for any firmware using topjohnwu's guide over here. However, Magisk installation will always trip Knox.
Also, TWRP might be helpful in flashing various patches, especially for GSI releases that you cannot do with the stock recovery.
t3chg33k said:
You can always install Magisk with stock recovery for any firmware using topjohnwu's guide over here. However, Magisk installation will always trip Knox.
Also, TWRP might be helpful in flashing various patches, especially for GSI releases that you cannot do with the stock recovery.
Click to expand...
Click to collapse
Thank you so much for the link. I'm good without TWRP for now, not a fan of GSI since many things are broken, magisk is what I really needed. Thanks again.
Eamo5 said:
Would you mind attaching the kernel source?
Click to expand...
Click to collapse
Good to see you here lol