[Q] Glide wont reboot stright into Recovery - Samsung Captivate Glide

I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve

This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)

Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve

Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk

gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.

Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219

Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.

If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.

Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...

There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.

Related

Telus s2x wont enter download mode, or boot, or cwm

I FOLLOWED ALL TUTORIALS BUT I AM STILL STUCK, PLEASE I NEED SOME HELP
So here is the story:
I had Jedi Mind Trick X, but i wanted to upgrade to CM10, and they said that the best was to get CWM Recovery 6, so i open up the ROM Manager app, and clicked on Flash CWM, everything was working fine untill the app asked for root rights, i granted it and then the app frozze. So i tried it again, and same results. So i figured out i had to see if it has updated (the cwm recovery), so i enter recovery mode, and then i can see there that it was updated (this i think, was the bad choice).
And so i start the process of flashing CM10 following the instructions, i already had a nandroid backup so i skipped that step and go right into the wipe data / factory reset. When i was on that screen the app froze, after waiting for a while that it was still froze, i shut down my device and started up again. Of course the phone didnt boot.
So at this point i had a phone that didnt boot, and a recovery that wasnt full installed (so it didnt work either). So i thinked ODIN might be the solution.
i flashed trought odin CWM 5 again and Telus stock ROM.
BUT now, the phone wont enter download mode (shuts downs), and it wont boot either. Althought, the phone DID boot once so i was happy, but it didnt work, the phone shut down by himself.
So now i cant enter recovery mode, download mode, neither boot. every time it enters a mode, it shuts down. so i need gelp
Im thinking of attaching a video of my situation.
Im sory for my english, im from Argentina.
Thanks in advance.
im starting to think tha might be a hardware problem of the power button

[Q] HELP!!!! Phone wont boot

I just tried to load a new rom on to my phone. I used twrp to do a factory reset and now it wont turn on, at all. I wont even get to the splash screen. I've tried removing the battery and then turning on, no luck. I've also tried holding the keys to get into recovery mode, nothing works!!
Please tell me its not a brick!
which rom where you running
which rom are you trying to load
kingskater said:
I just tried to load a new rom on to my phone. I used twrp to do a factory reset and now it wont turn on, at all. I wont even get to the splash screen. I've tried removing the battery and then turning on, no luck. I've also tried holding the keys to get into recovery mode, nothing works!!
Please tell me its not a brick!
Click to expand...
Click to collapse
It really helps to know what ROM you were flashing, what method you used to flash, i/e ODIN flash then TWRP wipe, or TWRP zip install and wipe.
I would highly bet that you flashed an incompatible ROM, that was meant for another version of the S III, which would cause you to be in this current state. Which best case scenario you take it back to AT&T and tell them you were in the middle of using KIES to upgrade to the new OFFICIAL Jellybean, and your computer froze during the install, after which your phone never turned back on.
Second case scenario, you call up Samsung and get an RMA from them, wait 2-4 weeks and get your phone back, often times not having to pay the "fee" for repairing it.
Worst case scenario, you have a nice shiny new beer coaster. In which case you could mail to me and I could use it as such, as I am currently out of coasters.
Try using Odin to fix
1. Download Odin and stock ROM rooted
2. Put phone in Download mode (not recovery) by pressing and holding Vol Down + Home + Power
3. Open Odin on computer and load the ROM
4. Hit Start
Refer to the following thread for a more in-depth guide:
http://forum.xda-developers.com/showthread.php?t=1739426
I got it fixed. I had to pay some kid to JTAG repair it.

phone will not go into recovery mode

ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
probablecauz69 said:
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
Click to expand...
Click to collapse
Just press and hold volume down + power and once the blue letters " booting in recovery mode" show up let go you will be in recovery mode
rudyp9 said:
Just press and hold volume down + power and once the blue letters " booting in recovery mode" show up let go you will be in recovery mode
Click to expand...
Click to collapse
lol wow. don't know how that worked. every time before when i wanted to get into recovery i held it until it actually went into recovery. thanks:good:
My phone is verizon s4 sch-i545 when I try to boot up in recovery mode it shows booting in recovery but it just boots up normally .I wanted to do a factory reset but the factory reset just restarts my phone and when I try to get into recovery mode for a hard reset I cant boot into recovery mode. I don't know what to do
For recovery, try holding down the volume up, home and power button. Once the phone starts to boot, release the power button only. Keep pressing the volume up and home button. When you see the dead android, release all buttons.
Rahimwahid said:
My phone is verizon s4 sch-i545 when I try to boot up in recovery mode it shows booting in recovery but it just boots up normally .I wanted to do a factory reset but the factory reset just restarts my phone and when I try to get into recovery mode for a hard reset I cant boot into recovery mode. I don't know what to do
Click to expand...
Click to collapse
Odin stock firmware.
probablecauz69 said:
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
Click to expand...
Click to collapse
Try rooting your phone and then you may install flashify app and reflashed your recovery. For more info visit - youtu.be/dUb7oISR6wA
my video where I hv solves this problem

[Q] [P5210] As soon as it boots to Stock Recovery, it Reboots!

