I think I just bricked my phone, Interestingly enough I hold down the power button and the phone doesn't even power on. Absolutely nothing happens, I plug in the charger and no powered off charging Icon shows up either. The phone is just downright dead.
This is what occured moments before.
Booted into CWM 6.0.1.1
Performed Factory Reset/Wipe
Cleared Cache Partition
Cleared Dzavik Cache
Flashed Siyah-s2-v4.1.5-CWM
Flashed cm-9-20120909-UNOFFICIAL-celoxhd.zip TWICE
Flashed gapps-ics-20120429-signed.zip
All flashes were successful.
Phone was Rooted prior.
Rebooted, The phone turned off and since then I cannot get it to even power on or charge while off. Pulled Battery, nothing.
Any ideas?
skodazek said:
I think I just bricked my phone, Interestingly enough I hold down the power button and the phone doesn't even power on. Absolutely nothing happens, I plug in the charger and no powered off charging Icon shows up either. The phone is just downright dead.
This is what occured moments before.
Booted into CWM 6.0.1.1
Performed Factory Reset/Wipe
Cleared Cache Partition
Cleared Dzavik Cache
Flashed Siyah-s2-v4.1.5-CWM
Flashed cm-9-20120909-UNOFFICIAL-celoxhd.zip TWICE
Flashed gapps-ics-20120429-signed.zip
All flashes were successful.
Phone was Rooted prior.
Rebooted, The phone turned off and since then I cannot get it to even power on or charge while off. Pulled Battery, nothing.
Any ideas?
Click to expand...
Click to collapse
Have you tried just going into download mode and then plug into the pc to see if it picks it up.... Also here is a link that they have the jig for G2*s just a thought. .http://mobiletechvideos.mybigcommerce.com/ This guy does really good work and I have seen some phones fixed with NO hope.
Problem determined.
eMMC Brick bug. It would seem that this bug effects the SGH-I757M (Bell Samsung Galaxy S2 HD LTE) as well as just the i9100's.
Before the full wipe, which kernel did you have? if not siyah or any other kernel which disables the super EMMC bug, then you hard bricked your phone.
However i remember there is a guide somewhere on how to recover a bricked phone
Sent from my GT-I9100 using Tapatalk 2
I don't think Siyah supports the SGH-I757M model of SII. That is likely where your problem originated...
ctomgee said:
I don't think Siyah supports the SGH-I757M model of SII. That is likely where your problem originated...
Click to expand...
Click to collapse
SGH-I757 comes with a Qualcomm Snapdragon processor and siyah is based on 'Exynos', i think thats where the problem is
Oh my..you flashed a wrong kernel...The siyah kernel is only compatible with the I9100 and I9300 international models....
Sent from my GT-I9100 using Tapatalk
UnwiredDroid said:
Oh my..you flashed a wrong kernel...The siyah kernel is only compatible with the I9100 and I9300 international models....
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Oh I was not aware the Siyah Kernel did not support the SGH-I757M, are there any kernels that do? (non stock)
Spent some time on google. Seems there are no custom kernels that support the SGH-I757M. That is very dissapointing, as I really wanted to get the Siyah Kernel or at least any aftermarket kernel that improved on what we get stock.
PS. Bell Replaced my SGH-I757M Thankfully, albeit no amount of begging could convince them to upgrade me to the S3
skodazek said:
Spent some time on google. Seems there are no custom kernels that support the SGH-I757M. That is very dissapointing, as I really wanted to get the Siyah Kernel or at least any aftermarket kernel that improved on what we get stock.
PS. Bell Replaced my SGH-I757M Thankfully, albeit no amount of begging could convince them to upgrade me to the S3
Click to expand...
Click to collapse
If you're planning on installing CM10 or CM9, why do you need a different kernel?
Sent from my SGH-I757M using xda app-developers app
Looking for kernel that supports a number of functions, iptables, aostp, etc
Sent from my SGH-I757M using Tapatalk 2
Related
I just flashed "phone-bricker" ICS rom on my phone. I went to install the roms update, and when it restarted it froze on the first boot up screen.
I've tried to get to:
download mode
CWM
and normal restart
it always freezes on that screen
is there any way I can un-brick my phone?
Am i being trolled?
any power = not bricked
LiLChris06 said:
Am i being trolled?
Click to expand...
Click to collapse
lol no this is really happening, if it means anything it was a cool rom till i shut it down.
felixnigh7 said:
lol no this is really happening, if it means anything it was a cool rom till i shut it down.
Click to expand...
Click to collapse
I just had the same problem with another ICS Rom. I ended up going to recovery and and wipe data/cache.
Pretty sure it's one of the apps that I downloaded since yesterday. Probably Antutu battery saver.
I appreciate all the hard work and sacrifice made by early adopters.
Anything that underclocks your device WILL cause it to crash - this is the case for all I9100 ICS kernels, stock or custom.
It almost surely applies to the I777 leak kernel too, since that build is an older codebase.
Entropy512 said:
Anything that underclocks your device WILL cause it to crash - this is the case for all I9100 ICS kernels, stock or custom.
It almost surely applies to the I777 kernel too, since that build is an older codebase.
Click to expand...
Click to collapse
+1 Don't underclock I had my phone enter a sleep of death and then got really got while it was in my pocket. It then would freeze on boot until I wiped data.
Sent from my GT-I9100 using xda premium
I ended up installing the wrong ROM on my Galaxy S3.
The phone will not power up now. No Omega boot or CWM Boot. Tried battery pull, charging, usb/pc charging and nada.
I made a backup under CWM, wiped the factory, wipied cache, and did all the wipes. Afterwords, I installed the rom from the internal sd, went back and restored the backup I had previously made through CWM. I proceeded to reboot after all this.
My phone just turned off, no reboot. No power whatsoever.
So....is this thing just paperweight now or what? Any help would be appreciated! Thanks!
Model: SCH-I535
ROM: VillainROM- I9300 w/Ninphetamine Kernel
Verizon Wireless
Samsung Galaxy S3
you should have read the only sticky thread in this forum.
You tried flashing a rom for the international model on a US model.
Not good.
You should see if you can get help in the vzw forum.
Sent from my GT-I9300 using xda premium
Download mode?? Or buy a USB jigg which forces your phone into download mode
Sent from my GT-I9300 using xda premium
Thank you all for your prompt responses. I was stupid enough to download and install the wrong rom, but I was able to convince my retailer that the phone came in defective and they are exchanging it for me no questions asked! Thanks again all. Sorry for the wrong forum post!
Yes, I believe this is what happened to mine!
nodstuff said:
You tried flashing a rom for the international model on a US model.
Not good.
You should see if you can get help in the vzw forum.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Still can't power it up, only have a black/blank screen...
Boo hooo
StNtMaN said:
I ended up installing the wrong ROM on my Galaxy S3.
The phone will not power up now. No Omega boot or CWM Boot. Tried battery pull, charging, usb/pc charging and nada.
I made a backup under CWM, wiped the factory, wipied cache, and did all the wipes. Afterwords, I installed the rom from the internal sd, went back and restored the backup I had previously made through CWM. I proceeded to reboot after all this.
My phone just turned off, no reboot. No power whatsoever.
So....is this thing just paperweight now or what? Any help would be appreciated! Thanks!
Model: SCH-I535
ROM: VillainROM- I9300 w/Ninphetamine Kernel
Verizon Wireless
Samsung Galaxy S3
Click to expand...
Click to collapse
Your S3 is not The INTERNAIONAL VERSION,you said it yourself Verizon Wireless i-747 S3? this is not the right the thread for you.
Check the other thread for Rom and problem related.
StNtMaN said:
I ended up installing the wrong ROM on my Galaxy S3.
The phone will not power up now. No Omega boot or CWM Boot. Tried battery pull, charging, usb/pc charging and nada.
I made a backup under CWM, wiped the factory, wipied cache, and did all the wipes. Afterwords, I installed the rom from the internal sd, went back and restored the backup I had previously made through CWM. I proceeded to reboot after all this.
My phone just turned off, no reboot. No power whatsoever.
So....is this thing just paperweight now or what? Any help would be appreciated! Thanks!
Model: SCH-I535
ROM: VillainROM- I9300 w/Ninphetamine Kernel
Verizon Wireless
Samsung Galaxy S3
Click to expand...
Click to collapse
Same thing happened to me, after hours, and hours of researching i had to send it in to Samsung, who than after 3 weeks of me waiting, replaced the motherboard and sent it back. Now im too scared to do anything on my S3 rom related. Only basic rooting for me . (Even when doing that when i got my phone back, i was ****ting my pants the entire time.).
---------- Post added at 05:00 PM ---------- Previous post was at 04:55 PM ----------
StNtMaN said:
I ended up installing the wrong ROM on my Galaxy S3.
The phone will not power up now. No Omega boot or CWM Boot. Tried battery pull, charging, usb/pc charging and nada.
I made a backup under CWM, wiped the factory, wipied cache, and did all the wipes. Afterwords, I installed the rom from the internal sd, went back and restored the backup I had previously made through CWM. I proceeded to reboot after all this.
My phone just turned off, no reboot. No power whatsoever.
So....is this thing just paperweight now or what? Any help would be appreciated! Thanks!
Model: SCH-I535
ROM: VillainROM- I9300 w/Ninphetamine Kernel
Verizon Wireless
Samsung Galaxy S3
Click to expand...
Click to collapse
The best thing you can do is what I did. When you send it into Samsung tell them you were using the phone to send emails and whatnot and suddenly the phone started heating up and then it shut down and would not turn on.
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
This is the situation and what ive tried to fix it. I was on cm9 and wanted to try jellybam so I flashed using cwm . It was successful but wouldn't boot so I tried to reinstall the rom still no luck so I tried going back to cm9 and it got stuck on the s2 logo screen ! I tried odin to flash a stock rom and it was successful but still stuck on the logo screen. Ive tried gb and ics ive tried to flash with and without bootloaders ive tried reparation but that only fails unless I use the pit file but still didn't fix it. If I flash the stock rooted ics rom and then flash cwm zip i can wipe system then flash cm9/10 but that only gets me to the cm animation . It will sit there till the end of time but wont boot! In cwm If I check the log I get this error I:can't partition unsafe device:/dev/block/mmcb1k1p1. It wont factory reset on stock or cwm it only freezes then bootloops. I hope this is enough info please help me! I love my s2 and even tho I have my s3 I miss my s2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Did you factory reset? What do you mean you reset and it bootloops
Sent from my GS4 running CM11 Kandy Kane
122ninjas said:
Did you factory reset? What do you mean you reset and it bootloops
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
. yes I tried to factory reset but it just freezes then after 5 min. It try's to boot but gets stuck on the galaxy s2 logo screen. I checked the log in cwm and got the error I posted above. I've been flashing for years and never run into an issue I couldn't fix but this one has me stumped
troutslayermv said:
. yes I tried to factory reset but it just freezes then after 5 min. It try's to boot but gets stuck on the galaxy s2 logo screen. I checked the log in cwm and got the error I posted above. I've been flashing for years and never run into an issue I couldn't fix but this one has me stumped
Click to expand...
Click to collapse
Sorry if this sounds rude but have you googled that error?
Sent from my GS4 running CM11 Kandy Kane
Lol no that's not rude. I would ask the same question. ..I did and from what I've gathered its a corrupt sd card or part of the emmc brick bug. There are patched kernels to fix the same issue on the note but nothing for i777. All it says is factory reset and flash a new rom . Ive done that but still no boot. Roms flash fine and I can get into download mode and recovery but It wont factory reset or boot. Stock recovery says your ui is not prepared please factory reset and a bunch of can't mount data errors but it won't factory reset it just freezes then trys to reboot but gets stuck on the s2 logo then back to recovery. Here is the kicker tho. If I install a duel booting kernel I can install a second rom that boots but primary won't. ...I tried swapping primary and secondary roms but it froze....im just lost on this one and out of tricks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm not sure what partition that is. You've go a typo in it, but if the last three letters are correct "1p1", I don't remember seeing that as one of the system partitions. The kernel is in "mmcblk0p5" for instance. It should be "mmcblk1p1" I guess.
If you suspect memory damage to that partition, you can confirm that by trying to pull the data from that memory block with adb or terminal using the following command:
Code:
dd if=/dev/block/mmcblk1p1 of=/sdcard/testBLK
If the memory is damaged, you will get an error message. If the memory block is good, you will get no error message. I guess you could also look into "testBLK" to see what is in there, but of course it will be binary data most likely.
That's the error I got 1p1. Abd is something I haven't done yet. I've used terminal emulator back in the days of my cliq dext but im sure I can handle it...im pretty sure it is corrupt but if I do the test and confirm this how do I fix it? Is it just a matter of deleting or do I have to rewrite the path? Im confused on this
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Actually, this was bad advice. Since your phone is bootlooping, you can't use terminal, doh! If you can get into recovery, you might be able to use adb. Or you could use Red_81's adb portable. You could also try his adb batch file from download mode to see if you can boot it into recovery mode. I guess it will take a little study if you have no experience with it.
Oh, and if the memory is bad, its bad. This is just a way to find out, maybe.
So what your saying is it's dead?!!!
Noooooooo! Lol im looking into maybe getting another one or shipping this one to Samsung to have a new motherboard put in . Just trying to see if there is any hope of bringing her back to life...
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
troutslayermv said:
So what your saying is it's dead?!!!
Noooooooo!
Click to expand...
Click to collapse
Not saying that unless you verify for sure that the memory is bad. The only time I've actually heard of eMMC damage, and seen it verified, was in conjunction with the bad stock kernel on 4.0.4. There was also another case where a member sent his phone to Josh at Mobile Tech Videos for Jtag repair, and it was sent back unrepairable due to memory damage. I can't remember for sure, but I think that was due to the 4.0.4 stock kernel too.
You might talk to Josh at Mobile Tech Videos by phone to see what he thinks, before you send it to Samsung.
I tried contacting josh and couldn't reach anyone. I left a message and sent and email but haven't heard back. I tried using adb portable and as I did that I think that I didn't make the phone issues clear. I can get into recovery mode fine I can also get into download mode fine . I can flash roms fine but it won't go past the s2 logo screen . If I flash cyanogen it will go to the cyanogen boot screen but again won't boot. I am still trying to find a solution in my free time but nothing yet
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
troutslayermv said:
I tried contacting josh and couldn't reach anyone. I left a message and sent and email but haven't heard back. I tried using adb portable and as I did that I think that I didn't make the phone issues clear. I can get into recovery mode fine I can also get into download mode fine . I can flash roms fine but it won't go past the s2 logo screen . If I flash cyanogen it will go to the cyanogen boot screen but again won't boot. I am still trying to find a solution in my free time but nothing yet
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
Click to expand...
Click to collapse
I have run into something similar, my wife has the s2... I have the s3....
this is the steps I run to get the s2 working after it gets stuck...
1 - installed stock rom I777UCKH7 OCD Root No BL = self executable from windows.... brings you to stock with root..
forget this one, this is when I was first rooting... 2 - DooMLoRD_v4_ROOT-zergRush-busybox-su
3 - MobileODINLite-v3.57
4 - MobileODIN_FlashKernel_I777-v1.0
5 - flash kernal Siyah-v2.6.14-att.tar = installs recovery clockwork mod
6 - install any rom....
Download mode on S2 is volume up and down and power button....
I can't get it to boot up so I can't use mobile odin. I've tried one click and also tried every stock tar I could find . I even tried to reinstall the bootloaders. They all install successful but it wont boot past the s2 logo screen. Im not a noob , I've flashed hundreds of times. I've fixed a few bricks in my day but this has me stumped. ...if you install the stock rom there isn't any reason why it shouldn't boot. But it is just stuck. Nothing has worked. I think the only thing that may work is the re write the memory but im not that patient to do that lol
sent from my stock galaxy s3
devices: g1 died
cliq/dext sold to developer on simply android
atrix 1 and 2 sold
s2 in a comma
nexus 7 stock
s3 stock
iphone 4 stock
Have U tried threatening it? Just give it a little scare. It'll back dowin. Gotta keep thoz hoez in line.
Phalanx7621 said:
Have U tried threatening it? Just give it a little scare. It'll back dowin. Gotta keep thoz hoez in line.
Click to expand...
Click to collapse
ROFL
Sent from my SGH-I777 using xda premium
gireeshtty9 said:
ROFL
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Just curious if you unmounted and remounted the partitions?
or maybe formatted them individually?
Soft-bricked Galaxy 2 SGH-I777. Odin of no use
I bought a galaxy 3. I literally tried everything with this phone. Was able to root, went to install siyah kernel from zip and now I get the samsung logo. I can boot into CWM recovery, but none of the functions work--just hangs on the hat. Any ideas are greatly appreciated. Thanks.
keltaurn said:
...Any ideas are greatly appreciated...
Click to expand...
Click to collapse
Please don't re-post; your question has been answered in the thread you created. Please search for answers first; the solution to your problem is safely housed in a sticky in the General section.
Thanks but...
I can't flash anything so this would be a new thread. The poster above said he/she could flash toms. I CANNOT. Also, I've been looking on here for solutions for over a month. This is my first post.
Hello,
For the past months I've been experiencing a lot of problems with my device: The device frozes or slow up with no apparent reason. It happens either when I'm in Whatsapp, or Facebook, or just listening music. It doesn't look to have any special app to behave like that. Locking and unlocking the screen becomes a pain and at some point after freezing it just turns off or reboot. Sometimes it just reboots even when I don't use it.
At the beginning I thought that the problems were related to the operator stock rom, then I jumped to Rootbox rom and nothing has changed. The phone keeps freezing and rebooting.
I've read that it might be related to a RAM issue, but I don't know if still have warranty so I'd like to check out everything else before taking it to a specialist.
Any idea or advice?
Fer
When you were on the 'operator stock ROM', was it rooted stock? My only idea is that it's possibly kernel related, ie unstable kernel. Try flashing full stock unrooted and see what happens? Else yes, probably hardware unfortunately
Sent from a galaxy far, far away
Hopper8 said:
When you were on the 'operator stock ROM', was it rooted stock? My only idea is that it's possibly kernel related, ie unstable kernel. Try flashing full stock unrooted and see what happens? Else yes, probably hardware unfortunately
Sent from a galaxy far, far away
Click to expand...
Click to collapse
before anything. Thank you for your response.
I had experimented this problems with Siyah on stock and The kernel that comes with rootbox (different pone).
i've noticed that battery life has been also greatly reduced.
Fer
I'm not 100% sure what you mean... I'm asking if you've had this problem with stock ROM & stock kernel? No root / custom kernel.
Sent from a galaxy far, far away
I'm 95% sure your battery is about to die.
Is it a genuine samsung battery?
Swap it and see how it goes.
Also, going stock to see if the device behaves funny would be wise, as hopper is trying to tell you there.
Sent from...this is not even my S2
gastonw said:
I'm 95% sure your battery is about to die.
Is it a genuine samsung battery?
Swap it and see how it goes.
Also, going stock to see if the device behaves funny would be wise, as hopper is trying to tell you there.
Sent from...this is not even my S2
Click to expand...
Click to collapse
My wife's phone has the exact same problem. However I had recently returned her phone back to stock jelly bean. I downloaded the original software from sammobile for her carrier (Bell) and didn't expect to have any problems. I think I may try to swap out the battery.
gastonw said:
I'm 95% sure your battery is about to die.
Is it a genuine samsung battery? 2
Click to expand...
Click to collapse
Yeah, it appears to be a genuine Samsung battery.
However, I'll jump back to stock toda y and see how it goes. If that doesnt work I'll get a new battery. Finaly, if that doesnt work I might start thinking on a new phone :'( .
Thanks again to everyone
esponges said:
Yeah, it appears to be a genuine Samsung battery.
However, I'll jump back to stock toda y and see how it goes. If that doesnt work I'll get a new battery. Finaly, if that doesnt work I might start thinking on a new phone :'( .
Thanks again to everyone
Click to expand...
Click to collapse
Can you please keep me updated. My samsung is already on stock. I flashed it using ODIN, using the official carrier firmware and the problems actually started after flashing it. My wife said her keyboard freezes as well. Sometimes the Samsung logo appears and then the phone shuts off, or she is forced to shut it off herself.
What ROM were you currently using?
rizzyc said:
Can you please keep me updated. My samsung is already on stock. I flashed it using ODIN, using the official carrier firmware and the problems actually started after flashing it. My wife said her keyboard freezes as well. Sometimes the Samsung logo appears and then the phone shuts off, or she is forced to shut it off herself.
What ROM were you currently using?
Click to expand...
Click to collapse
This morning I reflashed to stock rom from my carrier, NO ROOT (stock kernel). So far I've had no problems. The phone runs smoothly and the battery life is okay. I have not experimented any of the problems like the ones listed above.
I'll keep informing along the week.
A factory reset + dalvik wipe combo would be wise.
Tho you need CWM or Mobile Odin to wipe dalvik.
PS: Root has got nothing to do with this.
Sent from the little guy
rizzyc said:
Can you please keep me updated. My samsung is already on stock. I flashed it using ODIN, using the official carrier firmware and the problems actually started after flashing it. My wife said her keyboard freezes as well. Sometimes the Samsung logo appears and then the phone shuts off, or she is forced to shut it off herself.
What ROM were you currently using?
Click to expand...
Click to collapse
Sorry, the ROM I was using was Rootbox and the kernel before with stock rom was siyah.
gastonw said:
A factory reset + dalvik wipe combo would be wise.
Tho you need CWM or Mobile Odin to wipe dalvik.
PS: Root has got nothing to do with this.
Sent from the little guy
Click to expand...
Click to collapse
excuse me, but root doesnt change the kernel to a kernel with custom recovery? I say this cuz now with stock kernel im not experimenting any issue, which I had with stock+siyah and rootbox ROM.
No, root gives you admin access to your device.
A custom kernel will give you CWM.
Of course the only way to keep it all stock with root is with Mobile Odin Pro EverRoot option, framaroot, ExynosAbuse and any one-click-root.
Sent from the little guy