As the thread title states...I was on 7.1 and downloaded/updated it to 7.2 Now the phone doesn't boot up and all I get is the Kernel Panic Upload Mode.
Anyway I can fix this? And if so, is there a way of doing it without completely formatting my phone and losing all my apps?
Oh and if it makes any difference I had to install that Siyah Kernel or whatever it was called to get out of the bootloop issue that I had with CM7.1. I'm thinking that that may be causing the problem....? But then again what do I know
wipe cache only.
valentinrascu said:
wipe cache only.
Click to expand...
Click to collapse
How? I've been trying [Power+Volume Up+Home] and it hasn't been doing anything. Can I do it through download mode somehow?
Had this problem when i flashed Lite'ning rom. Had to go into download and flash stock with odin. Took me a few tries to actually get the rom to work. As far as I know, that'd be your only option, seeing as recovery doesn't work for you.
take a deep breath and read, there is a very small chance of bricking your phone just so you know. Flash back original with Odin and start everything again
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/2011/10/samsung-galaxy-s2-firmwares-bell-canada.html[/url
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
nubreed000 said:
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
Click to expand...
Click to collapse
If you flashed stock, you should be fine just rebooting.
Its stuck on the boot screen. I tried just rebooting, then wiping/factory reset, then both wipes...reinstalled stock a few times and nothing worked each time. I'm suck on the Samsung Galaxy SII GT-I9100 screen
:-\...when I go into recovery, I get a ton of red messages/errors
I'm gonna try somethig other than stock firmware see if that helps.
edit Ok so I rooted the phone and it got past the first boot screen and now appears to be stuck on the "animated S" boot screen...progress!!
nubreed000 said:
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/...msung and their changes to Android framework.
Click to expand...
Click to collapse
Ok everything back to somewhat normal. Stock ROM didn't work but 2.3.6 did, so I'm on that. Now do I wanna go back to CM is the question...
Either way, thanks again for all the replies and helping me out with this. Greatly appreciated!
Related
I recently got a galaxy player 5 international with froyo. I rooted it with no problems, but when I tried to flash a kernel with cwm recovery it would get stuck in a boot loop unless i went into the cwm recovery mode. I noticed that the kernel I used, rumirand's r14, was based off of GB and thought that might be my problem. I tried updating my firmware to GB using WT Ho's custom rom, and now it just hangs on the samsung logo, but I can still get into cwm. I made sure to wipe both caches and wipe data before installing the rom. Is this fixable or have I turned it into an expensive paperweight?
Did you try a factory reset?
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Chris4evernoob said:
Did you try a factory reset?
Click to expand...
Click to collapse
Now or before installing the rom? I did a factory reset before installing, but I haven't done one since.
DZonikg said:
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Click to expand...
Click to collapse
I just flashed the R13 kernel, but I'm still in the same situation.
Instead of flashing a new kernel there should be factory reset option on the first set you have or in "mounts and storage"
I had this problem once and I managed to solve it flashing a full rom (like 2.3.5 rooted and with rj kernel). It seems some users are having problems when flashing only the kernel. After you solve the problem, flash back group rom.
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
jnmaster said:
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
Click to expand...
Click to collapse
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
WT Ho said:
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
Click to expand...
Click to collapse
No, I'm not able to get a response from the power button.
I used the ROM + kernel you posted http://forum.xda-developers.com/showthread.php?t=1446774
Hello all, could use some help here.
I'm trying to restore my Note to the factory ROM and I'm running into an issue.
Fyi, I had the latest Paranoid JB Rom from Oct 13.
I followed the proceedures outlined in the forums (used ODIN to restore the default "attstockrom") and after that restore the phone would loop rebooting into ATT rethink possible animation screen.
I found and downloaded the latest 4.04 rom for the phone (I717UCLF6) and rebooted. Now it just hangs at the "ATT Rethink possible" graphic (no animation, no loop).
Odin does see the device fine so I can reflash again with no problems if I need to. I'm thinking of trying the I717UCLA1 version from Jan to see if that works but I'm hoping I can get some better advice before I do something that might cause more permanent problems.
Any advice on how to get back to stock ICS (or even JB) and get the phone working again?
Thanks!
Try doing a factory data/cache wipe from Recovery.
I flashed the stock rom via ODIN. There is no factory data/cache wipe since there's no custom recovery.
Are you suggesting flashing CWM/TWRP on the phone now then doing that?
Houston we have liftoff. Thanks for the tip Fappa, that got me into the phone (reinstalled cwm, factory reset). However I'd still like to remove CWM and go back to completely stock....
I'm not overly worried about it as I'm selling the phone but I'd like the new owner to have a completely clean phone in case they need to send it in at some point for repair. But in any case it's up and running with CWM and factory ICS rom.
santiagodraco said:
I flashed the stock rom via ODIN. There is no factory data/cache wipe since there's no custom recovery.
Are you suggesting flashing CWM/TWRP on the phone now then doing that?
Click to expand...
Click to collapse
I'm sure fappa meant to use the stock android recovery and wipe. when I go back to stock it always hangs at AT&T boot logo and have to wipe/reset from stock recovery to get it to boot.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Yes do what they say or you will continue to boot loop.
Sent using cheezoline.
After issues with the stock 4.0.3 to 4.0.4 upgrade, I wanted to root my ATT Samsung Galaxy S2.
I used Odin and UCLE5_Stock_Rooted.tar as suggested on the forum. I did not do a factory wipe- someone said I would not need to since ICS was on it.
Now when it boots I get errors: Logs Provider stopped, android.process.acore stopped, avrcp.service.samsung stopped
I can't access phone apps, call, etc.
When I hold vol +- and power, it comes up Android System Recovery <3e> ... it doesn't say ClockWork Recovery.
I'm not sure what direction to go now. Any help is appreciated.
First thing. Why does the thread title say UNLE5 ?. Second thing, yes you would need a factory reset wipe to fix your errors popping up. But that brings us to the third thing, you flashed a stock image of UCLE5 4.0.3. Which obviously has the stock 3e recovery in it, as you must know our kernels come with recovery installed and when you flashed that stock image it flashed the stock kernel that comes with 4.0.3 . Which takes us back to your factory reset/data wipe you need to do. You are now on stock ics kernel, which has been confirmed to have the EMMC brick bug. Which is just a fancy way of saying that if you do a factory reset/data wipe when on this kernel, it could hard brick your device. So if you want to stay stock with everything, just flash a custom kernel(siyah.tar file is easy to find) with Odin, then reboot into recovery and do a full wipe. Then simply flash your UCLE5 image again with Odin and you're good to go. But I would suggest just using a custom kernel and getting off the stock kernel, don't want to accidentally forget and brick your device.
Phalanx7621 said:
First thing. Why does the thread title say UNLE5 ?. Second thing, yes you would need a factory reset wipe to fix your errors popping up. But that brings us to the third thing, you flashed a stock image of UCLE5 4.0.3. Which obviously has the stock 3e recovery in it, as you must know our kernels come with recovery installed and when you flashed that stock image it flashed the stock kernel that comes with 4.0.3 . Which takes us back to your factory reset/data wipe you need to do. You are now on stock ics kernel, which has been confirmed to have the EMMC brick bug. Which is just a fancy way of saying that if you do a factory reset/data wipe when on this kernel, it could hard brick your device. So if you want to stay stock with everything, just flash a custom kernel(siyah.tar file is easy to find) with Odin, then reboot into recovery and do a full wipe. Then simply flash your UCLE5 image again with Odin and you're good to go. But I would suggest just using a custom kernel and getting off the stock kernel, don't want to accidentally forget and brick your device.
Click to expand...
Click to collapse
Thanks- sorry about the typo in the title... I meant UCLE5. I was able to get rid of the errors by clearing the data on those items in the application manager. Thanks for the info on the custom kernel... I wasn't sure which to use for 4.0.3.
^
Siyah 4.3.3 ICS Without Mic Swap...http://forum.xda-developers.com/showthread.php?p=24675557
[email protected] said:
Thanks- sorry about the typo in the title... I meant UCLE5. I was able to get rid of the errors by clearing the data on those items in the application manager. Thanks for the info on the custom kernel... I wasn't sure which to use for 4.0.3.
Click to expand...
Click to collapse
All good I'm glad you got it sorted.
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Exodus885 said:
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Click to expand...
Click to collapse
I like TWRP. It works well with the new phone and Roms that are coming out plus it is so easy to use. Never liked CWM very much. You did right by reverting to an older version of TWRP I had to do that once.
TWRP... i don't even consider anything else.
Do you guys know why my phone gets stuck on the samsung logo everytime i restart my phone?
Doesn't matter what ROM i use it always happens....
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Dubbsy said:
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Click to expand...
Click to collapse
I did ALL of those, still have the problem.
So.... I just ODIN-ed back to stock and going to root and basically re-do everything -_-
I have a Galaxy S2 intl version. I was on carbon rom with siyah kernel. All was fine then suddenly it force reboots. but while rebooting it just didn't happen. Nothing happened. The screen logo just flashes for a second and then disappears, and then nothing happens. I tried entering the recovery mode, but doesn't enter the recovery mode. The download mode is working just fine. So I flashed a custom rom with siyah kernel using ODIN, hoping it would help, but nothing seems to happen though both rom and kernel are flashing perfectly alright! Please help me recover my phone guys. Would be extremely grateful, please!
Don't use siyah on custom roms. Flash Dorimanx 9.xx through odin . Recovery should now work. Go into recovery and factory reset clear the caches and reboot. Should work fine after this.
Remember
Dorimanx 8.xx is for stock and custom rom
Dorimanx9.xx is for custom only.
andrewwright said:
Don't use siyah on custom roms. Flash Dorimanx 9.xx through odin . Recovery should now work. Go into recovery and factory reset clear the caches and reboot. Should work fine after this.
Remember
Dorimanx 8.xx is for stock and custom rom
Dorimanx9.xx is for custom only.
Click to expand...
Click to collapse
Okay so I left my phone overnight, with the battery pulled out. I had flashed a stock rom before going to sleep. And i woke up and just put the battery back in to flash Dorimanx, and, something happened. The phone entered recovery mode :cyclops: I had been trying to get in the damn thing for the whole day yesterday, and today it happened, so i did as you said, wiping all that, and rebooted the phone. In a little odd fashion though, but it booted up and the setup process started, and it's working fine now. So, now I'm on a custom rom JB 4.1.2 and siyah kernel. I want a stable 4.3 on my phone. What can I do, sir? I dont wanna run into trouble again, so what would be a safe way?
emviveem said:
Okay so I left my phone overnight, with the battery pulled out. I had flashed a stock rom before going to sleep. And i woke up and just put the battery back in to flash Dorimanx, and, something happened. The phone entered recovery mode :cyclops: I had been trying to get in the damn thing for the whole day yesterday, and today it happened, so i did as you said, wiping all that, and rebooted the phone. In a little odd fashion though, but it booted up and the setup process started, and it's working fine now. So, now I'm on a custom rom JB 4.1.2 and siyah kernel. I want a stable 4.3 on my phone. What can I do, sir? I dont wanna run into trouble again, so what would be a safe way?
Click to expand...
Click to collapse
I am installing the Carbon Rom, JB 4.3 as I already have a copy of it on my phone, and I'm doing it with the same previous kernel on it, ie, Siyah-s2-v5.0.1. Should this create a problem?
Yes it will. DONT USE SIYAH. Use dorimanx 9.xx for any custom rom. Including carbon rom
andrewwright said:
Yes it will. DONT USE SIYAH. Use dorimanx 9.xx for any custom rom. Including carbon rom
Click to expand...
Click to collapse
Okay now I'm really sorry it's starting to bug you but my phone seems to develop new problems every time I reboot. Now, I havent changed anything, On a stock rom with siyah kernel. and i rebooted, and stuck again! I am able to enter recovery mode though (CWM recovery) and download mode also. BUT, now what happens when I boot is, the samsung logo shows with the triangle and, the boot tune plays but there's nothing on the screen, it's just black, and a few secs later, it gives a small vibration, all still with the phone screen black. Later i get to know that my phone has apparently turned on, but the screen is not showing anything. I called my cell and to my surprise it rings meaning its actually ON!! Why is the screen not ON then?? Please help, kind sir! Also if you could provide me with links to the required kernels/roms or whatever else required. Eagerly awaiting your saviour reply! :crying:
You need to go bk to stock with Odin. Test and see if it still happened with fully stock rom and kernel.
andrewwright said:
You need to go bk to stock with Odin. Test and see if it still happened with fully stock rom and kernel.
Click to expand...
Click to collapse
Hey, problem solved now, dont know what it was though! What i did was flash the Carbon rom with siyah, and it booted and then i flashed dorimanx and its working fine now. But the gapps package is reacting weirdly. I flashed it perfectly and when i reboot, it says "Google + stopped working" and then i check the app menu and there's no google apps whatsoever. http://goo.im/gapps/gapps-jb-20130813-signed.zip I then installed play store apk and it opened up and looked fine but then that is all it did! It won't download anything. What shall I do?
Full wipe. So format
Data
System
Preload
Cache
Dalvik cache
Then flash
Rom and gapps
Then flash dori
Then reboot
andrewwright said:
Full wipe. So format
Data
System
Preload
Cache
Dalvik cache
Then flash
Rom and gapps
Then flash dori
Then reboot
Click to expand...
Click to collapse
I did everything! I never got the option to format preload though. Everything else went smooth. Rebooted. Same problem persists.
Go bk to recovery and factory reset. Also maybe if that don't work redownload gapps and try again. May have curupt gapps.
emviveem said:
I did everything! I never got the option to format preload though. Everything else went smooth. Rebooted. Same problem persists.
Click to expand...
Click to collapse
And to top it all off, long pressing the home button refuses to bring up the recent apps/multitasking facility now. The notification bar doesn't work.
What nightly of carbon are you on?
Edit: also format pre load must be there? Mounts and storage. under format system I think.
andrewwright said:
What nightly of carbon are you on?
Edit: also format pre load must be there? Mounts and storage. under format system I think.
Click to expand...
Click to collapse
How do I check to tell which nightly I am on? And the first time I had done the full format, i had preload, and while i foramtted that, it gave me some error saying it couldnt do so. I completed the procedure anyways, availing no success. So, repeated it second time and found no preload option. The recovery menu seems to have changed. Is it a matter of concern? I am on a CWM recovery, apparently. and i found the preload option. tried. it says "Error foramtting /preload" how should i proceed?
Okay this is what I'm using "CARBON-JB-NIGHTLY-20131018-0102-i9100" Please help! I've run into more problems than I had anticipated! I am so worried. What should I do now?
emviveem said:
Okay this is what I'm using "CARBON-JB-NIGHTLY-20131018-0102-i9100" Please help! I've run into more problems than I had anticipated! I am so worried. What should I do now?
Click to expand...
Click to collapse
Sir, please reply. I'm sincerely apologize if I'm coming across as impatient but I'm **** scared. Please tell me how to proceed now..:crying:
Download 11/10 nightly and Dori 9.41.
Preload not formatting is worrying mate. Flash them and get bk to me
Try gapps for jb 4.3. It will surely work.
Sent from my GT-I9100 using xda app-developers app
20130810 is 4.3 isn't it? I'm sure it is.
andrewwright said:
Download 11/10 nightly and Dori 9.41.
Preload not formatting is worrying mate. Flash them and get bk to me
Click to expand...
Click to collapse
I am not able to locate the download links. Could you please do it for me?