Hi there,
I'm running CM 10.1 20130219 and today bought franco.Kernel and auto flashed to I think it was version r20. The phone restarted and got to the Sammy screen with the red exclamation mark at the top left which I'm assuming is fastboot mode? So it stayed at that screen for 3 or so secs and it turns off. I found this post http://forum.xda-developers.com/showthread.php?t=1392310 but the toolkit is for the Nexus only. Would flashing stock firmware through Odin do the trick?
Thanks
unknownmember said:
Hi there,
I'm running CM 10.1 20130219 and today bought franco.Kernel and auto flashed to I think it was version r20. The phone restarted and got to the Sammy screen with the red exclamation mark at the top left which I'm assuming is fastboot mode? So it stayed at that screen for 3 or so secs and it turns off. I found this post http://forum.xda-developers.com/showthread.php?t=1392310 but the toolkit is for the Nexus only. Would flashing stock firmware through Odin do the trick?
Thanks
Click to expand...
Click to collapse
Try to flash a stock kernel/CM10 kernel or another custom kernel (e.g. Siyah) and see if it fixes the booting.
Soz been busy with work. But kinda fixed it by flashing stock ROM. I flashed it with stock but it wouldn't go any further than Sammy boot screen and kept restarting. So I CF rooted and luckily was able to get into recovery mode and luckily also I made a backup...I almost didn't in the first place. lolz. Thanks heaps for the tip tho, at least now I know where to get the stock kernel.
khob-kun-Krub i'm assuming you're Thai since your location is Bangkok. I'm born Thai but can't read, write or speak Thai to save my life. lolz
Franco kernel doesn't support AOSP. Only Samsung ROMs.
Exynos SIII; CM10.1
unknownmember said:
Soz been busy with work. But kinda fixed it by flashing stock ROM. I flashed it with stock but it wouldn't go any further than Sammy boot screen and kept restarting. So I CF rooted and luckily was able to get into recovery mode and luckily also I made a backup...I almost didn't in the first place. lolz. Thanks heaps for the tip tho, at least now I know where to get the stock kernel.
khob-kun-Krub i'm assuming you're Thai since your location is Bangkok. I'm born Thai but can't read, write or speak Thai to save my life. lolz
Click to expand...
Click to collapse
Good to hear that it is working.
As you can see by my flag, I am German but living in Bangkok for several years now. I can speak, read & write Thai as well (basics though). Let me know if you are in Thailand on accident some day.
Related
After rooting my phone for the first time about a month ago, I though to myself "This is awesome!". After thinking that, I dug deeper and deeper into the Android Universe and found custom ROMs. The first one I flashed was just a standard 4.0.3 ROM that worked fine. The second one I flashed was a CM10 JB ROM (for my device), and this also worked. But yesterday, (22nd August) I realised that flash player wouldn't work, even though I had the .apk installed on my phone. I found out what dual-booting was when I flashed the CM10 ROM but I didn't need to do it at that time. I downloaded the latest Siyah kernel, flashed it, turned on my phone and it worked fine (CM10) and then I realised I had to go back into recovery mode to change my primary and secondary ROM. I did this, and then next time I tried to turn it on, it just stays on the boot logo. (Siyah logo when I had the SIyah kernel on there and the default SGS2 boot logo with the yellow triangle when I changed back to a plain, old, boring, nothing special kernel). I am currently downloading an OSP file to see if that will help.
That is pretty much all the info I can supply with my knowledge of Android devices but I can try and give some more if needed.
Also, do you think if I took my phone back to **** Sith (Australian retailer where I bought it from) and played dumb (eg. I went to turn it on and the screen just stayed like this, I even left it like that over night and nothing happened) they would give me a new one? I know it voids warranty when you root but maybe if I get someone who doesn't know much about these phones I could get lucky.
Please give me as much help as you can. I haven't told my parents yet because I'm not prepared to face their wrath yet. God knows what they'll do to me!
So your hoping theres someone like you on the other side of the counter when you take the phone back?
Can you get into recovery/download mode lol
Maustin96 said:
After rooting my phone for the first time about a month ago, I though to myself "This is awesome!". After thinking that, I dug deeper and deeper into the Android Universe and found custom ROMs. The first one I flashed was just a standard 4.0.3 ROM that worked fine. The second one I flashed was a CM10 JB ROM (for my device), and this also worked. But yesterday, (22nd August) I realised that flash player wouldn't work, even though I had the .apk installed on my phone. I found out what dual-booting was when I flashed the CM10 ROM but I didn't need to do it at that time. I downloaded the latest Siyah kernel, flashed it, turned on my phone and it worked fine (CM10) and then I realised I had to go back into recovery mode to change my primary and secondary ROM. I did this, and then next time I tried to turn it on, it just stays on the boot logo. (Siyah logo when I had the SIyah kernel on there and the default SGS2 boot logo with the yellow triangle when I changed back to a plain, old, boring, nothing special kernel). I am currently downloading an OSP file to see if that will help.
That is pretty much all the info I can supply with my knowledge of Android devices but I can try and give some more if needed.
Also, do you think if I took my phone back to **** Sith (Australian retailer where I bought it from) and played dumb (eg. I went to turn it on and the screen just stayed like this, I even left it like that over night and nothing happened) they would give me a new one? I know it voids warranty when you root but maybe if I get someone who doesn't know much about these phones I could get lucky.
Please give me as much help as you can. I haven't told my parents yet because I'm not prepared to face their wrath yet. God knows what they'll do to me!
Click to expand...
Click to collapse
Can you still boot to your second Rom ie CM10?
Can you still get to CWM recovery?
If your answer are yes.
-boot to CWM recovery
-flash your Samsung custom ROM again
-wipe dalvik cache
-wipe permissions
-flash Siyah kernel
-reboot phone
Swyped from my Samsung Galaxy SII
Dude, take a chill pill. This is XDA, there are a lot of awesome people here who might know a solution to your problem
Luckily, you are not the only person alive to screw up their flash player while they were on cm.
If you can go to download mode, you can start all over again from scratch by flashing a stock firmware.. and from there, let your custom stuffs begin!cheers
Sent from my brain using telekinesis
Thanks for all the responses guys!
I have managed to fix through scouring every corner of the internet. It probably took a lot longer than it should have since it i sme, oh well! I'm just so thankful everything is working again.
I think I'll stay away from dual booting!
How do I close this thread?
Send a PM to prbassplayer. He's the moderator.
Sent from my Galaxy S2 GT i9100
Thread closed
Per request.
Hi All,
I have had my S3 for about 6 months now, in November 2011 after taking a call my phone turned off and refused to turn back on. I did all the usual stuff, taking the battery out, trying recovery mode etc but nothing worked. Searched Google and forums and basically said it was a known fault with some of the S3's and it'd have to go off to be repaired. It came back within 2 weeks and worked great again.
Yesterday, the LED was flashing blue so went to look at incoming message / email and it wouldn't come to life...exactly the same problems as before! I was gutted. My conclusion is that it will have to go off and be repaired / replaced. My question is, is this likely to be happening because I rooted my phone with the CF-Root-SGS3-v6.3? I have had no other issues.
Thank you
you need to use a kernel that has the sudden death fixed
Glebun said:
you need to use a kernel that has the sudden death fixed
Click to expand...
Click to collapse
So if I can find another CF-Root version it should be okay once I get it back from being 'repaired'
chrisbrawn said:
So if I can find another CF-Root version it should be okay once I get it back from being 'repaired'
Click to expand...
Click to collapse
Yes. Assuming your repaired phone is running a recent build of the stock ROM, it will include the fixes for the brick bug. You can then root as you did before. I would also flash a more recent recovery, the CWM bundled with CF-Root is out of date.
Thanks greatly!
I have found the following root file: CF-Auto-Root-m0-m0xx-gti9300.tar
Does anyone know (providing it matches my phone when it come back from Carphone Warehouse) if this is the most recent one?
If it's for the I9300, it'll work.
I still prefer to flash some custom recovery and flash zip SuperSU..
I've just bought myself a USB JIG..I'm going to try to recover it myself. My problem is that it won't turn on, the USB JIG appears to be able to boot it into download mode. I can then use odin to flash a stock rom, which i'm downloading from SamMobile.
What custom recoveries would you suggest?
Not my first time to root and install a custom rom on other phone, but this phone isn't treating me well.
So I followed the root guides to root the phone.
Downloaded an insecure kernel for i9100. Although, oddly enough, I bought this phone 2nd hand, and when I went to the "about" part for the kernel look up before tried to root it, the kernel info just contained ICS3.?? (forgot) and the date. There was no four or five letter kernel code like I've been seeing. But according to cnet (one of many rooting tutorials), the kernel version doesn't matter as you can change the kernel anytime, or after rooting in this case.
So I installed Kies to get the Samsung drivers installed. Done.
Restarted phone to download mode (volume down, home, power)
Started Odin 3 v1.83
Phone was recognized. Click the 2 boxes (Auto reboot and F. Rest Time).
Clicked PDA, loaded up an insecure kernel.
Status went through OK, ended up with "Pass!"
Phone automatically restarted.
Now the problem. It restarts, shows the Samsung Galaxy S2 logo with the big triangle underneath it, and thats it. Never leaves this screen. I thought maybe it's a kernel problem, so I tried several different insecure kernels, all with no change. I have no idea how to find what kernel was the original one that came with this phone. Would using Odin with the original secure kernel (or even insecure) solve this problem? Otherwise, what else can I do? My note 2 was stolen so I bought this s2 second hand until I can scrape up enough money for a note 2 again, but the damn thing won't even boot up now. :crying:
How can I get this working again, even to have it stock again I'd be fine (though obviously putting on a custom room with root would be best).
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
TheATHEiST said:
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
Click to expand...
Click to collapse
There wasn't much to try, at least as far as my noob self knows about. I tried flashing 6 other kernels I found, merely taking guesses at which might possibly be the Chinese s2 one, I remember from flashing other phones that i had to look for Z or D in the kernel ID. But all of them just led to the same problem of not booting past the logo screen.
Besides just trying to start it up as normal (which doesn't work) and starting it up in download (by holding down vol+home+power), what others ways can I start it up? I don't know how to boot into recovery, and I didn't know I can flash a rom without first rooting it, which I haven't done yet because it's still stuck in start-up.
Searching enough xda threads and just googling seems show a pretty large consensus supporting the existance of a China i9100, plus I see them everywhere (as well as s3, s4, and notes), so I'm 99% sure they are an official and semi-large market for them here (after iPhones unfortunately). But even still, that doesn't help me locate the original kernel.
Under the battery, is says this:
Samsung WCDMA
Model #: GT-I9100
CMIIT ID: 2011CP2751
Do these help? So is any of the steps I did wrong, or can you otherwise point me in the right direction? Appreciate the help.
Don't post your IMEI (or your SN for that matter).
MistahBungle said:
Don't post your IMEI (or your SN for that matter).
Click to expand...
Click to collapse
Thanks for the tip MistahBungle. Edited out.
Hate to say it, but found more help on youtube... Found a guide that walked me through replacing all the files (not just kernel) in Odin that got it back up and running. I'll follow the xda guides again and hopefully it'll work this time... Thanks anyways...
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Kari458 said:
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
Click to expand...
Click to collapse
Yup
cyril279 said:
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Click to expand...
Click to collapse
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
I've raged on this device a time or three myself, I promise.
The most abnormal part of each of your posts is the battery involvement. You shouldn't have to touch the battery at all for recovery mode, download mode, or flashing, so I would guess that you're up against dirty or failing charge port, a near-dead or failing OEM battery, or similar issue which made your flashing journey more troublesome than it should have been.
There are several posts [like this one] about troubles using i9100 batteries. They fit and function, but exhibit undesirable charging issues, which consequently tend to get blamed on some other aspect of the device.
The symptoms of a dirty or failing charge port also commonly mis-direct users to blame firmware, batteries, and everything-else.
-Cyril
Kari458 said:
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
Click to expand...
Click to collapse
hi guys don't know if this has been posted before so if so sorry..
my problem I have galaxy s3 i9300 which I have flashed custom roms many times..
now this time I got more brave and flashed different kernel..
so to start and help you guys i flashed Resurrection_Remix_KK_v5.1.5-20140609-i9300
thought the battery was going down to fast so flashed boeffla kernel correct version etc. thought it was a bit sluggish no offence intended..
so decided to flash stock kernel back which I got from boeffla site correct version for my phone..
now is were the fun started my phone rebooted into screen loop on resurrection screen.
oh and by the way I have no power button my mate tried soldering another and failed
so you can guess my fun anyways I got round this with usb jig, went into download mode and flashed stock rom back to phone, which I have done hundred times..
this time it would not boot at all I searched and searched for answers and managed CF-Root-SGS3-v6.0 which boots straight into recovery for a sec which helps with no power. now with this I wiped every thing cache etc then with the correct timing used toolkit to reboot etc etc anyways.
problem is now that when I flash stock it seems I still have resurrection in the background don't ask me how ?? but once stock flashed and rebooted i goto file system and its still emulated/0 file system which it isnt normally and the same wallpaper is there so weird. now to top it all my menu and wifi and back button will only work when I flash back to resurrection rom and not stock...
driving me nuts sorry for long essay but theres more and I needed to explain hope you can help...
thanks andy