Database Info

Bootloop Galaxy S+ with any Firmware

Hi everyone,
my colleague has a Galaxy S+ on Stock rom and when he pulled out his phone of his pocket it was boot looping. The blue animation and the big white S is looping all the time.
He has no root or no rom or whatever modification made.
From my experience of my GS2 I first installed FeaMod Recovery and deleted the dalvic cache and fixed permissions --> no change.
I made a factory reset --> no change
I installed several firmwares KGS, KGP, KP4 --> no change
I have no idea if I am doing something wrong..
I flashed via Multi Downloader and when flashing was done or almost done the phone rebooted as multi downloader said in status menu and the white Samsung Logo appears.
What to do next?
Nothing happened and phone didnt start so I turned off the phone and restarted which resulted in boot loop as mentioned in the beginning.
Am I doing something wrong?
Any other idea what do do?
How could I format the internal sdcard?
Via the recovery it cannot be mounted for whatever reason.

deepflash said:
Hi everyone,
my colleague has a Galaxy S+ on Stock rom and when he pulled out his phone of his pocket it was boot looping. The blue animation and the big white S is looping all the time.
He has no root or no rom or whatever modification made.
From my experience of my GS2 I first installed FeaMod Recovery and deleted the dalvic cache and fixed permissions --> no change.
I made a factory reset --> no change
I installed several firmwares KGS, KGP, KP4 --> no change
I have no idea if I am doing something wrong..
I flashed via Multi Downloader and when flashing was done or almost done the phone rebooted as multi downloader said in status menu and the white Samsung Logo appears.
What to do next?
Nothing happened and phone didnt start so I turned off the phone and restarted which resulted in boot loop as mentioned in the beginning.
Am I doing something wrong?
Any other idea what do do?
How could I format the internal sdcard?
Via the recovery it cannot be mounted for whatever reason.
Click to expand...
Click to collapse
So....
U've got FeaMod. Have u tryied mount as usb storage? computer should see two sd card.
If u can put phone in download mode u should try install by Odin 2.3.4 - 3 files rom? it should delete everything in phone
I flashed via Multi Downloader and when flashing was done or almost done the phone rebooted as multi downloader said in status menu and the white Samsung Logo appears.
What to do next?
Click to expand...
Click to collapse
How long do u wait? Phone should reboot after while up to 10minuts.
Maybe try on other computer? I had problems before on windows 7, then i tryied on XP and went smoothly....

mounting as usb storage does not work.
Any other possibility to format the internal sd card?
I waited several minutes and tried XP and Win7 with the same result.
When the phone reboots automatically when flashing, do I just have to wait?

deepflash said:
mounting as usb storage does not work.
Any other possibility to format the internal sd card?
I waited several minutes and tried XP and Win7 with the same result.
When the phone reboots automatically when flashing, do I just have to wait?
Click to expand...
Click to collapse
It should restart once and show android come out of box, then restart again.
Second restart is taking bit longer at flashing "big S" at screen.
I flashed my sgs+ today twice because i tryied install custom roms.
Unfortunately if thats not help u probably only service can help u due to damaged partition. System or internal sd
Before u send phone to service, flash 2.3.4, unroot and bring back stock recovery.
Oh, try to flash it again without sim card and external sd

After flashing only the Samsung Logo shows and nothing else happens.
I was flashing without sim and sdcard all the time.
Btw, I managed to format the internal sd after reflashing the feamod recovery but still the same result.
He will now return the phone. I flashed a stock firmware, I now do have to see how to remove the feamod recovery.
thanks for your help anyway

deepflash said:
After flashing only the Samsung Logo shows and nothing else happens.
I was flashing without sim and sdcard all the time.
Btw, I managed to format the internal sd after reflashing the feamod recovery but still the same result.
He will now return the phone. I flashed a stock firmware, I now do have to see how to remove the feamod recovery.
thanks for your help anyway
Click to expand...
Click to collapse
Flash 3 files rom by Odin. Should restore stock recovery. http://forum.xda-developers.com/showthread.php?t=1346245
Definitely 2.3.4 XXKP4 is 3 files rom but is rooted. Try 2.3.3 roms

[Q] [URGENT] Need Help For MY DEAD DEVICE

I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english

Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .

I don't know what my buddy did...

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So, I have years of experience rooting and flashing Samsung phones with minimal adb experience. My buddy from work asks me if I can try to fix his shield tab that he F'd up trying to flash a rom on. Come to find out he never unlocked the bootloader or flashed a recovery or rooted the dang thing, just tried to flash the rom over stock like a numbskull. We thought it was dead forever because the only thing that would mount or connect in adb was the side load through the stock recovery. So, I finally got it to connect to fastboot (don't ask me how, I don't know), unlocked the bootloader, and flashed twrp. Now it won't flash supersu in adb sideload, so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one? I have no idea which version bootloader, kernel, or os is, or was, on this device, I'm not familiar with any of the roms for it, and I'm not sure what prerequisites there may be for some of them....
Thanks for the help!

rom fiend said:
it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one?
Click to expand...
Click to collapse
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)

OverBit said:
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
Click to expand...
Click to collapse
I can't wipe them because they won't mount. It's as if the partitions were erased completely. Not like the partitions were wiped, but like they don't exist at all anymore...
What do you mean by changing the file format? Format of what?

rom fiend said:
What do you mean by changing the file format? Format of what?
Click to expand...
Click to collapse
TWRP, wipe ,Advanced wipe
If that doesn't work just try installing a rom, boot it
If that doesn't work try this

Tried all recovery options and tried flashing bliss 6.2 with no luck. It says that it flashes successfully but also shows some errors about not being able to mount the system and data partitions. Then when I try to reboot it gets stuck at the nvidia logo (this is the closest that I've gotten to booting a rom). I can provide pictures if you want. I'm going to try the steps that you linked to as soon as the files download.

[Completed] My phone only boots into Recovery mode. (CWM)

So recently I've taken my hand at attempting to install Cyanogen on my phone. But I believe something went wrong.
I installed CWM onto my phone and wiped my SD card clean. Then via ADB, I transferred the files required into my phone and installed the firmware. However, upon loading it, I ran into multiple errors so I decided to format the system/sdcard again and reinstalled it.
Now whenever my phone turns on, it just goes straight into recovery. I've attempted to use multiple ROM files to install onto my phone but nothing works. My phone is an LG Optimus G Pro ("e980") using CWM recovery if that helps. I'm honestly a little scared that I permanently damaged this phone. The only real thing I can accomplish is installing a ROM into the phone, so I know for a fact that if I can pass this loop, there's an OS waiting for me. :/

veez21 said:
You flashed the recovery as boot, you can flash your boot img or reflash the whole rom...
You should be able to boot properly
Click to expand...
Click to collapse
With the assistance of TWRP in a zip file, I was able to flash my outdated CWM away.
Thank you for the confirmation, was scared if I flashed a recovery in a recovery, I would of lost something.

Great that you solved your problem.

[HELP] Stuck on Recovery Bootloop after OTA Update (CM14.1) , can't access Fastboot

Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.

I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.

[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date

Same thing happened to me! Where did you get a copy of the stock recovery? Link?

resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.

Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.

corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse

resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!

First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.