My rom is on android 9 binary 4, when i try to install twrp by odin, the message "fail" appears. I already waited a week, I did the procedures, I emphasize that the OEM is always activated, it never disables even reinstalled the rom. I can't see where I'm going wrong, I would at least like to get back to android 7.0, because it was lighter
Related
Hey everybody,
i hope so much, that anyone can help me. After i installed the recovery TeamWin (TWRP) (it was successful), i tried to flash Xposed Framework manually, i got again an massage "it was successful". But after that i can not start my Samsung Galaxy S5. It shows me only the Samsung Logo and nothing happened. Of course i tried via TeamWin an factory reset but i still can not boot my smartphone (Stop at the Samsung Logo). My S5 ist rooted, i`m using 5.0 (lollipop). Version of the TeamWin was 2.8.7.0 and of the Xposed Framework "xposed-v74-sdk21-arm". Has anybody an idea? I would be very happy. Should i delete the TeamWin recovery? But how? I want to install the standard recovery of Samsung, but how to do this? Where can i find the original Recovery from Samsung?
Xposed isn't supported on latest Android versions (r23). You should just remove Xposed from your phone, by using this tutorial:
Code:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Deadclysm said:
Xposed isn't supported on latest Android versions (r23). You should just remove Xposed from your phone, by using this tutorial:
Code:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Click to expand...
Click to collapse
Thank you, but i cant find the xposed folder...because i made a factory reset
Just delete the files and folders that you can see (those which are Xposed related). It should fix your problem.
Or just flash ovet your rom again (dirty, without wiping).
Sorry it took long time for me to answer.
Edit:
Read sticky, there's a script that uninstalls it automatically. This should work 100%
always make nandroid backup before flashing
Having the same problems
So I'm having the same problem. The Framework says it installs correctly, but after reboot, device gets stuck at the Samsung screen. I don't understand the comment android r23. I'm looking at the build info and I don't see this anywhere. Some explanation or assistance would be great.
I'm not sure why sdk 23 was even mentioned as Lolliopo 5.0 is sdk 21.
@LieberKerl, you got the xposed-v74-sdk21-arm.zip from Rovo89's thread, correct? If so this will not work on stock Samsung Touchwiz ROMs as mentioned in the first post of that thread.
There is no Xposed that will work on a stock Samsung Touchwiz ROM, it must be deodexed first and if you have a deodexed ROM, you need arter97's unofficial Xposed from this thread: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463.
If you don't know what deodexed is, there's a bit of reading ahead of you. If you don't want to deodex your Lollipop 5.0 ROM, then you're out of luck.
It takes longer to boot after the install, how long did you leave the samsung boot logo up? it took nearly 15 mins to boot after rom install and around 5 mins after xposed framework. I went through alot of hassle just to discover i was impatient.
Reflash stock ROM with Odin.
after flashing in my unite 3 notification bar disappeared and phone is restarting again and again
Nerotech11 said:
It takes longer to boot after the install, how long did you leave the samsung boot logo up? it took nearly 15 mins to boot after rom install and around 5 mins after xposed framework. I went through alot of hassle just to discover i was impatient.
Click to expand...
Click to collapse
Happened to me too on an Oukitel C4. After flasing it needs quite some time to boot.
Cannot Install Xposed in Samsung Galaxy S6
I have the same issue with a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
InfiniteSegovia said:
I have the same issue with a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
Click to expand...
Click to collapse
Most likely your issue is caused because you did not install the correct framework version. You need the one from wanam. Just search for "Xposed Samsung wanam" and you'll find your answer.
Alright, here we go.
I am trying to install a custom ROM on my Galaxy Note 4. I bought it refurbished a year ago and in the past few days it has been pissing me off. The Note lags like crazy and reboots often (Usually in the process of opening an app)
If anyone has a direct fix, awesome. But I tried and gave up. This led me to factory reset, but the issue persisted. I hope its not a hardware issue.
The seller said it was never rooted, but with the issues that the stock recovery has, I have my suspicions.
So now I'm at trying to root the Note. I've already rooted a Galaxy S4, but that was a few years ago.
This is my issue. I have tried many things. I tried to root with CF auto root on Odin, but it is always stuck at recovery.img. It reaches that point and just stops.
I also tried just flashing CWM or TWRP through Odin, but it also stops at recovery.img.
I tried to flash TWRP through adb, but although the device was recognized in "adb Devices" nothing comes up later on when I type "Fastboot Devices".
Any Ideas how to fix these issues or any new solutions? I know this is an old issue, but I love the Note 4.
Sorry for the weird Capitalization,
Samsung SM-N910T
Running Marshmallow 6.0.1
"Never rooted" (Probably previously rooted)
Running Windows 10 PC (With very capable specs)
Installed Samsung USB Drivers
Odin 3.12
Using the original cable
I can't update to Pie my Mi A2, "Error on install" "Can't Install" Bootlop
When it came out the first version also happened to me, flashed everything with fastboot, and had the critical partitions unlocked as well. But the result: vibrated, lit, turned off, and so on again and again. I had also tried the VPN method, downloaded via OTA, the same thing happened and I had an error when installing. All this having tried several times to install the rom with MiFlash downloaded from the official page.
Now finally the version came out, reinstall of 0, I do not have root, nothing, the official version 2 of Pie that was released in my country is downloaded, and the same thing happens, I do not know what to do, why my device does not turn on after update ?, keeps appearing "Error when installing", it did not happen to me with roms like Pixel Experience ..
AlvaroBenitez99 said:
When it came out the first version also happened to me, flashed everything with fastboot, and had the critical partitions unlocked as well. But the result: vibrated, lit, turned off, and so on again and again. I had also tried the VPN method, downloaded via OTA, the same thing happened and I had an error when installing. All this having tried several times to install the rom with MiFlash downloaded from the official page.
Now finally the version came out, reinstall of 0, I do not have root, nothing, the official version 2 of Pie that was released in my country is downloaded, and the same thing happens, I do not know what to do, why my device does not turn on after update ?, keeps appearing "Error when installing", it did not happen to me with roms like Pixel Experience ..
Click to expand...
Click to collapse
You don't loose nothing, stay at oreo until next update which maybe is not beta
So, I had Xiaomi phones before and I know that they can get little bit buggy sometimes, because of that I always keep "allow OEM unlocking" checked, just in case something happens. Okay back to what happened, I was running latest Pie version when I got notification that update to Android 10 was available, so naturally I tried to update and got stuck in a bootloop. This had happened before, so i decided to just roll back to the previous update and try again but no, even tho i have my bootloader unlocked and I can flash in fastboot mode, It doesn't work (I tried with just running .bat file and with MI Flash). It writes 'success' but when it reboots it can't past android one logo (and after few attempts to boot it gives error 'can't boot would you like to retry or power off' or something like that), I have tried to flash many 'update versions' but to no avail, only thing to work is first official ROM (android 8.1)
after flashing that it boots and works normally, it successfully updates once, to Android P and than same thing, It downloads file, applies update and when I reboot phone to finish update it gets stuck in bootloop.
Please help me, thanks in advance.
My advice is to unlock the bootloader and install the Pixel experience ... It is much better than the official Android 10 ... And get rid of Xiaomi's update issues.
Badotti said:
My advice is to unlock the bootloader and install the Pixel experience ... It is much better than the official Android 10 ... And get rid of Xiaomi's update issues.
Click to expand...
Click to collapse
(My bootloader is unlocked) something strange happened I tried again installing latest pie update and for some strange reason ( to be honest I tried to boot 30-50 times) it worked and it successfully updated to Android 10 ( again after ~50 or so tries to boot) so yeah.
Samsung Galaxy Tab S2, SM-T813, android 7.0
So after a few attempts, I finally got TWRP installed. I tried to install magisk, but that failed.
But when I go into TWRP recovery, and then select system to reboot, it starts as a new/reset device and I have to go through the initial setups again.
I have tried this twice now, and it's the same.
Perhaps I missed something and there is some security protection going on, but I don't know enough and am a bit stuck.
Can someone please give me some pointers to resolve this. Thanks.