I am on 6.0.1 CyanogenMod13. I haven't done a whole lot root-wise but just today I was looking to get something from xposed and it turned out I didn't even have it installed, so I downloaded it and installed it but needing to flash the .zip I tried to boot into TWRP recovery. Somehow it got uninstalled or something because I could only get into the LG stock screen asking if I wanted to wipe everything. So I tried to install TWRP using Flashify, I installed and on the reboot it gave me a "Can't Enter Recovery Or Update" and some more things about it on the top left above the boot logo. I can't do anything recovery-wise. I'm looking to sell my G2 but I want to make it stock or at least a clean install and I can't do any of that. What can I do??
NinjaChachi said:
I am on 6.0.1 CyanogenMod13. I haven't done a whole lot root-wise but just today I was looking to get something from xposed and it turned out I didn't even have it installed, so I downloaded it and installed it but needing to flash the .zip I tried to boot into TWRP recovery. Somehow it got uninstalled or something because I could only get into the LG stock screen asking if I wanted to wipe everything. So I tried to install TWRP using Flashify, I installed and on the reboot it gave me a "Can't Enter Recovery Or Update" and some more things about it on the top left above the boot logo. I can't do anything recovery-wise. I'm looking to sell my G2 but I want to make it stock or at least a clean install and I can't do any of that. What can I do??
Click to expand...
Click to collapse
Same happened to me still cant fix it but you could try going back to stock (wouldn't work for me driver problems on windows 10)
http://forum.xda-developers.com/showthread.php?t=2432476
bump
homegrown1982 said:
Same happened to me still cant fix it but you could try going back to stock (wouldn't work for me driver problems on windows 10)
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This got me down to 4.4.2 but when trying to install TWRP it gives me the same Boot certification error and I can't
EDIT: I used AutoRec on 4.4.2 and I have TWRP working!
Related
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
thanks for everything
On the official Oppo forum's there's a guide on how to install the latest Omnirom. Under known issues it says:
5)After installing the TWRP recovery the Screen Touch firmware update goes on for more than 5-7 minutes, do a hard reboot and you would be fine,
Click to expand...
Click to collapse
I haven't tried it myself since I didn't get the problem when flashing Omni and Asylum, but it seems to be worth a shot.
In case you are looking for the topic, search for "How to Install OmniRom 4.4".
Background: So i bought this used S5 900f from someone and it gave me "recovery is not seandroid enforcing" error while rooting and installing recovery. i found a workaround for this error by immediately pulling the battery trick after root. I have installed TWRP and root and they work but this "Recovery is not seandroid enforcing error" still displays when i try to enter recovery for about 2-3 seconds and then the recovery boots.
Now the Problem is : My s5 900f is not saving Wifi password on any of the lollipop builds i have tried Many UK 5.0 (BTU) Builds from Sammobile , and Nordic Countries 5.0 as soon as i restart or shutdown m phone Wifi password is reset and i have to enter it again after turning my phone on again. Surprisingly When i downgrade to any of the kitkat Builds Wifi starts saving passwords just fine?
Things i have tried
Format, Clear dalvik cache, cache, data, system, internal Storage and install different 5.0 builds.
Enabling disabling Google backup, it doesn't help.
Kindly Help me out does Wifi not saving password has anything to do with this "Seandroid not enforcing Error" . And how to fix this issue i am at verge of smashing this phone. .....:angel:
http://forum.xda-developers.com/galaxy-s5/general/s5-forget-wifi-passwords-reboot-fix-t3105976
Thanks alot buddy, you just saved my phone....Phewwww do you know why it happened in the first place?
Buggy ROM is all I can think, it happened to me with a clean install of the latest LP ROM so I went looking for a fix for myself
I tweeted to Samsung UK about it, and they just talked to me like I was stupid, I guess they don't want to admit to it being their fault
UPDATE NOW after the build prop fix, i rebooted fine once... After installing TWRP the phone is crashing on boot up....touchwiz crashes along with all other programs it wont let me boot up. Maybe TWRP messed something up.
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
*Detection* said:
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
Click to expand...
Click to collapse
does your phone display "recovery is not seandroid enforcing" just before entering twrp? i tried clearing cache and battery pulling didnt work....now flashing earlier 5.O btu.
Yea, just means it's a custom recovery
*Detection* said:
Yea, just means it's a custom recovery
Click to expand...
Click to collapse
Some folks are able to flash any 5.0 build and they don't get the Build.Prop issue. i just reflashed and the issue came back...will re edit the build.prop till now i have rooted + installed TWRP no issues so far only build.prop left to be edited..... could you please tell me why is it persistent on some phones that even reflashing, formating doesn't help.
Unfortunately Nothing works....I have been more than patient with this device...been flashing and trying different things for 18 hours now. It works fine but after going to recovery (Just by entering it) and then rebooting will freeze my phone with "Unfortunately Media storage has stopped working...and everything else like touchwiz also crashes".......i was so...so wrong to move to a samsung This Definitely is my last samsung phone...for now i will keep trying different things.
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
*Detection* said:
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
Click to expand...
Click to collapse
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
dork997 said:
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
Click to expand...
Click to collapse
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
*Detection* said:
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
Click to expand...
Click to collapse
Thanks for your Help, i guess this problem is too complicated. Anyway this time i installed Philz recovery > formatted everything > remove user content and data > custom formatted everything > flashed 5.0 BTU. and surprisingly its saving WiFi passwords without any build prop changes. So i am going to leave it here . 5.0 Unrooted with stock recovery everything working (FOR NOW) . This time i used Odin 3.10 instead of 3.07. I hope it does not get stuck at boot logo and start crashing. Only one problem it kept connecting to "update server" evem tho i had disabled the auto update option from settings>about >updates . i restarted immediately hopefully it wont try to update again. Thanks again for your help.
I followed the instructions here http://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery <3e> LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
PhreeqQitsikk said:
I followed the instructions here http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
Click to expand...
Click to collapse
S5 doesn't have a custom recovery per se, so any app that "reboots to recovery" will go to the Android stock recovery which your in. You can't flash anything of value in there, and can't install a custom recovery. You should just be able to turn the phone off then on again to get back to the stock rom, right?
It's been so long since I've done it, but won't safestrap only install on kitkat? Doors it even work in lollipop? Must people use flashfire I think
I should probably mention now that I got it fixed. Following more instructions in that thread, I did everything in the order of the first step again, using ODIN, flashed back to NC2 (I think? Going off memory) rooted, installed Safestrap, flashed MOAR, and the OC4 firmware, and here I am.
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
almost looks like it can't mount the system
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed
keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate
snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw
snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.
So I've installed TWRP onto my S8 and have wiped it completely, though I did have to change and then change back the file formats so that TWRP would register them correctly
I downloaded renovate ice 1.1, copied it onto my sd card and then flashed it everything installed well
When I then reboot it doesnt get past the first screen as in showing (not sure if it freezes at this point but have left it for 2 hours so Im guessing so)
Samsung Galaxy S8 POWERED BY android
Then the only thing I can do is get the phone back into recovery mode (then when I go to reboot it says there is no OS)
Before I installed the custom ROM I had an error message stating that the integrity verification had failed, I pressed on believing that this would be fixed once I had installed renovate
I know that my phone is a exynos variant, is there any way to check exactly what variant withing TWRP
The download mode is still working
Extra Information
and also when I go into TWRP it asks me about if it should be only system read each time it starts up
it also prompts for me to install the app when I try to reboot through TWRP though I believe that is normal
thegasovi said:
So I've installed TWRP onto my S8 and have wiped it completely, though I did have to change and then change back the file formats so that TWRP would register them correctly
I downloaded renovate ice 1.1, copied it onto my sd card and then flashed it everything installed well
When I then reboot it doesnt get past the first screen as in showing (not sure if it freezes at this point but have left it for 2 hours so Im guessing so)
Samsung Galaxy S8 POWERED BY android
Then the only thing I can do is get the phone back into recovery mode (then when I go to reboot it says there is no OS)
Before I installed the custom ROM I had an error message stating that the integrity verification had failed, I pressed on believing that this would be fixed once I had installed renovate
I know that my phone is a exynos variant, is there any way to check exactly what variant withing TWRP
The download mode is still working
Click to expand...
Click to collapse
should I try to reinstall TWRP and see what happens
thegasovi said:
should I try to reinstall TWRP and see what happens
Click to expand...
Click to collapse
I've tried to install the Batman ROM but to the same avail,
still prompting me to install the TWRP official app (but not always)
am going to try reinstalling twrp using odin
could it have anything to do with knox values changing (need to research)
installed batman rom after using Odin to BL some new firmware(think that's what its called) onto the device
now am stuck on the next boot loading screen
will wait for some time to see if its my phone
-so 1 problem was due to the previous stuff on the device hopefully this means that the integrity verification thing is fixed (not sure how to check
-still havent re-'downloaded' a new twrp via odin, may try next
-could also try reinstalling batman as it was installed before the firmware, may be worth it
-could try to use default rom (need to find download page)
not sure about next step
reinstalled renovate and booted up and got back to the verification failed screen, may have something to do with me selecting knox when I installed it
-niw will try to solve integrity verification problem as when I try to reset it wont work w/ twrp
Maybe too many little things that are causing issues, maybe rather just use Samsung Switch and do a recovery and it will reinstall as per stock, then try the rooting, custom ROM thing from scratch. I know I battled with mine, got TWRP installed but coult get passed samsung boot screen. So i did used Samsung Switch recovery function and got phone back to stock, now I just use package disablers to kill stuff and all is well.
at first, why did you choose renovate 1.1 when 2.2 is availiable?
i would start from scratch again...
flash stock rom via odin. boot and test device. there should be no problem, after this, flash twrp again and put latest renovate rom on memory or external usb device.
with aroma installation you can choose to full wipe your phone. this should make no problems.
Tim Niklas said:
at first, why did you choose renovate 1.1 when 2.2 is availiable?
i would start from scratch again...
flash stock rom via odin. boot and test device. there should be no problem, after this, flash twrp again and put latest renovate rom on memory or external usb device.
with aroma installation you can choose to full wipe your phone. this should make no problems.
Click to expand...
Click to collapse
looking back on it I guess I just didnt realise that that version was available
could you give me a link to where I can download the stock rom from, that would be great
Jostian said:
Maybe too many little things that are causing issues, maybe rather just use Samsung Switch and do a recovery and it will reinstall as per stock, then try the rooting, custom ROM thing from scratch. I know I battled with mine, got TWRP installed but coult get passed samsung boot screen. So i did used Samsung Switch recovery function and got phone back to stock, now I just use package disablers to kill stuff and all is well.
Click to expand...
Click to collapse
I tried to open samsung switch earlier but it believed that my phone was no longer supported and I guessed that this was due to the rooting, what mode where you in to be able to connect to samsung switch
not sure now but atm I cant get into TWRP anymore
Put phone into download mode, then use recovery option on switch.
thegasovi said:
looking back on it I guess I just didnt realise that that version was available
could you give me a link to where I can download the stock rom from, that would be great
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/how-to/official-stock-firmware-update-odin-t3598172
take a look here,
there is described, how you can download stock rom with the tool samfirm.
keep this rom safe you may need it once or twice again.
---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------
thegasovi said:
not sure now but atm I cant get into TWRP anymore
Click to expand...
Click to collapse
and again...
as long as you are abel to go into download mode, everything is fine.
flash stock again -> twrp -> custom rom with full wipe in aroma installer
reverted back to stock os using odin
checked that all is well and there was no lasting damage (knox was still working fine)
reinstalled twrp, same problem happened again with twrp not recognising the internal storage so had to reset the file format
flashed the batman rom, now am back at the second boot screen and cannot get past
thegasovi said:
reverted back to stock os using odin
checked that all is well and there was no lasting damage (knox was still working fine)
reinstalled twrp, same problem happened again with twrp not recognising the internal storage so had to reset the file format
flashed the batman rom, now am back at the second boot screen and cannot get past
Click to expand...
Click to collapse
with internal storage you mean data partition?
sorry, i forgot. thats a common known issue with twrp , wipe data partition in twrp menu, after that you are able to install custom roms