Hi, I don't know what to do anymore, I can't flash any rom because phone reboots by itself when im in recovery, after 15-20 second it restarts, I tried to flash stock rom using odin but same thing happens, when new stock rom booted when I come to that part where I need to setup a langugage it shuts off all by itself and reboot, I can't charge him because same thing happens and I have about 30% battery left so don't have much time to fix this problem, did anyone had that kind of the problem?
after flashing new rom, go to recovery and do factory reset or wipe all data. and try new charger
Sent from my E6653 using Tapatalk
what about this, it says there is some bug and phone turn off in the middle of backup or when I'm installing new rom? I think that the same thing is happening to me, I tried fixed recovery but no luck, phone is still turning off after 20 seconds in recovery, I would like to install cm 11 but as soon as installation starts phone turns off in recovery
i think this could be some problem with hardware, i have galaxy s plus for 6 years, and few days ago i played it, and flashed pacman rom 4.2.2, all i had is some problems with newer twrp recovery, but after i flashed twrp 2.2.2.1 and everything was fine later.
gs+ was one of my favorite android phone, so easy to flash custom roms.
Sent from my E6653 using Tapatalk
everything was ok 4 years until I flashed cm 12, it was slow and I wanted to flash cm 11 but when I tried to flash it after 30% installation phone shut off, from then I can't flash nothing normally
in order to flash cm 12 I had to format data partition to ext4, maybe that is the problem with restarting?
it could be, I dont have that phone anymore, my sister's son is using this phone right know as a toy
Sent from my E6653 using Tapatalk
Related
I think my daughters tablet has been soft bricked but im unsure of how to fix it.
It was running ICS i believe. We had two of the tablets(both bought at exactly the same time). I went to update them both and the first one downloaded and installed an update absolutely fine without any issues. The second one (the one in question) downloaded it but wasnt able to install the update. It just failed and reset the clock every time i tried.
I decided to reset it completely and was then going to flash the latest jelly official rom( onto it which i found here
http://forum.xda-developers.com/showthread.php?t=1704668
So i booted into recovery and wiped it and did a factory reset but then the thing just got stuck in a continuous boot loop.
So i wiped it again and now everytime it boots it just boots into recovery unless i specifically hold power and volume up to boot into download mode.
So i thought that was odd but i would just go ahead and put the rom on and maybe that would fix the issue. So i used odin and the jelly bean rom shown in that thread above
P5113UECLK7 (4.1.1) - Cellular south November 2012 (Official)
It all went fine it passed and i thought it would now work. I had to unplug the cable and it turn the thing on as it just started charging after completing instead of restarting and it did come up with a status loading bar as if it was going to do something but then it just turns itself off again after a few seconds and again when you try to turn it on it just goes straight into recovery.
The tablet is charged up to 100% but i cant get it to do anything else.
I tried using ICS instead P5113UEBLI1 (4.0.4) - Singapore September 2012 (Official)
but still the same. Not sure what else to do? Any suggestions would be much appreciated.
In Odin did you have the auto reboot option selected? I'm asking because I was in the situation as you..I flashed wrong cm10 ROM and it was just in a boot loop.. I let the battery run out and then I charged it while it was off. I downloaded the stock jb firmware(mine came with jb preinstalled) and flashed with only auto reboot checked nothing else and it worked..
Sent from my GT-P5110 using xda app-developers app
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
Hi everyone. My Nexus 5 was running good until some days ago. Then it started bootlooping. It wasn't turning on , so I unlocked the bootloader and flashed the stock image. Nothing happened,so I flashed stock KitKat rom and after 2-3 hours it booted and lasted 30 minutes. I mean, after thirty minutes, it stucked to Google screen again. Then I somehow managed to flash lineage 14 and it booted again successfully.But as you all know that GOD Hates me a lot, after 2-3 hours it started the same drama again. And that's the story, I tried lineage,RR,aokp ... everything flashed successfully but doesn't last more than 4-5 hours or even less.But If I try stock, that never boots.
I just can't understand where is the problem.The power button is ok, I installed a kernel and underclocked it to see if there is problem with processor. No luck. This thing can boot ,but can't hold on that very long.
Another thing,when it start looping, it forget about TWRP too. I have to flash stock first,then install TWRP,then lineage /RR.
Can anybody say where is the problem??
I have used some nokias, samsung, even some Chinese phones,none of my phones died themselves, it was my only Google/LG and I faced this.
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
audit13 said:
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
Click to expand...
Click to collapse
What can I do?? Is it recoverable with pertitioning softwares or I should think about buying a grave plot for it?
Anyway,thanks a lot, man. You are the only one who atleast tried to help me.
Please help me out as I messed my phone up real bad recently and I need to fix it as soon as I can as I have interviews right now and need to be updated with them.
So here's what I did:
I was using Pixel Experience ROM on Android 12, with OrangeFox recovery, it was working fine with no major issues.
I really wanted to try out Android 13 though it's still in Beta but I have heard good things about it, specially the one by Project Elixir.
But since I was already using Pixel Experience and loved the ROM so much, I decided to be on the safer side and look if they have a Android 13 ROM for my phone.
That's where the story began, I mistook the Redmi Note 7 forum (lavender) as Redmi Note 7 Pro forum, I forgot how they were two separate devices.
So I flashed the Redmi Note 7 recovery on my phone and it it didn't boot into recovery when I tried it to, then I downloaded the original (correct one) from OrangeFox's official site and flashed it after which the recovery works. But then as I tried installing the new ROM, my adb sideload kept getting stuck at "Starting ADB Sideload feature" and I couldn't make it work, so I flashed the new OS from my sdcard. It was all fine, I set it up and was loving the experience until I plugged it out of the charger. After a few minutes of plugging it out of the charger, it literally started rebooting and it restarts just in the middle of the boot animation. And when I manually power it on by pressing and holding the power button, it displays that It has no charge left.
I tried flashing quite a few other ROMs too, even Android 12 and 13 both, and at a point for some reason it also showed "system has been destroyed. press the power button to shut down" while booting into recovery but it went away once I re-flashed the recovery, and after no luck, I flashed MIUI but the same thing still persists.
I read in a few forums that it might be a battery issue which I too thought at first but the fact that it happened exactly after I flashed the wrong recovery bothers me. I thought installing the stock MIUI rom through fastboot would solve it by replacing every corrupted files and partitions but the issue seems to persist.
What might have been the issue and what can I do to fix it, and can flashing a wrong recovery cause this even if I have flashed the right one just after that?
Hi guys I used PixelExperience 11 rom for 4-5 months last week phone freezed while charging I force rebooted it, after reboot, it freezed again I waited for the respond but phone turned off and not responded to anything until (charging, odin mode etc) phone charge finished and I booted with stock rom same thing happened again today. now I will wait again but I don't want this to happen again. what do you think is the problem? (so sorry for bad englsıh)
Note: this problem not happens on OrangeFox or TWRP recovery, only on system
please guys help
Try using some stable rom, kernel and recovery. Also while installing custom rom clear the system and other data neatly.