I think i might have wrecked my P5110!
I rooted it to Cyanogen mod about 6 month ago to CM10.1.1 and that was great.
I had been using the built in updater to get the latest Cyanogen firmware without any problem. Decided to try a CM 10.2 nightly but was having big problems with it draining battery, crashing and rebooting for no apparent reason.
No problems thinks I, just unwind it to an older version of CM from the built in Cyanogen Mod Updater. I selected 10.1.3 RC2, and left it be.
Came back to it some time later to find the old logo spinning there. Figured it was still running and left it some more, and some more, and some more and it just kept spinning. I guess its knackered. I DID NOT wipe the cache and data as i was doing it from within Cyanogen so naively thought it would work okay.
Okay thinks I, go into recovery, wipe the cache. No dice. Try as i may i can NOT get ClockWorkRecovery to come up, only ODIN.
Talk about fools rush in. Simple thinks I, reinstall CWM from ODIN, go back into CWM, wipe the cache, see if that works.
flashing goes smoothly, but try as i may i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Any suggestions for a next step. Had the worst day at work and really shouldn't have bothered touching the damn thing!
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Vannystick said:
Oh, I might well have spotted the problem
I thought I was flashing the CWM for P5110, but a closer inspection of the filename
GT-P5100_ClockworkMod-Recovery_6.0.1.0.tar
Shows quite clearly what i've done.
I'm guessing there is no coming back from this?
Click to expand...
Click to collapse
Flash stock firmware via pc odin this will solve your issues. ....
Sent from my GT-N7100 using XDA Premium 4 mobile app
Every time you flash with ANY ROM you need to wipe data or bootloop obviously will appear.
Vannystick said:
i can no longer get into ODIN or CWM, only into a never ending circle of Cyanogen bootup.
Click to expand...
Click to collapse
Even though your recovery may be screwed up, it's strange that you can't get to the download mode... So, what exactly happens if you force reboot by holding power for several seconds, and immediately after that hold power and Volume Up together while it's powering up?
When stuck in the CM boot up, pressing and holding the power button would force a shut down, but the tab would then instantly reboot.
Holding the volume up (or down, i was desperate) until the samsung logo appeared wouldn't get me to ODIN, it would go to the CM boot screen.
If i plugged it into the charger once in the CM splash, and powered down, it would take me to the charge screen. Pulling the plug would then turn it off, without it rebooting.
Initially this wouldn't work, but perhaps because i was being impatient. All the instructions i had read say that the volume button can be released once the samsung logo pops up, perhaps i've miss read. Ultimately i found (more by accident than anything), you need to keep the volume button pressed until the second time the samsung logo pops up, then it will enter ODIN.
I managed to download a a stock rom from SamMobile, and flash it in.
It still wouldn't boot though, until i went into recovery and wiped data/cache. It also then took rather a long time to boot back up, presumably unpacking various 'stuff', had me a little concerned, so i left it alone for a few hours and came back to find the first boot welcome screen.
Lesson to be learned, always wipe the cache/data before an update, even if the previous half dozen CM updates had been fine.
I think what actually screwed things up was going from a 10.2 beta BACK to a 10.1 RC ROM.
Oh well, its working happily again, and not falling over like on the 10.2 beta. And i dont need to buy a RIFF box!
Related
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
I plugged in my device and Kies said there was a firmware update. I let it go through it's paces and upon reboot, it just sits at a pulsating samsung logo.
I've tried reflashing a stock GB image using Odin. Even tried an ICS one. All of them result in the same pulsating samsung logo going nowhere.
What steps can I take from here?
Power + Vol Up
Select Wipe/Factory Reset
Cross your fingers...
Good Luck
I couldn't get recovery to come up before. But it did this time . Anyway, we're back in business. ICS is fantastic on this!
Hi people, I update my tab7+ 6210 to ICS everything was fine, but sometimes I got random reboots and today it suddenly turn off, I tried to turn on but nothing happens, so I plugged into charge but show no signs of life, I tried to enter stock recovery but accidentally enter download mode, Im screwed?, please I need some guidance. Thanks.
--------_______________________-----------
IT boot again, Im going to try enter recovery and do the wipes.
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
Hi there everyone, recently signed up on here as xda seems to be the holy grail when it comes to all thing smartphone.
I'm fairly new to these type of phones and recently was given an infuse 4g that was suffering a power button problem.
The power button problem has been resolved with a new one and the phone was working fine for 3 / 4 weeks.
One day the phone shut down by itself and entered the boot loop syndrome. Factory clearing it hasnt seemed to do anything to resolve the problem as it continued to reboot continuosly.
I came across the thread about gtg ultimate unbrick guide in the developers forum and this seemed like a good way to go, get the phone all the way back to stock and then work from there.
Kies installed and all drivers installed fine. downloaded the gtg unbrick pack and followed the instructions line for line. Odin reports everything passed, took about 2:59 to complete.
phone rebooted and continued to do boot loop so went into recovery as stated and wiped data and cache and rebooted again.
phone is still stuck in some sort of boot loop, but it gets to display the 1st of the setup android phone screens, then just as you get a chance to select next to go onto the next screen, the phone reboots.
Any one have any idea what could be going wrong or as im fairly new to this, is there anything im doing or not doing right that is causing this.
The phone is an at&t infuse.
regards
Trevor
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
tt33333 said:
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
Click to expand...
Click to collapse
I've already replaced the power button with a new one, but the technician i use did say he will remove the power button completely to see if it does the same, just to rule that out
Trev
just redone the gtg flash and it boots into the os (ver2.2.1) and then within about 5 seconds turns off and reboots
can the new on off switch be faulty......im not so sure as in recovery mode, i can leave it on that screen forever and it doesnt attempt to reboot
Tried the one click repair with hemdial or what its called, updating thisnpost via a moto defy mini so excuse any typos.. The hemdiaOl just seemed to meas it up further. So got baxk into downliad mode with odin and reflashed to gtg brick recovery. Not fixed, still booting but at least the screen is now viewable.
To recover one of these phones, is there like a definitive guide as to what to do to first prepare one of these phones for recovery, ie, first, flash to this with cwm and then clear data, cache, dalcik etc. like an idiots fuide, i feel i may need one
Regards
Trev
I've tried Carbon but that one wouldn't actually boot up, just shut my screen off and would shut itself off.
AospExtended ROM, is just sitting at these bouncing dots.
Ressurection Remix, sits at the boot screen of whatever that...logo is supposed to be.
I'm at my witts end here and about to smash this piece of junk. Nothing on this phone has ever worked right since I got it. Figured I'd fix it by getting rid of their trash UI and do custom roms but apparently it can't even do THAT right.
Upgrade your device to EMUI 8. Then flash one of the Treble ROMs.
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Spykez0129 said:
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Click to expand...
Click to collapse
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
SuperSwordSmasher said:
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
Click to expand...
Click to collapse
That's something I do automatically without thinking. That stuff was finicky back in the OG Droid days so I always do it like 3 times just to make sure.
Anything else that would cause it to get stuck at the booting up screen? I get passed the blue screen and the your device is insecure or whatever. Then it just goes into the fancy booting logo and just sits there. Never on any of the phones I've rooted over the past decade ever got stuck like this.
WOHOOO! I MADE PROGRESS!
My phone is now stuck in a never ending bootloop and can't seem to get into any recovery. Can't even shut the phone off because it just turns itself back on. Backwards progress is where it's AT!
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Spykez0129 said:
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Click to expand...
Click to collapse
What honor 8 model do you use? It should not be Bootlooping then, if there is no solution you can always go to stock.
You could flash twrp again, with fastboot
Boot with power + volume up to boot into twrp
Use dload method