I have an S4 rooted on MDK with TWRP 2.5.0.2
I have been on Eclipse TW 2.0 since he put it out, and decided to try CM11 today. I flashed, booted, set it up and upon reboot I get stuck at the splash screen.
I restored my backup, which won't boot. I flashed the new Eclipse ROM, which booted and upon reboot it hangs at the splash screen,
I restored my orignal nandroid and it booted, but upon reboot it hangs at the splash screen.
No matter what I do now, I can only get one boot before it hangs on that splash screen. I have done "Fix Permissions" and wiped dalvik/cache
Any ideas? at this point I am even thinking of just odin back to MDK and re-rooting if it is possible.
Is TWRP out of date or something? This is really weird.
sparkerjc said:
I have an S4 rooted on MDK with TWRP 2.5.0.2
I have been on Eclipse TW 2.0 since he put it out, and decided to try CM11 today. I flashed, booted, set it up and upon reboot I get stuck at the splash screen.
I restored my backup, which won't boot. I flashed the new Eclipse ROM, which booted and upon reboot it hangs at the splash screen,
I restored my orignal nandroid and it booted, but upon reboot it hangs at the splash screen.
No matter what I do now, I can only get one boot before it hangs on that splash screen. I have done "Fix Permissions" and wiped dalvik/cache
Any ideas? at this point I am even thinking of just odin back to MDK and re-rooting if it is possible.
Is TWRP out of date or something? This is really weird.
Click to expand...
Click to collapse
In my experience the hanging at samsung splash screen has been normal upon reboots about 50% of the time on any aosp rom ive run. Have you tried when it hangs at the samsung screen to do a battery pull and try to turn device back on? For me this always fixes the issue.
Well, I pulled the battery about 20 tines last night and I think it boots about 10% of the time, even after flashing back to a TW ROM.
Any suggestions to try?
sparkerjc said:
Well, I pulled the battery about 20 tines last night and I think it boots about 10% of the time, even after flashing back to a TW ROM.
Any suggestions to try?
Click to expand...
Click to collapse
Wow thats terrible. Have you tried changing recoveries? I know most people have great luck with twrp 2.5.0.2 which you are running but maybe try cwm to see if it helps? I am currently running philz touch recovery based off of cwm 6.0.4.5 and it seems to happen less frequently. Also twrp has an updated version that you may try if you prefer that recovery. Just a thought
---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------
You can try twrp manager from the play store. Advanced then install recovery to get updated to the most recent version. I believe the goomanager install of twrp is borked at this point.
---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------
sparkerjc said:
I have an S4 rooted on MDK with TWRP 2.5.0.2
I have been on Eclipse TW 2.0 since he put it out, and decided to try CM11 today. I flashed, booted, set it up and upon reboot I get stuck at the splash screen.
I restored my backup, which won't boot. I flashed the new Eclipse ROM, which booted and upon reboot it hangs at the splash screen,
I restored my orignal nandroid and it booted, but upon reboot it hangs at the splash screen.
No matter what I do now, I can only get one boot before it hangs on that splash screen. I have done "Fix Permissions" and wiped dalvik/cache
Any ideas? at this point I am even thinking of just odin back to MDK and re-rooting if it is possible.
Is TWRP out of date or something? This is really weird.
Click to expand...
Click to collapse
Here is cwm 6.0.4.4 if you want to try that as well. It's already loki'd so just flash it.
https://www.dropbox.com/s/ldlgv0iaxf1j8ya/recovery-cwm-touch-6.0.4.4-jfltevzw(loki).zip
Remember that your backups will not work when you change/update recoveries so you will want to make sure to backup your current setup if you want.
flyinj54 said:
Wow thats terrible. Have you tried changing recoveries? I know most people have great luck with twrp 2.5.0.2 which you are running but maybe try cwm to see if it helps? I am currently running philz touch recovery based off of cwm 6.0.4.5 and it seems to happen less frequently. Also twrp has an updated version that you may try if you prefer that recovery. Just a thought
---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------
You can try twrp manager from the play store. Advanced then install recovery to get updated to the most recent version. I believe the goomanager install of twrp is borked at this point.
---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------
Here is cwm 6.0.4.4 if you want to try that as well. It's already loki'd so just flash it.
https://www.dropbox.com/s/ldlgv0iaxf1j8ya/recovery-cwm-touch-6.0.4.4-jfltevzw(loki).zip
Remember that your backups will not work when you change/update recoveries so you will want to make sure to backup your current setup if you want.
Click to expand...
Click to collapse
Thanks for the help, my current backup appears to be no good anyway so I'm kind of hosed.
Once I get stuck at that splash I have only made it through 1 time by fixing permissions, then it froze the next boot. 5-6 battery pulls and it still won't go.
I'm afraid to try a new recovery, I'm afraid to do anything really. I almost want to just odin to MDK and start over. Currently I am on a fresh install of CM11, on the first boot just trying to make it through my work day without rebooting lol.
Took me 5 flashes to get it to boot at all.
After pull the battery,did you hold the vol up and the power and wait until the phone vibrate and release the power button and keep holding the vol up until vibrate again and then choose your nandroid.....
android-incredible said:
After pull the battery,did you hold the vol up and the power and wait until the phone vibrate and release the power button and keep holding the vol up until vibrate again and then choose your nandroid.....
Click to expand...
Click to collapse
No I just booted into TWRP and did it from the menus. Is there something special about doing it this way?
Related
Hi all,
I got this S2 today, did unlock and root, when tried to load CMW in recovery mode,did mistake and run update form sdcard. I guess, I had old stuff on sdcard. So now I cannot get out from there at all, I tried to reboot or power off option, but it just sit there and does nothing. Tried to remove battery and reboot, it takes me back to CMW recovery. Please, help me to fix this matter.
---------- Post added at 01:37 AM ---------- Previous post was at 01:22 AM ----------
I tried to get in Downloading mode and install Lite'ning Rom v6.1 XXKH3, it went though, but after reboot I got into ClockworkMode Recovery again
Hmmmm, this is very weird, if you can get into download mode, you should try flashing a stock rom, and not Lightening Rom....
Thnx, I got it fixed. I am coming from Samsaung Captivatre and button there are diiferent combination as navigation vise. Stupid me.
Warning: I'm a total n00b. I'm afraid I permanently wrecked my phone and I want to know if I can get it back to normal again.
Here is a step by step of what I think happened:
I tried flashing CyanogenMod 10.1 by using the ClockWork ROM Manager. I went to the Download ROM section of ROM Manager and found Cyanogen 10.1. It gave me the prompt "Backup existing ROM" and "Wipe Data and Cache," and I selected both. My phone started downloading the ROM. After it finished downloading the recovery menu popped up and I pressed Reboot System Now which I think was my first mistake.
It rebooted into Samsung's TouchWiz, not CyanogenMod, and asked me to sign into my Google account, which I did. I knew I had made a mistake so I went back to the ClockWork Recovery menu to start over. I made a backup of my ROM (which at this point was not even useful due to my first attempt), wiped the data/Factory Reset, wiped the cache, and wiped the Dalvik Cache. Then I tried to install the CyanogenMod ROM by going to "choose zip from sd card," however I couldn't find any ROM saved! I then tried to restore from a safe point, but no files could be found to restore from. At this point I panicked and hit "reboot system now" not knowing what it would do.
It rebooted into TouchWiz again, except this time with zero of my contacts, apps, anything. And it kept freezing every couple of seconds. I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes.
At this point I just want to get out of the jam I created and hopefully get some files back, especially the photos I have saved. Can anyone help me?
ps sorry for the long post
Well the good news is that as long as your phone is booting all the way into ANY OS, you're doing okay. Here at XDA, the ROM MANAGER method is frowned upon. From this point, your best (safest) bet is a clean slate, and I think that the best way for you to get there is to ODIN to stock touchwiz jellybean 4.1.2 (UCMD8) -then start the root - ROM process over again.
Odin 1.85 or 3.07 will both work
the UCMD8 firmware can be found in creepyncrawly's download repository
---------- Post added at 07:35 AM ---------- Previous post was at 07:23 AM ----------
gschmutz said:
...I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes...
Click to expand...
Click to collapse
What you describe here indicates that you booted into download mode, not recovery. Although it seems as though the phone is actively downloading something, it's just entered a ready-to-receive mode until you actively tell ODIN to send data (from a PC).
the keypress to get into download mode or recovery:
download mode: usb cable PLUGGED IN; vol- & vol+ & power --> until the prompt appears, then release and follow the instructions on screen
recovery: usb cable UNPLUGGED; vol- & vol+ & power --> until bootlogo appears, then release, and the phone should continue to boot into recovery.
---------- Post added at 07:43 AM ---------- Previous post was at 07:35 AM ----------
Once you're comfotably back to stock, this is the easiest way to get from stock to custom recovery on the i777:
Framaroot <-- tool to establish root-access to the device
Mobile Odin Lite <-- tool that uses root-access to install...
Custom Kernel <-- a custom kernel (there are many available) installed primarily to provide cwm recovery, but are also commonly used to:
-install a different ROM
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different kernel
-flash cleanup scripts
-and many many other things
The ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.
This guide will walk you through the steps, but read through the thread carefully to be sure that you understand everything before leaping.
-happy flashing
Great thank you so much! I will try to flash Jelly Bean when I get home from work. You lifted a weight from my chest.
Here's another update before I go any further. Late last night my phone stopped its bootloader cycle and seemed to be stably running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
gschmutz said:
...running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
Click to expand...
Click to collapse
probably not, I'm glad to hear that things have stabilised.
From here, my strongest recommendation is that whenever you flash firmware, do some house-cleaning:
-either run a rom-wipe script before-hand
OR (at least)
-factory reset
-format /system
Hi,
My phone boots to TWRP recovery only. I can boot into TWRP recovery, flush any ROM and set it up but after reboot my phone is not coming up.
It boots to the Samsung logo with BLACKSTAR BLACKJELLY ROM or to the AOKP logo with [ROM][4.3.1]*10/24 update* AOKP for SGH-I717 [The Family/AllianceROM]
Any help?
ursusca said:
Hi,
My phone boots to TWRP recovery only. I can boot into TWRP recovery, flush any ROM and set it up but after reboot my phone is not coming up.
It boots to the Samsung logo with BLACKSTAR BLACKJELLY ROM or to the AOKP logo with [ROM][4.3.1]*10/24 update* AOKP for SGH-I717 [The Family/AllianceROM]
Any help?
Click to expand...
Click to collapse
I got similar problem with beanstalk 4.3.
CWM and TWRP were tried to make backups, and every time of rebooting need a fully wipe and restore.
Even when a rom failed to boot, backup, factory reset and restore will make it bootable once.
Any idea?
---------- Post added at 05:03 PM ---------- Previous post was at 04:28 PM ----------
Not knowing the reason, but I tried to the oldest TWRP I can found (2.2) and it worked well.
First restore with 2.6 then flash 2.2, and after another cycle of backup and restoring, without booting up yet, boot up at last and it works seamlessly with rebooting. Don't know if I can flash back to 2.6 but no need to bother again. 2.2 is just as good, for me.
Hope it help.
hotgly said:
I got similar problem with beanstalk 4.3.
CWM and TWRP were tried to make backups, and every time of rebooting need a fully wipe and restore.
Even when a rom failed to boot, backup, factory reset and restore will make it bootable once.
Any idea?
---------- Post added at 05:03 PM ---------- Previous post was at 04:28 PM ----------
Not knowing the reason, but I tried to the oldest TWRP I can found (2.2) and it worked well.
First restore with 2.6 then flash 2.2, and after another cycle of backup and restoring, without booting up yet, boot up at last and it works seamlessly with rebooting. Don't know if I can flash back to 2.6 but no need to bother again. 2.2 is just as good, for me.
Hope it help.
Click to expand...
Click to collapse
Thank You, Man!!! It helped I've just downloaded the 2.2 viersion from here http://goo.im/devs/OpenRecovery/sgh-i717, flashed it and reinstalled BLACKSTAR
Thank you!! I have been having this same issue, and couldn't figure it out for the past few days. AT&T Samsung SGH-i717.
I started with TWRP 2.6.3.0 and using ROM BeanStalk-4.3.1009-20131015-quincyatt.zip (from thread [Rom][JellyBean][4.2/4.3][4.4 Apha Preview][PAC kernel]).
I used ODIN3.07 to get TWRP 2.6.3.0 set up, then did backups, wiped, and installed 4.3. It would run FLAWLESSLY, until it was powered down, or rebooted, at which point I would get the initial Samsung pop, then black screen. This was happening with 4.3 as well as the backup from stock 4.1.2 (I think).
TWRP files:
http://goo.im/devs/OpenRecovery/sgh-i717
Started with:
openrecovery-twrp-2.6.3.0-quincyatt.img.tar
Downgraded to:
openrecovery-twrp-2.2-sgh-i717-signed.zip
In case anyone is confused, as I was initially..... here is what I did to get it to work....
1. From TWRP 2.6.3.0, wipe & restore backup of 4.3, then shut down.
2. Boot to TWRP, install openrecovery-twrp-2.2-sgh-i717-signed.zip from within TWP, shut down again.
3. Boot to TWRP again, should be at 2.2 now, do a backup of current install.
4. DO NOT REBOOT OR POWER DOWN
5. Restore the back up you JUST MADE
6. Reboot
So far so good, over a dozen test reboots and power offs, no issues yet.
3 new members, helping each other, help themselves.
this is great, some folks who are not afraid to read and the confidence to experiment.
good job to all 3 of you and an official thanks to each by using the thanks button at the bottom left of each post of that person
welcome to all
ursusca said:
Hi,
My phone boots to TWRP recovery only. I can boot into TWRP recovery, flush any ROM and set it up but after reboot my phone is not coming up.
It boots to the Samsung logo with BLACKSTAR BLACKJELLY ROM or to the AOKP logo with [ROM][4.3.1]*10/24 update* AOKP for SGH-I717 [The Family/AllianceROM]
Any help?
Click to expand...
Click to collapse
okay so this is a very old post but i guess i found a working solution for this!
i have Galaxy A7 (SM-A700FD) 5.0.2
in basic terms:
-u need to remove TWRP recovery from your phone totally.
-i Flashed stock android recovery (well i got it by experimenting, as i rooted my phone again by ODIN it replaced the TWRP recovery with android recovery(turn off Auto-Reboot))
-you will be stuck in boot loop mode (stuck with the logo- good news is you are out of TWRP recovery boot loop)
-you have to get to boot loader anyhow (either by adb commands or vol down, home, Power key pressed all together)
-Flash TWRP recovery again using ODIN (turn of Auto-Reboot)
-hold the power key which will try to restart the phone.
-still it is boot loop mode.
-enter Boot loader (pressing Power key, Volume down, home- all three keys together or by adb commands)
-enter TWRP recovery (pressing Power key, Volume up, Home key- all three keys together or by adb commands)
-Restore your backup
-and you are good to go
hotgly said:
I got similar problem with beanstalk 4.3.
CWM and TWRP were tried to make backups, and every time of rebooting need a fully wipe and restore.
Even when a rom failed to boot, backup, factory reset and restore will make it bootable once.
Any idea?
---------- Post added at 05:03 PM ---------- Previous post was at 04:28 PM ----------
Not knowing the reason, but I tried to the oldest TWRP I can found (2.2) and it worked well.
First restore with 2.6 then flash 2.2, and after another cycle of backup and restoring, without booting up yet, boot up at last and it works seamlessly with rebooting. Don't know if I can flash back to 2.6 but no need to bother again. 2.2 is just as good, for me.
Hope it help.
Click to expand...
Click to collapse
Thank you very much for this tip! :laugh: Simply went to the official twrp .me site, chose the first img, and flashed it in the way described there. Phone booted fully now.
Tried flashing SR KK Rom.. Was on AOKP 4.4.4 but was super buggy.
Flashed without issue, but stuck in red verizon bootup screen. I skipped flashing via ODIN the 4.3 firmware. I resorted back to stored TWRP backup, all good and usable.
To try and fix, i changed from TWRP to Philz per recommendation int he thread. Then reflashed. No go still. Tried to go back to TWRP backup, but Philz doesnt like it, and now i cant get to my phone via USB to reinstall TWRP.
I have AOKP still on my phnoe, so tried to reflash, but no dice.
I'm stuck with an unusable phone, and it looks like NO way to fix it.
I can access phone and flash via ODIN. But, i can not see phone via USB (in order to copy over ZIPs). I can mount my external SD, but then when i unmount, data goes away.
So screwed - need help so bad.
Rom that started it all:
http://forum.xda-developers.com/showthread.php?t=2582313
Okay, used ADB push to get TWRP to the phone. That worked... Restored backup, but because of flashing the 4.3 firmware, lost root per TWRP
However, when i boot now, it just sits at "Samsung Galaxy Note II" screen. Doesnt go any further. EFf me.
EDIT: I see why.. backup restore failed. arghhhhhhhhhhhh
I cant flash anything. Everything fails.
Bump
Stop trying to restore backups and wipe everything in twrp and then flash a clean a rom of your choice.
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
DatacomGuy said:
Bump
Click to expand...
Click to collapse
No need to bump your thread. We have small, but talented group of ppl that can help you but bumping because of no response instantly isn't good taste.
I've just unlocked the bootload and flashed TWRP on to my moto G4 plus and went to flash magisk after to get root. After i flashed it I rebooted my phone but it wouldn't boot into the system and wouldn't even show the boot animation. I tried to use the Stock recovery I made after putting TWRP on my phone but it kept on saying error 255. This lead me to sideload lineage OS onto the phone which work. However when I tried to boot into android it did the same thing again. I have a feeling that something is wrong with the /boot partition as when i go to recover using my stock img there is only a system box.
Any help is appreciated
Welcome to XDA,
and did you try reflashing stock firmware?
That will always work.
Hello there. I'm having a major issue with flashing magisk right now. So all was fine. Then today, I flashed OxygenOS open beta 19 on my OnePlus 5T. I then tried flashing Magisk. What's really weird is it boots, but as soon as it does, I get a split second of enter pin, before my phone just says shutting down before it does just that. I've tried the uninstaller then reinstalling it with no luck. I'd really like to stay rooted without wiping data, but I can live without root. Does anyone know how I could fix this problem? Thanks so much in advance.
---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------
Oh very sorry, I mean open beta 29.