Hello,
I just flashed the latest ROM for the S8+ (AQL5) and that went well.
Afterwards I tried to flash TWRP, but now the phone is stuck on the Samsung screen.
I then followed the guide I found here to use the BL file of AQF7 in Odin and spam the Start button so I managed to get into TWRP.
Question is, what do I do next? I restart the system it's the same problem all over again.
No one explains anywhere what to do in TWRP to save the phone.
Can I remove TWRP or somehow save the phone (without wiping my data)
Please help
Can you get to download mode? Then go to ODIN and redo your flashing of the OS and then TWRP. After the flash of TWRP, immediately boot into TWRP, and do Verity if you want that, and your root, if not already done. Clear Dalvik/cache and reboot to system.
It is not uncommon for folks, following TWRP flash, to get stuck in boot loop, unfortunately. Can take a little time, but you will get through it and finally to System.
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
nkomp18 said:
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
Click to expand...
Click to collapse
Would you please provide the info from my first post? and Exynos of Snapdragon?
JeffDC said:
Would you please provide the info from my first post? and Exynos of Snapdragon?
Click to expand...
Click to collapse
I have Exynos - model SM-G955F
Yes I can go to download mode but I won't do the things you ask because they're guaranteed to soft-brick the phone again and I have it working now
i have the same problem, followed this guide https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009 managed to get to TWRP no problems, once i reset the device though im stuck at the samung galaxy s8+ boot screen and can't get it off
any suggestions ? i did try to search but this old thread was the only relevant one i could find
stuck on boot screen after flashing twrp for magisk manager
i flashed magisk manager in twrp youtube.com/watch?v=r3R9kiBIx34 by this and now not booting to android . before i had this i reflashed miui 11 using official software and coulnt be sucess this time also please help me any one . my mobile is redmi 6 pro.:crying::crying::crying::crying:
Related
..
you asked the same question I was going to ask....hopefully someone replies to you, I'll keep asking around the interwebs for a solution I already asked Max Lee and still no reply. I'm rooted too (cf auto root) but i want twrp just in case.
I'm trying for 2 days for my 920i and I ha e twrp now I flashed 920f and boot fine!
https://www.fshare.vn/file/B38M8WL1ZQDE
merrykid said:
I'm using G920I Australia version.
I can successfully root using CF-Auto-Root.
But I can not get into TWRP recovery after I flashed that (tried both versions of the recovery) using odin. It stops at the first screen (samsung logo). I tried using adb commond reboot recovery and the hardware key (volum up+power+home), both of them do not let me in to the custom recovery.
I had tried enabled knox before flash TWRP, which made it into boot loop. And then recoveried using the official firmware. Now I can only get into the official recovery.
Any suggestions for how to get into the TWRP?
BTW, how to backup the pit file using adb? On previous models it was mmcblk0, but Galaxy S6 seems to have changed the memory map to sda1, sda2, etc.
Click to expand...
Click to collapse
I got the 920i Aus version too. I was told two different things.
Update firmware to AOD1 and flash TWRP and it should work.
-or-
Use the 920t as jah2110 says. I would find the file from somewhere more 'reputable'.
Downloading a AOD1 firmware now from sammobile which is awful slow. First one I tried to flash gave me fail in odin so im trying a different one.
Stuck at the Samsung logo after trying to flash the recovery via twrp app, now it doesn't even boot normally. so if you want to install twrp don't use the app, G920I telstra version
Just flash an AOD1 firmware or more. The new zealand firmware for instance and then twrp is gonna work.
If you are stuck after flashing twrp on the australian firmware just flash root using odin and you will be able to start your device again
massacreur75010 said:
Just flash an AOD1 firmware or more. The new zealand firmware for instance and then twrp is gonna work.
If you are stuck after flashing twrp on the australian firmware just flash root using odin and you will be able to start your device again
Click to expand...
Click to collapse
really? i didn't know that, anyway, if you want to update/reinstall the stock firmware, sammobile is so bloody slow, i deem it unusable, so i found this gem, much faster than sammobile, i downloaded at 1.3MB/s so it takes just over 20 minutes for the whole firmware. http://galaxys6root.highonandroid.com/galaxy-s6-stock-firmware/ give it a try if sammobile just pisses you off.
Yes it took me a few days to figure it out and everyone kept saying that twrp should work ...but thats just a matter of firmware version.
So is there a fix? I can get root but TWRP just sites and the boot screen.
I've been in the same situation using a Aussie Voda 920i, I was able to root using CF auto root but then had deep sleep issue & couldn't install TWRP. Now i've installed the singapore firmware & also got TWRP running but cant root.
If I use ODIN to root its gets stuck on logo screen & If I use TWRP it appears to go OK but just doesn't work. Also although CPU Spy says I am getting deep sleep battery life seems awfull
Twrp gave me the boot screen for infinite as well. I live in Alaska. I had to reflash root file to boot. Never got twrp to work. I tried to flash via app. I don't even want more possible headache flashing it with Odin.
Surely if you've got root you can install twrp from the app store and let it replace the recovery.
Same issue
I had exactly the same issue, flashed TWRP from a reliable source and my phone bricked at start up logo screen, could only get into download mode, once i did that i reflashed with ODIN and autoroot file and phone came back alive. Thank god.
---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------
Tried to install TWRP from official APP, said it installed recovery successfully would you like to attempt reboot and get into recovery, got stuck again at boot screen LOLLLL awesome...... piece of ****ware.
Same for me G920F. I tried twice both failed.
First time use this thread The phone was successfully rooteded. I installed "TWRP Manager.apk". It cause phone infinitely reboot.
Then I restore the stock ROM (you won't know how painful to download the 1.5G+ ROM).
Second time, I rooted again. And tried use freshily (?) to manually install an img in sdcard. It said success and reboot. But it stayed in boot logo.
I restore the stock ROM again (but the kies3 needs to download ROM again!).
I will not try a third time unless there is an right answer.
__________________
btw, the first one say 'oem unlock' must be checked. But I do not have this option, maybe because my phone is unlocked already (not binded to any one).
GrandMstrBud said:
So is there a fix? I can get root but TWRP just sites and the boot screen.
Click to expand...
Click to collapse
im a Noob but i was told that my TWRP was being overwritten during the reboot and that i Must flash a custom kernal after rooting so that the TWRP wouldn't be overwritten
SillyTAO said:
im a Noob but i was told that my TWRP was being overwritten during the reboot
Click to expand...
Click to collapse
This only happens when you fail to force the reboot into recovery yourself.
If you let the phone reboot automatically after flashing, it will be stuck @ bootloop; so you have to be faster & hold the vol up+home+power buttons *immediately* when Odin finishes the process.
Don't bother removing the cable or waiting for the screen to change, that will be too slow.
Cant boot in twrp after flashing thru odin
knox counter trips
Just got my XT1644 G4 Plus 16GB here in America and brought it home for some testing.
Everything was a piece of cake, I did these things in order with no issues. There are other guides for these things all over XDA so I won't be giving detailed instructions.
Unlocked the bootloader here - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Installed TWRP from here. - http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
And flashed SuperSU from here - https://download.chainfire.eu/696/supersu/
When TWRP first boots it will ask if you want to run in systemless mode. Make sure you tell it YES!!!
Rebooted on the first try with no issues.
I have Xposed installed with a few modules and it works great.
Sent from my Moto G (4) using Tapatalk
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
mystx2112 said:
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
Click to expand...
Click to collapse
Can extract it from the stock ROM here: https://www.androidfilehost.com/?fid=24572369242687085
not sure if this is full proof i got bootloop
After flashing SuperSu 2.76 the phone is stuck forever at the "moto" logo. Is it because I'm using such a new version of SuperSu? Why do you use 2.46?
How long did it take to get the unlock code? I am waiting for a couple hours now...
LE: 4 hours... and finally I got the code.
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
craigl14 said:
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
Click to expand...
Click to collapse
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
I can't get twrp to install. I keep getting told that the image is not signed or corrupt
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
SoNic67 said:
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
Click to expand...
Click to collapse
that's just it... I can't boot to twrp. It's not there.
Where? You can't find it on the SD by browsing in the recovery?
because that's just it, there's nothing in recovery. This has gotten so convoluted that I don't even know what I'm supposed to have where....
@davidkoby
Stock ROM Recovery starts with a "Dead Android" and "no command" written under it, it is you see or something else?
Does supersu need to be in systemless mode?
craigl14 said:
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
Click to expand...
Click to collapse
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
sam9s said:
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
Click to expand...
Click to collapse
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
craigl14 said:
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
Click to expand...
Click to collapse
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
sam9s said:
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
Click to expand...
Click to collapse
Hmmmm...I don't know if you have XT1644. Most who have that version are still waiting on OTA I think and certainly didn't get it month's ago. It is the G4 Plus North American version. If you still have the box it will be on the UPC label. It will also be in your phone info in settings once your phone works again. Did your phone work fine before you tried to root it? Anyway, Nougat will not root with this method. If you can boot into recovery, try factory reset. If that doesn't work, you're going to have to reflash the Nougat ROM...make sure you get the right one for your phone. You will need to search around on this forum for instructions and which download to get, etc. Once you have Nougat up and running again, you will need to leave it unrooted or use one of the proven methods of root. Again, I don't think systemless supersu works for Nougat. I have no idea what bad key means. The only thing I've ever had is "N/A" come up in the unlock warning. Incidentally, you can get rid of the bootloader warning screen if you want to.
Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.
Update: I tried flashing TWRP by Askuccio through fastboot and I successfully did. Then I flashed PixyOS v2.4 and flashed it successfully then flashed Gapps and stock recovery then followed rest of the required steps and everything went smooth and right. Using PixyOs now. Great rom with great stability with Android P. ?
I was on Oreo on my 6x. I wanted to flash this pixyos rom on my Honor 6x. I unlocked the bootloader of my phone installed the Twrp successfully without any hassle. Now it was time to flash PixyOs and unfortunately I did not do any backup of any sort. The PixyOs Package showed some error when I tried to clean flash it. And here we go my phone had No Os now. I searched a lot and found this thread
https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I gave it a try step by step thinking about that it would work but after successfully following all the mentioned steps and flashing everything I got this "System failed" error when the device was booting. In other words it didn't work eventually.
I tried the dload method with the same update zip from the thread linked above but it failed too.
I tried erecovery to restore my device but it gave me "Getting package info failed".
I don't know what to do now. Please help me with this and help me restore my phone.
I had the same issue
i made something like this a month ago
only one temporary solution worked is flashing EliteRom via twrp and i got the phone working again but still can't flash a stock rom.
tanaybitw said:
I was on Oreo on my 6x. I wanted to flash this pixyos rom on my Honor 6x. I unlocked the bootloader of my phone installed the Twrp successfully without any hassle. Now it was time to flash PixyOs and unfortunately I did not do any backup of any sort. The PixyOs Package showed some error when I tried to clean flash it. A then nd here we go my phone had No Os now. I searched a lot and found this thread
https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I gave it a try step by step thinking about that it would work but after successfully following all steps and flashing everything I got this "System failed" error when the device was booting. In other words it didn5 work eventually.
I tried the dload method with the same update zip from the thread linked above but it failed too.
I tried erecovery to restore my device but it gave me "Getting package info failed".
I don't know what to do now. Please help me with this and help me restore my phone.
Click to expand...
Click to collapse
Can you boot to fastboot. What did the PC say when you ran the script. Try to flash TWRP if EMUI 5 and then press and hold Volume Up and Power to boot into it. If it works, good. If not then again boot to bootloader and try to flash TWRP of EMUI 8. Again try to boot into it. If it works, good. Anyway, once you're in TWRP don't let your phone turn off. Plug it in charging. Now go-to wipe, and format data
»FáRéS...?« said:
i made something like this a month ago
only one temporary solution worked is flashing EliteRom via twrp and i got the phone working again but still can't flash a stock rom.
Click to expand...
Click to collapse
I'd suggest you to try PixyOs (With Askuccio TWRP). It's a great and fluid ROM. Only downside is it doesn't have Stock Emui camera and I didn't even try flashing it because I read somewhere that it causes the device to get stuck in bootloop.
Mannan Qamar said:
Can you boot to fastboot. What did the PC say when you ran the script. Try to flash TWRP if EMUI 5 and then press and hold Volume Up and Power to boot into it. If it works, good. If not then again boot to bootloader and try to flash TWRP of EMUI 8. Again try to boot into it. If it works, good. Anyway, once you're in TWRP don't let your phone turn off. Plug it in charging. Now go-to wipe, and format data
Click to expand...
Click to collapse
Thank You for your reply.
Hello,
I'm running the samsung galaxy a8 (2018) canada version, so sm-a530W
Recently tried installing twrp, everything was looking okay, i booted up got to regular booting and accessing the phone, then i powered it off and powered it back on and i'm stuck at Downloading mode only.
What are my options here? I can't seem to boot into twrp now either or flash it again, seems to go back to download mode regardless
Hm actually so I just went into odin and flashed twrp again but let it auto-reboot this time and it lets me get through to my twrp and system but turning it off again leads it back to downloading mode, do I need to reflash a boot image and where do I get one?
Realized I may not have turned on USB debugging when I installed twrp, is that what's causing all these issues? and how would I best resolve this
After installing TWRP you have to treble-ize your phone. For this, reboot into TWRP with the given option. Then flash TWRP treble so you avoid getting locked out. Details of the procedure in this thread. Depending on your android version steps might be different so make sure to read everything and follow it carefully.