Related
hi.
i flashed stock rom S5830XWKS2 through Odin. the phone started rebooting randomly.
then i flashed custom rom TheMyth KS3 but the problem kept getting worse. when i'm using the phone, it reboots every few seconds.
i flashed stock rom S5830XWKS3. but the Baseband version in the phone didnt change (S5830XWKS2). and the problem is still persistent.
the phones does not do full reboot. it freezes, the screen goes black, then goes strait to the boot animation.
also, if it reboots while transferring files through mass usb storage, the transfer doesnt stop, to continues normally.
1. any idea why is this happening?
2. why didnt the baseband version change when i flashed KS3?
3. do you recommend another stock rom to flash.
p.s: KS3 seems fast. i got 1040 score in quadrant on stock rom.
i would appreciate any help. thanks
dali47 said:
hi.
i flashed stock rom S5830XWKS2 through Odin. the phone started rebooting randomly.
then i flashed custom rom TheMyth KS3 but the problem kept getting worse. when i'm using the phone, it reboots every few seconds.
i flashed stock rom S5830XWKS3. but the Baseband version in the phone didnt change (S5830XWKS2). and the problem is still persistent.
the phones does not do full reboot. it freezes, the screen goes black, then goes strait to the boot animation.
also, if it reboots while transferring files through mass usb storage, the transfer doesnt stop, to continues normally.
1. any idea why is this happening?
2. why didnt the baseband version change when i flashed KS3?
3. do you recommend another stock rom to flash.
p.s: KS3 seems fast. i got 1040 score in quadrant on stock rom.
i would appreciate any help. thanks
Click to expand...
Click to collapse
Hey !
The Baseband Version is KS2 while Build is KS9 (in my stock rom)
If you end in Bootloops, press Power + Home till you get into recovery, then Clear data/Factory Reset and clear Cache, then reboot.
Come back and tell me if it worked for you.
Greetings
thank you for your reply.
it's actually not a bootloop. the phone boots normally and works fine for some times (few seconds/minutes) then it freezes for few seconds, then the screen turns black for a second, then shows the boot animation (doesn't show the boot screen with the samsung logo). it works fine for some time, then again.
it seems that the problem is related to the wifi. it only happens when wifi is on.
On Samfirmware.com they say that you should make a Factory Reset after flashing, maybe that works for you ? I flashed the KS9 Stock today and had some problems till I did this in Recovery. Else I would have no Idea, maybe reflash or get another Version ?
You could also try to install any custom Rom, like Jusada´s ICS for example, just to test if there are problems with CM also ..
Umm, maybe a question to those who only touch the Earth to answer our Newb questions...is it possible that the Ace restarts when it get´s attacked from the outside ? I faced that after flashing a Rom that I modified and didn´t have the right Permissions the Phone restarted/bootlooped when I tried to install any App (\data\app wasn´t set correct)
Greetings
thank you. i guess i'll try to flash again. or maybe try a different stock.
dali47 said:
thank you. i guess i'll try to flash again. or maybe try a different stock.
Click to expand...
Click to collapse
If you had the Android SDK Tools , you could show me a logcat of what's going on
EmoBoiix3 said:
If you had the Android SDK Tools , you could show me a logcat of what's going on
Click to expand...
Click to collapse
hi. i do have the sdk. here are a few log files:
http://pastebin.com/Amt00nuY
http://pastebin.com/SHeasfvq
http://pastebin.com/sirV2FEe
this is the first time i use logcat, so if there is a command or option i should use to make the log file more useful, just let me know.
thank you for your time
dali47 said:
hi. i do have the sdk. here are a few log files:
http://pastebin.com/Amt00nuY
http://pastebin.com/SHeasfvq
http://pastebin.com/sirV2FEe
this is the first time i use logcat, so if there is a command or option i should use to make the log file more useful, just let me know.
thank you for your time
Click to expand...
Click to collapse
The original TheMyth creator said that KS3 was badly unstable .
Use KS2 instead
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
The original TheMyth creator said that KS3 was badly unstable .
Use KS2 instead
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
He should try to upgrade to KS3 v1.1. That's final update for TheMyth KS3 with:
- Meizu Myth theme
- BLN Control activated
- changed some small things
>> I think this update can help him to solve frequent random reboot in TheMyth KS3
http://mobile.livemodding.com/forum/398-samsung-galaxy-ace/
Click to expand...
Click to collapse
my first attempt was with KS2. that's when the problem started, even before i install TheMyth. The 1.1 update didnt help either.
I guess my phone is not getting along with the KS2 baseband. i will just switch to GingerReal, hopefully it will be stable.
thank you everyone
Hi to all !
I´ve flashed this kernel ( http://forum.xda-developers.com/showthread.php?p=42378027&nocache=1 ) with latest CM 10.1 nighty and after rebooting gave some graphical glitches , and then i cannot go further with that.My phone kept in black screen
I even cannot go to recovery or download mode . After some minutes i was sucessfully enter in recovery, but the problem now is that i have´t touch in my phone . I have acess only at the physical buttons .
I´v sucessfully flashed the latest nightly , but i cannot put my pin , or do the normal thing with the phone because I have no touch.
Can someone help ? Any solution besides formating ?
thanks
what phone model do you have? what does it say under the battery?
Glebun said:
what phone model do you have? what does it say under the battery?
Click to expand...
Click to collapse
GT-i9300
After some minutes with power off, i´ve tried to reboot , and now is in bootloop
Edit : Stuck in CM10.1 bootlogo .
Tuga2010 said:
Hi to all !
I´ve flashed this kernel ( http://forum.xda-developers.com/showthread.php?p=42378027&nocache=1 ) with latest CM 10.1 nighty and after rebooting gave some graphical glitches , and then i cannot go further with that.My phone kept in black screen
I even cannot go to recovery or download mode . After some minutes i was sucessfully enter in recovery, but the problem now is that i have´t touch in my phone . I have acess only at the physical buttons .
I´v sucessfully flashed the latest nightly , but i cannot put my pin , or do the normal thing with the phone because I have no touch.
Can someone help ? Any solution besides formating ?
thanks
Click to expand...
Click to collapse
so as your physical buttons are working, you should be able to enter download mode(remove the battery for 5 minutes and re-insert) . then try flashing a stock rom. if you can backup the data, do it. good luck.
sriram231092 said:
so as your physical buttons are working, you should be able to enter download mode(remove the battery for 5 minutes and re-insert) . then try flashing a stock rom. if you can backup the data, do it. good luck.
Click to expand...
Click to collapse
does flashing stock rom via odin help?
I forget to mentioned , that the menu button and the back button ( non - physical ) works.
psndna88 said:
does flashing stock rom via odin help?
Click to expand...
Click to collapse
not 100% sure. but it's worth trying.
sriram231092 said:
not 100% sure. but it's worth trying.
Click to expand...
Click to collapse
didn´t solve the problem .
if it doesn't work after a factory reset, send it to service, no other solution
Tuga2010 said:
didn´t solve the problem .
Click to expand...
Click to collapse
agree with glebun.
sriram231092 said:
agree with glebun.
Click to expand...
Click to collapse
Can anyone pass here and see the problem : http://forum.xda-developers.com/showthread.php?p=42383555&posted=1#post42383555
The developer by mystake as uploaded a Galaxy Note 2 kernel in Galaxy S3 thread , and he said that is probably a kernel boot.img problem.
thanks
Tuga2010 said:
Can anyone pass here and see the problem : http://forum.xda-developers.com/showthread.php?p=42383555&posted=1#post42383555
The developer by mystake as uploaded a Galaxy Note 2 kernel in Galaxy S3 thread , and he said that is probably a kernel boot.img problem.
thanks
Click to expand...
Click to collapse
note2 kernel is totally different from s3. probably that should have damaged the touch on your phone. that is a big mistake by the dev and you can do nothing but taking it to service center. good luck.
okay, now it's a 100% that you need a service center job. your touch chip is fried due to the voltage differences
Hey All,
I tried looking up answers here and via google, but all of them refer to bootloops/hangs after flashing a rom.
I've been using the prerooted JB rom via the guide given by Pandemic . Following the guide to the letter, the rom is working fine, and the recovery is accessible after installing via atis112's method. However, the problem I've run into is that whenever I restore a backup through CWM after flashing a mod (tested with Cybershot mod and ACiD audio mod), my phone hangs upon cold booting.
Immediately after restoring the backup, the phone boots into the restored OS without any problems, and hot boots (Power button + Volume Up button) also work fine - when I power off the phone and then start it up, it hangs on the sony logo (no bootloop, and can't access CWM recovery), after which I have to use flashtool and follow Pandemic's guide again to get JB. I've tried the following methods to see if anything changes, but the result is the same:
Method 1:
1- Backup through CWM recovery
2- Flash mod and wipe cache+dalvik cache
3- Reboot and test mod
4- Reboot and access recovery
5- Restore created backup
Result: Hangs at cold boot
Method 2:
1-4: same as method 1
5- Advance Restore > restore only /data from created backup
Result: Hangs at cold boot
Method 3:
1-4: same as method 1
5- Normal restore
6- Wipe data/factory reset (preserves any changes on /system, wanted to see if /data was the culprit)
Result: Hangs at cold boot
The above 3 methods were also tried by wiping cache+dalvik cache after restoring the backup, but that had no effect either. Has anyone else been having the same or a similar problem? Can someone kindly refer me to a solution to this?
Edit 1: The phone was finally able to boot into android after about hanging at the sony logo for about 20-25 mins. Tested restoring various other restore points and each time the phone hung for about 20 minutes or so. After that initial boot, the phone boots up within a minute as always. Still haven't been able to narrow down the problem causing the delay on the first boot.
@H4R81N63R bro,I think that's because you installed cybershot mod and AC!D . Try with a clean install of the rom and try installing only cybershot without intsalling AC!D and check if boots without issues. Not sure if this causes the issue but test it if you want.
Thanks for the suggestion. Flashing works fine and the phone boots up without issues. Its just that whenever I restore any backup I had made before flashing the mod, the phone takes a long time at the sony logo only during cold boots (kind of annoying really).
H4R81N63R said:
Thanks for the suggestion. Flashing works fine and the phone boots up without issues. Its just that whenever I restore any backup I had made before flashing the mod, the phone takes a long time at the sony logo only during cold boots (kind of annoying really).
Click to expand...
Click to collapse
Try backup a fresh flashed Rom with only cybershot mod installed and check if restore works.
DaRk-L0rD said:
Try backup a fresh flashed Rom with only cybershot mod installed and check if restore works.
Click to expand...
Click to collapse
Tried that as well, still the same. The hang ups seem to vary in time though, sometimes its just 10 mins, other times its about 30 mins. Is it possible to somehow see the processing that android is doing during bootup to see where its hanging up (similar to desktop OS'es)?
H4R81N63R said:
Tried that as well, still the same. The hang ups seem to vary in time though, sometimes its just 10 mins, other times its about 30 mins. Is it possible to somehow see the processing that android is doing during bootup to see where its hanging up (similar to desktop OS'es)?
Click to expand...
Click to collapse
Don't know how do that mate. Did you try using a custom kernel with cwm5?
DaRk-L0rD said:
Don't know how do that mate. Did you try using a custom kernel with cwm5?
Click to expand...
Click to collapse
Can't - have a locked bootloader (might unlock it if someone figures out how to bring back the drm keys, or to circumvent them). It's possible that the devs might know something about this issue, but I'm not sure who to call on.
H4R81N63R said:
Can't - have a locked bootloader (might unlock it if someone figures out how to bring back the drm keys, or to circumvent them). It's possible that the devs might know something about this issue, but I'm not sure who to call on.
Click to expand...
Click to collapse
here is how to relock bootloader http://forum.xda-developers.com/showthread.php?t=1920195&highlight=relock+bootloader
So you can unlock it if you want. Works on jb also
DaRk-L0rD said:
here is how to relock bootloader http://forum.xda-developers.com/showthread.php?t=1920195&highlight=relock+bootloader
So you can unlock it if you want. Works on jb also
Click to expand...
Click to collapse
Hmm, looked into your link and another, but it seems DRM keys are lost in the process - I'm partial to Bravia
Hopefully a dev might have some more info regarding the boot hang up.
Hello people, since today i have the exact same problem as the topic maker
I am on stock Jelly Bean 6.2.A.1.100 with thesliding XP kernel (tried v8.3 and v9 beta with same results)
I am really frustrated right now because i don't have cybershot mode nor acid, it started to happen today after i tried a custom rom and didn't liked it so i did a restore with the backup i made .... :/
arnes_king said:
Hello people, since today i have the exact same problem as the topic maker
I am on stock Jelly Bean 6.2.A.1.100 with thesliding XP kernel (tried v8.3 and v9 beta with same results)
I am really frustrated right now because i don't have cybershot mode nor acid, it started to happen today after i tried a custom rom and didn't liked it so i did a restore with the backup i made .... :/
Click to expand...
Click to collapse
I haven't been able to find a solution yet. For now, the only thing that works is to boot it up so that it gets stuck on the sony/kernel logo and wait till it boots into the OS (may take 10 mins, or may take 40, can't seem to find a pattern). I do tend to attach the power cable just to be sure that it doesn't run out the battery.
A little off topic and near to your problem, cybershot is only supporting ICS roms at the moment, but I have found that their 4.7.2 and 5.1.1 work with the JB based MoonBreakers v3.5 rom that I have. As for AC!D, haven't been able to make their mod work on JB yet (even the universal one supporting JB 4.1 and above doesn't work).
Hello all, i just wanted to share with you that i have successfully fixed the problem and here is what i did :
I just used Flashtool and flashed the latest stock JB FW which was on the phone earlier, but i unticked the "Wipe data" option, after that i flashed again a custom kernel and now the phone boots normal and i didn't loose any data
Actually that doesn't fix the problem - we are talking about restore because we have multiple mods installed as well - we can't just keep reinstalling all of them every time we test something new.
Sent from my LT22i using xda app-developers app
H4R81N63R said:
Actually that doesn't fix the problem - we are talking about restore because we have multiple mods installed as well - we can't just keep reinstalling all of them every time we test something new.
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Yeah you are right the problem will surely be there again if i do a restore, but anyhow now i don't have the problem and i am happy for now
I have same problem.
After restored backup, device booted successfully only first reboot.
but device hung up on the sony logo thereafter.
My device is installed cybershot7.9.1 MOD without acid.
Same error here, is there any solution?
Gesendet von meinem LT22i mit Tapatalk
xaver54645 said:
Same error here, is there any solution?
Click to expand...
Click to collapse
Sorry mate, I haven't found any solution but to leave it alone (plugged in with the charger of course) for up to 40 mins while it waits at the logo before booting up
xaver54645 said:
Same error here, is there any solution?
Gesendet von meinem LT22i mit Tapatalk
Click to expand...
Click to collapse
Hmmm I had this too.
What if you install the CWM for LB reboot and restore again?
I had this too couple of days ago
H4R81N63R said:
Sorry mate, I haven't found any solution but to leave it alone (plugged in with the charger of course) for up to 40 mins while it waits at the logo before booting up
Click to expand...
Click to collapse
Is the next cold boot faster then? If yes, I could live with that.
@ChikeD
Nope, still the same. Even with my second phone with unlocked bootloader I'm stuck at Sony logo after restore
I somewhere read that immediately after restoring the backup reflashing the kernel should help, but that's only an option for UB I guess.
Didn't try that yet.
xaver54645 said:
Is the next cold boot faster then? If yes, I could live with that.
@ChikeD
Nope, still the same. Even with my second phone with unlocked bootloader I'm stuck at Sony logo after restore
I somewhere read that immediately after restoring the backup reflashing the kernel should help, but that's only an option for UB I guess.
Didn't try that yet.
Click to expand...
Click to collapse
And resoring after flashing stock?
I would have tried that but I didn't realized the problem is related to the kernel.
Hey guys,
I have tried to upgrade my Micromax A116 to the official update of 4.2 jelly bean. But as soon as i reboot my phone after flashing it using the basic SP tools method, my screen continuously goes on and off. Has anybody else come across this problem? If yes, then can you please share with me the solution? Now i am back to the stock rom of 4.1.2..Any kind of help is appreciated..Thank you..:cyclops: I really want to update it to 4.2.1..
PS: Am i the only one around here who thinks that the stock rom is better than any other custom roms for micromax a116?:laugh:
There are others who reported the same problem. But as of now there doesn't seem to be any solutions as its happening to only some of CHD devices
Thanks
tmohans said:
There are others who reported the same problem. But as of now there doesn't seem to be any solutions as its happening to only some of CHD devices
Click to expand...
Click to collapse
Just wanted to see if I was the only one. Thanks anyway
Possible Solution
1. Don't keep your mobile on auto-brightness.
2. Go to your WiFi and click on it and then hit the menu button on left and then go to advanced option and turn off WiFi optimization.
This will solve your flickering issue.
======================================
or enable Hardware overlay from developer options.
P.S: I am not experiencing any flickering so these steps haven't been tried by me.. try on your own and reply if it helped.:good::fingers-crossed:
I am facing the same problem. I tried hardware overlay and auto brightness but no success. I never tried WiFi though. I had flashed my device more than 10 times now.
Sent from my Micromax A116 using xda app-developers app
---------- Post added at 06:38 PM ---------- Previous post was at 06:30 PM ----------
Same problem with my handset as well. So far no resolution.
Sent from my Micromax 6 using xda app-developers app
neatearth said:
I am facing the same problem. I tried hardware overlay and auto brightness but no success. I never tried WiFi though. I had flashed my device more than 10 times now.
Sent from my Micromax A116 using xda app-developers app
---------- Post added at 06:38 PM ---------- Previous post was at 06:30 PM ----------
Same problem with my handset as well. So far no resolution.
Sent from my Micromax 6 using xda app-developers app
Click to expand...
Click to collapse
Worth waiting for service center for 4.2 update for your phone. Stop experimenting further and stay on 4.1.2 backup.
WARNING: If you try SP TOOL to flash 4.2 on your phone for some more time, you may LOSE IMEI codes and phone will be literally useless and you need to give it to service center, with a RISK of service rejection coz you rooted it. If you dont know how to unroot and restore stock recovery, you will be in trouble. So keep using 4.1.2 and be safe. Later, dont tell people, no one warned you. Telling you from my own experience.
Should I flash using recovery mode ?
Sent from my Micromax A116 using xda app-developers app
adizrox said:
1. Don't keep your mobile on auto-brightness.
2. Go to your WiFi and click on it and then hit the menu button on left and then go to advanced option and turn off WiFi optimization.
This will solve your flickering issue.
======================================
or enable Hardware overlay from developer options.
P.S: I am not experiencing any flickering so these steps haven't been tried by me.. try on your own and reply if it helped.:good::fingers-crossed:
Click to expand...
Click to collapse
Tried it..but it didn't work.. But thanks anyway
Lyyclec extraneus
cmahendra said:
Worth waiting for service center for 4.2 update for your phone. Stop experimenting further and stay on 4.1.2 backup.
WARNING: If you try SP TOOL to flash 4.2 on your phone for some more time, you may LOSE IMEI codes and phone will be literally useless and you need to give it to service center, with a RISK of service rejection coz you rooted it. If you dont know how to unroot and restore stock recovery, you will be in trouble. So keep using 4.1.2 and be safe. Later, dont tell people, no one warned you. Telling you from my own experience.
Click to expand...
Click to collapse
@cmahendra I have read one of your posts where you have mentioned that you had the same problem(Screen Blinking). Did you manage to get over it? Which method did you try to flash. Please share your experience. It will be quite helpful. At present I am planning to try TWRP recovery to flash. I do not know if it will work.... Will keep update.
Screen Blinking
Hello,
I followed the procedure several times.
this saturday I spent the whole day trying to flash 4.2.1 sotck rom on my phone. But, got the same screen blinking issue.
I've TWRP installed and tried the tweaked Flash-able rom as well as the SP tools flash-able one. but the same issue.
I followed below three routes:
1. Flashed stock rom .16 to make the phone factory state.
2. Then first tried flashing .20 update. Flashed successfully, but the screen started blinking as soon as the phone rebooted, i.e. right when the boot animation starts. I disabled auto brightness as well as disabled HW overlay. but the issue stayed.
3. I again flashed .16 and then 4.2.1 updated rom, first as 'Download' option in SP flash tools, but the same issue occured. I then tried, 'Firmware upgrade' still the same issue.
4. flashed .16 again; flashed TWRP, tried the tweaked zip flash-able rom, but same issue.
5. Tried custom ROM JellyDemon v2.2, the phone was not stuck at bootscreen.
6. in so much of flashing lost IMEI. so, flashed stock .16 again, installed TWRP, extended phone storage to 2.5 GB flashed Jellyxperia 4.1.2 based custom rom, swapped internal storage and then used Mobileuncle MTK toolkit to restore IMEI (I had used the same earlier to backup the IMEI to external SD card.
So, basically I'm back to square one after spending almost 8 hours to get 4.2 update :crying:. If only the blinking screen issue could be fixed :crying:
Sauravh said:
Hello,
I followed the procedure several times.
this saturday I spent the whole day trying to flash 4.2.1 sotck rom on my phone. But, got the same screen blinking issue.
I've TWRP installed and tried the tweaked Flash-able rom as well as the SP tools flash-able one. but the same issue.
I followed below three routes:
1. Flashed stock rom .16 to make the phone factory state.
2. Then first tried flashing .20 update. Flashed successfully, but the screen started blinking as soon as the phone rebooted, i.e. right when the boot animation starts. I disabled auto brightness as well as disabled HW overlay. but the issue stayed.
3. I again flashed .16 and then 4.2.1 updated rom, first as 'Download' option in SP flash tools, but the same issue occured. I then tried, 'Firmware upgrade' still the same issue.
4. flashed .16 again; flashed TWRP, tried the tweaked zip flash-able rom, but same issue.
5. Tried custom ROM JellyDemon v2.2, the phone was not stuck at bootscreen.
6. in so much of flashing lost IMEI. so, flashed stock .16 again, installed TWRP, extended phone storage to 2.5 GB flashed Jellyxperia 4.1.2 based custom rom, swapped internal storage and then used Mobileuncle MTK toolkit to restore IMEI (I had used the same earlier to backup the IMEI to external SD card.
So, basically I'm back to square one after spending almost 8 hours to get 4.2 update :crying:. If only the blinking screen issue could be fixed :crying:
Click to expand...
Click to collapse
I feel you bro.. I also have tried to install the 4.2 update like 3-4 times.. Everytime i get the same issue.. But I haven't occured an issue with any other custom roms.. But I have the same issue with tweaked roms.. GOD HELP US:crying:
hardiktrivedi0612 said:
I feel you bro.. I also have tried to install the 4.2 update like 3-4 times.. Everytime i get the same issue.. But I haven't occured an issue with any other custom roms.. But I have the same issue with tweaked roms.. GOD HELP US:crying:
Click to expand...
Click to collapse
Now, I'm thinking as My phone is less than 30 days old, Should I give it to SVC to upgrade, I'll first flash the stock rom and then give it to svc, So, If they face the blinking issue, may be I could get replacement with updated stock ROM.. But need to find the svc in Noida or nearby
Sauravh said:
Now, I'm thinking as My phone is less than 30 days old, Should I give it to SVC to upgrade, I'll first flash the stock rom and then give it to svc, So, If they face the blinking issue, may be I could get replacement with updated stock ROM.. But need to find the svc in Noida or nearby
Click to expand...
Click to collapse
:laugh::laugh: But make sure that you properly unroot it first and flash .16 stock rom..
hardiktrivedi0612 said:
Hey guys,
I have tried to upgrade my Micromax A116 to the official update of 4.2 jelly bean. But as soon as i reboot my phone after flashing it using the basic SP tools method, my screen continuously goes on and off. Has anybody else come across this problem? If yes, then can you please share with me the solution? Now i am back to the stock rom of 4.1.2..Any kind of help is appreciated..Thank you..:cyclops: I really want to update it to 4.2.1..
PS: Am i the only one around here who thinks that the stock rom is better than any other custom roms for micromax a116?:laugh:
Click to expand...
Click to collapse
tmohans said:
There are others who reported the same problem. But as of now there doesn't seem to be any solutions as its happening to only some of CHD devices
Click to expand...
Click to collapse
neatearth said:
I am facing the same problem. I tried hardware overlay and auto brightness but no success. I never tried WiFi though. I had flashed my device more than 10 times now.
Sent from my Micromax A116 using xda app-developers app
---------- Post added at 06:38 PM ---------- Previous post was at 06:30 PM ----------
Same problem with my handset as well. So far no resolution.
Sent from my Micromax 6 using xda app-developers app
Click to expand...
Click to collapse
neatearth said:
@cmahendra I have read one of your posts where you have mentioned that you had the same problem(Screen Blinking). Did you manage to get over it? Which method did you try to flash. Please share your experience. It will be quite helpful. At present I am planning to try TWRP recovery to flash. I do not know if it will work.... Will keep update.
Click to expand...
Click to collapse
Sauravh said:
Hello,
I followed the procedure several times.
this saturday I spent the whole day trying to flash 4.2.1 sotck rom on my phone. But, got the same screen blinking issue.
I've TWRP installed and tried the tweaked Flash-able rom as well as the SP tools flash-able one. but the same issue.
I followed below three routes:
1. Flashed stock rom .16 to make the phone factory state.
2. Then first tried flashing .20 update. Flashed successfully, but the screen started blinking as soon as the phone rebooted, i.e. right when the boot animation starts. I disabled auto brightness as well as disabled HW overlay. but the issue stayed.
3. I again flashed .16 and then 4.2.1 updated rom, first as 'Download' option in SP flash tools, but the same issue occured. I then tried, 'Firmware upgrade' still the same issue.
4. flashed .16 again; flashed TWRP, tried the tweaked zip flash-able rom, but same issue.
5. Tried custom ROM JellyDemon v2.2, the phone was not stuck at bootscreen.
6. in so much of flashing lost IMEI. so, flashed stock .16 again, installed TWRP, extended phone storage to 2.5 GB flashed Jellyxperia 4.1.2 based custom rom, swapped internal storage and then used Mobileuncle MTK toolkit to restore IMEI (I had used the same earlier to backup the IMEI to external SD card.
So, basically I'm back to square one after spending almost 8 hours to get 4.2 update :crying:. If only the blinking screen issue could be fixed :crying:
Click to expand...
Click to collapse
try to flash this file..
this file fixed the issue for some people..
build prop values are stock 4.2
http://d-h.st/L22
hottesthunkkush said:
try to flash this file..
this file fixed the issue for some people..
build prop values are stock 4.2
http://d-h.st/L22
Click to expand...
Click to collapse
Will try it for sure.... Love your work BTW!! keep up the good work:good:
hardiktrivedi0612 said:
Will try it for sure.... Love your work BTW!! keep up the good work:good:
Click to expand...
Click to collapse
Did you try the flickerfix.zip ? Please let me know
---------- Post added at 05:38 AM ---------- Previous post was at 05:30 AM ----------
hottesthunkkush said:
try to flash this file..
this file fixed the issue for some people..
build prop values are stock 4.2
http://d-h.st/L22
Click to expand...
Click to collapse
I am using TWRP and right now on 4.1.2 . Can not upgrade to 4.2 due to blinking issue. Should I flash using flickerfix.zip before upgradation to 4.1 or should do after upgrading to 4.2 ? I will use SP lfash tool to upgrade. I will really appreciate if you can provide a step by step guidance.
thanking you
neatearth said:
Did you try the flickerfix.zip ? Please let me know
Sorry haven't got the time yet.. But will surely let you know when i do.
Click to expand...
Click to collapse
neatearth said:
I am using TWRP and right now on 4.1.2 . Can not upgrade to 4.2 due to blinking issue. Should I flash using flickerfix.zip before upgradation to 4.1 or should do after upgrading to 4.2 ? I will use SP lfash tool to upgrade. I will really appreciate if you can provide a step by step guidance.
thanking you
Click to expand...
Click to collapse
Flash 4.2 First then flickerfix.zip
same situation
Sauravh said:
Hello,
I followed the procedure several times.
this saturday I spent the whole day trying to flash 4.2.1 sotck rom on my phone. But, got the same screen blinking issue.
I've TWRP installed and tried the tweaked Flash-able rom as well as the SP tools flash-able one. but the same issue.
I followed below three routes:
1. Flashed stock rom .16 to make the phone factory state.
2. Then first tried flashing .20 update. Flashed successfully, but the screen started blinking as soon as the phone rebooted, i.e. right when the boot animation starts. I disabled auto brightness as well as disabled HW overlay. but the issue stayed.
3. I again flashed .16 and then 4.2.1 updated rom, first as 'Download' option in SP flash tools, but the same issue occured. I then tried, 'Firmware upgrade' still the same issue.
4. flashed .16 again; flashed TWRP, tried the tweaked zip flash-able rom, but same issue.
5. Tried custom ROM JellyDemon v2.2, the phone was not stuck at bootscreen.
6. in so much of flashing lost IMEI. so, flashed stock .16 again, installed TWRP, extended phone storage to 2.5 GB flashed Jellyxperia 4.1.2 based custom rom, swapped internal storage and then used Mobileuncle MTK toolkit to restore IMEI (I had used the same earlier to backup the IMEI to external SD card.
So, basically I'm back to square one after spending almost 8 hours to get 4.2 update :crying:. If only the blinking screen issue could be fixed :crying:
Click to expand...
Click to collapse
i tried almost everything u tried, now back to stock .16 , all other roms had the screen flickering issue, never tried jellyxperia though, are u using jellyxperia now?? have u found any solution?? is jellyxperia facing the same problem?? thanks
sweetrascal said:
i tried almost everything u tried, now back to stock .16 , all other roms had the screen flickering issue, never tried jellyxperia though, are u using jellyxperia now?? have u found any solution?? is jellyxperia facing the same problem?? thanks
Click to expand...
Click to collapse
I'm using Jellyxperia. it does not have blinking issue as it is based on 4.1.2.
It's faster than stock and I like the Walkman music player. However, I noticed that battery drains faster comparing to stock 4.1.2.
My collegue in office used to play Temple Run Brave during the complete office period with breaks of about 10-20 mins (he was serving notice period ). but the battery used to be at 30-40%.
But yesterday, the battery was down to 10% much before.
However, I would be sure only after a few days usage.
This is the ONLY thread you guys will talk about the CrDroid ROM.
DONT post questions or whatever at the other leaked AOSP ROM thread else it'll create much confusion
So far annoyances thats been reported are:
• Random reboots (at least for some people)
• Auto-brightness
• Underclocked CPU
• Not working HDR & Panaroma (solved with workaround)
DOWNLOAD LINK FOR CRDROID ROM
http://pan.baidu.com/s/1bnzqPBL
Reserved
Via the Internet
Regarding Random Reboots !
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
M3gAtR0N said:
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
Click to expand...
Click to collapse
LKspro said:
after u have the first reboot, cover the upper sensors and touch the screen while it is off. Then the screen should freeze and rebbot after a while
Click to expand...
Click to collapse
This is from @LKspro
Via the Internet
TiTAN-O-One said:
This is from @LKspro
Via the Internet
Click to expand...
Click to collapse
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Good rom lots of settings but useless... always reboot..
M3gAtR0N said:
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Click to expand...
Click to collapse
Yeah, first time it happens random, but if it once happens to you, then you will be able to reproduce it.
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
wai10691 said:
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
Click to expand...
Click to collapse
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
krispuniq said:
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
Click to expand...
Click to collapse
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
wai10691 said:
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
Click to expand...
Click to collapse
Done... Flashing went ok but after booting all my apps are gone (I didnt do a clean wipe while flashing.. only wiped dalvik)
The apps are gone anyway.. so i went back to recovery and did another clean flash.. Reboot the phone, but no mobile network. Unable to latch on to network even manually.. so may be there is something missing in the boot.img ?
Back key
Anyone can confirm back key in this rom didnt behave as it should after deleting pre-install files such as baidu services apps
edit 1 - looks like it has been warned by the dev as do not delete keyboard input method or else back button wont work..
Where is the link to the ROM. I'd update OP. Also, is there any bugs with the ROM? Or is it working like AOSP?
Via the Internet
Download link
http://pan.baidu.com/s/1bnzqPBL