I've got a Galaxy Tab P5210 that's stuck in a constant boot loop. I flashed it with the correct stock firmware from SamMobile using Odin, but it fails to boot properly. It automatically boots to the stock recovery screen, but the problem is it will instantly reboot as soon as it reaches this screen. I see the dead android with the red triangle and exclamation point for just a second, and it instantly reboots. Is that normal? I don't think that's normal. From what I've been reading, this screen is supposed to stay there until you push the volume keys to bring up a menu, but it reboots so fast that I don't have a chance to even push anything.
I've tried flashing it with other recovery images. I tried using CWM, and it almost worked. With that, as soon as the tablet booted, I'd see the CWM splash screen, and it would instantly reboot. Similarly to how it's booting now but with stock recovery.
I'd like to point out that I've never messed with anything like this before. I work in a computer/small electronic repair shop and a customer brought it to me. She ended up getting into stock recovery and a friend of hers did some serious damage in there which prevented it from booting properly. Normally we don't mess with things like this but, with it being how it was, I figured there was no way I could make it even worse than it already is by working on it. I thought if I flashed the original stock firmware back to it, it would fix it, but that looks like a no-go since it's still booting the same way it was when she first brought it to me.
Is this thing completely broken or is there still hope for it?
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
M,
this firmware was always my goto for device recovery/restoration https://www.androidfilehost.com/?fid=23060877490005046
posted by user chpettit , flash with odin 3.07
m
OKAstro said:
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
Click to expand...
Click to collapse
Not interested in rooting, just wanna get the stock firmware back on. Maintaining data isn't a necessity, the customer just wants it back in working order. I tried using that firmware, but I had Auto-Reboot checked.
EDIT
Yeah, it's still doing the same thing. When I first boot it up post-firmware flash I see an Android with a loading bar underneath it, and then it reboots. When it boots again, I see the same Android and then it suddenly changes to the dead one with the red triangle. Maybe I'm just doing something wrong here with the button presses following the flash?
EDIT2
It looks to me like the stock recovery image is just broken, since the tablet just automatically reboots the instant it attempts to load it up. Flashing a new firmware replaces that though, so I don't know how or why it would even be corrupted. Odin reports no errors, so I don't know what's going on. And every guide I'm reading with fixing bootloops all say "go into stock recovery and clear the cache", but I can't even boot into stock recovery. It's like it's not even there. And I know it's not a power button issue causing it to shut down, I can power the device off fully with it, and it will stay off until I press it again. I'm banging my head against the desk here.
What if you flashed a TWRP recovery in Odin. Then if that's successful, boot into recovery and wipe/format everything except ext SD, Then try the ODIN flash again with filr your stock tar
I'm having the same problem and that didn't work for me. It shows the twrp splash screen and reboots. I'm looking for the .pit file it has to be the recovery partition right?
Sent from my LG-D851 using Tapatalk

Possible hardbrick of s4 sgh m919 after twrp restore

Hi, I have a rooted s4 sgh m919. I am running twrp custom recovery. So I just flashed cm 13 nightly build for the s4 and it worked and ran through boot up and everything. Then I realized that I had stupidly forgotten to backup my apps(I though I had but it was a twrp backup). So I returned to recovery mode using adb because my up volume buttons dont work(biggest problem for me now) and used twrp restore of a backup I made before the new rom. Now I know that my twrp backups work because I have successfully restored before but that was using the same rom, this is the first time flashing a new rom. Since I am a noob, I didn't know that I have to factory reset and delvik cache wipe before I restored my backup since they were different roms. Now after booting up and getting past the boot animations it goes straight to a black screen with a bunch of "Unfortunately ______has stopped" for just about every single app I have including system apps and UI. I can boot into the download mode prompt(where it says volume up to download mode, down to reboot) but since my volume up button doesn't I cant boot into recovery or download and do a factory reset. I can boot into safe mode but I still get the same black screen with a bunch of "Unfortunately ______has stopped". I also can't do it through adb since I have no access to phone settings and when I connect to the computer, the computer make a sound recognizing something was plugged in but won't show my phone in the libraries and when I use "adb devices" my phone isn't there. I stored my backup onto my ext sd card if that helps. Is there anyway to get into recovery mode or even just do a factory reset without using volume buttons or the computer? And has anyone else had this problem and if so what is it called(hard brick, soft brick, bootloop.....). Thanks!
You need to fix your up-vol button.
There is also a special micro USB loopback plug which I think can make the device boot into a special firmware loader mode. Then you would use heimdall/odin to replace the firmware, but I have never done that.
As for what to call the problem, I say "dumb user with broken hardware". You knew that your up-vol button was broken and what would happen if you could not get into recovery. Now that it has happened you want a magical fix instead of doing what you already know you need to do. Sorry for honesty.
1st- buy a usb jigg, they go for less than $5 amazon, eBay etc.
2nd - while phone is powered off use the USB jigg to put it into download mode
3rd- use Odin to flash the latest ok3 firmware.
4th - use Odin again to flash cf auto root. (No need to check if it has root the recovery you flash should be able to root it)
5th- use Odin again to flash Philz touch cwm recovery.twrp causes lots of problems when flashing. Philz recovery has been flawless.
6th- flash any rom of your choice. If you can't get into recovery theres an app called quickboot that can put you in recovery as long as you're rooted.

Categories

Resources