Hello,
I have tried to install CM 9 and i tried 9 times and at the 10th i succeed but with cm 10.1 so i wanted try again and install CM 9.But after the usual procedure of installing stock rom,root and custom rom it was stuck on boot screen.I tried many times but is not working i have flashed stock recovery and i cant still get in recovery mode.I know if go to recovery mode i will succeed but i cant.
If you can't boot into recovery then bootloader is your last hope. Try volume down, home and power buttone - if it works then flash a stock ROM via odin to recover your phone.
If bootloader is not working then your phone is bricked, you can try the various fixes here in Q&A but it isn't certain.
boomboomer said:
If you can't boot into recovery then bootloader is your last hope. Try volume down, home and power buttone - if it works then flash a stock ROM via odin to recover your phone.
If bootloader is not working then your phone is bricked, you can try the various fixes here in Q&A but it isn't certain.
Click to expand...
Click to collapse
as i said i was flashing stock roms 9 times so i cant do nothing?
1. what phone do you have?
2. flash a stock rom via odin
Related
I've been trying to find an answer on this forum and on google but I cannot find anyone with a problem similar to mine.
All of a sudden after trying to update CWM, (failed), I cannot go into recovery anymore.
I know the button combinations and have previously done it before but now it just vibrates and displays the Samsung logo.
If I try and use an app to boot into recovery mode it soft bricks the phone I believe (does not boot and I have to get it into download mode to
flash the system.img).
Does this mean that I have no recovery?
Yes. It means you have no recovery. I would suggest flashing TWRP with Odin.
Sent from my SGH-I717D using xda premium
I tried to flash TWRP using Odin but after the Check status, Odin is crashing and force closes. I tried installing CWM but the progress bar seems like it is stuck on 0%.
I'm not quite sure how to fix this. I am trying to install CM10 but this is the first android I have had.
It's rooted but everything is stock. I am not sure if I need a custom kernel also.
Is your phone a Canadian version? There's an extra step needed when you flash a custom recovery.
It's just an American version
try this and flash cwm-touch-i717-120414.tar.md5 with odin if twrp does not work, then download the updated zip from twrp and flash that via recovery. unless u just want to keep cwm touch.
ODIN + CWM Touch or TWRP
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
Did you hold the button combinations when your phone is off for more than 4 seconds? If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom. Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
gsstudios said:
Did you hold the button combinations when your phone is off for more than 4 seconds?
Click to expand...
Click to collapse
Yes, I almost got blisters on my fingers, thats how often (and long) I tried it. Also released the power button but continued to hold vol-up+menu as soon as the boot screen showed up.
If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom.
Click to expand...
Click to collapse
Does sound a little crazy indeed, but it also makes sense to add such a feature (i.e. boot into recovery if rom isn't present). Any particular suggestion for a KitKat kernel or should I just pick one of those mentioned here?
Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
Click to expand...
Click to collapse
Nope, no recovery, ergo no factory reset (or is there another way with a softbricked phone?)
Anyway, that would delete the userdata from the phone as well (e.g. photos), correct? Or are they already gone due to my rom flashing etc.? Oh wait, there is this difference between internal memory and internal usb storage, right?
Update
So I could not decide which one of Kitkat Kernels mentioned here to take. But I tried flashing the CWM recovery files, both GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar and CWM-KitKatCompatible-i9100.tar, with Odin. Flashing went fine, but on boot I only see the bootlogo and then the screen went black.
Any suggestion on what other kernel I could try would be welcome.
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
summerchild said:
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
Click to expand...
Click to collapse
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash CM11 from the CWM, not through Odin).
dapperdanman said:
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash km from the CWM, not through Odin).
Click to expand...
Click to collapse
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
summerchild said:
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
Click to expand...
Click to collapse
I don't have a backup of the original ROM, but I can flash a stock ROM and that still gets stuck on the animated Samsung logo.
Anybody else with an idea?
im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
scarface195894 said:
im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
Click to expand...
Click to collapse
Pull battery let it sit for two minutes. Push menu button, volume down button, and power button at the same time boot into download mode. once there flash a fresh copy of your OS which ever version of KitKat your running. You lose all your personal data, but your beyond that now. Then here is link to my thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 enjoy !!!
uknow said:
Yeah ive said it a few times this should not be used
If youve bricked your phone you can get back into your phone by holding volume down menu botton and power botton at the same time when it pops up the warning screen to enter download mode hit cancel your phone will then boot up after your phone is on if you do not have a computer the way you fix the phone so you dont have to do this every time your phone is off you need mobile odin and a kitkat cwm.img.tar for our phone flash it and problem solved you can now boot into cwm recovery then if you want you can flash a twrp img zip through cwm or just keep cwm hope this helps
Ps if you Google mobile odin the dev gives it away on his xda mobile odin page
Click to expand...
Click to collapse
.............^^^^^^...........
stuck in recovery loop also
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
update-- i found an updated version of the philz tar file and installed it with odin and that got me out of the loop..just havent tried to get back into recovery yet...lol
Cat1970 said:
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
Click to expand...
Click to collapse
First, pull the battery for a minute then reinstall hold the power, menu, and volume down buttons at the same time and boot into download mode. The version of Phil'z CWM you flashed is to old for 4.4.4 NK4. Now download to your desktop the right Philz CWM recovery file (Phil'z_Touch_6.48.4-hlte.tar.md5 ) here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ there are two listed use the second one. Flash with odin and you should be good to go. Go to my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 for more info.
done exactly as you said and the same screen came up saying recovery is not seandroid enforcing and then it jumps to Philz Touch 6 so im assuming everything is right now...i really appreciate the help! tyvm
different rom
ok..i installed cyanogen rom..i also used titanium backup..i want to go back to where i was but i dont see titanium backup on there anymore..how do i revert back?
i guess i need to update my phone n900p (help)
my rooted note 3 was running 5.0 L so i tried flashing a custom recovery both TWR and CWM now its stuck in boot loop. i read all the post showing you how to get out the bootloop. how ever i still need to put a recovery on my phone are there any updated links for this with odin because i was using the odin 3.0 sorry odin 307
My S3 was working fine and then a few days ago it just shut off out of no where and now I can't boot into my OS. It will only boot into download mode so I tried a firmware flash through Odin and it was successful but I still can't boot up but now I can boot into stock recovery and download mode. Any suggestions on how to fix this?
JamesB3 said:
My S3 was working fine and then a few days ago it just shut off out of no where and now I can't boot into my OS. It will only boot into download mode so I tried a firmware flash through Odin and it was successful but I still can't boot up but now I can boot into stock recovery and download mode. Any suggestions on how to fix this?
Click to expand...
Click to collapse
what ROM you were using?.
Factory reset in recovery.
I can't remember exactly what ROM I had on it.
I'll try factory resetting later today to see if it works.
Hello everyone,
I own a samsung galaxy s2 gt-i9100 I've been using it for a long time. A few days ago i installed cynogenmod 13 marshmallow on it but faced some severe issues like dialler problems,battery drain,google play services not working. So, i switched it back to my previous rom i.e. cm 12.1 lollipop but my old twrp recovery got replaced by cynogenmod default recovery. Now some people who may have used it know that its very basic and does not has backup,restore, has bugs,does not flashes some zips or files that i wanted so i tried to replace it with twrp/cwm through rashr,flashify,rom manager,etc. But none of it worked, whenever I'd boot after flashing the twrp/cwm recovery it'll go back to the default cynogenmod recovery. Now, me not knowing what im doing stupidly downloaded mobile odin lite app then i downloaded the cwm kernel recovery kitkat compatible and installed via mobile odin lite. After that it got screwed, it won't just startup it'll just start and go into recovery i mean continuously! It was annoying, then i read an article on a forum to download any cm nightly or stable mod and flash it but i did a little bit of tweak of removing the recovery boot img file with twrp to get preinstalled twrp recovery but i gotta admit it was the last mistake possible. Now i sit here, with a bricked phone in my hand which is looping continuously only on the samsung logo. If anyone out there can assist me correctly it'll be a life saver for me. Thanks for reading this and please reply with a solution asap. Please! Im in danger!
can you get into download mode?
if yes you can download a stock firmware and flash but you will have to hope it will work, otherwise you will get stuck on nand write start which means the nand is stuffed/corrupted and then basically only a motherboard replacement will do the job, or you can try using another computer, reinstall usb drivers..
can you get into recovery mode?
if you can, you can flash a rom
The 'nand stuffed' assumption is a last resort, tried everything and nothing works assumption. There is *plenty* to try before assuming that the nand is 'stuffed'......
It sounds like (from your description) that you may have rendered recovery useless and inaccessible.
I've a feeling what you need to do is to go into download mode and Odin flash a firmware.
Even if it doesn't boot, you should have a recovery that you can flash PhilZ recovery from and then use that to flash a custom rom. Initially, I'd stay away from the MM builds and instead flash something KK or LP based as they're less 'volatile' and have a higher degree of stability than the MM roms.
http://i.imgur.com/rVnFwJM.jpg