Hello I am from Argentina, desperately need help.
I rooted my SGSII ICS 4.0.3 phone with CF Root LPJ everything went as expected. Odines PASS! and all but when my phone reboots it just turns off after logo screen with triangle.
I can get into recovery and download mode but that is all.
What should I do?
Might commit suicide if there is no fix.
Flash stock rom.
You can find it at sammobile.com.
elemenofi said:
Hello I am from Argentina, desperately need help.
I rooted my SGSII ICS 4.0.3 phone with CF Root LPJ everything went as expected. Odines PASS! and all but when my phone reboots it just turns off after logo screen with triangle.
I can get into recovery and download mode but that is all.
What should I do?
Might commit suicide if there is no fix.
Click to expand...
Click to collapse
If you can get into recovery and download mode, you are only softbricked. It could be worse.
Please be more precise, I lack experience but I will understand.
Which stock ROM should I flash now?
Because I got a downloaded I9100UHLPS_I9100AROLP4_ARO but it is not LPJ.
I also managed to find Kernel_I9100XXLPJ at intratech. Would flashing this kernel fix it? Could it possibly mess my recovery mode and brick my phone?
Flash the same ROM again using Odin, do not flash the wrong kernel.
ARO is a good ROM, just flash it again, it will boot, then root with the cfroot for that ROM later.
What do you mean by the SAME rom? I got this problem flashing a CF-Root kernel not an entire ROM.
The ROM I had before was ICS 4.0.3 which I upgraded officially via Kies.
Should I flash ICS 4.0.3 UHLPS that is for my region? I9100UHLPS_I9100AROLP4_ARO
I'm pretty sure that's what Atifsh meant, yes.
Thank you all! Thanks given with the button for all!!!
I flashed stock ICS 4.0.3 for my country downloaded from sammobile.com and the phone recovered with no trouble! I got my soft bricked SGSII working again!
Is there anything I need to wipe now to make sure there is no crazy leftover from the CF-Root boot fail?
If it's working fine, then probably not. I mean, you could always backup your contacts, call logs, SMS, etc and your apps with Titanium, do a factory reset, and then restore contacts, call logs, sms and user apps/data only (do not restore system apps or data).
But if it's working fine now, I don't see the point.
I want you to do two things for me tho.
First, get kTool either from Google Play (it's free) or from Hellcat's thread on here. Then backup your EFS. Keep one copy on your external SD card in your phone, and keep another copy on your PC. Then I want you to do a Nandroid backup in CWRecovery.
That way if anything does ever go wrong, you should be able to recover/get up and running again easily without losing your stuff. For example, if your phone ever borked & you had to send it in for warranty service/replacement, you could restore that backup when you get your phone back/a new phone.
Do a backup at least once a week and certainly every single time before you flash a new kernel/rom or if you make major changes to your system.
I am afraid of doing anything with this phone now. First experience = soft brick.
Damn I almost die. Now I need to find a way to get out of this stock 4.0.3 ICS because it is ramming through my battery and is as slow as a potatoe.
4.0.4 is eMMC hard-brick possibly if I wipe after flashing.
Now I feel like an expert.
I also tried flashing cf root today and it softbricked my phone. Weird.... next time I try to root my phone, I wont be using cf root.
Which Kernel was yours? Leave it here logged for future brickers.
Mine was LPJ
Related
Hello all,
I have tried many things before asking for help, but nothing worked so far.
Here is the story:
I was on ICS 4.0.4, with default ROM coming from carrier.
I wanted to install CM9.1,
spent countless hours doing all backup and reading tutorial.
Tried finally yesterday and it was stuck doing "wiping data". Left it for 20min+ and nothing.
After restarting it, it is now stuck on the boot logo.
I couldn't enter anymore CWM or stock recovery (up+home+power), but could enter Download mode.
So I tried a couple of things I have read on the forum, like installing Siyah-s2-v5.0.1.tar through Odin 3.04 but I still cannot enter recovery mode.
I've read (too late) about the mmc brick bug (couldn't find anyone speaking about it in any tutorial until I reached this point... nothing on CM wiki or in other tuto... classic!).
I hope I'm not in this case though as I can still go to DL mode, and the phones having the brick bug are completely dead (blank screen or no DL mode), as per http://forum.xda-developers.com/showthread.php?t=1756242
I managed to finally get CWM working only by using GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar from Odin, then tried to install CM9.1 from SD card but after reboot it is stuck on the blue cyanogenmod animation boot screen and nothing happens.
Tried also to restore from CWM my nandroid backup, but during the restore it seems to hang then restart by itself, and then I'm back to Galaxy S boot logo (the animated one with the big S).
And after this I have lost again access to recovery mode.
I can't go back to stock and I can't install CM... I was not expecting such issues, it all seemed pretty basic on paper.
I'm really stressed and don't know what to do
Flash a stock rom in Odin (download mode), re-root your phone/flash a kernel with CWM, restore your backup ?
Hi,
thanks for answering,
I have tried to locate such a rom, but I'm not sure which one... is there a specific one to try ? could you point me to it please ?
so far I have tried I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5
but no luck
you also say "re-root", at the time I used this method:
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel - xda-developers
http://forum.xda-developers.com/showthread.php?t=1501719
Do I need root to install Siyah kernel from Odin ?
I'm trying one from sammobile... let's hope :/
The bad thing is I had no Yellow triangle at the beginning since I'm stuck in this boot loop or no boot to be precise.
Now that I have tried different things to fix it, it is still not working and I have my flash counter = 10.
I cannot even go back to the shop, is there a way to reset it knowing I cannot even reach the OS, I have only DL mode or CWM...
Use a stock rom for your region/carrier (or any stock rom from any region really), it doesn't really matter as I presume you'll be restoring a backup and/or going back to a custom rom anyway won't you ?
Samfirmware & AndroidFirmwares.net have lots of stock roms.
No, you don't need root to flash an Odin version of Siyah. So yes, you can flash that after you've got stock up & running to root your phone rather than re-rooting your phone by flashing a CFRoot kernel or using another root method. Just make sure the version of Siyah you're going to flash matches up with the stock rom you've got on (I.E if you flash a GB stock rom use GB Siyah, ICS stock = use ICS Siyah, etc, etc).
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Don't worry about the flash counter. That's the least of your problems while your phone is borked Worry about it when it's fixed. There's nothing you can do about the triangle while your phone is cactus.
When you've got it up & running again, use Triangle Away.
But first things first.
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
You're welcome.
Um, no. Absolutely not. Nothing personal, but if I did that for every person who's asked me for 'hands on' help since I've been here, I'd have spent my time doing nothing else. I don't do 'personal' with people from XDA (which is why I have PM's blocked except for mods).
Besides, you're going to learn much more fixing this yourself. I've given you a stack of information thus far, ball is in your court. Every answer to every question you could possibly ask is on this site. It just sometimes takes a bit of work/reading on your part to find it.
megosu said:
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Click to expand...
Click to collapse
ok I understand.. it is just I have literally spent more than 8 hours on it and had not make any progress at all (even worse I cannot return it to the shop because of the yellow triangle).
I appreciate your help, it gives me a bit of hope but I'm in a very bad situation and I feel I have read and do so much already with no success at all.
I will try your option of restoring the one from Sammobile, I have tried other before without any luck, maybe this one will do... (5min left to DL it).
thanks again for your support
I know where you're coming from. The first flash I tried when I got my phone in 2011 borked because I was careless, and it took me a bit over a day to get the right info/files/etc to get it fixed. I know it's frustrating/tiring/annoying & you're wondering at the start whether you can even fix it. But as long as you've got download mode 99 times out of 100 you can save it.
And as I said, it's good experience; once you've fixed it, you'll be able to handle anything that comes up in future
Let us know how you go. I'm going to bed shortly, but I'm sure someone else will step up & help if you have any further problems.
You're welcome Happy to point you in the right direction.
I have flashed the rom, the exact same one as I had before everything happened...
if it helps, I flashed it from Odin 3.04 as PDA.
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5
I'm now back to the Samsung GALAXY S2 GT-I9100 logo and nothing happens.
I cannot use recovery mode,
I can use DL mode (it shows 11 counts and current binary as Samsung official.)
update:
I left the phone on the first logo for about 5min and it moved to the next Samsung Galaxy S2 logo, with the big animated S.
I'm waiting but nothing else is happening.
I'm still desperate to fix it.
One thing which can be relevant, whenever I try to wipe or format /data from CWM, my phone is restarting after a few minutes or is saying it cannot be done.
I can format /cache and /system.
Could it be the root cause ? Any way of fixing it ?
Thank you
update: I cannot mount /data from CWM, it says Error mounting /data!
is it the brick bug ? :|
Easy now....your device is still good.
Those animations should take like 1-2 mins when you flash a rom.
Now, you are completly sure that you are actually flashing the right ROM for your device model?
If so, just keep flashing stock roms until you're up and running again, so you can start from scrap.
I tried, the issue is as soon as I flash a stock rom (through Odin), then I can't get into stock recovery mode anymore, I have to flash GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar to get back the recovery mode.
I tried to flash several times, I think it is down to the fact I cannot mount or format /data.
Which is why I'm wondering if it is the famous brick bug.
My device is GT-I9100 and I took the stock rom from sammobile:
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 which is ICS 4.0.4 (that I had before trying to move to CM9.1 and having all this mess in my hands.)
flash this:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/.
you are on siyah kernel right?
what you wanna do know is to get to whatever rom your flashing, forget about cmw for now.
this also might help:
http://forum.xda-developers.com/showthread.php?t=1457458
So it is not lost yet ? Not the brick bug ?
just to be sure:
you want me to install through Odin: Siyah-s2-v5.0.1-CWM.zip
then going back to DL mode
I flash through Odin: I9100XXLSJ_I9100OXXLS1_OXX.zip (coming from your link).
anything I'm missing (even if it seems obvious, please let me know as I'm maybe missing something important)
?
I still cannot do Factory reset... is it a problem ?
I dunno what kernel you are using, If stock 4.0.4 kernel you should flash siyah first (safe kernel, no brick bug), and then countinue flashing the ROM. Check out the brick bug thread in general SII forum for directions if you want.
BTW, Odin recognizes your phone right? Check it out, you'll get a huge long breath.
BTW 2: you don't have any kies applications running in your pc.....am I right? if so, CLOSE THEM ALL!
I did had stock 4.0.4 kernel when I first tried to follow CM9.1 wiki, and I did a factory reset through CWM... which is why I think I might have bricked it...
I have checked the brick bug thread (too late it seems...) but so far I can't be sure if I'm in this case or not as they say they can't even reach DL mode, and I can.
Odin recognizes my phone, yes, but anything I flash is stuck on the animated logo.
I do not have Kies installed, just installed the drivers.
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?
Hi guys,
Ok so I have managed to get my GT-I9300 (inter) network free stuck in a boot loop, after trying to put it back to stock I somehow lost my EFS folder and now get an error "E: Faild to mount EFS (invalid argument)"........yes everyone face palm as Im another one of them. However I have got a copy of my EFS folder that I made with Ktool, but its at this point im stuck.
Im really sorry to be posting another about this issue but after spending hours searching I can't find an answer, lots about people not having a back up but nothing for those that have.
What i need to know is how do I get the back up onto my phone?
I have the stock firmware and the back up EFS folder, but Im stuck as to what to do to "mount" the EFS and replace all this. I have downloaded EFS prof but the phone won't connect to it, it also won't connect to the Kies package either.
I admit I am a noob and should of stuck with the crayons rather than messing with things that i didn't really know, but its done now and i would really love to get your help (in simple talk if possible).
Rather than someone typing out the instructions again why not follow the guide in general stickies on how to return to stock?
Once the phone boots again you can root and copy the efs backup onto the phoen again.
Cheer, will look there. Hadn't found that section in my search, will give it a go and keep my fingers crossed
boomboomer said:
Rather than someone typing out the instructions again why not follow the guide in general stickies on how to return to stock?
Once the phone boots again you can root and copy the efs backup onto the phoen again.
Click to expand...
Click to collapse
Gone through the stickies, and followed the steps to return to stock. But due to the EFS issue its still stuck in bootloop, I flashed the stock recovery tar and then the stock rom.
Mmmmm I need to get the efs off the pc onto the phone again without having to have the phone boot
Obvious question, did you do a factory reset in recovery? Also, did you go from an EMG rom back to an earlier version when flashing stock?
You shouldn't need to flash a recovery, a stock rom downloaded from sammobile includes everything you need.
The only way to restore the efs folder in recovery would be to flash a custom recovery, like Philz, and then use AromaFM to copy the files to the phone.
Hi, yes tried the reset but it did nothing still stuck on bootloop. Erm EMG?? I had just put "I9300_Omega_v46.1_XXUFME7_md5_1C591CA15E556884E4B6AFC89E5A682F" on and then went back to stock.
Odd, a full stock flashed using odin should solve the efs mounting problem.
Did you remove kies before using odin? Did odin give any errors?
If in any doubt use this guidance to flash your stock rom, read it carefully and follow each step exactly:
http://forum.xda-developers.com/showthread.php?t=1671969
Which stock rom are you trying to flash?
Im using this one BTU-I9300XXEMG4-20130724164355, I didnt remove Kies didn't know that could cause a problem. Thanks for the link will check that over, I'm just a bit gutted that I backed up as always and I'm still getting the issue ahhhhhhh.
boomboomer said:
Odd, a full stock flashed using odin should solve the efs mounting problem.
Did you remove kies before using odin? Did odin give any errors?
If in any doubt use this guidance to flash your stock rom, read it carefully and follow each step exactly:
http://forum.xda-developers.com/showthread.php?t=1671969
Which stock rom are you trying to flash?
Click to expand...
Click to collapse
You my friend are my hero (also the guy that wrote the guide)................followed the steps and the phone has booted no problem......I can not add my imei back with ktool once rooted again!!!!!
Glad to hear it worked, flashing a full stock rom often fixes the imei problem but if not then you have your backup to restore.
Easiest way to root is CF Auto Root, make sure you follow the guide exactly.
boomboomer said:
Glad to hear it worked, flashing a full stock rom often fixes the imei problem but if not then you have your backup to restore.
Easiest way to root is CF Auto Root, make sure you follow the guide exactly.
Click to expand...
Click to collapse
I might just take a break from messing, the misses gives me the dead eye every time I pick the ohone up now :crying:
One last question to you sir, the firmware of the guide has put me on 4.0.4, and its not letting me update off Kies. Is this because the build is old or not official. If I download the most upto date firmware off sammobile will I have to up date the kernal again too??
model number - GT-I9300
Android version - 4.0.4
baseband - I9300xxle8
Kernel version - 3.0.15-554452-user
build number - IMM76D.I9300XXALE8
cheersagain
Kernel is included
Ideally you should have used the guide to flash the EMG4 rom you'd already downloaded. Don't leave it long on that old firmware as it doesn't protect against SDS.
Oh, don't use kies as it's a waste of time.
boomboomer said:
Ideally you should have used the guide to flash the EMG4 rom you'd already downloaded. Don't leave it long on that old firmware as it doesn't protect against SDS.
Oh, don't use kies as it's a waste of time.
Click to expand...
Click to collapse
Well its all gone a bit strange to be honest, after getting the phone to boot finally I went ahead and flashed the newer firmware I9300XXEMG6_I9300PHNEMG2_I9300CEEMG2_HOME.tar.md5 . The phone went straight back to bootloop!!!
So currently re doing what i did to get it running in the first place, problem is that leaves the phone in factory mode and the ktool says it is restoring my efs but it doesnt seem to do anything!
so after more grief off her im stuck again.
I have writen down PDA:ME7 PHONE:ME7 CSC:ME7 (eur) which i think is off the last working firmware but not sure which one it is!
Now you can get the phone to boot the problem is mostly done. You should find several threads in this forum on restoring the efs and factory mode (the two are related) also about bootloops with corrupt efs partition.
Well tried all of what i can and understand, still nothing! Stuck with the 004999010640000/01 imei, its out of factory mode and everything works bar the network connection. Managed to restock and set counter to No, all official and ready for warrenty fix....that is unless anyone has any ideas.
This thread answers all the efs questions, if you have now flashed an EMG stock then the efs partition is probably corrupt. As you have a backup this shouldn't stop you from getting it working.
http://forum.xda-developers.com/showthread.php?t=2393289
In particular, this post:
http://forum.xda-developers.com/showpost.php?p=44734012&postcount=99
boomboomer said:
This thread answers all the efs questions, if you have now flashed an EMG stock then the efs partition is probably corrupt. As you have a backup this shouldn't stop you from getting it working.
http://forum.xda-developers.com/showthread.php?t=2393289
In particular, this post:
http://forum.xda-developers.com/showpost.php?p=44734012&postcount=99
Click to expand...
Click to collapse
Thanks again for all your help, I had followed these as best i could but no joy. I think I've 100% killed it. Like I say managed t get it back to stock and use the fantastic triangle away package....thus phone is as untouched......so swallowed the I told you so pill off her and took it to the service centre (which happens to only be 3miles from my house bonus). They did all the checks and accepted it under warrenty, down side i just have to wait up to two weeks its return!!!
Lots of lessons learnt, I origionally just wanted to delete the bloat ware and got carried away, thinking I was not a noob and some sort of phone god the roming followed.
Thanks again for all your help, I will read so much more about what to do if I do go down this line again.
Hello,
I tried to upgrade my S2 for Android 4.3 and i did the XWKDD Kernel. I flashed it sucessfully then i went to super click thingy and then rooted it. It was sucessful. After that, it shows the yellow triangle and tried restarting but the same thing. Eventhough after i flashed the kernel and it restarted then it goes to yellow triangle then i rooted it sucessfully. Same story all over again. Help as i need to use my phone!
btw its i9100. SSN- i9100GSMH
Boot into recovery, factory reset/wipe. No recovery ? Back to stock via Odin & start again (re-root your phone & restore backup, or re-flash custom rom/kernel & start again). How ? Get stock rom from Samfirmware, follow flashing instructions in thread stickied near the top of Q&A.
MistahBungle said:
Boot into recovery, factory reset/wipe. No recovery ? Back to stock via Odin & start again (re-root your phone & restore backup, or re-flash custom rom/kernel & start again). How ? Get stock rom from Samfirmware, follow flashing instructions in thread stickied near the top of Q&A.
Click to expand...
Click to collapse
for the stock rom, i am confused as i cant remember which android version is it but it was 4.X.X for sure!
i tried to factory reset and wipe but nope. tried to start over again. same thing. how? how do i put android 4.3??
Forget Android 4.3. Your only focus right now should be getting the phone working normally again.
Go to Samfirmware, download a stock rom for your carrier/country (it doesn't matter which, just not 4.0.4), flash it with Odin. I'm not going to post this again :-/
MistahBungle said:
Forget Android 4.3. Your only focus right now should be getting the phone working normally again.
Go to Samfirmware, download a stock rom for your carrier/country (it doesn't matter which, just not 4.0.4), flash it with Odin. I'm not going to post this again :-/
Click to expand...
Click to collapse
i did download the stock rom and everything is working well thanks to you allthough my contacts are wiped out. i did back up on my computer except i lost the contacts....
so for now, how can i put 4.3 or some custom rom? i am bored staying stock for like 3 years and never rooted it. I mean i had this phone for too long.. and never had a chance to have a new one like S4 etc..
Glad you got it working.
Always, always, always follow the flashing instructions for the rom in question. They're always on the first page of the thread devoted to the rom in Android Development or Original Android Development & they're always very clear/simple.
So head on over to those sections & do some reading/research before you do anything else.
Edit - And the first thing you do after you root your phone (and before you install any custom rom) ? Backup. Everything. Contacts/calendar/etc synced to Google, backup call/SMS logs with TiBu, do a nandroid backup in CWRecovery, and backup your EFS with kTool/similar (keep one copy of this backup on your PC, and another on the external SD card in your phone if you have one). Backup, backup, backup, backup. At least once a week or before you make any major changes to your phone (like flashing a new version of a rom or kernel). That way you don't lose your contacts/other stuff if things go pear shaped.
thanks to u as i followed the instructions via researching haha
Now i have official CM10.2 which i have done with cmw yet i might try for a custom CM10.2 like something to do with hybrid or stuff like that...
But, when i restart or switch on. it still have the yellow triangle then for a few seconds later n it booted to CM which is fine.
Why is the yellow triangle there? have i not done it properly?
Thanks
If it were me, I wouldn't worry about the triangle. You only need to worry about it if you need to make a warranty claim. If you want to get rid of it, read the Triangle Away thread on here.
Hey,
My friend was running a flawless custom rom on his s3. Suddenly, it turns off by itself and the phone is then stuck on boot logo.
1. I tried to factory reset with no luck.
2. I tried to install stock 4.3 with no luck.
3. I tried to install 4.1.2. The phone booted but with no recovery. Then i noticed that imei changed to *0049 and i'm not registered on network (even though it was working well on the custom rom).
4. I tried to upgrade to 4.3, i got succeeded but recovery didnt install.
5. I tried to install the custom rom again but no luck.
6. I tried all patches of modems and kernels and ariza. All Failed.
7. I also tried EFS backup/restore and Failed.
My only concern is to know what made this issue appear all by itself ?? Because i guess we should take it to a mobile repair shop.
One last thing to say is that every time i try to install a software, available space gets low, and even if i delete some files from internal storage the storage wont free up.
Thank you !
get stock 4.3 fom and flash it via Odin (wipe everything before flash). Then flash recovery via odin. then backup efs. then flash custom roms.
downgrade from 4.3 to 4.1.x causes efs to become corrupted
Seems like a corrupt nand. Was it rooted previously when it died the first time?.
Going from 4.3 to 4.1.2 will cause the imei to be lost as the efs encryption changed at 4.3. You cannot go back.
If the phone has a custom rom on it try an official cwm recovery, if not or it doesn't work then proceed to the following:
If you can get the phone into download mode try flashing the stock firmware twice or thrice with a factory reset in between each flash. Do not allow the phone to boot into the os!!. If it attempts to boot to OS after the blue pass in odin then pull the battery out immediately and boot to recovery or download mode respective of what you are doing at the time, resetting or flashing.
If that fails you can then call it a dead phone.
Beamed in by telepathy.
Wow these are new solutions to me..
I really thank you guys and i'll look forward into trying them in any upcoming problems.
Thank you so much for sharing your knowledge
And just to mention, yes the phone was rooted when it went bricked suddenly.
I'd try to flash an official cwm and if it takes then flash back to stock twice with a reset, reroot and leave it as that. Custom roms aren't worth the paper they're written on.
In addition to downgrading from 4.3 to an earlier version, but forgot at the time of writing, you can downgrade but you need an efs backup from the time it was at 4.1.2, which has to be restored but I'm not sure of the process. I couldn't tell you if it has to be restored before flashing, after or both.
Not a lot of people have an efs backup from 4.1.2. I do, but then my phone hasn't acted wierd yet. Sods law.
Kies 2 (not kies 3) can restore the phone but only if it was in original condition. You can try the emergency recovery routine but don't hold your breath.
Beamed in by telepathy.
You're right.. Efs is the only part most of us miss !!
I wrote all of the steps you said in order.. So that if any problem occur ill deal with it based on your info.
Btw do you suggest using KK TW 4.4.4 by back-to-n00t ? Or this wont be considered as a kind of official firmware ?