I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer
Hi folks, mid last week I woke up to a non responsive Galaxy S2. It's been happily running stock Vodafone ICS for over a year, and somehow spontaneously went soft brick on me. Gets stuck at logo screen or goes into boot loop.
Download mode is accessible. I can flash through Odin (1.85 and 3.09) and it reports success. I have successfully put CWM (various versions) on it can can boot into them fine.
Recovery mode is also accessible and appears to be working fine. I can access external SD card no problem.
Attempting to flash through zip from external SD aborts with Mode 7, reporting bad zip or unable to read source file. I have tried removing asserts from install script (educated myself to the risks and made sure the ROM was correct!!) and multiple versions of CM (10.1.3 stable, 10.2 nightly) and multiple versions of CWM recovery (6.0.2.9 is what I've been using mostly, as recommended by CM guide)
Tried running GS2ROMNukeV2.12.zip which reported successful wipe, then attempted zip install from SD with same result (aborted mode 7). Repeated wipe and attempted stock (I9100TDVLSK_I9100THUTLSD_I9100TDVLS3_HOME.tar) from flash through Odin. Reported success, phone booted into recover and applied KOR CSC successfully, then reboot and still stuck at logo screen/boot loop.
I have attempted the fix in http://forum.xda-developers.com/showthread.php?t=1449771 as best I could wish the resources I could find, but it's hard to follow to the letter with the links broken!!!
I have not tried repartition with PIT as I'm not sure where to get an appropriate PIT file. Advice on this appreciated!
I want to make this clear because people seem to not want to believe it: I did not soft brick my phone flashing it. My best theory at this point is some kind of memory corruption or hardware failure that's causing a boot loop. Any help or suggestions would be appreciated. This week I will probably take it in to a repair shop and hope for the best, but tomorrow is a public holiday and I've got nothing to lose by trying any more suggestions.
Kaine said:
Mode 7
Click to expand...
Click to collapse
If memory serves me right this is due to an old version of Recovery, i had the same thing, updated recovery and it flashed zip fine. just as you know. :fingers-crossed:
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
I have a SGP311 and started to root by following the guide at http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377. Works prefectly! Unlocked using the guide at http://wiki.cyanogenmod.org/w/Install_for_pollux_windy which also worked.
But once I flashed the boot.img it start bootlooping. The option "backup and restore" isn't visable in the recovery mode. I can't find install from zip either. I can install from external storage, but that doesn't work either.
I managed to get in to the tablet again by replacing the boot.img to another boot.img, but that doesn't help me to get CyanogenMod 12 though.
I'm new to this, so I might have made something wrong here, please tell me if so
I have a little problem of my own also when I try to unlock the bootloader following the Sony web page everything looks ok but when I boot the tab it's stuck in a bootloop at the xperia logo.....
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
skift said:
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
Click to expand...
Click to collapse
it seems that you just haven't unlocked you bootloader or using boot.img with broken recovery.
The bootloader was unlocked fine. Went through Sony to get the code and unlock it. I was even able to flash Previously using flashtool. I re ran the flashing to get back to where I was and tried it again and it seemed to work. The only way I could reboot was to hold power and volume up till I got the 3 flashing lights. Then I could get into recovery.
Hello!
Yesterday, after succesfuly installing the modified VBmeta image and flashing TWRP, i ended up wiping my OS accidentaly.
Trying to take advantage of the situtation, i searched some custom roms to install, and found the Lineage OS 18.0 Thread on the Galaxy a10 custom roms. I wiped the required caches, and flashed the OS, Magisk and Gapps (NikGapps) in this order.
However, my phone won't boot anymore. It shows the first samsung screen (warning me that i'm not using a official firmware), then the screen warning that the bootloader is unlocked, and then the phone just goes black screen indefinitely. I can force restart with power + volume down, but can't access recovery or download mode by any means, as it just goes black when i try. PC won't recognize the phone as well, giving me no way to install scatter firmware of any sorts.
Is there anyway to save my phone?
Hello! If you still have issues, I have the same phone. The problem was the custom rom I was trying to install (LineageOS). Crdroid booted up just fine.