My Xperia S recently took a fall, nothing actually seems damaged though, but now the phone will not boot and is constantly stuck in a bootloop. This was on stock ROM and was looping on the Xperia logo, did a repair via Sony software and no joy. Have now installed CM9 and still looping on the logo. It boots in to recovery fine and I can also mount the USB. Is there anything that may be damaged thats not so obvious to stop this from booting up?
Abandoned-Trolley said:
My Xperia S recently took a fall, nothing actually seems damaged though, but now the phone will not boot and is constantly stuck in a bootloop. This was on stock ROM and was looping on the Xperia logo, did a repair via Sony software and no joy. Have now installed CM9 and still looping on the logo. It boots in to recovery fine and I can also mount the USB. Is there anything that may be damaged thats not so obvious to stop this from booting up?
Click to expand...
Click to collapse
As far as i know, you cannot corrupt data on a phone by dropping it. Of course you can defect parts of the device however, so i don't think this would be involved in the bootloop. Have you tried factory reset? Have you tried to flash a custom kernel / and or ROM?
Growly_ said:
As far as i know, you cannot corrupt data on a phone by dropping it. Of course you can defect parts of the device however, so i don't think this would be involved in the bootloop. Have you tried factory reset? Have you tried to flash a custom kernel / and or ROM?
Click to expand...
Click to collapse
Yeah given that's it's flash memory I didnt think I could break it. Have tried CM9 as mentioned in the OP and still stuck, have just formatted the SD card as well and will see if that helps, just flashing again now.
Abandoned-Trolley said:
Yeah given that's it's flash memory I didnt think I could break it. Have tried CM9 as mentioned in the OP and still stuck, have just formatted the SD card as well and will see if that helps, just flashing again now.
Click to expand...
Click to collapse
Just CM9? Try Xcream, or another stock ROM. Let me know the results :victory:
Growly_ said:
Just CM9? Try Xcream, or another stock ROM. Let me know the results :victory:
Click to expand...
Click to collapse
Same problem with LT26i_6.1.A.2.45_SG_Generic_(1257-6921).ftf will have to do Xcream tomorrow, need to reinstall custom kernal again.
Growly_ said:
Just CM9? Try Xcream, or another stock ROM. Let me know the results :victory:
Click to expand...
Click to collapse
Almost worked, it got further than most, got past the boot logo and loaded in to the Android is updating applications, where it just hung there instead. Have tried rebooting again and now just sticking on the bootlogo again.
Can you flashmode and go back to stock. Could be you jostled something inside like the battery or one of the few components that are loose. I have torn down an Xperia s and there are a few things that could have been knocked loose in a fall.
Sent from my LT26i using Tapatalk 2
mrsatan said:
Can you flashmode and go back to stock. Could be you jostled something inside like the battery or one of the few components that are loose. I have torn down an Xperia s and there are a few things that could have been knocked loose in a fall.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
All functions are working in terms of fastboot, recovery etc, it just doesn't want to boot up past the logo. Tempted to strip it down and see where that gets me. Failing that it's a £50 excess insurance claim
Have you unlocked your bootloader?
rhogz said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
Before the drop it was locked, I reflashed an official ftf file via flashtool and still the same issue, I have since then unlocked the bootloadeer and installed custom kernel and custom ROMS and still nothing is getting past boot logo.
Ended up calling insurance company, only £30 excess and will get a new phone in 7-10 days
Maybe this will work
cant say about it much..may be a hardware issue but u can sure try flashing the KA 12 rom or the Erachter rom.....it shows very less bootloop problems..or the best way will be to flash the official sony firmware through flashtool and use akramar ics kernel to get root...
PEACE
Related
This is the second phone this has happened to, so I'm inclined to believe the problem resides in either the recovery package or there is no way to go from ICS to stock. Here's what I did and what the result was.
1. Initial phone was having hardware issues. I needed to return it to the warranty exchange depot, so I went to flash the no BL file that you can download from the recovery thread. Everything indicated that it flashed just fine. Phone reboots after the process and it gets the the "rethink Everything" splash screen and just sits there. After a minute, it reboots the phone again. Does the same thing. I take the phone in and get it swapped out under warranty.
2. Load CM9 on new phone and notice that GPS doesn't work. Everyone else says theirs works for the same nightly (5/22), so obviously it's my phone that's the problem or a bad flash. Flash a new nightly (5/29) and GPS still doesn't work. I want to flash back to stock to ensure that it's the hardware that's the problem, not the software. I download the most current recovery NO BL file from the recovery thread to ensure I have a good one. Flash it and the exact same thing happens. I get the splash screen then a reboot.
So now the question is, does flashing ICS permanently make it so you can't flash back? Does ICS work fine, but for some reason CM9 doesnt? Has anyone else done this without a problem? If so, what did you do because 2 phones 'bricking' like this isn't convinsing me that it can be done.
stalked_r/t said:
This is the second phone this has happened to, so I'm inclined to believe the problem resides in either the recovery package or there is no way to go from ICS to stock. Here's what I did and what the result was.
1. Initial phone was having hardware issues. I needed to return it to the warranty exchange depot, so I went to flash the no BL file that you can download from the recovery thread. Everything indicated that it flashed just fine. Phone reboots after the process and it gets the the "rethink Everything" splash screen and just sits there. After a minute, it reboots the phone again. Does the same thing. I take the phone in and get it swapped out under warranty.
2. Load CM9 on new phone and notice that GPS doesn't work. Everyone else says theirs works for the same nightly (5/22), so obviously it's my phone that's the problem or a bad flash. Flash a new nightly (5/29) and GPS still doesn't work. I want to flash back to stock to ensure that it's the hardware that's the problem, not the software. I download the most current recovery NO BL file from the recovery thread to ensure I have a good one. Flash it and the exact same thing happens. I get the splash screen then a reboot.
So now the question is, does flashing ICS permanently make it so you can't flash back? Does ICS work fine, but for some reason CM9 doesnt? Has anyone else done this without a problem? If so, what did you do because 2 phones 'bricking' like this isn't convinsing me that it can be done.
Click to expand...
Click to collapse
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
nakedninja42 said:
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
by factory reset, you mean from the recovery console?
nakedninja42 said:
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok. You may now mock me. I did a factory reset and it worked. Feel like such a noob.
nothing to see here folks. Move along. Red, you can shut 'er down.
stalked_r/t said:
Ok. You may now mock me. I did a factory reset and it worked. Feel like such a noob.
nothing to see here folks. Move along. Red, you can shut 'er down.
Click to expand...
Click to collapse
No one would mock you over this. It is your experience.
Next time, when somebody hit the same or similar problem, do help them.
Friendly reminder.. If you can start your title with [q], it probably belongs in QA...
Mock mock mock!
Great to know, this may not be posted and is only available as "common knowledge". You sir have made this solution available to anyone searching for it. Thank you!
Clay
Sent from my SGH-I777 using XDA
Hi there,
i tried a lot of word combinations to get a thread with my specific problem but i didnt manage it to find one.
So here is the deal:
i have german galaxy s 2 (9100, bought in september 2011) and i flashed it last year with darkyrom HD something gingerbread-style.
so it was rooted and all that stuff.
it worked pretty fast and it was stable and it looked sleak.
Last year in November i put Ressurrection remix 3.x (dont know which version of it) on my phone.
It had a lot of crashes, freezes and while playing ingress it always drained around 20% of the battery within 10-20minutes.
So i stopped it. I put the last version of it 3.1.3. of it onto my phone with a full wipe, cache partition, factory reset onto my phones and the problems went keep going.
As an example:
-I couldnt access options where i can select ringtones or to see what is on the sd. it crashed and went back to the "main screen".
-Yesterday i tried around 15 roms, and nearly everything except militant rom keep crashing while iam installing them.
-Sometimes it crashes already while iam installing the rom, sometimes its after a couple of hours, that i cant access the rom any more.
-The newest problem is, that sometimes the power button doesnt respond, when i push it (in jelly bam)
Please explain, what iam missing or is my phone just broke?
It never fell down, no water or anything freaking other things.
I hope you can help me.
should i send it back or what is wrong?
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Try changing kernel
Sent from my GT-i9100
sreehari.007 said:
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
so what do i have to do to make it work flawlessly?
i cant boot it right now without the power plug.... and the battery is at 90%....
so something is completely broken within the system....
jootanen said:
Try changing kernel
Sent from my GT-i9100
Click to expand...
Click to collapse
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
flash a stock ROM and see how it behaves.
Sent from the little guy
Sakujou_Kei said:
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
Click to expand...
Click to collapse
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
kmaq said:
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
Click to expand...
Click to collapse
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
If you did everything from Factory reset to changing kernel, and everything is still bad like that. I think that there's something with your phone's hardware.
Sakujou_Kei said:
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
Click to expand...
Click to collapse
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
kmaq said:
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
Click to expand...
Click to collapse
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Sakujou_Kei said:
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Click to expand...
Click to collapse
just as an example, when i tried to put on the neatrom-lite on my phone, it crashes while iam selecting the country. and this is just 2-3seconds after booting into the fresh and new system.
something is completely ****ed up....
so right now, i have the militant rom on my phone, got booted up, but the power button doesnt work.... when the phone is on...
so everytime, when i want to switch of the screen, i have to wait, or take of the battery. and switching on is only possible with the home button.
whats wrong?
Given you have the same problems on stock, hardware problem. Back to stock, reset counter, send it in for warranty service (if you have warranty), if not, take it to local mobile repair shops.
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Sakujou_Kei said:
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Click to expand...
Click to collapse
You have two option. Either flash a custom kernel (siyah, for example), then reset the counter using triangle away app. Then flash a stock firmware using odin. This wont increase the counter.
Or, if you have a USB jig, flash an older bootloader (have to careful here), then simply plug in the jig.
Sent from my GT-I9100 using xda app-developers app
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Sakujou_Kei said:
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Click to expand...
Click to collapse
Unzip first.
I'd advice you to read about flashing with odin and watch a couple of videos on youtube before you put yourself up to it or else you're gonna have a bad flash, and that means trouble.
Sent from the little guy
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
Been playing with my phone all day and somehow it crashed/rebooted & now I'm getting "Process system isn't responding"ever time it boots back up. Im rooted and have TWRP recovery...made a backup before all this started. Tried restoring my backup, didnt work, nor did using ODIN to flash a stock file. Full wipes and format data doesn't do any good either...Any suggestions?
I had the same issue this morning and after wiping and odin'ing what seems liked 30 times for 4 hours, I ended up taking it back. BB swapped it out with no questions asked.
The only thing I can think that happened was I tried restoring a backup with TWRP. I thought I read on here that restoring was not a good idea right now.
Looks like I am going to have to return this as well...every time it boots I get that error message and then it reboots itself....Did you do anything to flash back stock status??
jauger said:
Looks like I am going to have to return this as well...every time it boots I get that error message and then it reboots itself....Did you do anything to flash back stock status??
Click to expand...
Click to collapse
Oh yes, many, many times! After I got stuck in a boot loop (or bootup system error), I wiped every partition I could find on the phone using stock TWRP and OUDH recoveries. Than I would odin multiple times using the MI3 tar. The odin process would be successful, but I would get stuck in a boot-loop every time. I'm fairly savvy with Samsung phones as I have rooted all 5 that I've owned but I couldn't figure this one out so I just took it back.
jauger said:
Looks like I am going to have to return this as well...every time it boots I get that error message and then it reboots itself....Did you do anything to flash back stock status??
Click to expand...
Click to collapse
After the successful Odin, have you tried booting into stock recovery and wiping data? That can often fix problems booting up after a restore..
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
lmemma16 said:
After the successful Odin, have you tried booting into stock recovery and wiping data? That can often fix problems booting up after a restore..
Click to expand...
Click to collapse
Edit: Nevermind, just read your op more carefully, lol. So you did try that?
runner77 said:
Oh yes, many, many times! After I got stuck in a boot loop (or bootup system error), I wiped every partition I could find on the phone using stock TWRP and OUDH recoveries. Than I would odin multiple times using the MI3 tar. The odin process would be successful, but I would get stuck in a boot-loop every time. I'm fairly savvy with Samsung phones as I have rooted all 5 that I've owned but I couldn't figure this one out so I just took it back.
Click to expand...
Click to collapse
I did the same thing, finally gave up and took it back for an exchange...( had my sad story all figured out.. :cyclops It felt like it should of been an easy fix but I could never figure it out...
same issues...
jauger said:
I did the same thing, finally gave up and took it back for an exchange...( had my sad story all figured out.. :cyclops It felt like it should of been an easy fix but I could never figure it out...
Click to expand...
Click to collapse
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
derail412 said:
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
Click to expand...
Click to collapse
I'm 99% sure that's what killed mine....TWRP restore. I told the store I woke up and my phone was boot looping. No further questions asked.
Sent from my Note 3 on Android
derail412 said:
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
Click to expand...
Click to collapse
All I said was a System Update notification popped up, I clicked OK and it went into a full on boot loop.....
jauger said:
All I said was a System Update notification popped up, I clicked OK and it went into a full on boot loop.....
Click to expand...
Click to collapse
Did you by at Sprint or BB or some other retailer? I'm afraid that I'm SOL as I bought from Sprint.
derail412 said:
Did you by at Sprint or BB or some other retailer? I'm afraid that I'm SOL as I bought from Sprint.
Click to expand...
Click to collapse
The Sprint store is not going to have the software to restore your phone yet. So they will replace it as they want even be able to tell its rooted...Well unless they go into download mode which i don't see why they would do that right now. .. BUT This is something you can fix yourself. From what i read you only flashed the stock TAR once. Flash it again and see what happens. Pay attention to what you are restoring. The first time i rooted i couldn't make phone calls...I have no idea what cause it. Now i am on Stock but mi3 as i forgot to pull the SD card.. And its not that serious to go to mi5 at this point.
Edit: If stock still dosent work after multiple attempts.... GO ahead and flash stock rooted ROM. In the next week or so everything will be figured. out. There want be any big updates that you miss in the next month. I wouldn't worry about being on stock rooted or stock unrooted. All the same for now.
I've retried several times with the STOCK unrooted tar. No go with that. Just boot loops...
I didn't see where there is a stock rooted ROM. I'll look in the development areas for it. If you have link would you reply with the link?
derail412 said:
I've retried several times with the STOCK unrooted tar. No go with that. Just boot loops...
I didn't see where there is a stock rooted ROM. I'll look in the development areas for it. If you have link would you reply with the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2472664
Got it thanks!
No Luck...
jauger said:
All I said was a System Update notification popped up, I clicked OK and it went into a full on boot loop.....
Click to expand...
Click to collapse
derail412 said:
I have similar issues. I tried to recover my original TWRP backup and now my phone is in a boot loop. Even taking the original system and restoring it via ODIN won't fix this?
No questions asked by the store?
Click to expand...
Click to collapse
dallastx said:
http://forum.xda-developers.com/showthread.php?t=2472664
Click to expand...
Click to collapse
I downloaded the ODEX'd and Deodexed STOCK rooted ROMs and neither worked for me. I am at a loss for what to do. I'm not sure if I wait I'll have any better luck. I am so frustrated at this point...
I do appreciate your help. Thank you.
derail412 said:
I downloaded the ODEX'd and Deodexed STOCK rooted ROMs and neither worked for me. I am at a loss for what to do. I'm not sure if I wait I'll have any better luck. I am so frustrated at this point...
I do appreciate your help. Thank you.
Click to expand...
Click to collapse
Still bootloop?
Sent from my SM-N900P using Tapatalk 2
Sprint store....
Sent from my SM-N900P using xda app-developers app
Yes... still boot loop.
derail412 said:
Yes... still boot loop.
Click to expand...
Click to collapse
Just out of curiosity reboot your phone then press and hold the menu button when the Sprint boot screen pops up on reboot..see if by some weird chance your phone boots into Safe Mode...
jauger said:
Just out of curiosity reboot your phone then press and hold the menu button when the Sprint boot screen pops up on reboot..see if by some weird chance your phone boots into Safe Mode...
Click to expand...
Click to collapse
Wow just did this in my note 2 and it worked. Booted into safe mode. . Didn't know the phone had a safe mode. . Do you know what the difference is. . I didn't see my apps.. anything else?
Sent from my SPH-L900 using Xparent Purple Tapatalk 2