Related
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?
sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo
Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help
erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X
encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?
Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what
Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
Cwm 5.0.2.7 all day.
Sent from my SGH-T989 using xda app-developers app
I have exactly the same issue. I had problems trying to wipe cache on CWM 5 so I installed through Goo, now when I boot into recovery, it gets stuck on TEAMWIN screen.
files- images
make sure you have the file in the right place wwhen you know you do get the switcher and then down ld. the file again i had to trial and error it a few times :victory:
The newest twrp gets stuck for me too. I just flashed back to a cwm
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Same issue here on the Telus T989D. Any solutions without using cwm?
You can always try the manual method if your brave and familiar with the terminal. Go to Team Win's for our phone here: http://teamw.in/project/twrp2/101. Download the .IMG file and follow the instructions under Download - Recovery Image Method (using dd): Not hard but doublecheck your typing before hitting enter or you'll brick your phone.
I'm not responsible for any actions taken because of this post. Good Luck, its worth it in the long run.
Sent from my SAMSUNG-SGH-T989 using xda premium
One small problem with that.....
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
This worked for me:
reflash CWM, flash superwipe, install TWRP through goomanager.
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
dailo23 said:
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
Click to expand...
Click to collapse
I flashed that version through Odin and it seems to be running just fine. I wiped caches and now TWRP appears to be working normally :fingers-crossed:
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
EDIT: Wow I guess I didnt read the critical part where your stuck on the recovery boot screen so the attachment below wont help.... JUMP DOWN TO POST #21 AND FOLLOW IT TO RECTIFY THE GETTING STUCK ISSUE
Here, try this file guys. Someone over in the Jedi threads made a CWM flashable TWRP zip. You can thank me for bringing it to your attention if you want, but I did not create this ( I just clicked on the attachment paperclip for the thread and browsed through all the attachments because I knew I saw it somewhere in the development section...)
I also checked TWRP's own website and for the Hercules, v.2.3.1.1 is the latest version supported for our device so far but I only found 2.3.0.0 packed in a recovery flashable form.
Just flash it via CWM like any other zip and once its done it'll reboot your device automatically to system, so just reboot it back to recovery to make sure it worked. It did for me when I did awhile back with v.2.2.2.0 and I just used the below file to flash and update it in TWRP to v.2.3.0.0
Hope it helps
incgnito said:
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
Click to expand...
Click to collapse
i just started having this exact problem with the cache partition. it will freeze on me whenever i try to reformat it, i can't unmount it, etc. i also get stuck on the twrp "teamwin" blue start up screen. have you figured out a solution?
edit- got it working again.. ended up odin flashing twrp 2.2 and i was able to wipe everything and install the new rom stuff.
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Will you kindly explain how you did this?
y0urm0msname said:
Will you kindly explain how you did this?
Click to expand...
Click to collapse
What exactly is your issue?
Eks Dee Aye said:
What exactly is your issue?
Click to expand...
Click to collapse
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
y0urm0msname said:
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
Click to expand...
Click to collapse
Do you currently have CWM or TWRP as your recovery?
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
Currently the non-functioning TWRP. I tried flashing CWM from the Rom Manager app, but that froze too. Looking for a reliable fix. I do not have a preference for recovery.
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
If you have either I guess it doesn't really matter. Just install/flash the attached file below just like you would any other rom via your recovery.
After it installs reboot back into recovery and you will see the old recovery replaced with the latest TWRP for the T989.
Lemme know if this works for ya.
Eks Dee Aye said:
Just install/flash the attached file below just like you would any other rom via your recovery.
Click to expand...
Click to collapse
This is the part I don't understand. If my TWRP is stuck, how do I install/flash via my recovery?
So today i was gonna try to install a custom rom, more specifically Cyanogenmod 10.2. for my Tmobile Galaxy S3 (SGH-T999). When i went to boot into recovery, i saw the screen that is displayed right before you enter recovery, but then after that it just stayed on a black screen. I took out the battery for a few seconds and powered on my phone. Then i tried entering recovery directly through ROM Manager. I got the same black screen, but now if i try to power on my phone without entering CWM, it automatically tries to go into CWM recovery regardless. . I tried a few battery pulls and nothing has worked yet. Luckily i am able to enter download mode so i can flash the stock rom via odin and then restore my backup from the SD card later. I just wanted to know if there is a simpler fix than this so i don't have to go through the trouble of flashing stock rom again. Btw i am still on the stock rom running android 4.3 jelly bean.
Try flashing custom recovery again and make sure it's the newest.
serio22 said:
Try flashing custom recovery again and make sure it's the newest.
Click to expand...
Click to collapse
The problem was i couldn't boot up my phone in the first place because it would automatically go into recovery. I actually fixed it by going it to download mode and then pressing the down button which rebooted the phone properly. I used rom toolbox and now im just gonna stick with TWRP.
RootNoob1299 said:
The problem was i couldn't boot up my phone in the first place because it would automatically go into recovery. I actually fixed it by going it to download mode and then pressing the down button which rebooted the phone properly. I used rom toolbox and now im just gonna stick with TWRP.
Click to expand...
Click to collapse
That's what I meant, you can flash recovery in download mode but as long as you got it working its all good. And yes I highly suggest using twrp over cwm
Thanks anyway man! TWR FTW!!
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw
thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
@thetinyjesus You could also try this app. No PC necessary.
Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe
thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.
Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks
If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.
Okay once im back home ill show the output
Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.
Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
Anyone?
Hi
Been trying to install twrp-3.5.2_9-0-starlte.img.tar to my S9.
First i succesfully unlocked bootloader. Then installed twrp through Odin v3.14.1.
Then the phone succesfully boots into twrp recovery. Then i flashed and tried to install no-verity-opt-encrypt.. 6.1 didnt work so i flashed and tried all down to 4.0. Nothing worked. Just got the error 1 all the time.
Then i tried the read somewhere that i could try the multidisabler. Ref this thread: XDA link. This succsefully installed. Then i rebootet through twrp with the option to install twrp app. The phone got stuck in a start up screen for 10 min and took me right back to start.
After again logging in and setting up the phone Nothing seems to have changed. Only that the bootloader is still unlocked.
Am i doing something wrong? Is it suppose to boot up again to stock OS?
Wheelx said:
Hi
Been trying to install twrp-3.5.2_9-0-starlte.img.tar to my S9.
First i succesfully unlocked bootloader. Then installed twrp through Odin v3.14.1.
Then the phone succesfully boots into twrp recovery. Then i flashed and tried to install no-verity-opt-encrypt.. 6.1 didnt work so i flashed and tried all down to 4.0. Nothing worked. Just got the error 1 all the time.
Then i tried the read somewhere that i could try the multidisabler. Ref this thread: XDA link. This succsefully installed. Then i rebootet through twrp with the option to install twrp app. The phone got stuck in a start up screen for 10 min and took me right back to start.
After again logging in and setting up the phone Nothing seems to have changed. Only that the bootloader is still unlocked.
Am i doing something wrong? Is it suppose to boot up again to stock OS?
Click to expand...
Click to collapse
All you've done is installed custom recovery over stock. This by it's self doesn't effect stock system firmware. The only thing is because knox is trip you lose knox related apps functions.
spawnlives said:
All you've done is installed custom recovery over stock. This by it's self doesn't effect stock system firmware. The only thing is because knox is trip you lose knox related apps functions.
Click to expand...
Click to collapse
Hi and thank you.
Knox is trip?
So how do i know that this worked and twrp is succesfully installed?
Wheelx said:
Hi and thank you.
Knox is trip?
So how do i know that this worked and twrp is succesfully installed?
Click to expand...
Click to collapse
Knox is a Samsung thing. Once tripped it stays tripped and there is no cure for it. As said you will loose knox related apps functions like secure folder,samsung pass,Shealth etc.
To enter twrp is the same process as entering download (odin) mode except you use to volume up button ( power/bixby/vol up ) while device is starting up.
spawnlives said:
Knox is a Samsung thing. Once tripped it stays tripped and there is no cure for it. As said you will loose knox related apps functions like secure folder,samsung pass,Shealth etc.
To enter twrp is the same process as entering download (odin) mode except you use to volume up button ( power/bixby/vol up ) while device is starting up.
Click to expand...
Click to collapse
Yeah it says warranty something 1 on download screen.
I tried to shut down phone and start in recovery mode, but i loded into the stock recovery, not twrp. Am i doing something wrong?
Wheelx said:
Yeah it says warranty something 1 on download screen.
I tried to shut down phone and start in recovery mode, but i loded into the stock recovery, not twrp. Am i doing something wrong?
Click to expand...
Click to collapse
Without knowing your exact steps it a bit hard to say.
I would say that the multidisabler zip you tried didn't work. The zip you tried is for the S10 series. It's also a common problem on latest version of android that the no-verity-opt-encrypt.. 6.1 fails. Very basically this zip, after format data stage,
will prevent phone from re-encrpyting itself when booting into the system.
Try using this zip when installing twrp
Edit:
Installing the twrp app i leave up to you. Can be install later by twrp or playstore and not necessary for installing twrp recovery.
spawnlives said:
Without knowing your exact steps it a bit hard to say.
I would say that the multidisabler zip you tried didn't work. The zip you tried is for the S10 series. It's also a common problem on latest version of android that the no-verity-opt-encrypt.. 6.1 fails. Very basically this zip, after format data stage,
will prevent phone from re-encrpyting itself when booting into the system.
Try using this zip when installing twrp
Edit:
Installing the twrp app i leave up to you. Can be install later by twrp or playstore and not necessary for installing twrp recovery.
Click to expand...
Click to collapse
I have the same problem. Im Gonna try it out
EDIT: i got the write error. gonna try flashing stock again
edit2: flashing stock didnt work. gonna try turning off bootloader and turning it back on. if it does not work then im just gonna install normal XEO instead of PLS
EDIT3: yeah didnt work. just gonna install XEO now