Here is the story!
My i9100 was working great, the only thing i noticed was a couple of time the screen changed the regular colors to something like a "negative" one.
Right now the phone boot but freezes as I try to do something...even the initial setup.
So far I tried almost everything: flashing a stock rom, flashing all the developers rom, erase and format everything and start again; no luck! the problem still there: with some rom the phone stuck on the boot screen, with others it boot up but freezes.
Any advice would be appreciated!
Thanks:fingers-crossed:
Did you try to wipe Dalvik Cache etc.?
Sent from my GT-I9100 using xda app-developers app
linzinator said:
Did you try to wipe Dalvik Cache etc.?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes, was the first thing...
I tried the guide to determine if you have bricked sector, but no bad sectors came up.
griskaitalia said:
Yes, was the first thing...
I tried the guide to determine if you have bricked sector, but no bad sectors came up.
Click to expand...
Click to collapse
Your problem seems very similar to having memory brick blocks, because for "one person" the phone even booted fine but /data wasn't mounted which made applications to behave weird. But since no bad sectors came up it must be something else..
Using GT - I9100
Just hit the damn help button if I helped you.
i could be a kernel problem or display problem (maybe u dropped ur phone sometime)
Related
Hey.
Am using a i9100 running cwm recovery and sensation 3.4 rom. Recently i got the eMMC chip error. Ever since whenever i pull my battery out, the date and time gets reset to 1/1/2000 & 12.00am respectively. Is there.any way to prevent the resets??
Sent from my GT-I9100 using XDA
daniel9895 said:
Is there.any way to prevent the resets??
Click to expand...
Click to collapse
Yes, don't take the battery out.
My phone has always behaved this way.
daniel9895 said:
Hey.
Am using a i9100 running cwm recovery and sensation 3.4 rom. Recently i got the eMMC chip error. Ever since whenever i pull my battery out, the date and time gets reset to 1/1/2000 & 12.00am respectively. Is there.any way to prevent the resets??
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
I didn't have a prob like this 'til now, but did u try to make a clean full wipe reflash?
Wipe data, factory reset
Wipe cache partition
Format data/system/cache
Reflash Rom (later maybe kernel, too)
U have connection to inet? All settings in set correct?
CHEERS
Hannibal226 said:
I didn't have a prob like this 'til now, but did u try to make a clean full wipe reflash?
Wipe data, factory reset
Wipe cache partition
Format data/system/cache
Reflash Rom (later maybe kernel, too)
U have connection to inet? All settings in set correct?
CHEERS
Click to expand...
Click to collapse
I don't think it's a problem with the ROM as it worked fine until i tried to dual boot with resurrection remix via siyah 3.1 kernel.that's when the infamous eMMC chip error came up.so i switched back to cmw recovery and sensation. Flashed n wiped everything. But everytime i restart the date and time goes back to the default one. And yes i have set the correct settings and everything.
Sent from my GT-I9100 using XDA
oinkylicious said:
Yes, don't take the battery out.
My phone has always behaved this way.
Click to expand...
Click to collapse
Get gotbrickbug app by chainfire from the market and check whether your eMMC chip has been fried or not
Sent from my GT-I9100 using XDA
daniel9895 said:
Get gotbrickbug app by chainfire from the market and check whether your eMMC chip has been fried or not
Click to expand...
Click to collapse
If your eMMC chip had been fried, you wouldn't be able to do a lot with your phone. I don't understand why you're linking this to your date/time problems. Also, Chainfire's app won't tell you if your eMMC chip is fried, just whether a particular erase method could brick your device.
Well when i enter into recovery, i get three four files missing.Those which you get if your chip is fried. And yourphone can continue working fine with a fried chip.only when the bogus corrupted sector is accessed again does it gets your phone into a Brick.Plus am not able to dual boot in siyah anymore.
Emmc being something to do with cache. I think the local settings like time and date is not getting stored to be brought back during a reboot.
Sent from my GT-I9100 using XDA
Hi! I've searched on and off this forum, my husband and I are on the road all week and his phone had been rooted over a year ago by myself, no splashy roms and no problems. His screen froze so he booted, now stuck in bootloop. I have gone into recovrry but its not working. I'm hesitant to wipe data without computer access. He is active military and needs his phone. I will have computer access in the next few days. Please help!
DMDewey22 said:
Hi! I've searched on and off this forum, my husband and I are on the road all week and his phone had been rooted over a year ago by myself, no splashy roms and no problems. His screen froze so he booted, now stuck in bootloop. I have gone into recovrry but its not working. I'm hesitant to wipe data without computer access. He is active military and needs his phone. I will have computer access in the next few days. Please help!
Click to expand...
Click to collapse
If you can't get out of the boot loop without wiping data or sbf'ing there's nothing you can do but that. If you are in cwr you can try wiping delvik and cache but if not wiping data couldn't hurt since you'll lose everything doing an sbf anyway. Hope this helps
Sent from my MB870 using xda app-developers app
what do you mean, recovery is not working?
when you see android andy, you have to press both volume buttons
to continue to recovery options
Strubie42 said:
If you can't get out of the boot loop without wiping data or sbf'ing there's nothing you can do but that. If you are in cwr you can try wiping delvik and cache but if not wiping data couldn't hurt since you'll lose everything doing an sbf anyway. Hope this helps
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
I would have to agree here.
sd_shadow said:
what do you mean, recovery is not working?
when you see android andy, you have to press both volume buttons
to continue to recovery options
Click to expand...
Click to collapse
Don't think she was saying that her recovery doesn't work, think she meant that going into didn't help. Although I am not sure what she thought just loading the recovery would accomplish?
Any who, GL!
sometimes wiping cache is enough to stop bootloop
Sent from my DROID2 using xda premium
sd_shadow said:
sometimes wiping cache is enough to stop bootloop
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
This. Seems to always stop those little, alien like happenings regardless of the device.
I'm curious to know what exactly you tried to do in recovery -- did you try to restore a nandroid?
Sent from my Galaxy Nexus using Tapatalk 2
My 2nd topic in about 20 mins!
I've just flashed Siyah Kernal but made a mistake and flashed an older version accidently (I flashed 1.3 instead of 1.7)
Now my phone doesn't boot, it gets to the loading screen where it displays model etc and then stops. I can boot into recovery, I was thinking I can just flash the other kernal but I don't have it on my storage.
I wiped cache then davlik cache and then installed the old version and rebooted and now I'm stuck
I'm thinking just wipe data and reflash ROM but I've never messed around with kernals before so I don't know if it's any different
Help is GREATLY appreciated!
If you have an external SD, transfer the updated 1.7rc1 syiah to that, and flash it from recovery.
Should solve the problem.
If it doesnt, wiping and reflashing the rom, then the corect kernel should work as well.
NewAussiefromCanada said:
If you have an external SD, transfer the updated 1.7rc1 syiah to that, and flash it from recovery.
Should solve the problem.
If it doesnt, wiping and reflashing the rom, then the corect kernel should work as well.
Click to expand...
Click to collapse
shall I just straight flash the kernal? no wiping cashe or anything?
UrbanDesigns said:
shall I just straight flash the kernal? no wiping cashe or anything?
Click to expand...
Click to collapse
I would start with that.. if any problems occur, then go to wiping.
I would wipe delvic and cache
Update Syiah myself a few times without a wipe. Although I am sure some would recommend a wipe.
I've just put my external SD into its adapter so that my laptop can read it and I get write protection errors.
Can I just wipe data/factory reset and reflash the ROM to gain access to my phone again and then flash the kernal?
UrbanDesigns said:
I've just put my external SD into its adapter so that my laptop can read it and I get write protection errors.
Can I just wipe data/factory reset and reflash the ROM to gain access to my phone again and then flash the kernal?
Click to expand...
Click to collapse
first off is the switch on ur adapter set to lock?
Yes if you factory reset and wipe, then install rom, then you can flash the kernel and enjoy all the benefits!:victory:
aaaaand I'm back!
I noticed the little slidy thing on the adaptger and put it the other way and it worked, having that "lock" is pretty ridiculous if you ask me.
I'm all sorted now, I would be useless if it wasn't for the people on this forum
Thank you all so much for the help, whenever stuff like this happens I overact and instantly assume my device is bricked
Thanks to you all!
UrbanDesigns said:
aaaaand I'm back!
I noticed the little slidy thing on the adaptger and put it the other way and it worked, having that "lock" is pretty ridiculous if you ask me.
I'm all sorted now, I would be useless if it wasn't for the people on this forum
Thank you all so much for the help, whenever stuff like this happens I overact and instantly assume my device is bricked
Thanks to you all!
Click to expand...
Click to collapse
LOL Those Pesky little lock sliders always causing trouble!
Glad I could help!
Hopefully your enjoy the benefits of Syiah after all your hard work! :victory:
UrbanDesigns said:
aaaaand I'm back!
I noticed the little slidy thing on the adaptger and put it the other way and it worked, having that "lock" is pretty ridiculous if you ask me.
I'm all sorted now, I would be useless if it wasn't for the people on this forum
Thank you all so much for the help, whenever stuff like this happens I overact and instantly assume my device is bricked
Thanks to you all!
Click to expand...
Click to collapse
I'm glad you got this sorted. I personally love when something like this happens, you get such a sense of achievement when your phone finally boots again
Sent from my GT-I9300 using Tapatalk 2
ChrisHRocks said:
I'm glad you got this sorted. I personally love when something like this happens, you get such a sense of achievement when your phone finally boots again
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
ive been new to root for just 2 days.. but i have assumed i have bricked my device a couple of times.. but yeh I agree, when you get it working you feel like you are finally understanding how these things work..:victory:
i have just one issue left unresolved that I have in another thread, when thats fixed i'll have the phone I wanted it to be and I'll be satisfied ( that wasnt trolling by they way.. erm, assuming trolling is trying to redirect a thread to another.. im not sure what trolling is.. but i didnt do it lol )
ChrisHRocks said:
I'm glad you got this sorted. I personally love when something like this happens, you get such a sense of achievement when your phone finally boots again
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
indeed and 3 cheers for XDA, the best place to get help.
Hi, i'm a new user of SG SII, and i don't know much about it. I was trying to install new ROM on it, first I tried to unroot my phone with CF ROOT, after that everthing was OK. Then i tried to install REVOLT JB i9100 ver 2.8.2, when i got by CWM in recovery, instead of clicking wipe data, then cache and ccache partition i did: wipe data/factory reset, and wipe cache partition, wipe dalwik cache and format system. I flashed kernel and during ROM installation phone turned off and did turn on. i think it's hard bricked. I don't know what to do, please help.
Are you still able to get into don't download mode o your phone ? ( volume down, home key, power button )
If so, reflash your kernel and go from there.
Also have a look at CyanogenMod, they have a good post with instructions on here.
Sent from my GT-I9100 using xda premium
x
Dorbian said:
Are you still able to get into don't download mode o your phone ? ( volume down, home key, power button )
If so, reflash your kernel and go from there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
no, phone doesn.t response on anything, even if i'm charging the battery.
Try removing your battery and unplug cables.
Then try download or recovery mode again.
If it really doesnt work then there is probably something fried on your system board, doubt anything you can do about it as i had the same not that long ago out of the blue.
Sent from my GT-I9100 using xda premium
.
Dorbian said:
Try removing your battery and unplug cables.
Then try download or recovery mode again.
If it really doesnt work then there is probably something fried on your system board, doubt anything you can do about it as i had the same not that long ago out of the blue.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Did it and still nothing, do you think that maybe JIG plug could be a good idea?
You could always give it a go, havent had any experience with i myself tho so hopefully someone else here can give you a hand
Sent from my GT-I9100 using xda premium
I had a similar issue with sgs1 back in the day. I built a jig and got it working so give it a shot if you can. Its worth it for the cost of a jig surely?
Sent from my GT-I9100 using xda app-developers app
.
ok, i'll try to do it. but i have to ask if that will not work, can i save my phone by changing main board on warranty in service?
You can always tell them that you were updating via kies and it dropped dead just like that.
Your battery was low when you tried to flash it, wasn't it?
try a jig first tho; there's something fishy about those wipes you mentioned.
pawlo130 said:
Hi, i'm a new user of SG SII, and i don't know much about it. I was trying to install new ROM on it, first I tried to unroot my phone with CF ROOT, after that everthing was OK. Then i tried to install REVOLT JB i9100 ver 2.8.2, when i got by CWM in recovery, instead of clicking wipe data, then cache and ccache partition i did: wipe data/factory reset, and wipe cache partition, wipe dalwik cache and format system. I flashed kernel and during ROM installation phone turned off and did turn on. i think it's hard bricked. I don't know what to do, please help.
Click to expand...
Click to collapse
On some occasions flashing a device can use 40-50% of battery to prep and flash device which is why its advised to never flash your phone unless you have at least 50-60% battery.
If power cuts out during flashing procedure it can damage nand/ic chip, corrupt bootloader, corrupt sdcards etc.
After leaving it plugged into to charger overnight try a USB jig to see if you can get it to wake up in download mode, If you can re-flash rom and go from there.
gastonw said:
You can always tell them that you were updating via kies and it dropped dead just like that.
Your battery was low when you tried to flash it, wasn't it?
try a jig first tho; there's something fishy about those wipes you mentioned.
Click to expand...
Click to collapse
battery was about 70%, so it should not have turned off
pawlo130 said:
battery was about 70%, so it should not have turned off
Click to expand...
Click to collapse
then I was right with the fishy wipes.
pray for the jig.
From what you described, it couldn't have hard bricked your phone. In fact, it isn't easy to hard brick our phone unless you install that infamous ICS 4.0.4 leaked ROM or mess with flashing of PIT file. Try to use another fully charged battery to boot up or go into CWM recovery.
Sent from my GT-I9100 using Tapatalk 2
xdanoober said:
From what you described, it couldn't have hard bricked your phone. In fact, it isn't easy to hard brick our phone unless you install that infamous ICS 4.0.4 leaked ROM or mess with flashing of PIT file. Try to use another fully charged battery to boot up or go into CWM recovery.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
while i was installing new rom, process was like 0% for about 5 minutes, and then phone just turned off. When i did flashing and installing CWM everything was ok. I rooted it with CF root.
Exact same problem here. Followed the root guide to the letter and all OK. Set omega rom installing and it stayed at 0 for five mins then it shut off. Now no life at all.
Gonna build a jig tomorrow so I'll update here if it works.
Really hope so as it's a mates phone.
I've done my s3, s1 and the Mrs s2 without it going wrong so I'm not sure how it went wrong this time.
Sent from my GT-I9300 using xda premium
SkinBobUk said:
Exact same problem here. Followed the root guide to the letter and all OK. Set omega rom installing and it stayed at 0 for five mins then it shut off. Now no life at all.
Gonna build a jig tomorrow so I'll update here if it works.
Really hope so as it's a mates phone.
I've done my s3, s1 and the Mrs s2 without it going wrong so I'm not sure how it went wrong this time.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Your phone have got super brick, and the JIG nothing to do.... You must go to service.
The reason for this is stock kernel who has kode cause brick.
Sorry for my english!
Ah that's a shame. Fingers crossed it's still under warranty or it's gonna be an expensive month.
Sent from my GT-I9300 using xda premium
SkinBobUk said:
Ah that's a shame. Fingers crossed it's still under warranty or it's gonna be an expensive month.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Don't worry will be fine. JTAG must be repair all
Wysyłane z mojego GT-S6500D za pomocą Tapatalk 2
First of all: I have had my S II water damaged some months ago. It works fine that far (exept that the sensor keys are dead). Not sure if there is some other hardware malfunctioning...
Currently im running on MIUI and everything is fine, but recently I found out that no other ROM will work on my Phone:
- Samsung stock ROM runs extreme (!) laggy. Took me about 5 Minutes to go through the menus and enable USB debugging.
- CM9/ AOKP will reset immediately after system startup
- CM10 shows laggy boot animation for few secs, then bootloops
Only other ROM that works is "cMIUI". Which is a CM10 based ROM only with a MIUI userinterface...
What can I do to find out whats the problem with my phone??
Thats weird. Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache. Also, have you tried using those kernel cleaning scripts, etc?
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Thats weird.
Click to expand...
Click to collapse
YES :laugh:
Spiralzz said:
Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache.
Click to expand...
Click to collapse
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
Spiralzz said:
Also, have you tried using those kernel cleaning scripts, etc?
Click to expand...
Click to collapse
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Rottnroll said:
YES :laugh:
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Click to expand...
Click to collapse
Only one option I can think of is to go back to stock samsung rom then claim your warranty if you have it. Or, make a logcat and paste it here (upload to Dropbox or somewhere then past a link over here) and someone experienced might take a look.
Since you've already wiped everything, I'm more inclined to think that it's a hardware problem now. However, let's hope someone more experienced pops in and helps. Good luck
Sent from my GT-I9100 using Tapatalk 2
See two logs below, trying to boot cm9. One with default kernel, one with Siyah. Would be great if anybody could find out whats the issue.
https://www.dropbox.com/s/z7q3wbz1h9uhhvg/logcat_cm9_s2.txt
https://www.dropbox.com/s/r1l9umovmxx7jpo/logcat_cm9_s2_siyah.txt
In both logs the phone booted and showed the Pin dialog, then after few seconds rebooted.
As the Phone had been waterdamaged Im pretty shure warranty is absolutely void Also I think that the problems are due to some Hardware malfunctioning. Just want to know what and if theres some way to workaround.