Hello everyone! ^^
My phone now can not boot up when i press and hold power button. Here is my work before that:
- First, i use Odin to flash stock ICS I9100DXLPF
- Then, reboot to stock recovery, flash cwm (on sdcard) and use cwm flash superuser for root the phone and remove yeallow icon
- When completed, i reset the phone -> all worked
- Next, i reboot to stock recovery and flash cwm (on sdcard) again and wipe data/factory reset (i want flash custom ROM)
-> I wait for 10' but this cwm can't wipe
- Then, i press and hold power button for reboot -> And the phone poweroff, and never boot up again
Some questions:
- Does my phone got bricked? And how do it can brick, when i don't wipe system, only wipe factory/reset?
I need your help, friends
- I have efsbackup, if i change the motherboard, can i use my backed up efs for apply old imei? ^^
- If i buy a new s2 phone (but lost IMEI, so that dont hear the SIM), can i use efsbackup to apply my old imei for new phone?
Krensii said:
Hello everyone! ^^
My phone now can not boot up when i press and hold power button. Here is my work before that:
- First, i use Odin to flash stock ICS I9100DXLPF
- Then, reboot to stock recovery, flash cwm (on sdcard) and use cwm flash superuser for root the phone and remove yeallow icon
- When completed, i reset the phone -> all worked
- Next, i reboot to stock recovery and flash cwm (on sdcard) again and wipe data/factory reset (i want flash custom ROM)
-> I wait for 10' but this cwm can't wipe
- Then, i press and hold power button for reboot -> And the phone poweroff, and never boot up again
A question: Does my phone got bricked? And how do it can brick, when i don't wipe system, only wipe factory/reset?
I need your help, friends
Click to expand...
Click to collapse
Sounds like you may have had the unfortunate eMMC superbrick bug which hard-bricks your phone beyond saving (even by JTAG) this happens if you were one of the unfortunate ones (like me). If you running stock 4.0.4 kernal then this is certainly what has happened as you tried to wipe... give me a few mins i will get you thread
edit: couldnt find thread but i am 99% sure. What kernal were you running?
rsr1 said:
Sounds like you may have had the unfortunate eMMC superbrick bug which hard-bricks your phone beyond saving (even by JTAG) this happens if you were one of the unfortunate ones (like me). If you running stock 4.0.4 kernal then this is certainly what has happened as you tried to wipe... give me a few mins i will get you thread
edit: couldnt find thread but i am 99% sure. What kernal were you running?
Click to expand...
Click to collapse
Im using stock kernel of Stock ICS ROM (4.0.4). I just rooted, removed yellow icon...by cwm only, on sdcard
(This cwm independent work, and dont need custom kernel )
What can i do for save my phone? Thank bro
Krensii said:
Im using stock kernel of Stock ICS ROM (4.0.4). I just rooted, removed yellow icon...by cwm only, on sdcard
(This cwm independent work, and dont need custom kernel )
What can i do for save my phone? Thank bro
Click to expand...
Click to collapse
thanks for the quick reply..
i had same problem and didn't realize at first and sent it in for JTAG but it cannot be fixed..
ONLY option now is motherboard replacement.. if you still have Samsung warranty you will be fine as they cannot tell if you modified the phone because they change the whole board
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from the little guy
i have been monitoring many of your posts lately and they are all garbage. stop commenting useless stuff for post count moron
Are you stalking me?
Lol, why would I want to increase my post count? Think about it...WHY?
Nothing good comes to mind?
Let me spell it for you:
I.A.M.H.A.V.I.N.G.F.U.N.
And trying helping while I'm at it too.
Now go read something funny.
Sent from the little guy
rsr1 said:
thanks for the quick reply..
i had same problem and didn't realize at first and sent it in for JTAG but it cannot be fixed..
ONLY option now is motherboard replacement.. if you still have Samsung warranty you will be fine as they cannot tell if you modified the phone because they change the whole board
Click to expand...
Click to collapse
I have efsbackup, if i change the motherboard, can i use my backed up efs for apply old imei? ^^
Update some questions in #1
No, you can't. Your device should have the same IMEI if it's done by an authorised repairer. If it's done by someone who isn't an authorised repairer, who knows what will happen. One thing is for certain tho, if you try and restore your EFS backup when you get your phone fixed, there's a fair chance you'll bork it.
Don't try it.
Edit - No you cannot restore an EFS backup from one phone to another phone. The IMEI is a unique identifier that identifies a specific (one) device. Changing IMEI's is illegal in most countries, I suggest you stop talking about same or mods will close your thread (Per XDA rule "Don't do/say anything that gets us 'in trouble'")
Extra edit - @OP:- I've done a bit more rummaging through my SGS2 bookmarks, so far as whether you keep your existing IMEI or whether you get a new one when the board is replaced, it seems to vary a bit. Most old examples I could dig up where the person posted after they got the phone back kept their existing IMEI's, and a couple say they got new ones. Hard to say whether it's a country to country thing (seems that way) or whether it varies even amongst individual authorised repairers in the same country (less likely).
Regardless of what happens in your case, why would it matter whether you had the existing IMEI or a new one ? It makes absolutely no difference to you as a phone user, and would only make a difference to someone if there was some dodginess or 'shenanigans' going on. Rest assured, if your phone is fixed by an authorised repair, it will work exactly as it did before you borked it (minus the data you had in the internal storage, obviously).
Extra extra edit () - Tho if you get a board from a 'donor' phone & replace it yourself/get a local mobile shop to do it, you'll end up with the IMEI on that board. Again, I don't really recommend attempting to restore an EFS backup from another phone (And talking about same on here is nada).
MistahBungle said:
No, you can't. Your device should have the same IMEI if it's done by an authorised repairer. If it's done by someone who isn't an authorised repairer, who knows what will happen. One thing is for certain tho, if you try and restore your EFS backup when you get your phone fixed, there's a fair chance you'll bork it.
Don't try it.
Edit - No you cannot restore an EFS backup from one phone to another phone. The IMEI is a unique identifier that identifies a specific (one) device. Changing IMEI's is illegal in most countries, I suggest you stop talking about same or mods will close your thread (Per XDA rule "Don't do/say anything that gets us 'in trouble'")
Extra edit - @OP:- I've done a bit more rummaging through my SGS2 bookmarks, so far as whether you keep your existing IMEI or whether you get a new one when the board is replaced, it seems to vary a bit. Most old examples I could dig up where the person posted after they got the phone back kept their existing IMEI's, and a couple say they got new ones. Hard to say whether it's a country to country thing (seems that way) or whether it varies even amongst individual authorised repairers in the same country (less likely).
Regardless of what happens in your case, why would it matter whether you had the existing IMEI or a new one ? It makes absolutely no difference to you as a phone user, and would only make a difference to someone if there was some dodginess or 'shenanigans' going on. Rest assured, if your phone is fixed by an authorised repair, it will work exactly as it did before you borked it (minus the data you had in the internal storage, obviously).
Click to expand...
Click to collapse
Thank you sir, now i know that is not good thing. I'll dont talk about it again
You're welcome I hope having it repaired goes smoothly/quickly for you.
Related
This HOWTO is for users who want to switch from stock LG 2.3.3 ROM to CM7 or other older ROMs that are NOT based LG's on v20? ROM or vice versa. Eventually, all new ROMs will switch to new baseband by default, so it is useful as well if you want to avoid the complete KDZ/Russian way flash which wipes everything.
Step 1:
- Download (see attachment) P500-v10E-baseband.7z or P500-v20G-baseband.7z
- unzip it via 7-Zip
Do NOT proceed until you fully understand the following:
- P500-v20G-baseband.7z is for official v20[abdg....] ROMs and ROMs based upon it (e.g., GingerLOL, v20G stock ROM, customized v20G ROM, 0x0v3rfl0w ROM and GingerCriccoROM).
- P500-v10E-baseband.7z is for all other ROMs.
Click to expand...
Click to collapse
Step 2:
- Browse to the folder where you unpacked the 7z and run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Do NOT mess with anything else. Leave everything else as is.
- Close the window
- Click Download button
- Let it do the job. It will backup your IMEI and MACs to .NV2 file, reboot your phone to emergency mode, flash recovery, reboot and restore the NV2 backup.
MUSTREAD!!!
Do NOT interrupt it or disconnect your phone until it says "Download complete"! - Do NOT delete the NV2 backup!
I repeat, no matter what do NOT interrupt the process until the NV2 restore is complete. It will take some time after the first reboot. Even if your phone appears to be booting normally to the OS, do NOT interrupt the process and do NOT disconnect the USB cable until the NV2 is restored and phone rebooted once again and the utility says "Download complete"!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Step 3:
Congratulations. You are done! Now you can enjoy working GSM if you have installed the right baseband for your ROM.
Q: I am confused. Which baseband do I need?!?! I do not understand any of this!!!
A: Kindly re-read "Step 1: Do NOT proceed until you fully understand the following... " section. If you still do not understand after re-reading it a couple of times, then simply continue using your phone, do NOT flash anything and generally go on with your life. This guide is NOT for you. Kindly do NOT ask which baseband you should use here on the thread. The instructions will be updated if/when some ROM switches to the new v20g baseband by default.
Q: This appears dangerous. Is there an alternative for switching between ROMs based on LG's GB and others like CM7?
A: Life is dangerous. If you want to flash CM7-based ROM (like mik_os' CyanogenMod 7, andy572's Gingerbread ROM or Noejn's void. #forever) and have the new baseband already, there is a baseband fix by mik_os. However, due to a bug, data (2G/3G) unfortunately does not work at the moment. Wait for a new fix. If you have already flashed the mik's patch and want to undo it, flash REVERT-new-baseband-patch-signed.zip - you do not need to reflash the whole ROM. (Note: Only tested with mik's ROM! Do not complain if it does not work elsewhere.)
Q: But - I am a genius and came up with a better way to flash baseband! This one sucks!
A: If you come up with a way to flash the baseband via ZIP from recovery, kindly share it.
Q: My phone is not detected by the LGMDP-v1.5.exe utility! What to do?
A: Run devmgmt.msc (Device Manager), go to Ports (COM and LPT) and disable LGE Virtual Modem there. Disconnect and reconnect your phone and try again.
Q: I run the utility and the initial NV2 backup fails. What to do?
A: Disable the LGE virtual modem (see above), disconnect and reconnect the phone and try again. If it still fails, reboot your computer first before trying again. If it still fails, try to boot the phone to recovery (Home + VolDown + Power) or even emergency (Back + VolUp + Power) mode.
Q: Still have issues with phone not being detected or initial NV2 backup failing! Argh!
A: First of all, do NOT connect your phone to an USB hub with other devices connected! There will not be sufficient power for reliable phone connection. Otherwise, I would suggest trying this on another computer, or waiting for a better day. At minimum, clean all LGE drivers (set DEVMGR_SHOW_NONPRESENT_DEVICES to 1 in your Windows environment (kindly Google it), in device manager enable "Show hidden devices", uninstall all Android/LGE-related drivers, reboot your computer, reinstall the drivers.) Then try again. Anything else - you are on your own with high chances of bricking your phone.
Q: How do I know it worked?
A: If everything worked, you will have a working GSM (calls, 2G/3G data) with the proper ROM installed.. On stock ROMs, you can check the baseband version via hidden LG menu. It will show AMSS6150 if you flashed v20G baseband. If you see AMSS6038, then you have a baseband from v20[ABCD...] versions. If you see anything else, you have a baseband from v10? ROM. LGMDP utility also shows which ROM version does the baseband come from (see screenshot attached). Note (CM7 users): V07u-000-000-MAR-23-2009 is NOT your baseband version but some irrelevant CM7 crap.
Q: I would like to flash a custom recovery at the same time (I am on stock unrooted ROM, or just want to switch to another one, or whatever). Do I need to flash twice?
A: No, absolutely not. You can just download the recovery of your choice, stick recovery.img to the same directory where you have unpacked the baseband and it will get picked up and flashed automagically by the LGMDP utility! Chances to brick your phone reduced by 50% this way!
Q: I am not a moron! Did everything right but still have no GSM! What gives?!
A: You need to flash the right ROM for your baseband. Have you done that already (see the "Do NOT proceed" section)?
Q: I screwed big time, did not read the instructions and I now have no IMEI!!!! No GSM!!!!! My phone is useless!!!! You suck!!!!
A: You did not delete the backup, did you? If not, you can try restoring it via the utility. Otherwise - congratulations, you are a proud owner of a shiny hi-tech brick now. Go to LG service center and tell them that Error ID-10-T occured when using the phone.
--- reserved ---
Which file should i flash if i want to switch to cm7? If i have to flash p500 v20g baseband to get back to cm7, the name seems to be a misnomer.
Sent from my LG-P500 using Tapatalk
Do NOT proceed until you fully understand the following:
...
If you want to flash CM7-based ROM (like mik_os' CyanogenMod 7, andy572's Gingerbread ROM or Noejn's void. #forever) and have the new baseband already...
Click to expand...
Click to collapse
FAIL!
I am asking what to flash to come back to cm? Because your thread starts with "for those who want to come back to cm".
Sent from my LG-P500 using Tapatalk
lekhwani said:
I am asking what to flash to come back to cm? Because your thread starts with "for those who want to come back to cm".
Click to expand...
Click to collapse
Or vice versa. Look. If you do not understand the pretty much ID-10-T proof instructions, you simply do NOT flash anything. The instructions are explaining your question in great detail. If you are confused, get someone who understands English better to explain it to you. Read it AGAIN!!!
Similar noise is something that I will not tolerate on this thread. I have spent 1 hour of my time writing this howto (plus many more hours while testing this with different ROMs) and you come, fail at the first sentence and go flood this thread with completely ridiculous questions. For sure I am piss*d off like hell.
Thx again, another "flashing new roms problem" solved!
+1 dok
doktornotor said:
Or vice versa. Look. If you do not understand the pretty much ID-10-T proof instructions, you simply do NOT flash anything. The instructions are explaining your question in great detail. If you are confused, get someone who understands English better to explain it to you. Read it AGAIN!!!
Similar noise is something that I will not tolerate on this thread. I have spent 1 hour of my time writing this howto (plus many more hours while testing this with different ROMs) and you come, fail at the first sentence and go flood this thread with completely ridiculous questions. For sure I am piss*d off like hell.
Click to expand...
Click to collapse
LOL!! Life is tough mate!!! and this world isn't perfect either,
Back on Topic .... Will try this out and post results
Thanks
Yo! Really needed this (for the N00B repo I mean )
BTW still playing around with RIL files for making Gingerbread work on froyo baseband
And I like ID-10-T hahaha
ciaox said:
BTW still playing around with RIL files for making Gingerbread work on froyo baseband
Click to expand...
Click to collapse
While at it, perhaps you could fix mik's patch to have working data?
doktornotor said:
While at it, perhaps you could fix mik's patch to have working data?
Click to expand...
Click to collapse
Will look
Sorry dok, for the confusion. I had completely forgotten that v10x are froyo versions. (I was on cm since february)
Btw, you should move this guide to development section. Great work, anyways.
Sent from my LG-P500 using Tapatalk
Doktornotor is doing exellent job by writing these guides especially this one. I hear many newbie people getting their phones bricked. It a very risky precedure so do be carefull. Follow the guides to the letter and only when you completely understand the whole precedure. Keep up the good work dok
After the backup, my phone goes into emergency mode but the program keep saying checking and nothing happens...
onlymeipse said:
After the backup, my phone goes into emergency mode but the program keep saying checking and nothing happens...
Click to expand...
Click to collapse
Bad day. See the FAQ
Disabled the virtual modem? It it has not started flashing yet, might try to kill it via task manager and rerun.
D: stuck on LG logo if importing these ril files. BTW some files weren't already there
Lookin' into mik's fix,and taking libs' name from there yo
BTW agree with mprou. Doktornotor is one of the best forum members ever
ciaox said:
D: stuck on LG logo if importing these ril files.
Click to expand...
Click to collapse
Hmmmm, promissing. Looks like you are almost there, LOL.
doktornotor said:
Hmmmm, promissing. Looks like you are almost there, LOL.
Click to expand...
Click to collapse
O RLY?
And btw that v70u-000-MAR-23-2009 or whatever appears in Sense too
Sent from my LG-P500 using XDA Premium App
ciaox said:
And btw that v70u-000-MAR-23-2009 or whatever appears in Sense too
Click to expand...
Click to collapse
For this baseband version detection, I tried to make LgHiddenMenu.apk work on CM7 and miserably failed... It really has useful **** incl. the HW tests but I fail with Java altogether (oh, I should have said that Java fails )
BTW, that v70u-000-MAR-23-2009 - I suspect that nonsense is hardcoded somewhere in the sources, makes zero sense.
Lite'ning ROM v6.1
12/20/2011 - ROM hasn't been updated, but due to some users not having much luck with the included stock modem I've added a CWM flashable UCKK6 modem. I've also added the stock for those that need/want it for some reason. The download links are available at the bottom of this post.
11/27/2011 - Updated with haptic fix (credit to amtrakcn) and Entropy512's latest kernel (11/23/2011). Download link at the bottom has been updated to this one. Enjoy!
11/12/2011 - Updated image with fixed root!
The previous image was almost impossible to get root working. On the surface it was installed, but wouldn't / couldn't gain root access. After many attempts I finally decided to build the port from scratch again. Fixed a couple of file issues, build.prop edits, script tweaks, csc, etc. The result is better WIFI establishment and root that works from install.
This time I didn't use Hellraiser files, but definitely continue to use Entropy512's awesome kernel. No issues with Hellraiser as I've used it to Hellraise other I9100 ROM's without issue, I just didn't need its files in this go around. You should check Hellraiser out. It is an awesome tool.
This ROM is a port of Lite'ning Rom v6.1 XXKH3 found here made for the SGSII I9100. This is a single CWM install of the ROM.
New download link is at the bottom of this post.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit and thanks to LitePro for his image source, and to Entropy512 for his awesome kernel!
Donations are appreciated, but not required. Thanks is good enough
Save the Zip to your internal SD Card
Boot into CWM
Highly recommended doing a format /data in Mounts and Storage
Do a install zip from sdcard
Point to the downloaded Zip file
Install the Zip package
This CWM package will wipe your cache, system and Davlik-cache for you
Download link: (11/27/2011)
http://www.multiupload.com/74QB78HAI3
Modem downloads (12/20/2011)
UCKK6 Modem
UCKH7 Modem stock
What good is a CWM package if you don't have CWM?
CWM = ClockWork Mod
Note: Your phone needs to be rooted for a non-Odin install. There are many threads in this forum on how to root so I won't get into it here.
Now you need to obtain a kernel that has CWM included. I recommend the latest kernel from Entropy512's thread located here.
You'll want to extract the zImage file out of the Zip and save it on your computer.
If you have the Android SDK installed and working on your computer then save the zImage in its tools directory and then type the following command from this location:
Code:
adb push zImage /sdcard/zImage
Otherwise you'll want to plugin your phone to your computers USB connection and paste the zImage file in the root of your internal SD Card.
Next you need to flash the kernel.
Via ADB (press Enter after each line):
Code:
adb shell
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Via a Terminal Emulator installed on your phone (If you don't have one download "Android Terminal Emulator" from the Market and install it. It's free):
Code:
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Reboot.
Note that in the above two code examples when you type su you'll get a prompt to allow the "Superuser Request" if its the first time you invoke it from either program.
To boot into CWM in ADB type:
Code:
adb reboot recovery
Or, unplug your USB cable if plugged in, and press and hold vol UP + vol DOWN + Power buttons. Wait until it reboots and you see the Samsung Galaxy S II boot screen and release all 3 buttons. This should place you in your CWM menu.
Doing it this way should keep you from getting an exclamation point on your boot screen which is the main reason why I explained how to do this in this manner. If, by chance, you still get an exclamation point or already had one to begin with the only option I can think of is to use a jig. Not that a jig isn't a good thing to have anyways. Any ROM you flash from within CWM will not be added to your Custom Image count and will not produce the annoying exclamation point on the boot screen.
Absolutely first thing you want to do is boot into CWM.
As of this writing, press the Home button to choose an entry and press your Power button or the back button to go back to the previous screen.
Go to: backup and restore
Choose Backup
This will take a few minutes, but is well worth it. Now if you ever mess up your install you can always boot into CWM and restore the image you backed up. This, however, doesn't protect you from flashing bad bootloaders so word to the wise... DO NOT FLASH BOOTLOADERS!!! At this point and time there is no need to.
Reserved for awesomeness
_______________________
Fresh Install:
Home button has a bit more of a delay to it. - Fixed
Quite a few services running.
Broke my Root. - Fixed
I would recommend someone putting more than the 10 minutes I did into this ROM.
Going back to UnNamed, dont have to the time to mess around too much. Getting late, and Skyrim is coming...
I wont be using this rom but wanted to give serious props for getting this working! Awesome job to everyone involved!!
Sent from my SAMSUNG-SGH-I777 using XDA App
Sweet... wouldn't mind giving it a shot. Thanks for sharing
Is this a sign that we'll be seeing more OGSGS2 ROMs coming over? How hard was it to port?
Sent from my SAMSUNG-SGH-I777 using XDA App
i was thinking about installing this but ive read that the dev who started this, LITEPRO, hasnt updated the rom for a while now. abandoned? will we get new updates?
simpl3lang said:
i was thinking about installing this but ive read that the dev who started this, LITEPRO, hasnt updated the rom for a while now. abandoned? will we get new updates?
Click to expand...
Click to collapse
While I cannot speak for LITEPRO, his last post on XDA being this past August... it's possible that he got burnt out (easy to do) and taking an extended break. I believe we'll see him again. Wherever he is now I hope he's doing well.
As far as updates I will do what I can to add updates as they come about and they provide a benefit to the ROM.
Thanks !!!
Cozmo1 said:
While I cannot speak for LITEPRO, his last post on XDA being this past August... it's possible that he got burnt out (easy to do) and taking an extended break. I believe we'll see him again. Wherever he is now I hope he's doing well.
As far as updates I will do what I can to add updates as they come about and they provide a benefit to the ROM.
Click to expand...
Click to collapse
backing up right now to have a go at it.
when you get the time have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1334124
it seems someone has continued to tweak and update the litening rom. what do you think?
downloading now. Reporting back soon.
I was waiting for something like this to come along
Sent from my SAMSUNG-SGH-I777 using XDA App
cwc3 said:
Fresh Install:
Home button has a bit more of a delay to it.
Quite a few services running.
Broke my Root.
Click to expand...
Click to collapse
While initially the home button does have a little lag to it didn't seem to persist after using it a little bit. However, I do recall reading that there was a fix for the issue. I will look into it.
It does have many processes listed in the background, but I didn't see it being different than a standard ROM install with a basic selection of apps. Mine currently has 59 in the background, but only 4 in actual use. It's how Linux based systems handle processes and it tends to do a real good job which is why task killers are frowned upon. So I tend to not be concerned with background processes, but more with how the battery consumption is on the ROM. It was rather good in that.
I installed this ROM several times in my testings of it and never had my root broken. I could've just been lucky. It comes with Entropy's daily driver kernel which includes root injected in initramfs as well as CWM. Still, strange things can happen. Did you wipe /data before installing, by chance?
Yea, wiped data first. Its all good. I probably should of flashed twice to be sure. If Skyrim wasn't coming out tomorrow, I would tweak this ROM to my liking then give it a proper test.
For the brief 10 minutes I used it, seemed fairly nice. Only thing that went wrong was the root, which would of been a quick fix I'm sure. I will come back at it in a couple years when I am bored of Skyrim.
cwc3 said:
Yea, wiped data first. Its all good. I probably should of flashed twice to be sure. If Skyrim wasn't coming out tomorrow, I would tweak this ROM to my liking then give it a proper test.
For the brief 10 minutes I used it, seemed fairly nice. Only thing that went wrong was the root, which would of been a quick fix I'm sure. I will come back at it in a couple years when I am bored of Skyrim.
Click to expand...
Click to collapse
LoL - I hear you. I can guarantee you that once Diablo 3 comes out my time on XDA will be severely cut
root not working here. great rom though. fast and smooth.
about to test. if you lost root, wouldn't installing entropy512 kernel fix it? let me try that for you
you think you could fix the home button haptic? its not a big deal but itd be nice lol
Also wifi wasn't working for me so I decided to nandroid back to UnNamed for now
confirming update of kernel bb and su did not give root. I was wrong, but will check back!
This is interesting. On the surface it looks to be rooted, but when you actually try using root capabilities it doesn't work. Not even when flashing a new rooted kernel. This will need some investigation to provide a fix. Will work on it tomorrow after work.
Hi,
Another Noob bricked his phone here SGS2 UK i9100.
I spent hours and hours reading all the FAQ's, various How To's but obviously not well enough although thought I had.
Im normally quite competent at things like this, dating back to early days chipping playstation 1's etc, done all sorts over the years without a hiccup. Had to fail sometime!
After the failed attempt, I suspect I may have flashed a custom ROM not compatible with the stock Kernel????
I rooted my i9100 using Chainfire's method:
[30.10.2012][CF-Root 5.6] K**,LA*,LP-126BHJQ73SC89DEFWGKIQOTUXY,LQ-5B - su+bb+CWM4/5
All went fine, root access, SU etc..
I then tried installing a custom ROM:
[ROM][4.2.1]Slim Bean - I9100 [Beta 2]
Followed the relevant instructions:
■Download software
■Enter CWM, wipe data, format system ( in mounts and storage)
■Flash Slim-GT-I9100-4.2.1.Beta.2-OFFICIAL then flash Slim_Gapps
All seemed to go fine, after flashing each of the above phone reported succesfu in CWM.
Anyway, rebooted as per instructions, phone shut down never to power up again!
Cant access download or recovery mode, nothing. Totally dead.
Ive ordered a USB Jig but doubt this will do anything at all?
Can someone please confirm what I did wrong (Should I have flashed Kernel 1st?)
Thanks.
nufcme said:
Hi,
Another Noob bricked his phone here SGS2 UK i9100.
I spent hours and hours reading all the FAQ's, various How To's but obviously not well enough although thought I had.
Im normally quite competent at things like this, dating back to early days chipping playstation 1's etc, done all sorts over the years without a hiccup. Had to fail sometime!
After the failed attempt, I suspect I may have flashed a custom ROM not compatible with the stock Kernel????
I rooted my i9100 using Chainfire's method:
[30.10.2012][CF-Root 5.6] K**,LA*,LP-126BHJQ73SC89DEFWGKIQOTUXY,LQ-5B - su+bb+CWM4/5
All went fine, root access, SU etc..
I then tried installing a custom ROM:
[ROM][4.2.1]Slim Bean - I9100 [Beta 2]
Followed the relevant instructions:
■Download software
■Enter CWM, wipe data, format system ( in mounts and storage)
■Flash Slim-GT-I9100-4.2.1.Beta.2-OFFICIAL then flash Slim_Gapps
All seemed to go fine, after flashing each of the above phone reported succesfu in CWM.
Anyway, rebooted as per instructions, phone shut down never to power up again!
Cant access download or recovery mode, nothing. Totally dead.
Ive ordered a USB Jig but doubt this will do anything at all?
Can someone please confirm what I did wrong (Should I have flashed Kernel 1st?)
Thanks.
Click to expand...
Click to collapse
What ROM were you on?
Please don't say 4.0.4.....
You should have done a nandroid backup after rooting. That would have given you something to fall back on.
Try removing battery for at least 10 mins. Refit. Plug in to wall charger. Give it an hour or so to see if it wakes up. If not then wait for the jig to arrive.
How much battery did you have when you flashed slim? Also, I wouldn't have formatted system. Always had issues with that.
Sent from my GT-I9100 using xda premium
YES, I was on 4.0.4
I did do a nandroid backup after rooting.
After trying to install another ROM prior to SlimBean, which kept hanging at the Samsung logo, I managed to restore from the nandroid backup fine, but after this one failing I cant enter recovery or download mode to recover, the phone is just dead! :crying:
If you wiped with a 4.0.4 kernel it's sayonara. Service centre for MB replacement. Fair chance they won't be able to tell you borked it & you'll get it done under warranty (assuming your warranty is still valid to begin with).
nufcme said:
YES, I was on 4.0.4
I did do a nandroid backup after rooting.
After trying to install another ROM prior to SlimBean, which kept hanging at the Samsung logo, I managed to restore from the nandroid backup fine, but after this one failing I cant enter recovery or download mode to recover, the phone is just dead! :crying:
Click to expand...
Click to collapse
Sorry man, but I gotta show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for confirming what I already thought!!!
The 4.0.4 brick was 1st thing I read after, the law of sod!
Well out of warranty unfortunatley, I had this phone since s2 release day.
Unfortunatley to make matters worse, this is the missus' phone now since I got my s3 so I am really in trouble!!!!!!
How much am I looking for a MB replacement at Service Centre in UK?
Would this be something I could do myself buying a spare/repair phone off ebay with broken screen or something?
Thanks again for help.
I also have one i9100 it was GB out of box.
1. I updated with kies to 4.0.4 or 4.0.3 im not 100% sure was some time ago.
2. I flashed with odin leaked 4.1.2 jb.
And leaked version have some bags and i would racher go back to ics. Is it safe to flash stock 4.0.3/4 with odin?
Sent from my GT-I9010 using xda app-developers app
nufcme said:
Thanks for confirming what I already thought!!!
The 4.0.4 brick was 1st thing I read after, the law of sod!
Well out of warranty unfortunatley, I had this phone since s2 release day.
Unfortunatley to make matters worse, this is the missus' phone now since I got my s3 so I am really in trouble!!!!!!
How much am I looking for a MB replacement at Service Centre in UK?
Would this be something I could do myself buying a spare/repair phone off ebay with broken screen or something?
Thanks again for help.
Click to expand...
Click to collapse
You're talkin 200 euro or something like that (mobo).
And yeah, you could buy a broken SII and replace it, long shot tho.
Don't tell your wife just now, let the weekend go by (Run now, while you can!)
could try jtag too, still a long shot
---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------
bg.stefan90 said:
I also have one i9100 it was GB out of box.
1. I updated with kies to 4.0.4 or 4.0.3 im not 100% sure was some time ago.
2. I flashed with odin leaked 4.1.2 jb.
And leaked version have some bags and i would racher go back to ics. Is it safe to flash stock 4.0.3/4 with odin?
Sent from my GT-I9010 using xda app-developers app
Click to expand...
Click to collapse
Go 4.0.3, learn from the OP.
Here, have a look.
HANG ON!!!!
Just realised the warranty is 24 months, got the phone on release day, this was end of April / beginning May 2011, right? That gives me 3-4 month left
Well, got to be worth a shot to save my balls!
Nothing to loose since its goosed!
nufcme said:
HANG ON!!!!
Just realised the warranty is 24 months, got the phone on release day, this was end of April / beginning May 2011, right? That gives me 3-4 month left
Well, got to be worth a shot to save my balls!
Nothing to loose since its goosed!
Click to expand...
Click to collapse
haha, time to practice "I dunno, I've just accepted an update when I was on wifi and all of a sudden, it went off, couldn't turn it on, crazy" rutine.
Hi guys!
My first thread, so please be gentle...
3 weeks ago I flashed the WanamLite ROM with full wipe. I was unaware to the EMMC brickbug and my phone died when reaching 10% of the installation process.
My phone is now being fixed (JTAG didn't help and thus MB is replaced), which is very expensive.
After reading some XDA threads I realized that I should have taken few steps before flashing the ROM.
When I get my fixed phone (probably today) with probably another "insane EMMC", I wanna make sure that it won't happen again. I've already read the xda threads, but still unsure and afraid that i'll miss some steps or that I didn't fully understand it.
Thus, my question are:
1) When I flashed the WanamLite ROM, I wiped it first, and only then flashed the ROM (using the Recovery). When installation reached to 10% the phone died. This goes in contrary to the XDA EMMC Threads that explains that it should happen only while wiping. How can that be ? Is this a different bug ?
2) If before ***any flasing or wipe*** I change the kernel to SIYAH (which has DISABLED CAP_ERASE) using ODIN, then no matter what kernel/ROM i am flashing after, is it totally safe from this bug ? is this the safest method ?
3) If not, what is the safest method to flash the ROM without having a brickbug (if I have the insane/unknown chip) ?
Thanks !!!
Lior
stlior said:
Hi guys!
My first thread, so please be gentle...
3 weeks ago I flashed the WanamLite ROM with full wipe. I was unaware to the EMMC brickbug and my phone died when reaching 10% of the installation process.
My phone is now being fixed (JTAG didn't help and thus MB is replaced), which is very expensive.
After reading some XDA threads I realized that I should have taken few steps before flashing the ROM.
When I get my fixed phone (probably today) with probably another "insane EMMC", I wanna make sure that it won't happen again. I've already read the xda threads, but still unsure and afraid that i'll miss some steps or that I didn't fully understand it.
Thus, my question are:
1) When I flashed the WanamLite ROM, I wiped it first, and only then flashed the ROM (using the Recovery). When installation reached to 10% the phone died. This goes in contrary to the XDA EMMC Threads that explains that it should happen only while wiping. How can that be ? Is this a different bug ?
2) If before ***any flasing or wipe*** I change the kernel to SIYAH (which has DISABLED CAP_ERASE) using ODIN, then no matter what kernel/ROM i am flashing after, is it totally safe from this bug ? is this the safest method ?
3) If not, what is the safest method to flash the ROM without having a brickbug (if I have the insane/unknown chip) ?
Thanks !!!
Lior
Click to expand...
Click to collapse
the emmc brickbug comes only with Stock android v4.0.4 (should not make any wipes in that Stock 4.0.4 recovery)
so the best way is to flash Siyah kernel v5.0.1 from odin to get rid of the brick bug issue since the emmc_cap_erase thing is disabled in siyah.
then u can use siyah kernel recovery to wipe/flash etc without any problem
in ur early case while installing the 'Wanamalite' rom u had made wipe in the stock 4.0.4 recovery which caused ur phone to brick
So the bottom line is: First root your phone, otherwise you will be screwed no matter what
Donnie Sins said:
So the bottom line is: First root your phone, otherwise you will be screwed no matter what
Click to expand...
Click to collapse
No, as long as u dont do anything silly as the OP did (wiping in stock 4.0.4 recovery) ur not affected by the emmc thing
its only when u want to install a custom rom is when u make it safe to install a brick bug free custom kernel first and then proceed
All I can say is your first bit isnt true.Ive read several threads about the problem and there are several other scenarios that people say have caused the brickbug.
Anyway,you can do what Sun says,or just avoid ever having stock 4.0.4 firmware on your phone.
eg. 4.0.3/gb/jb/custom
Thanks. So...
Sun90 said:
the emmc brickbug comes only with Stock android v4.0.4 (should not make any wipes in that Stock 4.0.4 recovery)
so the best way is to flash Siyah kernel v5.0.1 from odin to get rid of the brick bug issue since the emmc_cap_erase thing is disabled in siyah.
then u can use siyah kernel recovery to wipe/flash etc without any problem
in ur early case while installing the 'Wanamalite' rom u had made wipe in the stock 4.0.4 recovery which caused ur phone to brick
Click to expand...
Click to collapse
In my early case I indeed wiped, but isn't the "death" suppose to happen while wiping and not while installing (after wiping) ? I just want to make sure that this was the bug and I didn't do anything that have caused other bug.
I will do as you adviced (never install 4.0.4 and first install Siyah kernel). But after wiping and flashing new rom with new kernel, does it matters if the kernel is safe or not?
ThAnKs again!
stlior said:
In my early case I indeed wiped, but isn't the "death" suppose to happen while wiping and not while installing (after wiping) ? I just want to make sure that this was the bug and I didn't do anything that have caused other bug.
I will do as you adviced (never install 4.0.4 and first install Siyah kernel). But after wiping and flashing new rom with new kernel, does it matters if the kernel is safe or not?
ThAnKs again!
Click to expand...
Click to collapse
Yes, the Brick Bug appears while you're wiping. I wouldn't know what happened else... But maybe others do.
Only stock 4.0.4 kernels can be affected. Therefore you have to flash a custom kernel first, and then wipe, flash, etc. Custom roms will always be safe, so no need to worry after you've flashed Siyah or any other kernel.
The bottom line is, if you stay away from 4.0.4 & can follow instructions/learn 'how & why' before you do it so you understand why you do certain things a certain way/in a particular order, rather than post in Q&A and say 'Give me the instructions to...<insert name of phone modification here> !!' (like rooting, installing a rom, etc, etc) & someone lists a bunch of steps you don't understand, the only way you're bricking your phone is if you're unlucky, and I've seen maybe 10 people like that out of quite a few thousand on here over the past 18 mths.
Lol,theres always GB.Its the most stable and battery friendly.......thats why I use it.
To MistahBungle
MistahBungle said:
The bottom line is, if you stay away from 4.0.4 & can follow instructions/learn 'how & why' before you do it so you understand why you do certain things a certain way/in a particular order, rather than post in Q&A and say 'Give me the instructions to...<insert name of phone modification here> !!' (like rooting, installing a rom, etc, etc) & someone lists a bunch of steps you don't understand, the only way you're bricking your phone is if you're unlucky, and I've seen maybe 10 people like that out of quite a few thousand on here over the past 18 mths.
Click to expand...
Click to collapse
Well MistahBungle your post is excactly the kind i tired to avoid (sorry for bad english), so please let me defend myself.
I read the xda EMMC threads before I posted here, and my post isn't just "tell me the steps cause i'm too lazy".
I asked a few questions:
The first one i tried to understand if what I have is the standard EMMC brickbug, because as i read in the previous threads, it happens while wiping, and not while flashing as it happend to me (don't want to do the same mistake again).
The second one I asked is if it is safe to flash any kernel after I use the siyah, which is unclear from the other xda posts i read (and "on the way" i wanted to confirm that i indeed have to flash the siyah kernel).
The third question was only to answered if the assumption i made in the previous question is wrong (maybe this and only this was redundant). But you also must remmember
All the above shows that I indeed read the XDA threads and instructions, but didn't get the answers I wanted. In addition, keep in mind I've just spent few hundreds $$$ and lot of time, and I wanna be extra careful so it won't happen again.
I really think that all the rules were kept, even thought this is my first thread here.
Thanks.
To Stlior
stlior said:
-SNIP-
Click to expand...
Click to collapse
You seem to have trouble comprehending. I'll say what I said in my last post a bit more clearly for the slow kids up the back...
If you make sure you know/understand what you're doing before you do it & follow instructions, you won't brick your phone unless you're unlucky. This happens in 0.0001% of cases. You were not one of these cases.
This advice has served many thousands of XDA'ers well in the time I've been here. You broke your phone. Nobody else. All the information you could ever need is here if you're prepared to take the time to find & learn it. Thing is people like you aren't.
The end.
Happy ? (Yes you're now on my ignore list so I won't see any further posts from you).
Donnie Sins said:
Yes, the Brick Bug appears while you're wiping. I wouldn't know what happened else... But maybe others do.
Only stock 4.0.4 kernels can be affected. Therefore you have to flash a custom kernel first, and then wipe, flash, etc. Custom roms will always be safe, so no need to worry after you've flashed Siyah or any other kernel.
Click to expand...
Click to collapse
Thanks. I hope that this indeed was the brickbug and I don't have another hardware fault...
MistahBungle said:
You seem to have trouble comprehending. I'll say what I said in my last post a bit more clearly for the slow kids up the back...
If you make sure you know/understand what you're doing before you do it & follow instructions, you won't brick your phone unless you're unlucky. This happens in 0.0001% of cases. You were not one of these cases.
This advice has served many thousands of XDA'ers well in the time I've been here. You broke your phone. Nobody else. All the information you could ever need is here if you're prepared to take the time to find & learn it. Thing is people like you aren't.
The end.
Happy ? (Yes you're now on my ignore list so I won't see any further posts from you).
Click to expand...
Click to collapse
omg lol :laugh:
how much bitterness!
I explained well why i asked those specific questions, you chose not to listen and instead chose to attack and be bitter. It's ok thought this is kind of your problem. Feel well my friend ! (even if you do not see this).
Basically pal,it doesnt matter what happened in the past or whats going to happen in the future,because you should be removing samsungs stock 4.0.4 firmware.
You should be accepting experts advice rather than irritating them.
We dont know what you understand,but if you ask and get an answer/advice,then try it out.
If you want to improve your knowlege,then read guides and problems other people are having.
Man you guys been busy with this.
By reading about the brickbug you learn one thing:
If you are on 4.0.4 you either get the hell out of there or flash siyah, period.
Questions aroused?
Only if you should use Mobile Odin.
It's pretty clear I guess.
Now, you're saying that you wipped and didn't brick right away, but during flashing. I've seen that before, don't know why it happens.
Si, bottom line:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/ CWM
Sent from the little guy
gastonw said:
Man you guys been busy with this.
By reading about the brickbug you learn one thing:
If you are on 4.0.4 you either get the hell out of there or flash siyah, period.
Questions aroused?
Only if you should use Mobile Odin.
It's pretty clear I guess.
Now, you're saying that you wipped and didn't brick right away, but during flashing. I've seen that before, don't know why it happens.
Si, bottom line:
View attachment 2017049
/ CWM
Sent from the little guy
Click to expand...
Click to collapse
I second this, stock 4.0.4 was a noob flashers nightmare, the only pure stock I ever had was gb(yeah the one it came with long back), well OP I will give you a few points that will clear some some doubts, it's not the firmware that is risky, using ics 4.0.4 ain't a problem, it's the stock kernel of 4.0.4 that comes with the firmware who is the actual troublemaker, for example if you flashed cm9 stable (yeah ics 4.0.4) with the clockworkmod kernel, you're completely safe, since the custom kernel has the emmc_cap_erase command disabled and you can safely perform any wipe you want. So basically any kernel with the command emmc_cap_erase is dangerous for devices with brickbug effected chip(I am saying this because an old Siyah kernel had this command apparently, v3.xx something) , but no worries every new custom kernels are safe as far as I know.
So to trigger the brickbug there are three conditions,
1.Brickbug effected chip
2.Kernel containing emmc_cap_erase command
3.Performing any form of wipe operation.
If any one of the above condition is not satisfied your device won't get bricked.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
I second this, stock 4.0.4 was a noob flashers nightmare, the only pure stock I ever had was gb(yeah the one it came with long back), well OP I will give you a few points that will clear some some doubts, it's not the firmware that is risky, using ics 4.0.4 ain't a problem, it's the stock kernel of 4.0.4 that comes with the firmware who is the actual troublemaker, for example if you flashed cm9 stable (yeah ics 4.0.4) with the clockworkmod kernel, you're completely safe, since the custom kernel has the emmc_cap_erase command disabled and you can safely perform any wipe you want. So basically any kernel with the command emmc_cap_erase is dangerous for devices with brickbug effected chip(I am saying this because an old Siyah kernel had this command apparently, v3.xx something) , but no worries every new custom kernels are safe as far as I know.
So to trigger the brickbug there are three conditions,
1.Brickbug effected chip
2.Kernel containing emmc_cap_erase command
3.Performing any form of wipe operation.
If any one of the above condition is not satisfied your device won't get bricked.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
+ back up restore
Sent from the little guy
gastonw said:
+ back up restore
Sent from the little guy
Click to expand...
Click to collapse
Yeah lol, well that's why I said any "form" of wipe operation as a nandroid restore performs certain wipes before restoring.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
I second this, stock 4.0.4 was a noob flashers nightmare, the only pure stock I ever had was gb(yeah the one it came with long back), well OP I will give you a few points that will clear some some doubts, it's not the firmware that is risky, using ics 4.0.4 ain't a problem, it's the stock kernel of 4.0.4 that comes with the firmware who is the actual troublemaker, for example if you flashed cm9 stable (yeah ics 4.0.4) with the clockworkmod kernel, you're completely safe, since the custom kernel has the emmc_cap_erase command disabled and you can safely perform any wipe you want. So basically any kernel with the command emmc_cap_erase is dangerous for devices with brickbug effected chip(I am saying this because an old Siyah kernel had this command apparently, v3.xx something) , but no worries every new custom kernels are safe as far as I know.
So to trigger the brickbug there are three conditions,
1.Brickbug effected chip
2.Kernel containing emmc_cap_erase command
3.Performing any form of wipe operation.
If any one of the above condition is not satisfied your device won't get bricked.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks king_below_my_lord,
I see the final conclusion from everyone here is "do not flash (from) 4.0.4 !!!" (got the phone a few days ago, but the display was corrupted so i returned it).
can't wait to get my phone back.
ThAnKs for everyone (even the one who ignores me...) !
Lior
Hey everyone. The other day, I was installing a custom ROM and was also trying to unlock my Galaxy SIII. After both, Airplane mode somehow locked on... I did a factory reset - didn't help. I also reinstalled the stock image - didn't help. I tried several tar recovery files - didn't work or help. I tried everything! I can disable airplane mode in settings but my device simply displays a circle with a cross through it instead of the signal meter in the notification bar. It also doesn't detect SIM cards now... I don't know what is wrong. Help would be GREATLY APPRECIATED!!!!!
Thanks for your answers in advance!
My first thought is the Unlock process stuffed things for you. What did you try for the Unlock? Did you get it right? I've never had a locked phone so I don't know the process but try asking around on threads where they talk about unlocking phones.
What ROM did you try? Can you still get into the phone for menus etc?
And the biggie - did you try Restoring your Nandroid backup? (you DID do a Nandroid at some point, didn't you? )
If you've only done a factory reset from the phone I'd try getting MegaWipe and flash it in Recovery. Then try a ROM you know to be working for others.
Another thing to look at might be your Modem - I use Purelook HD ROM - one of the updates had a modem that screwed with my wifi and phone connection so I flashed the previous one that had worked well and all was right again.
You might also need to try a megawipe and then flash a stock ROM via Odin - get the phone back to a working state and then start ROM'ing again.
Yeah, I can get into menus alright. The MegaWipe didn't seem to work though Or the Purelook HD ROM. I've flashed the stock ROM about 100 times, restored Nandroid and did a full stock restore however nothing worked. Thanks anyway!!!
Do you have an EFS backup?
Is your modem correct? if not, restore your EFS backup
Another thing, dial *#06# on your phone and look at your IMEI. Do you see a bunch of zeros?
xpmode said:
Another thing, dial *#06# on your phone and look at your IMEI. Do you see a bunch of zeros?
Click to expand...
Click to collapse
When I dial *#06#, a box pops up and simple says "IMEI". There is no actual IMEI number displayed... That must be bad..??
astronomynerd said:
When I dial *#06#, a box pops up and simple says "IMEI". There is no actual IMEI number displayed... That must be bad..??
Click to expand...
Click to collapse
Yep, it says EMEI: null / null
astronomynerd said:
Yep, it says EMEI: null / null
Click to expand...
Click to collapse
Your EFS is corrupted. If you have a backup please restore it. If not Flash a fresh stock ROM and start over.
If I'm right, you turned your phone to a Wi-Fi tablet. There is not a real at-home solution other than searching your whole computer and your phone's internal memory and all SD cards you used on your phone for files that have "efs" in their names and hope you find some kind of EFS backup you took before. (About that, can you post a list of the ROMs you installed before? I know Sotmax takes[or used to take, don't know the new versions] automatic EFS backups, maybe other Samsung ROMs do too)
If you can't find any, you should contact with your carrier and ask if they can repair it. It won't be covered by warranty, and you would probably be asked to bring evidence(receipt and such) to prove the phone is not stolen.
Make sure you tell them the whole story, and don't try to cover up the fact that you rooted your phone, or you may end up being questioned by the police.
If they accept, they will restore your IMEI using advanced debugging hardware and software. If they reject, then you may want to start looking for a new phone.
(Procedures may vary)
actually, it will be covered by warranty if you restore it to complete stock
They may still look at the binary counter and tell Odin has been used.
Other than that, lying in such conditions may result in big trouble, so if they ask if you have rooted your device, you should say yes. Not worth risking much bigger trouble for a paid repair.
There is triangle away.
Triangle away+flash stock rom = full stock no binary counter.
Why do you say there might be problems with the police? Since the gs2 there have been lots of cases of lost/corrupted efs without doing anything. Are all those people in jail?
If there's proof of ownership, then there's nothing to it. I really don't know how much is the standard rate for lost/corruped efs fixing outside of warranty, if it involves motherboard replacing, its gonna be as expensive as a new phone.
I'm talking from looking at my country's regulations, so they might be different in other countries. Hence the "procedures may vary" in my reply.