Related
I bought a fascinate from good ol craiglist for a friend. When I bought it I noticed the original user had already rooted it and installed CM7.
Because I didnt know what he had done to it I decided to start from scratch and used Odin and flashed powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit
After that I flashed cwm4_fixed_for_cm7-ODIN.tar and began getting ICS on this baby (teamhacksung-ota-eng.BUILD2.zip followed by build 11 at the time).
Everything was gravy and I gave the phone to my friend who was a happy panda. Several weeks later he calls and tells me the phone is stuck in recovery, I assume he borked something so I headed over thinking I will just Nandroid the ICS ROM that I set up before I gave it to him.
Funny thing was after rebooting from the Nandroid, the phone goes back to recovery! I was a little confused but assumed that maybe the Nandroid went bad when I backed it up. So I decided to just reflash build 11 again, after the flash was successful i reboot and.... back to recovery?
At this point I was pretty confused, CWM appeared to be working but it wasnt. Nothing was working, not even flashing CM7. The only way I got it to work again was to Odin the powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit again. So that was what I did and got him back to ICS (build 13 this time).
Thinking it was a freak occurence I didnt pay it any mind, until he called me again several weeks later saying its stuck in CWM again!? So I check it out and sure enough it keeps booting to recovery and not able to nandroid or flash anything (even tho it says it does successfully).
At this point I assume its a hardware issue but dont understand what exactly, I bought another on craiglist and will swap with him and further investigate the issue.
I looked around the forums to see if anyone had a similar issue but have not seen anything like this. Anyone have any ideas??
This is most likely caused by doing the three finger reboot on the newer ICS roms. Tell them to pull the battery instead the next time their phone locks up. Also, there is boot loop breaker in the development section.
Sent from my SCH-I500 using xda premium
I assumed that as well, however my friend has no experience with these devices and would never hold down all three buttons for any reason. Both times he had reported that the phone randomly went into recovery on its own.
He could be BSing me of course, but I'll be testing it when I get it back tomorrow and see if I can recreate the scenario.
But I will be including the boot loop breaker file in the SD card and see if that at least makes this phone usable again instead of having to use ODIN every time. So thanks for that info!
Check kernel settings. Sleep Of Death, maybe?
Hi all,
I own a galaxy s2. I'm facing a issue which i've been trying to fix for the past couple of weeks. I tried many threads in this forum, but nothing seems to solve the issue.
This is the issue,
I used to flash custom roms on my device. I used many custom roms including cm9 RC1 and when samsung released the lastest 4.0.4 update i just wanted to chek it out. so I downloaded the generic russian (SER) firmware and flashed it using odin.
After flashing it I was stuck @ boot. i was stuck there for more than 10 mins, so I ended up removing the battery. then I went to samsung recovery(Volume Up+Power+Home) and cleared the cache and user data and rebooted the phone it worked fine. At this time I didn't bother to check whether my IMEI was there but everything worked fine.
After couple of days(without rebooting the device in that time) I droped the phone. battery came off, when I turned on the device again, prohibited mark like thing came in the status bar and there was no service, when I checked the IMEI it was not there.
At this moment I was not sure whether the drop caused the issue or the flashing caused it. I later realized IMEI issue comes because of EFS but sadly I didnt back it up. After diggin for few days I found when flashing one of the custom roms, efs was backed up automatically, I tried restoring it, but it didnt help (Maybe the backup was corrupted )
I followed various threads in this forum but nothing helped me.
Please help me get the IMEI back, I really miss my device :crying:
Shasinda said:
Hi all,
I own a galaxy s2. I'm facing a issue which i've been trying to fix for the past couple of weeks. I tried many threads in this forum, but nothing seems to solve the issue.
This is the issue,
I used to flash custom roms on my device. I used many custom roms including cm9 RC1 and when samsung released the lastest 4.0.4 update i just wanted to chek it out. so I downloaded the generic russian (SER) firmware and flashed it using odin.
After flashing it I was stuck @ boot. i was stuck there for more than 10 mins, so I ended up removing the battery. then I went to samsung recovery(Volume Up+Power+Home) and cleared the cache and user data and rebooted the phone it worked fine. At this time I didn't bother to check whether my IMEI was there but everything worked fine.
After couple of days(without rebooting the device in that time) I droped the phone. battery came off, when I turned on the device again, prohibited mark like thing came in the status bar and there was no service, when I checked the IMEI it was not there.
At this moment I was not sure whether the drop caused the issue or the flashing caused it. I later realized IMEI issue comes because of EFS but sadly I didnt back it up. After diggin for few days I found when flashing one of the custom roms, efs was backed up automatically, I tried restoring it, but it didnt help (Maybe the backup was corrupted )
I followed various threads in this forum but nothing helped me.
Please help me get the IMEI back, I really miss my device :crying:
Click to expand...
Click to collapse
hi there
you said that you have the backup of your EFS Folder, what you need to do is follow the steps in this thread
http://forum.xda-developers.com/showthread.php?t=1264021
its recover your imei in nine steps
my imei was lost as well and i recovered my imei following those stesp, its a great guide if you already have the backup of your EFS Folder
cheers
fr3nlysmil3 said:
hi there
you said that you have the backup of your EFS Folder, what you need to do is follow the steps in this thread
http://forum.xda-developers.com/showthread.php?t=1264021
its recover your imei in nine steps
my imei was lost as well and i recovered my imei following those stesp, its a great guide if you already have the backup of your EFS Folder
cheers
Click to expand...
Click to collapse
I tried this also, but it didnt solve my issue :crying:
...
I once had a similar problem.
My imei went lost because of a rom upgrade and I DIDN'T have a backup..
I solved the problem by flashing a stock rom (any samsung stock rom will do) with ODIN.
I am not sure what happened, but it looked like that the nv_data folder was "re-generated" and I got my IMEI back.
Now I have a copy of the folder in every storage media around my house
MistahBungle said:
If you have a backup, then you should be able to recover it. There are tons of threads on here with instructions on how to restore an EFS backup. Search (if you want it fixed, that is. If you don't want it fixed, keep posting to this thread in the hope someone spoonfeeds you. Might be waiting a while tho).
Click to expand...
Click to collapse
I tried almost every thread here in xda about restoring, tried GSII_repair, kTool to restore it but none of them recovered the IMEI. I did not made a backup of efs but when I installed the Hydra H2O ICS Rom for GS2 it made the backup i guess, because a file called "efs-backup.tar.gz" was in a folder called .hydra inside the sd card.
does the drop of the device has anything to do with the erased IMEI?
robdpi said:
I once had a similar problem.
My imei went lost because of a rom upgrade and I DIDN'T have a backup..
I solved the problem by flashing a stock rom (any samsung stock rom will do) with ODIN.
I am not sure what happened, but it looked like that the nv_data folder was "re-generated" and I got my IMEI back.
Now I have a copy of the folder in every storage media around my house
Click to expand...
Click to collapse
I have installed stock roms from samsung using Odin, but then I discovered that efs folder get unmounted everytime I install the stock rom, phone just starts after flashing without android setup wizard, also when I long press power button, menu wont appear, device just shut down, after I restore the efs from the backup i have, and mount the efs using the CWM recovery would bring back the power button long press menu. everything else working except for Mobile Networks. and imei/baseband shows unknown
Drop Caused this problem
Hi all,
Thank you for replying on this thread and helped me figured out my problem, I have contacted Odia and he thinks that dropping the phone damaged the baseband chip inside the main board, not a flashing of the roms or efs folder issue. i have only 2 options either replace the whole board paying LKR 35,000 (New s2 costs only LKR 65,000) or use it as a MP3 player :crying:
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?
Hello everyone,
I have SGS II (I9100) for about 2 years now. Im still on GB 2.3.4 KI4 (yeah dont ask why thats not my main issue here), rooted while ago with ZergRush exploit, and running HellCat's kernel. About two months ago, I fire up my phone and saw that I have no network. Went to About phone noticed that there is no baseband set, did *#06# and saw that my IMEI is empty. Luckily I had my EFS backed up with kTool, restored and was good to go. Today it happened to me again. Again restored with kTool and still good to go. So here is some facts regarding it, and I would like to know what might have causing it since I really dont update ROM's every 24 hours.
- 2 yearish old phone
- custom kernel with CWM
- did only one update from 2.3.2 (i think, cant recall what ROM was it shipped with) to 2.3.4
- didnt do factory reset after ROM upgrade
- happened before with soon-to-be-dead battery, but also with new one I got couple of days ago
- had running Dr.Web AV pretty much last year or so (I think only resident program running in background apart from loads of bloatware from Samsung)
Any info is more than welcomed since even I do have EFS backup, somehow I dont believe this is "expected behavior"...
Shall I (finally) upgrade to JB via Odin(Mobile Odin Pro?) and do factory reset/root after?
Can it be bad external card? Can internal memory can somehow be corrupted like hard drive with bad sectors or something? Really any info is more than welcomed.
Thank in advance
Here you go http://bit.ly/1bx9zPv
If you have actually read my post, before sending me to google, you would actually realized that I have EFS backup, and that I have recovered IMEI twice with kTool... Question is not HOW, but WHY. There is difference there. But hey, thanks for most ignorant reply you can actually think of. GZ you have just won the interwebs!
Hi,
i dont think its an hardware problem. I think that problem comes with your longtime running system und maybe that you didnt do a reset. Maybe you should finally upgrade to Jelly Bean - best way with Odin and a complete full wipe (save your data befor )
But keep cool, Jelly Bean looks very different to Gingerbread
Andi
andi2398 said:
Hi,
i dont think its an hardware problem. I think that problem comes with your longtime running system und maybe that you didnt do a reset. Maybe you should finally upgrade to Jelly Bean - best way with Odin and a complete full wipe (save your data befor )
But keep cool, Jelly Bean looks very different to Gingerbread
Andi
Click to expand...
Click to collapse
Thanks for the reply Andi. Actually I did that, and so far there is no issues with it (4.1.2). Did full wipe and so far all looking good, and I really like how it handles now. Still have EFS backup, just in case
Hi,
EFS Backup ist ever ever the first step after rooting don´t understand some guys who didnt do that or forget it.
Did you 4.1.2 root? If not, i recommed the philz kernel easy way, no triangle
have a nice day
Andi
andi2398 said:
Hi,
EFS Backup ist ever ever the first step after rooting don´t understand some guys who didnt do that or forget it.
Did you 4.1.2 root? If not, i recommed the philz kernel easy way, no triangle
have a nice day
Andi
Click to expand...
Click to collapse
Actually had some issues there... on 2.3.3 I had Hellcat kernel, wanted BLN, and some custom UOT Kitchen mods. Did full wipe from phone, and got it stucked in bootloop.
Let i a while, then said, **** it, and used Odin to flash 4.1.2 in from download mode. Stock ROM, so no binary counter issues. Started to boot up, showed me language selection and then crashed into bootloop... Assuming that it didnt finished wipe previously... Couldnt even got in into recovery (or was too stressed, but its 3 keys to press, dunno). Then, switched to download mode, flashed 4.0.3 that I had lying around, went to recovery, did wipe, and it booted up. Played with it, and in one point I said, "meh, Ill leave it on ICS"... Then something else said "You wuss! It took you 2 years to flash damn thing, and now you will stick to ICS?!?". Downloaded Mobile Odin Pro that I have purchased a while ago, flagged autoroot and flashed 4.1.2 from it. Again wiped it (just in case) and it booted up nicely. About 3 hours of stress, googling and browsing XDA Wife actually told my kid to stay away from me )
Then, wanted again BLN and thats the reason i skipped Philz and went for Siyah kernel instead. All nice and dandy so far *knock on the wood*
Still have EFS backup on numerous locations ofc
Cheers mate and thanks for participating
Hi guys, firstly I'd just like to say I have followed all the protocol that is required on here and been reading and researching/ applying fixes for the past few days now. I have tried to help myself as far as i possibly can but i am still having no luck and i don't think too many people have had the exact similar issue after reading all the other threads that are similar to my issue.
with some of the fixes it is my first time using them as i have never needed to in the past, so bare with me if my level of understanding isn't as great in some departments.
Now onto the issue:
I own a galaxy s3 i9300 and it has been rooted on stock rom since day 1 about a year ago. A few days ago my phone battery died, and when connnected to the charger it had this grey icon with a circle. It wouldn't boot up either so after searching on the net i thought i would listen to the advice of clearing the cache etc etc but this didn't work and neither did the wipe data/dalvik in CWM.
So i reflashed a stock jellybean rom and it worked fine.
It was then at this stage i thought i might as well upgade to a custom rom as every galaxy i had owned before i had done it on, and my current Note tablet is also running custom rom.
I first loaded a stock 4.3 rom and then flashed the slimbean 4.3 with gapps ...and it worked perfectly. I found a couple of issues with the browser which i use a lot so i downgraded to a 4.2.2 version of slimbean with gapps and this made the browser really fast again and all was perfect.
I had been using this for two days or so and everything was smooth, including charging etc until one night it had that same grey battery icon again with the circle and would get stuck booting at the samsung logo.
So as this had happened before i thought i would just flash a stock rom....this is where it all started going mad
Bearing in mind, every flash i always did it properly and wiped cache/dalvik cache and wiped data three times for each one just to make sure as i didnt have anything of value so wanted a fresh wipe each time and didnt need to back anything up.
now before i get flamed i realise i made a huge stupid error in not backing up my efs folder before hand as i had done with every previous phone but because i was under pressure to get it working it skipped my mind totally.
So i flashed a stock jellybean 4.2.2 rom and still bootloop with the EFS not found invalid argument error
i flashed a 4.3
i flashed a 4.1
i flashed a different 4.1
i flashed a different 4.2
i tried loads but nothing worked
so after reading that this would not help as it doesnt touch the efs i looked into fixes that others had done
i tried to follow this http://forum.xda-developers.com/showthread.php?t=2197515
So i downloaded efs professional / adb tool
i downloaded busybox
and cwm was already on the phone but i downloaded philz cm incase i needed that too
now as the phone doesn't turn boot up i can't access anything, i can only access download mode and CWM.
When i open efs professional it says current device offline, turn on allow usb debugging to confirm your phones RSA fingerprint and click ok.
I have no idea what to do about that because i can't get into the phone.
Regarding busybox i have no idea how to get that to install on the phone, i have tried writing some stuff to push it in the adb shell (but because its my first time using adb shell and command prompt i have no idea if i am doing it correctly). Can you install it with odin?
also regarding adb shell i followed the guide http://forum.xda-developers.com/showthread.php?t=2197515 and got into [email protected] and SU....and then when on the phone in cwm i clicked mount efs...and obviously it failed. I went into the log as said and /dev/block/mmcblk0p3 was the file it failed to mount
the thing is everything after that step doesnt work, as i can't create an image of mmcblk0p3 as it says it can't find it as if it doesnt exist.
So im screwed as it effectively is saying i don't even have that file or efs folder i think?
The thing is i never had any issue with losing imei or anything like that at all and this just happpened out of the blue without me doing anything as such
any ideas?.....would be HUGELY appreciative for anyone willing to take the time out and help me with this as i'm not sure i can explore any more avenues on my own with my limited knowledge and at the same time don't want to give up.
PS. I also have access to a galaxy s3 i9305 ....and can possibly try and source another i9300 from a family member IF this helps in any way or makes life easier?
Stickied faqs and guides .
No IME/ EFS
service centre repair is your best choice if you have read and tried the stickied fixes .
Reads like efs partition corrupted and your phone was already suffering with nand memory issues.
There is no substitute for an efs backup, you cannot recreate the unique information it contained.
Take it to a reputable repair centre, they will be able to get it back to normal, but you are still left with why it keeps corrupting -which may require a new motherboard.
Sent from my GT-I9300 using Tapatalk
Mod Edit
Please refer to ,and post in the stickies in the General section.
Thread closed
malybru
Forum Moderator