Related
I have a mac, so no odin, and Heimdall won't recognize my sgs2. Originally i rooted my phone with a shell script. I then used Rom Manager to install Cyanogenmod 7.1. All was good til I decided to give ICS a spin, so I downloaded kp8 from this thread:
http://forum.xda-developers.com/showthread.php
And tried to flash using Mobile Odin. It flashed, rebooted, and now I am stuck at the boot screen. I am guessing that maybe I needed to get a CF-Recovery compatible build??
Anyways, just want to get back in working condition. I currently have no way to mount the sd card (no sd card mount option in normal recovery), so I have to wait until tomorrow when I can borrow a friends phone. Should I just try to update to a CF- kernel?
Do I need a pc?
Thanks
Do you have CWM recovery, or stock recovery?
If you have CWM recovery boot into it and wipe data/cache and it may boot or flash a rom of your SD card.
Otherwise borrow someones PC and use odin to flash back to GB, make sure to flash the GB bootloaders first. (On that note, did you flash the ICS bootloaders? As if you didnt that might be why its not booting)
Do you have CWM recovery, or stock recovery?
Click to expand...
Click to collapse
stock
Otherwise borrow someones PC and use odin to flash back to GB, make sure to flash the GB bootloaders first. (On that note, did you flash the ICS bootloaders? As if you didnt that might be why its not booting)
Click to expand...
Click to collapse
Wasn't aware I needed to, sounds logical. I'll do some more research before trying again.
Thanks
j_s_1 said:
stock
Wasn't aware I needed to, sounds logical. I'll do some more research before trying again.
Thanks
Click to expand...
Click to collapse
Yup, you need new bootloaders for ICS, but beware, the current ICS leaks are buggy and not really ready to be daily drivers.
As you have stock recovery, I would just borrow someones PC and use odin to flash stock gingerbread back.
never mind
Just an update. I got the ability to copy files to my sd card. I have tried to do an update from sd card with
i9100XXKG1
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4
Both resulting in "Signature verification failed".
As you have stock recovery, I would just borrow someones PC and use odin to flash stock gingerbread back.
Click to expand...
Click to collapse
Is my only recourse to find a pc or should I try something else? If I get a pc I will only have access to it for a short time, so want to make sure I am trying the right things.
That flash failed as Rom Manager likely broke recovery (has happened to me in the past, Rom Manager - bad).
PC as previously advised. I'd say you've exhausted all the non-PC options.
j_s_1 said:
Just an update. I got the ability to copy files to my sd card. I have tried to do an update from sd card with
i9100XXKG1
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4
Both resulting in "Signature verification failed".
Is my only recourse to find a pc or should I try something else? If I get a pc I will only have access to it for a short time, so want to make sure I am trying the right things.
Click to expand...
Click to collapse
Ok. And one last question, as far as flashing stock gingerbread (or a diff stock ROM), what would be the best, safest package to try? I do not know my kernel version, and can't find out (as I can't boot)
My phone is the international version of sgs2, purchased in Germany, csc code DBT.
searching for stock gingerbread for my phone seems to come up with a bunch of different builds.
Thanks
KI4 seems to be the most recent in Intra's thread, so I'd go with that. Not that it makes a massive amount of difference tho.
j_s_1 said:
Ok. And one last question, as far as flashing stock gingerbread (or a diff stock ROM), what would be the best, safest package to try? I do not know my kernel version, and can't find out (as I can't boot)
My phone is the international version of sgs2, purchased in Germany, csc code DBT.
searching for stock gingerbread for my phone seems to come up with a bunch of different builds.
Thanks
Click to expand...
Click to collapse
Update:
Got a pc and got odin working. Flashed MultiCSC_OXA_I91000XXKI2.tar . rebooted and it tried to go into recovery mode then gave me a dead robot with a red exclamation point, which doesn't seem good.
Ideas?
UPDATE:
Nevermind, I just had to get the full firmware :
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
for DBT (Germany). Flashed with Odin and I am back. Awesome. Thanks
I did say to get KI4 from Intratech's thread, didn't I ? Anywho, glad you got you phone working again
j_s_1 said:
Update:
Got a pc and got odin working. Flashed MultiCSC_OXA_I91000XXKI2.tar . rebooted and it tried to go into recovery mode then gave me a dead robot with a red exclamation point, which doesn't seem good.
Ideas?
UPDATE:
Nevermind, I just had to get the full firmware :
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
for DBT (Germany). Flashed with Odin and I am back. Awesome. Thanks
Click to expand...
Click to collapse
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
Alright, so I went into the phone store to get data for my phone, but the person told me that since i upgraded to ICS, the phone is not going to be recognized etc. that was some time ago and I don't remember what he said entirely. He suggested I go back to the stock gingerbread that my phone came with, but looking around I can't exactly seem to find it. So going through androidfirmwares.net i downloaded and flashed one that looked promising, (JPKJ2), but after rebooting my data was not appearing. I guess my question is where can i find or do to restore my phone to the stock gingerbread that it came with? It's international and unlocked.
PDA:I9100JPKJ2
Phone:I9100XXKI4
CSC:Uknown
r3k0iL said:
Alright, so I went into the phone store to get data for my phone, but the person told me that since i upgraded to ICS, the phone is not going to be recognized etc. that was some time ago and I don't remember what he said entirely. He suggested I go back to the stock gingerbread that my phone came with, but looking around I can't exactly seem to find it. So going through androidfirmwares.net i downloaded and flashed one that looked promising, (JPKJ2), but after rebooting my data was not appearing. I guess my question is where can i find or do to restore my phone to the stock gingerbread that it came with? It's international and unlocked.
PDA:I9100JPKJ2
Phone:I9100XXKI4
CSC:Uknown
Click to expand...
Click to collapse
Intall the Titanium Backup Pro, backup your phone. Then flash the stock GB, install the CWM Recovery. Thru the recovery do a restore. That's it.
Mariacci said:
Intall the Titanium Backup Pro, backup your phone. Then flash the stock GB, install the CWM Recovery. Thru the recovery do a restore. That's it.
Click to expand...
Click to collapse
Yeah, that's the thing. I can't find the stock gingerbread to download. Also, the person told me once I went back to GB the data marker should appear, which it did not :/
r3k0iL said:
Yeah, that's the thing. I can't find the stock gingerbread to download. Also, the person told me once I went back to GB the data marker should appear, which it did not :/
Click to expand...
Click to collapse
Here you can get offical firmware's. But, registration required. Also here.
Hey there
Today I decided to root in order to install Clockwork Recovery Mod and from there install Android Revolution HD.
I used Titanium Backup Pro to backup everything before I installed ARHD and then when I tried to restore on ARHD it kept giving me problems so I decided I should just delete ARHD and go back to stock (original) ROM. The latest ROM for it is 4.1.2 while ARHD is 4.2.1 maybe it has something to do with it, but anyway I used Odin > PDA > chose original ROM which is I9300XXEMA2_I9300OJVEMA1_I9300XXELLA_HOME which I downloaded from SamMobile but now I am stuck in some sort of a boot loop where the SAMSUNG logo keeps appearing, disappearing, and some animations keep taking place.
I tried to reboot into recovery mode (held power, home, and volume up buttons simultaneously) but it just reboots to the initial black SAMSUNG GALAXY S3 I9300 screen and gets stuck, and there's some sort of red exclamation mark on the top left corner of the screen.
Any ideas on what to do now? I have Odin, the original firmware, Android Revolution, and CWM (.img not .tar) on my computer, is there anyway to use any of them in order to fix the device? I wouldn't mind formatting the device, for instance, if necessary.
ANY INFORMATION IS MUCH APPRECIATED! THANK YOU.
Any ideas guys? To make it short I installed the latest firmware for my device which is ( I9300XXEMA2_I9300OJVEMA1_I9300XXELLA_HOME ) but it keeps getting stuck in a boot loop, and I am assuming that's because perhaps when I updated to 4.2.1 (the above firmware is 4.1.2) the bootloader was updated or changed?
THANKS!!
Are you sure you're holding power, vol +, home for long enough to get into recovery??
Yes mate I am very sure. I have been trying different things for a while now but I still cannot get it to work. I am extremely frustrated I honestly want to break the phone but at the same time I know it's my fault and I WANT TO FIX IT!
Can you get into download mode? power, vol -, home.
Yeah mate I can. I finally was able to boot into recovery mode. The thing is, I had a .tar file of CWM (unlike the .img version from their website) which was old, but I was able to find a bit of a newer one which I flashed using Odin and it worked!
Now I am in the process of reinstalling Android Revolution HD and fingers crossed that it works. I already have access to download mode, but now that I have access to CWM I am guessing my chances of fixing everything is better?
UPDATE: Android Revolution HD booted and is working just fine. Should I just keep using it? I'd rather go back to the stock ROM, stay unrooted, and be able to receive OTA updates, but the latest firmware for my device is this "I9300XXEMA2_I9300OJVEMA1_I9300XXELLA_HOME" and I am assuming its bootloader is older than ARHD's which is why it gets stuck in a bootloop?
Thanks again for your help.
Good news
Personally, I'd just stay on ARHD if the ROM is ok.
It does sound like you have a newer bootloader which must have been flashed previously. I wouldn't have thought ARHD includes the bootloader though (I could be wrong).
Have you thought about flashing the latest MB5 BTU firmware? This is available from sammobile to flash via ODIN and you would get OTA updates.
Thanks for your reply, I truly appreciate all your help.
Well, I have not thought about that. I am pretty sure I have the MB5 bootloader (XXEMB5 or something like that) which I flashed via Odin in an attempt to resolve the issue, however it only seemed to work with ARHD but not 4.1.2 (XXEMA2).
So what you're saying is that I can install ANY 4.2.1 firmware available on SamMobile via ODIN and it'll work fine? Even if the country and provider are different? Mine is internationally unlocked but I am in Egypt in case that makes any difference.
Thanks again.
The bootloaders changed around ELLA/ELLC firmwares I think.
EMB5 is the latest BTU (UK) release. Its 4.1.2.
Yes, you can flash it, it doesnt make any difference where in the world you are as long as you have an I9300
You would then get OTA updates just like everyone else using stock EMB5 (BTU).
The BTU updates tend to come sooner rather than later as well so you'd likely be on a more upto date rom than an Egyptian one.
Hope this makes sense
Awesome. Well I cannot lie and say I fully understand but I get what you mean. I am going to download that firmware and install it using ODIN. Is there anything I should prepare before going ahead and doing that? I wouldn't want to get stuck in another bootloop! lol..
Would that stock ROM EMB5 BTU (which is 4.1.2 while my current Android revolution HD is 4.2.1) change my boot loader to the correct one?
TarekElsakka said:
Awesome. Well I cannot lie and say I fully understand but I get what you mean. I am going to download that firmware and install it using ODIN. Is there anything I should prepare before going ahead and doing that? I wouldn't want to get stuck in another bootloop! lol..
Would that stock ROM EMB5 BTU (which is 4.1.2 while my current Android revolution HD is 4.2.1) change my boot loader to the correct one?
Click to expand...
Click to collapse
I 'think' it includes the latest bootloader, I'm not too sure.
Just flash it with ODIN as you've done previously - in PDA etc...(make sure you dont choose repartition!)
If it bootloops, make sure you wipe data/cache & dalvik through recovery...
It should work. If not, flash CWM then ARHD again as you did earlier
good luck!
Alright mate I went ahead and installed the EMB5 BTU and it works flawlessly. Thanks again!
I am so stupid.. on the Android Revolution HD thread, XEMB5 is actually written in the title! lmao.. which means it did update my boot loader to that which is why my older firmware (XXEMA2) did not work.
Thanks for all your help, I truly appreciate it. Any ideas on when we're getting 4.2.1 or if it's even officially out yet? I have a feeling it's leaked because the latest I saw on SamMobile was 4.1.2.
Great news
There is a leak for 4.2.1 but it isnt very stable from what I have read.
Best to wait for an official release.
The S4 is out at the end of April so 4.2.2 should come along around then, if not before....
Glad its all sorted!!
Yeah I must say I agree with you. Android Revolution HD always comes without any visual changes, and while it is based on 4.2.1, I did not like the changes to how the sidebar, lockscreen, and some other things worked. There was this voice command feature that I really liked as in saying "Capture" for the camera to take a picture and "Play/Pause/Next/Previous" for the music application and such, but I am sure it is available on 4.1.2 as well I just haven't looked yet. I sure hope the S4 brings necessary updates to the S3 just like the S3 did to the S2. Between me and you, though, I'd have liked to have the 4G LTE version of the S3 just because it has 2GB of RAM which would have been nice since I keep a lot of applications on most of the time. I am pretty sure, however, that 4G affects the battery life much more than HSDPA and 3G, though, so that's a downside.
I'm pretty sure (but I may be wrong) custom roms don't update bootloader. The only way that a bootloader gets updated is via an OTA Update or reflashing firmware via pc Odin. If you did an OTA Update or flashed via pc odin to MB5 firmware then you flash back to MB1, you'll still have MB5 bootloader. All 4.1.2 bootloaders will not roll back via pc odin. When ever I (and everyone else) roll back android version (ie from 4.2.1 to 4.1.1 or 4.1.1 to 4.0.4) always get a bootloop at samsung logo, as mikep99 mentioned, a wipe/data factory reset fixes that issue but you had problems with your recovery.
I currently have ALEF bootloader after I updated to LLA firmware via pc odin. I rolled back by flashing a stock ICS firmware where the newest firmware for that country was 4.1.1. So after flashing XXBLH1 (4.0.4) I did an OTA update to XXDLK1 (4.1.1) and with that I got XXDLK1 bootloader then I flashed ALEF bootloader via pc odin. Problem now that samsung has pretty much updated all countries to 4.1.2 except Algeria TMC (Sammobile) so pretty much all OTS's now will give you the new bootloader.
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?