Related
Hey guys,
having a trouble for the last couple weeks.
about 5-6 times a day, with no apparent reason, nor something specific i'm doing.
my phone suddenly freezes and the screen goes black, and the notifications led goes blue (not blinking, permanent blue).
only way out of this is long pressing the power button, and the phone goes back on, as if it was turned off.
tried to find out the source of the problem but with no luck.
i'm using
GT-i9300 S3
Rom: cfDroid v13.1 - based on XXEMA2 (4.1.2 android)
Kernel: Perseus alpha 33 (the latest)
Modem: DXELK1
Mods: JKay, acid soundmod, and some other that comes with cfDroid rom
Anyway to pin point the problem and take care of it without having to fully wipe and install a fresh rom?
if you need any more details please ask and i'll post.
Thanks
Are you undervolting the cpu?
No i dont
Sent from my GT-I9300 using xda app-developers app
Re-flash ROM you're using, wipe cache and Dalvik only, if still no improvement change kernel.
Sent from my GT-I9305 using xda app-developers app
i have the same problem. wiping dalvik cache and cache doesnt fix that problem.
Rom: Omega Rom v43
Kernel: Perseus 33.2
currently im switching over to yank and report back, if the problem is gone.
Hey, please update if it is kernel related.
i want to know this before re-flashing the rom
Thanks!
i'm running yank since 2h and the problem is gone... please test this and report back, so we can send Andrei a message.
I had the same problem maybe you have bad blocks there is another thread having the same problem they have a solution in page 7
Sent from my GT-I9300 using Tapatalk 2
Can you please post the link to the thread?
Edit: did you mean this?
dontobi said:
i'm running yank since 2h and the problem is gone... please test this and report back, so we can send Andrei a message.
Click to expand...
Click to collapse
mmm i don't know whats happaned but for the last 24 hr the problem didn't occur again.
i didn't change anything, not the kernel also.
waiting to see if its happens again..
Same.
Hi there.
I got a very similar problem.
Screen freezes and turns black.
I ran an continues kernel output and saw a mmc action, but i removed the card before i booted up.
(See pastebin below for kernel log)
And besides the screen is black and the device isn't responding, the kernel is still active and running.
First my specs:
Model: GT-I9300
Android: 4.1.2 (latest Stock)
Base: I9300BUEMA1
Stock-Kernel: 3.0.31-919627 [email protected] #1 SMP PREEMPT
Build: JZO54K.I9300XXEMR2
Modifications:
TWRP Recovery (2.3.3.0-GTI9300)
SuperSU (0.99)
Busybox (BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT))
My kernel log:
pastebin.com/hRSpzu0D
I hope somebody is more kernel knowledge can take a look at the paste.
Thanks in advance.
Ok too early to be glad.
the problem is back, only now its less frequent, and the device simply turns off.
no blue led.
Now trying to flash Yanks kernel and will report back in a day.
Why don't you try stock Rom and see!
Sent from my GT-I9300 with a BIG
jaidev.s said:
Why don't you try stock Rom and see!
Sent from my GT-I9300 with a BIG
Click to expand...
Click to collapse
Thank you but i didn't have the problem with custom roms my friend
it started couple weeks back.
i'm running custom roms from the day i've got my S3.
thinking about that option as last resort :good:
jaidev.s said:
Why don't you try stock Rom and see!
Sent from my GT-I9300 with a BIG
Click to expand...
Click to collapse
I am on stock. I only added root to be able to see the kernel log.
So it appears to me it isn't really rom related. More like 'something in 4.1.2'.
I wish i could put my finger on it.
Regards.
edit:
Maybe we should start to compare the hardware components?
maybe I solved that.
xenonr said:
I am on stock. I only added root to be able to see the kernel log.
So it appears to me it isn't really rom related. More like 'something in 4.1.2'.
I wish i could put my finger on it.
Regards.
edit:
Maybe we should start to compare the hardware components?
Click to expand...
Click to collapse
There was some user reported that problem the last few days...
I had a similar issue, opened a thread yesterday, followed after Slaphead20 advice and make a factory reset.
what i've done was:
factory reset, cache delet from the recovery mode.
flashed and old rom, let kies do the upgrade.
(backed up through myback up) and re-install only what I really needed.
now the phone seem to be running much faster, no lag at all.
i'm still waiting to see if it's freeze.
Still, I think it a software related since so many users start feel those freezes at the same time, it might be some bug in the last update.
oravi said:
There was some user reported that problem the last few days...
I had a similar issue, opened a thread yesterday, followed after Slaphead20 advice and make a factory reset.
what i've done was:
factory reset, cache delet from the recovery mode.
flashed and old rom, let kies do the upgrade.
(backed up through myback up) and re-install only what I really needed.
now the phone seem to be running much faster, no lag at all.
i'm still waiting to see if it's freeze.
Still, I think it a software related since so many users start feel those freezes at the same time, it might be some bug in the last update.
Click to expand...
Click to collapse
Could you please state how far you downgraded?
I willing to try your aproach and want to be as close as possible to your setup.
Thanks.
xenonr said:
Could you please state how far you downgraded?
I willing to try your aproach and want to be as close as possible to your setup.
Thanks.
Click to expand...
Click to collapse
i've downgrade to the I9300XXDLJ4 (uk rom) firmware- as far as I remembered it was the first JB firmware.
I didn't wand to go back to ICS cause I heard it makes problem to downgrade from JB to ICS- I don't know if that right or not.
tell me if it helped you..
Let's give it a shoot
oravi said:
i've downgrade to the I9300XXDLJ4 (uk rom) firmware- as far as I remembered it was the first JB firmware.
I didn't wand to go back to ICS cause I heard it makes problem to downgrade from JB to ICS- I don't know if that right or not.
tell me if it helped you..
Click to expand...
Click to collapse
Thanks for the info. Here we go:
Code:
Start up recovery mode. (TWR v2.3.3.0)
Recovery: Wipe -> Factory Reset
Wipe -> Cache (already included in factory reset, but to be safe)
Reboot -> Power Off
Start up download mode.
Start up Odin.
Downgrade to: 4.1.1 PDA:I9300XXDLIH CSC:I9300VFGDLJ1 (Germany-VD2)
Start up Android 4.1.1.
System failed to boot up.
Start up stock recovery.
Wipe data/factory reset
Wipe cache partition
Reboot system now
Start up Android 4.1.1.
Start up Kies (v2.5.2.13021_10)
Connect Phone to USB.
Kies auto suggests: PDA:MR2 PHONE:MA1 CSC:MA3 (VD2) -> Update
"Proceed without saving"
"Start upgrade"
Disconnect USB.
Wait for startup Android 4.1.2.
Connect Phone to USB.
Final state: PDA:I9300XXEMR2 PHONE:I9300BUEMA1
I just configured my google account and two WLANs. Nothing else yet.
Will report back tomorrow.
---------- Post added at 02:33 PM ---------- Previous post was at 02:17 PM ----------
xenonr said:
I just configured my google account and two WLANs. Nothing else yet.
Will report back tomorrow.
Click to expand...
Click to collapse
Already crashed and burned. Tried to open YouTube.
Saw the "Introduction screen".
Wanted to clear the notifications so pulled down the notification bar.
Pressed "Clear" (don't know what the english text is there).
And freezed. No response at all.
Back to square one! :crying:
OK after running yank555 kernel for couple of days,
the problem still occurs, only now its more rare (1-2 times a day)
and now no led blinking in blue - the device turns off completely
Preface: I have zero knowledge of android development and rooted my phone myself.
Some months ago I decided to root my S2 i777.
I followed the instructions on this page word for word: http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
I decided to do it after my stock was getting laggy and was randomly shutting down and throwing the battery calibration off. After reading the good feedback in that page's comment section. I gave it a go.
Everything went fine and my now-rooted S2 was no longer randomly shutting down!
I noticed though that the caera and video playback stopped aorking. As in, the screen would be black. I could still take pictures, but I would knot know what it looked like until it was taken. That didn't bother me much though since not having the phone shut down random;y several times throughout the day anymore was more than worth that unfortunate loss.
Today, though. It started randomly cutting to black and boothing constantly. My battery calibration was all over the place. It has restarted at least 10 times today.
I talked to my friend that originally conviced me to root and he said to do a factory reset. I backed up my contacts on my SIM and did so.
Now it won't boot past the screen that reads "Samsung Galaxy SII GT-1900" with the yellow warning triangle underneath (this is wha tthe boot screen changed to after rooting.).
I can not boot into recovery mode via keeping all three side buttons pressed.
Any thoughts?
Thanks!
GPS_Music said:
Preface: I have zero knowledge of android development and rooted my phone myself.
Some months ago I decided to root my S2 i777.
I followed the instructions on this page word for word: http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
I decided to do it after my stock was getting laggy and was randomly shutting down and throwing the battery calibration off. After reading the good feedback in that page's comment section. I gave it a go.
Everything went fine and my now-rooted S2 was no longer randomly shutting down!
I noticed though that the caera and video playback stopped aorking. As in, the screen would be black. I could still take pictures, but I would knot know what it looked like until it was taken. That didn't bother me much though since not having the phone shut down random;y several times throughout the day anymore was more than worth that unfortunate loss.
Today, though. It started randomly cutting to black and boothing constantly. My battery calibration was all over the place. It has restarted at least 10 times today.
I talked to my friend that originally conviced me to root and he said to do a factory reset. I backed up my contacts on my SIM and did so.
Now it won't boot past the screen that reads "Samsung Galaxy SII GT-1900" with the yellow warning triangle underneath (this is wha tthe boot screen changed to after rooting.).
I can not boot into recovery mode via keeping all three side buttons pressed.
Any thoughts?
Thanks!
Click to expand...
Click to collapse
Have you tried getting into download mode to flash back to stock?
Sent from my SGH-I777 using xda app-developers app
chapelfreak said:
Have you tried getting into download mode to flash back to stock?
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
I do not know how to do that
Click the return to stock thread in this guys signature . Creepyncrawly has all the links http://forum.xda-developers.com/member.php?u=2916435
@GPS_Music,
If you still want a rooted phone, then rather than flashing straight stock, why don't you save yourself a step, and flash Stock plus root. The links in my signature give pretty clear directions.
Since you originally rooted with files from GalaxyS2Root, the problems you have experienced are very likely related to the quality of those files. If you avoid GalaxyS2Root in the future, and use files from these forums, you will have a much better experience.
Since you want JellyBean, after you flash stock plus root, you could follow my guide to install a custom kernel which contains ClockworkMod Recovery, and then flash one of the fine JellyBean firmwares available in the development section.
If you have any questions as you go along, feel free to ask them in this thread.
creepyncrawly said:
@GPS_Music,
If you still want a rooted phone, then rather than flashing straight stock, why don't you save yourself a step, and flash Stock plus root. The links in my signature give pretty clear directions.
Since you originally rooted with files from GalaxyS2Root, the problems you have experienced are very likely related to the quality of those files. If you avoid GalaxyS2Root in the future, and use files from these forums, you will have a much better experience.
Since you want JellyBean, after you flash stock plus root, you could follow my guide to install a custom kernel which contains ClockworkMod Recovery, and then flash one of the fine JellyBean firmwares available in the development section.
If you have any questions as you go along, feel free to ask them in this thread.
Click to expand...
Click to collapse
Thank you for your reply.
The main reason I opted to use that site was because of the ese of the steps, as well as the pictures. I wanted a method that was clear so I would minimize me messing up. I will look into your signature links now, but I should note that I don't recall stating I wanted JellyBean...my phone is 4.0.x last I recall, which is ICS.
Hey creepyncrawly,
I was able to download the material from your signature yesterday, but unfortunately my battery wa too low to safely put into downlaod mode (according to the phone, which read something along the lines of "Battery low! Can not download!" in red).
I tried charging it before I went to bed but it would not go past the screen that shows the battery indicator with a loading circle int he middle (which was not rotating). It would then go black and the screen would "retsart" constantly to black screens (I did not notice this until I turned off my room lights, the screen was very black but I could tell it was turning on and off).
I am trying again now to charge it but I seem to be having the same issue. I will leave it plugged to my charger for an hour and then try to turn it on.
-GPS
GPS_Music said:
Hey creepyncrawly,
I was able to download the material from your signature yesterday, but unfortunately my battery wa too low to safely put into downlaod mode (according to the phone, which read something along the lines of "Battery low! Can not download!" in red).
I tried charging it before I went to bed but it would not go past the screen that shows the battery indicator with a loading circle int he middle (which was not rotating). It would then go black and the screen would "retsart" constantly to black screens (I did not notice this until I turned off my room lights, the screen was very black but I could tell it was turning on and off).
I am trying again now to charge it but I seem to be having the same issue. I will leave it plugged to my charger for an hour and then try to turn it on.
-GPS
Click to expand...
Click to collapse
It sounds to me like you're trying to put it in Recovery Mode. Download mode is something completely different. Here's what you can do:
- Take the battery out.
- Leave it out.
- Hold down Vol Up and Vol Down.
- While they are pressed, plug the phone into your computer.
This should place you in Download Mode. Then used Odin to flash the Stock Plus Root package.
mattdm said:
It sounds to me like you're trying to put it in Recovery Mode. Download mode is something completely different. Here's what you can do:
- Take the battery out.
- Leave it out.
- Hold down Vol Up and Vol Down.
- While they are pressed, plug the phone into your computer.
This should place you in Download Mode. Then used Odin to flash the Stock Plus Root package.
Click to expand...
Click to collapse
Download mode is what I was intending for, and Vol Up and Vol Down is what I was pressing.
Are you saying to leave the battery out completely during the entire proces? That doesn't seem right.
As of now, I still can not get my battery to charge. I wonder if the ATT store cna loan me a replacement battery for a little bit.....
GPS_Music said:
Download mode is what I was intending for, and Vol Up and Vol Down is what I was pressing.
Are you saying to leave the battery out completely during the entire proces? That doesn't seem right.
As of now, I still can not get my battery to charge. I wonder if the ATT store cna loan me a replacement battery for a little bit.....
Click to expand...
Click to collapse
Yes, I'm saying leave the battery out for the whole process. The USB connection will supply the power.
Seriously, just give it a try.
mattdm said:
Yes, I'm saying leave the battery out for the whole process. The USB connection will supply the power.
Seriously, just give it a try.
Click to expand...
Click to collapse
It worked! Thanks so much!
However, It reverted me back to jellybean 2.3.4 and feels sluggish compared to when I had ICS, should i manually update it or should I install come custom rom?
GPS_Music said:
It worked! Thanks so much!
However, It reverted me back to jellybean 2.3.4 and feels sluggish compared to when I had ICS, should i manually update it or should I install come custom rom?
Click to expand...
Click to collapse
Should I eat Mexican or Italian for dinner tonight?
Sent from my Galaxy Nexus
GPS_Music said:
It worked! Thanks so much!
However, It reverted me back to jellybean 2.3.4 and feels sluggish compared to when I had ICS, should i manually update it or should I install come custom rom?
Click to expand...
Click to collapse
I think you mean Gingerbread 2.3.4. Also, if you're rooted, never attempt an official update.
You can do what you want, but if you want my personal opinion, I would suggest a custom rom. If you think ICS was fast, wait until you try Jellybean. If you want a Touchwiz rom, probably go with ShoStock 3. If you want a more stock Nexus-ish flavor, give Task's AOKP a try. Just remember to follow each thread's installation instructions exactly, which means a full wipe.
mattdm said:
I think you mean Gingerbread 2.3.4. Also, if you're rooted, never attempt an official update.
You can do what you want, but if you want my personal opinion, I would suggest a custom rom. If you think ICS was fast, wait until you try Jellybean. If you want a Touchwiz rom, probably go with ShoStock 3. If you want a more stock Nexus-ish flavor, give Task's AOKP a try. Just remember to follow each thread's installation instructions exactly, which means a full wipe.
Click to expand...
Click to collapse
The main thing I am looking for is a smooth interface, minimal lag, and reliable. Which ROM fits that description? And may you link me to it's instructions?
Thanks!
NOTE: I just experienced a random restart. I was using the phone and the screen suddenly went black and bootted again. This is the same issus I was experiencing before I re-rooted.
Should I be concerned?\
EDIT: It happened agian, not even a minute after the previous one after it was all re-booted up.
I am seeing he following under About Phone:
Model Number: SAMSUNG-SGH-I777
Android Version: 2.3.4
Baseband Version: I777UCKH7
Kernel Version: 2.6.35.7
Build Number: GINGERBREAD.UCKH7
GPS_Music said:
The main thing I am looking for is a smooth interface, minimal lag, and reliable. Which ROM fits that description? And may you link me to it's instructions?
Thanks!
Click to expand...
Click to collapse
Either of the roms I mentioned will give you a smooth interface and be reliable. And no, you can get to the instructions yourself. I'll give you a hint; the ShoStock 3 instructions are in the ShoStock 3 thread, and the AOKP instructions are in the AOKP thread.
It's pretty clear you don't really know what you're doing, so I'll spoonfeed you a little more. You're not going to use Odin to flash the rom. You're going to use CWM Recovery. You can get CWM Recovery by flashing a kernel that includes it. Here's what you do:
1. Download rom of choice and save it to your SD card.
2. Install Mobile Odin Lite.
3. Download Siyah kernel.
4. Extract the zimage and save it to your SD card.
5. Use Mobile Odin to flash the zimage.
6. Boot into Recovery.
7. Wipe Data, Cache, and Dalvik Cache.
8. While still in Recovery, install rom.
9. Reboot.
Most people will not (and should not) be as helpful as I just was. In the future, read read read. Read the stickies, search for threads that deal with issues you may be having, and read them. All the info you need is already out there, you just need to learn how to find it.
GPS_Music said:
NOTE: I just experienced a random restart. I was using the phone and the screen suddenly went black and bootted again. This is the same issus I was experiencing before I re-rooted.
Should I be concerned?
Click to expand...
Click to collapse
It'll go away once you flash a different rom.
mattdm said:
Either of the roms I mentioned will give you a smooth interface and be reliable. And no, you can get to the instructions yourself. I'll give you a hint; the ShoStock 3 instructions are in the ShoStock 3 thread, and the AOKP instructions are in the AOKP thread.
It's pretty clear you don't really know what you're doing, so I'll spoonfeed you a little more. You're not going to use Odin to flash the rom. You're going to use CWM Recovery. You can get CWM Recovery by flashing a kernel that includes it. Here's what you do:
1. Download rom of choice and save it to your SD card.
2. Install Mobile Odin Lite.
3. Download Siyah kernel.
4. Extract the zimage and save it to your SD card.
5. Use Mobile Odin to flash the zimage.
6. Boot into Recovery.
7. Wipe Data, Cache, and Dalvik Cache.
8. While still in Recovery, install rom.
9. Reboot.
Most people will not (and should not) be as helpful as I just was. In the future, read read read. Read the stickies, search for threads that deal with issues you may be having, and read them. All the info you need is already out there, you just need to
It'll go away once you flash a different rom.
Click to expand...
Click to collapse
Understood and much appreciated!
I suppose it's just me being over-over-over-careful and making absolutely sure I don't screw anything up (like last time). Though now I know this is the site to go to for any reference!
Thanks again!
Yup same problem i'm facing just tooooo carefull and i also read a lot of treaths but still i think sometimes That its not going to work sometimes the same thing would not work, deu to the fact that a Noob like me and u forgot a small step or someting
And then u had lucky u could take out the batterij.
I have 3 xperia's and all 3 can't take the batterij out so i don't had much time to fix it.
But as long as u try and say really good what u did and what u used.
Btw does everything work properly Again
verstuurd vanaf mijn Xperia Z using tapatalk
petervda87 said:
Yup same problem i'm facing just tooooo carefull and i also read a lot of treaths but still i think sometimes That its not going to work sometimes the same thing would not work, deu to the fact that a Noob like me and u forgot a small step or someting
And then u had lucky u could take out the batterij.
I have 3 xperia's and all 3 can't take the batterij out so i don't had much time to fix it.
But as long as u try and say really good what u did and what u used.
Btw does everything work properly Again
verstuurd vanaf mijn Xperia Z using tapatalk
Click to expand...
Click to collapse
Translation?
Sent from my SGH-I777 using xda app-developers app
Hi guys, i have this weird problem with touchscreen after i've had a faulty flash in Jelly Bean. My touches cannot hold and drag or drop items, for example i can't hold notification center halfway. Also, there is a problem with overall performance: Videos seem to skip 1-2 seconds every second, music plays the same way, and everything feels heavier, my battery also seems to drain very fast. The weird thing is that phone is perfect when i plug it in a power source, no problems at all. There are some other posts with this problem, but no one seemes to be able to solve this permanently. Some workarounds are flashing blazing v8 with any stock firmware, or flashing CM 10.1-20130121-EXPERIMENTAL-i9100g-M1 ROM, but both has SOD s and random reboots, and the vast battery drain still continues.
The milestone to solving this is this thread : http://forum.xda-developers.com/showthread.php?t=2147306, but it's still NOT solved for months... It seems like this is a problem that only a developer can solve, but i cannot post there, so if anyone finds another workaround/ have the same issue/ can-has solve this/ can post the problem on the developer page is welcome
EDIT: SOLVED!
"Thanks to hawkerpaul for making nuke script, and thanks to jimsilver for reminding me of it! If anyone has this problem, here are the steps i took:
1- Download GS2RomNuke (Read all instructions),
2- Download the rom you want and gapps ofc (Read all instructions),
3- Put them in your phone, i put in the sd card and it worked,
4- Flash GS2RomNuke, don't reboot or anything, flash your rom and gapps,
5- Reboot and done!"
So on that thread they say their phone works fine on stock GB/ICS;but not on JB.
You can either WAIT for a fix,code one yourself,use GB or ICS,or email the CEO of Samsung and complain to him.
Dakura said:
Hi guys, i have this weird problem with touchscreen after i've had a faulty flash in Jelly Bean. My touches cannot hold and drag or drop items, for example i can't hold notification center halfway. Also, there is a problem with overall performance: Videos seem to skip 1-2 seconds every second, music plays the same way, and everything feels heavier, my battery also seems to drain very fast. The weird thing is that phone is perfect when i plug it in a power source, no problems at all. There are some other posts with this problem, but no one seemes to be able to solve this permanently. Some workarounds are flashing blazing v8 with any stock firmware, or flashing CM 10.1-20130121-EXPERIMENTAL-i9100g-M1 ROM, but both has SOD s and random reboots, and the vast battery drain still continues.
The milestone to solving this is this thread : http://forum.xda-developers.com/showthread.php?t=2147306, but it's still NOT solved for months... It seems like this is a problem that only a developer can solve, but i cannot post there, so if anyone finds another workaround/ have the same issue/ can-has solve this/ can post the problem on the developer page is welcome
Click to expand...
Click to collapse
Have you tried using @hawkerpauls GS2RomNuke followed by clean ROM?
theunderling said:
So on that thread they say their phone works fine on stock GB/ICS;but not on JB.
You can either WAIT for a fix,code one yourself,use GB or ICS,or email the CEO of Samsung and complain to him.
Click to expand...
Click to collapse
The thing is, it works on JB stock firmware with blazing kernel v8, but not on the latest versions of this kernel, and this problem occurs to a minority of users so i don't think anyone is aware of this, which is why i started this thread, if the CEO of Samsung gave a hoot about our problems, this forum would not exist...
Jimsilver73 said:
Have you tried using @hawkerpauls GS2RomNuke followed by clean ROM?
Click to expand...
Click to collapse
I didn't, i will try now, thanks :good: Btw, i have tried buying a new original battery, didn't work
Dakura said:
I didn't, i will try now, thanks :good: Btw, i have tried buying a new original battery, didn't work
Click to expand...
Click to collapse
Can't really see how this problem would be related to battery though???
Jimsilver73 said:
Can't really see how this problem would be related to battery though???
Click to expand...
Click to collapse
When i plug in the phone to a power source, it is working perfectly well, which is why i thought there was a problem with my battery, it made sense back then
Hmm, it says that this nuke script is for GT-I9100, will it work for the G variant?
Dakura said:
When i plug in the phone to a power source, it is working perfectly well, which is why i thought there was a problem with my battery, it made sense back then
Hmm, it says that this nuke script is for GT-I9100, will it work for the G variant?
Click to expand...
Click to collapse
I read something from @hawkerpaul saying he couldn't see why not, but as I own an i9100 I obviously can't vouch for that. Suggest you search @hawkerpauls thread and read for yourself.
Flash it (at your own risk) and if that doesn't work you always have odin to go back to :good:
Jimsilver73 said:
I read something from @hawkerpaul saying he couldn't see why not, but as I own an i9100 I obviously can't vouch for that. Suggest you search @hawkerpauls thread and read for yourself.
Flash it (at your own risk) and if that doesn't work you always have odin to go back to :good:
Click to expand...
Click to collapse
I couldn't see why not too, so i went ahead already and nuked and flashed today's CM nightly :laugh: I'll test for some time and get back.
Dakura said:
I couldn't see why not too, so i went ahead already and nuked and flashed today's CM nightly :laugh: I'll test for some time and get back.
Click to expand...
Click to collapse
glad to see you give it a go :good:
Seems like everything is working fine now! Im really surprised this being so easy after 2 months, because i've already made many wipes and flashed brand new stock from odin, but looks like it literally nukes the phone! :laugh: Thanks to hawkerpaul for making nuke script, and thanks to jimsilver for reminding me of it! If anyone has this problem, here are the steps i took:
1- Download GS2RomNuke (Read all instructions),
2- Download the rom you want and gapps ofc (Read all instructions),
3- Put them in your phone, i put in the sd card and it worked,
4- Flash GS2RomNuke, don't reboot or anything, flash your rom and gapps,
5- Reboot and done!
i will try
Dakura said:
Seems like everything is working fine now! Im really surprised this being so easy after 2 months, because i've already made many wipes and flashed brand new stock from odin, but looks like it literally nukes the phone! :laugh: Thanks to hawkerpaul for making nuke script, and thanks to jimsilver for reminding me of it! If anyone has this problem, here are the steps i took:
1- Download GS2RomNuke (Read all instructions),
2- Download the rom you want and gapps ofc (Read all instructions),
3- Put them in your phone, i put in the sd card and it worked,
4- Flash GS2RomNuke, don't reboot or anything, flash your rom and gapps,
5- Reboot and done!
Click to expand...
Click to collapse
thanksssss to you and jimsilver so much
First off I would like to please ask everyone to thank the anonymous donor for this file because we wouldn't be seeing it today without them.
For all those that have been waiting, it's not the official release - but it is stable enough for daily driver use.
I haven't had much time to test this but the only issue I had with it was flashing it.
If it gets stuck trying to get to recovery pull the battery and flash again.
I am marking this a full restore because it looks like it wiped data, including pictures. YMMV.
At the moment I'm only putting the original file up.
I'll try to get an Odin one-click and a nodata version up later.
Link to NI3 folder:
http://www.rwilco12.com/downloads.p... Galaxy S5 (Sprint) (SM-G900P)/Stock ROMs/NI3
Steps:
1) Download EXE file, double-click to extract.
2) Put the phone in download mode.
If you've never done this before, easiest way is to shut the phone down completely.
Then hold Vol Down + Power until you see a warning screen. Press up to proceed.
3) Open Odin (I used 3.07), place in PDA slot and flash.
4) Profit!
Please feel free to leave feedback on the flash and ROM but please keep in mind I have no special contact to relay that feedback.
Do me a favor please - if you're going to reply don't clutter my thread with spam. Thank you.
Reminds me of that old Monty Python skit. LOL
Spam spam spam.
Changelog at someone's first opportunity please.
Screenshots too if there's anything worthwhile to show off.
tdunham said:
Reminds me of that old Monty Python skit. LOL
Spam spam spam.
Changelog at someone's first opportunity please.
Screenshots too if there's anything worthwhile to show off.
Click to expand...
Click to collapse
Only CL details I have:
anonymous source said:
...couple of Sprint bug fixes, SSL Google fix, and hd voice indicator (finally!)
Click to expand...
Click to collapse
And of course, the new version.
Boot screen logo (android) looks new typefont to me.
Will try rooting this shortly.
Very nice thanks a bunch
woot something new to play aorund with, TY once again gents. lol
Any noticeable changes as far as looks? Or just code and software related?
88EVGAFTW said:
Any noticeable changes as far as looks? Or just code and software related?
Click to expand...
Click to collapse
There is a problem with the screen not turning off when making a call. Other than that it seems smooth so far. Wifi calling is only new feature that i have tested, and it seems to work fine.
You cant root with towelroot you have to use cf-autoroot which trips knox. Since i had tripped it already WTF not. http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Screen shots please?
Sergekarol said:
There is a problem with the screen not turning off when making a call. Other than that it seems smooth so far. Wifi calling is only new feature that i have tested, and it seems to work fine.
You cant root with towelroot you have to use cf-autoroot which trips knox. Since i had tripped it already WTF not. http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Click to expand...
Click to collapse
I have that screen on while on a call problem with my not yet rooted S5 on NE5 from time to time. That one may not be new. I wonder if its possibly a hardware issue?
garwynn said:
First off I would like to please ask everyone to thank the anonymous donor for this file because we wouldn't be seeing it today without them.
For all those that have been waiting, it's not the official release - but it is stable enough for daily driver use.
I haven't had much time to test this but the only issue I had with it was flashing it.
If it gets stuck trying to get to recovery pull the battery and flash again.
I am marking this a full restore because it looks like it wiped data, including pictures. YMMV.
At the moment I'm only putting the original file up.
I'll try to get an Odin one-click and a nodata version up later.
Link to NI3 folder:
http://www.rwilco12.com/downloads.p... Galaxy S5 (Sprint) (SM-G900P)/Stock ROMs/NI3
Steps:
1) Download EXE file, double-click to extract.
2) Put the phone in download mode.
If you've never done this before, easiest way is to shut the phone down completely.
Then hold Vol Down + Power until you see a warning screen. Press up to proceed.
3) Open Odin (I used 3.07), place in PDA slot and flash.
4) Profit!
Please feel free to leave feedback on the flash and ROM but please keep in mind I have no special contact to relay that feedback.
Click to expand...
Click to collapse
Hiya, ty again! ! Question. The other files on "wilco"- can that be flashed w/o computer my friend?
Any chance this build includes improved Android Wear support?
garwynn said:
Do me a favor please - if you're going to reply don't clutter my thread with spam. Thank you.
Click to expand...
Click to collapse
Hiya. Sry to bother ya. But the. Tar file on wilco, can I use that w/o a computer?
Jrowe820 said:
Hiya. Sry to bother ya. But the. Tar file on wilco, can I use that w/o a computer?
Click to expand...
Click to collapse
I would also like to know this, I just downloaded it but dont want to attempt to try it and not have a phone until I can get back to my place later
Finally getting around to deodexing and rooting this build.
Wish me luck.
If anyone has it ready to go and is just going through testing, let me know so I don't spend hours getting it ready.
Has anyone tried to go back to ne5 after update?
tdunham said:
Finally getting around to deodexing and rooting this build.
Wish me luck.
If anyone has it ready to go and is just going through testing, let me know so I don't spend hours getting it ready.
Click to expand...
Click to collapse
I started it yesterday but work got in my way, how far along are u
vinman12 said:
I started it yesterday but work got in my way, how far along are u
Click to expand...
Click to collapse
I now have a bootable odexed version. I probably wont do deodexed right away, its not worth the extra effort. Going to try getting one done that is rooted with busybox to post later.
Edit: And it seems to be fine with the NE5 modem too so no worries there.
I'm on my way home I may deodex it. Will post back if I do.
Oh great, I was just getting my rom ready to release an update, lol. Thanks for working on this guys.
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.