I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
If someone here can help you, they will. But you might have better luck asking over at http://forum.xda-developers.com/galaxy-s4-att as this is the International S4 section.
Sorry, I didn't catch that. Thank you.
Just for the record, I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
Just a quick suggestion...
You just need to hold down both VOLUME buttons + POWER button + HOME key to REBOOT. No need to CANCEL, etc. This is how to reboot at any stage.
Related
A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?
The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.
I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf
You can't hold volume down and power button to enter recovery?
Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.
it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom
OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!
http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.
Thanks buddy. On my way to grab the files now
I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.
so this morning I tried to install xposed on PacMan 4.3. I installed it and it said to do a soft reboot.
after the soft reboot i am now stuck on the PacMan boot graphic.
I can't get into recovery any which way.
I have tried the power down to get into recovery and it just reboots.
I am now in download mode connected to my computer but want to know what to do get back into the ROM and if its possible to do a nandroid so I don't lose my texts/phone logs/app data.
You may be forced to go back to stock and start from scratch. If recovery isn't working then you can't really do much to fix the issue. What's the model?
ceredics said:
You may be forced to go back to stock and start from scratch. If recovery isn't working then you can't really do much to fix the issue. What's the model?
Click to expand...
Click to collapse
vs980
anyway to get into recovery via abd to backup info?
also why would xposed mess with recovery?
Getting into recovery will leave you with what options since your bootlooping? Wiping for a fresh install or trying to reboot for a another vicious cycle? Either way your going to lose texts app data and phone logs. Unless you have a backup your hiding from me? Lol
To get into recover
Try holding volume down + power*
Immediately when LG appears let go of both and ONLY hold onto power, should boot into option to factory reset*
Hit power button 3 times to continue, then itll load into recovery
Sent from my LG-VS980 using xda app-developers app
I got stuck in a bootloop last week as well and had to do a factory reset (on my Moto X). Good reminder to move my backups to my computer...
There was just an update (2.4.1) to the Xposed installer that says it "Fixed a bootloop which mainly occured on some x86 ROMs," so hopefully that fixes it.
I seem to be another victim of this issue. I was attempting to update my recovery (TWRP 2.6 installed) on my Verizon S4 via TWRP's app. It failed, so I figured I might try it from recovery. I attempted to boot into recovery, but it is stuck at the Samsung "custom" screen and the blue "RECOVERY BOOTING......" text is in the top left corner. I can leave the device alone for several minutes and it never goes into recovery. It does get very hot though, and occasionally it will reboot on its own. If I hook it up to my PC and then put in the battery, it will vibrate as if it is going to boot, then it vibrates again in 3 seconds and does this endlessly with nothing coming up on the screen. Without being able to get into recovery or have my desktop recognize the device, I'm not sure what to do. Any ideas before I chuck this brick?
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Strephon Alkhalikoi said:
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Click to expand...
Click to collapse
Ah ha, you are correct. I actually tried a variation of this (I think with volume up?) but it just attempted to go into recovery again. At the download screen I just told the phone to boot into the OS and all seems well. I'll look into updating TWRP via Odin and see if I have any joy, but at least I have a working phone again. Thanks for the help.:good:
When you update, do NOT try to use TWRP 2.8.5.0. It's bugged on the S4. Use 2.8.4.0 instead.
Thanks, good advice!
Looks like my recovery is toast. Doing some research, I never used Odin as my phone had the old MDK baseband. Sites tell me not to use Odin, so I followed the instructions on TWRP's site using Terminal Emulator and 2.8.4.0: http://teamw.in/project/twrp2/181 Everything seemed to go well, so I attempted to reboot into recovery, but now I get some warning/error about unauthorized software, turn off your phone and take it to Verizon, etc.
Sounds like I need to try again, but I'm not sure what my options are now.
I didn't even see you had a Verizon S4 until you mentioned it. Verizon encrypts the bootloader as a matter of course, and thus installing TWRP is not possible. You should however be able to restore the official firmware with Odin, and from there, follow the root guides at http://forum.xda-developers.com/galaxy-s4-verizon to get yourself back up and running.
mine get to the point where i select volume up, i see the android bot and message do not turn off target, and it shuts down. what do i do?
Hey guys,
i never flashed/rooted/modified my Samsung Galaxy S4 I9505 before. Sitting on my desk, my phone turned off suddenly. At the first moment i thought, that the battery is just empty. After i charged the phone and went away, i got back and saw, that it was rebooting (the whole time?)
As i said, i got never in contact with modding/flashing, so i had to read pretty much about these things. After several days of reading and trying i did this:
Tried to get into Recovery Mode with VOL Up and Power button to wipe - "recovery is not seandroid enforcing set warranty bit recovery" in blue, red and yellow.
Flashed several Stock ROMs by Sammobile. After every flash i flashed TWRP - no change.
I get easily into Download Mode to flash the Stock ROMs, no errors in Odin, didn't check autoboot and repartition
Yesterday i flashed I9505XXUFNA5 - Open Europe - KK 4.4.2 (four-pieced) sucessfully. Then i flashed TWRP and tried to get into Recovery Mode - same results, i thought. But after i put the phone on my desk to think about what to do next, TWRP Recovery Mode was starting. I was totally happy, but didnt want to do something wrong in my euphoria. So i put out the battery to read about what to do, allthough i knew i wanted to do a wipe. After i read i wanted to try it again - no chance! I couldnt get into recovery mode again. I waited, nothing happened. Tried it again and again.. and again. Then i flashed the Stock ROM again, flashed TWRP again - no change. Meanwhile did this 8 times again and i didnt get into recovery mode again. Thats absolutely illogical in my opinion.
Please help me to get out of this, i dont know what to do now... THANKS
Recovery is volume up, home, and power button?
audit13 said:
Recovery is volume up, home, and power button?
Click to expand...
Click to collapse
Yes, home is optional (as i read) but i press this 3 buttons. I pressed it in several variations, for example like one user here in xda: "right after it vibrates release the power button only, keep pressing the volume up and home buttons for another 5-10sec as Whosebat recommended..."
Home button is not necessary, just vol up / down + power button. I also have the same issue as you. I went to a GSM service earlier today and over there was another S4 with exactly the same issue. Looks like lifespan of our phone reached to an end?
http://forum.xda-developers.com/galaxy-s4/help/phone-stuck-boot-loop-flashing-stock-t3398068
alesu69 said:
Home button is not necessary, just vol up / down + power button. I also have the same issue as you. I went to a GSM service earlier today and over there was another S4 with exactly the same issue. Looks like lifespan of our phone reached to an end?
http://forum.xda-developers.com/galaxy-s4/help/phone-stuck-boot-loop-flashing-stock-t3398068
Click to expand...
Click to collapse
Just speculating, but: I didnt update to the firmware version, from which you couldnt get back to the earlier versions. The reason would be some safety reasons. I thought about a relation to that for a short period of time.
#push
harary said:
#push
Click to expand...
Click to collapse
I think "bump" is the word you're looking for
After you flash the stock ROM, does it actually boot into the stock recovery?
GDReaper said:
I think "bump" is the word you're looking for
After you flash the stock ROM, does it actually boot into the stock recovery?
Click to expand...
Click to collapse
No, i have never seen the stock recovery. I was 2 times in TWRP Recovery, but meanwhile i dont get there anymore. I have no clue why i get after doing exactly the same things into TWRP Recovery and 3 minutes later i dont get there anymore.
I came two times into TWRP with flashing I9505XXUFNA5 - Open Europe - KK 4.4.2, then TWRP 2.8.6.0.
With other Stock ROMs i got never into Recovery Mode.
Please help me
harary said:
No, i have never seen the stock recovery. I was 2 times in TWRP Recovery, but meanwhile i dont get there anymore. I have no clue why i get after doing exactly the same things into TWRP Recovery and 3 minutes later i dont get there anymore.
I came two times into TWRP with flashing I9505XXUFNA5 - Open Europe - KK 4.4.2, then TWRP 2.8.6.0.
With other Stock ROMs i got never into Recovery Mode.
Please help me
Click to expand...
Click to collapse
So stock recovery doesn't work either?
It's really weird.
Have you tried flashing TWRP using the app Flashify (requires root)?
GDReaper said:
So stock recovery doesn't work either?
It's really weird.
Have you tried flashing TWRP using the app Flashify (requires root)?
Click to expand...
Click to collapse
Unfortunately i cant start to install apps, because i am caught up in bootloop.
I tried to flash now a GT-I9505-Factory-Firmware-Full-Wipe-DBT with following files, but nothing changes except i get Warranty bit : kernel if i want to start normally without booting into recovery mode.
Hi, I'm new to everything so please bear with me.
I have a samsung note 3, I just tried to root it with kingoroot, and was successful. I then downloaded clockworkmod recovery. I also downloaded the new darklord rom, and a darklord kernel.
I booted in recover, flashed cache, data, etc (as per darklord instructions), 3 times, flashed ROM, flashed kernel. Then I rebooted. It just rebooted into the 'factory reset' version of samsung galaxy immediately., ie within 2 minutes. So I restarted the phone, this time it started going into a lengthier reboot/install. Again, approx 10 minutes later, back to the stock samsung os.
I rebooted once again, but then the phone just kept rebooted over and over on it's own. I tried the vol down, home and power button to get into odin, pressed vol down to 'cancel', but then back to the reboot loop. Went back to odin, pressed vol up to install, and it stayed stuck on the installing screen for greater than 15 minutes.
What can I do next? Holding the vol up and down button only brings it back to the recovery boot loop again.
edit:
A few things I've tried, with no success, after reading more threads:
Taken battery out for extended period of time (1.5hr) and then retried boot...
restart in 'odin mode' numerous times
vol down + home + power key while in odin mode
hold down these three buttons with battery out, while holding buttons down, insert battery
Why have you not flashed a stock rom through Odin??
JJEgan said:
Why have you not flashed a stock rom through Odin??
Click to expand...
Click to collapse
I'm not sure how to do so. Where is the option to flash anything? All that I can see is to either "cancel" (vol. down) or "start" (vol up)
edit: sorry misunderstood what you were saying -- I will try what you said
sdrtyh said:
I'm not sure how to do so. Where is the option to flash anything? All that I can see is to either "cancel" (vol. down) or "start" (vol up)
edit: sorry misunderstood what you were saying -- I will try what you said
Click to expand...
Click to collapse
flashed rom thru odin, said 'pass', rebooted phone, still the 'not seandroid' error, and then switches off, instead of reboot loop. I'm going to try to download a different stock rom -- dunno if that'll do anything... they take so long to download/access...you'd think it would be an easy access repository? A lot of paid download links, or restricted speed download links....
If your stuck on a BL reboot loop, there is a good chance you haven't turned OFF reactivation lock. With any Samsung Rooting adventure, turning off Samsung Reactivation Lock in Security Settings is a fundamental must. If you have forgotten to do this. You can...
A. Start again by reflashing stock firmware with Odin (when you setup your stock rom, just bypass logging in to samsung and you wont need to worry about a reactivation lock being present.
B. http://idlekernel.com Download just the bootloader file for your N9005, flash via BL field in Odin and this will bypass the reboot loop and you will save everything on your phone except your recovery which is easily reflashed back.
What i would do as well is flash a stock rom, when your in odin make sure you have auto reboot untick. Pull the battery for 30 secs and start your phone up then. When your phone restarts with the stock rom, you can update your phone through the regular system update or again go to odin and flash twrp 2.8.7.0 recovery tar file. Make sure all your new files to flash is the correct one for your phone.
Sent from my SM-n900p using XDA-Developers mobile app
thanks everyone -- i downloaded a different firmware upgrade and flashed it through odin -- successfully. I then tried to install the rom again, and similar problem - stuck on the 'samsung logo' screen... for up to 40 minutes.. restarted, same thing.. had to flash through odin again.
NOW the back button doesn't work..... didn't realize being a newb would complicate things so much.. :S
.. didn't realize being a newb would complicate things so much.. :S
Its a question of reading and understanding first .
,,successfully. I then tried to install the rom again, and similar problem - stuck on the 'samsung logo' screen,,,
You Factory Reset .
You make sure its a rom for your model and follow the instructions .
Flash the rom again through recovery .