i have a galaxy sl and after flashed with XXKP9, i face auto restart problem and it occur every 5 minutes and then i flash it with XXKPH, the problem still the same...can anyone help me?
after flashed, i install go launcher ex ,would it be the problem?
or i shud flash it back to the original rom? how to do so?
1. did you follow the flashing guides to the letter?
2. you just flashed a firmware so you should know how to flash back to a FROYO stockrom, just download one and follow the guides...
3. "posting as much info as you can" is your friend (how did you flash?, what EXACTLY did you do?, did you do a factory reset before flashing? did you get an error message when flashing etc etc)
4. go launcher should not be a problem, i use it and works like a charm
5. a LOT of people flashed KPE/KPH here and almost none had issues, so im sure you made a mistake somewhere
http://lmgtfy.com/?q=I9003+XXKPE+bootloop
EDIT: just saw you also posted in the other thread
Follow the guide under my signature. That should help, Also please avoid making new topics that doesn't relate to the [DEV] section.
sorry for the late reply..
i follow exactly your guide while flashing my galaxy sl from step 1 to step 18.
i dint factory reset before i flash but factory reset after i flashed.
after that, i flash it again for CWM "http://forum.xda-developers.com/showpost.php?p=15681160&postcount=1"
it works great within 7 or 8 hours after i flashed... but after tat it started to force restart on its own every few minutes ...
taylihiang said:
sorry for the late reply..
i follow exactly your guide while flashing my galaxy sl from step 1 to step 18.
i dint factory reset before i flash but factory reset after i flashed.
after that, i flash it again for CWM "http://forum.xda-developers.com/showpost.php?p=15681160&postcount=1"
it works great within 7 or 8 hours after i flashed... but after tat it started to force restart on its own every few minutes ...
Click to expand...
Click to collapse
if you are sure you did it all right,since rest of us dont have that problem it might be hardware.
I faced this problem and Service Center said that my memory chip was damaged. Should you come to Service Center for checking...
hi guys,
i have been following this thread for the past few weeks since i bought a second hand galaxy sl..i never thought that i will be encountering this kinds of problems with samsung..anyway to cut the long story short, ever since i bought this i was having a problem with a kernel panic mode error...then updated it into a GB 2.3.5 then later encountered an auto restart error and a boot loop error...after several tries of flashing different kinds of firmware none of those has solved the problem...i later came to think that the problem came from a faulty motherboard...i was helpless and i had no choice but to just bite my nails since my phone no longer has any warranty and replacing the motherboard is so expensive...then yesterday when i was going through with different forums about android..i found out that galaxy ace users are facing the same problems as well...then finally i found a solution to stop this unwanted restarts to occur...i downloaded the app LoadMonitor and WIFI Keep Alive.
For LoadMonitor you must make sure that these settings are applied.
-Add Notification
-Auto start
-Set the update interval to your preferred interval
-Wake lock
For WIFI Keep Alive
-Set your WiFi Policy to "Always On"
- Under "Advanced Options"
- Select "Enable Workaround 2"
- Enable Debug Logs
The downside for installing this apps is a increased battery consumption..so far from what i have observed I can use the phone for 6 hours straight without getting any auto-restart problems. Hopefully this will be a permanent solution while I save up to buy an iPhone..I will never buy any samsung phone again.
Related
Hi,
I installed a Cyanogenmod ICS 4.0.3. build 17 firmware on my Samsung Galaxy S I9000 almost 5 months ago from a tutorial. The update itself has been a fantastic experience from the start and I'm not sure if my current problem is even related to that firmware update. Apparently new users like me can't post URLs so I can't provide it now. If you need it let me know.
I have to admit that lately the phone has been rebooting every couple of days, or Android's been freezing and I had to remove the battery, but I didn't think too much of it. It wasn't too bad of a problem really, but this morning all of a sudden the device has become totally unusable. Help! :-/
The issue that's started since today is that my phone won't boot anymore. It seems to reboot somewhere during the boot process. There's only two screens that will be shown, before it reboots. When I remove the battery, put it back in and attach the charger, I will only see two charging screens. While charging, the device will also*reboot after a while.*
I can get into download-mode (volume-down + ok-button + power-key) but can't get into recovery mode (volume-up + ok-button + power-key).
Any ideas would be appreciated, thanks!
Greetings,
Adriaan
ps -> I have pictures of the booting screens and the charging screens but wasn't allowed to post them here. Again, if you need to see them please PM.
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
I'll try that, thanks.
switch_42 said:
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
Click to expand...
Click to collapse
just to be sure...
Just to be sure, could you please check that my logic is correct?
First off: the tutorial I had followed had me follow a few procedures:
first I updated Galaxy S with XXJVU Firmware
then rooted Galaxy S on XXJVU Firmware
after that I flashed CM 9, ICS 4.0.3. build 17 to the device
To which of these steps were you referring? My guess would be to take the last one, but perhaps it's wiser to restart the tutorial from the beginning. I'd appreciate any additional support you can give me, you can understand that I don't want to brick my device due to my misunderstandings..
Seems like a high overclock or high underclock
Sent from my GT-I9000
Helloworld294 said:
Seems like a high overclock or high underclock
Click to expand...
Click to collapse
Not sure what you mean there. In any event I've never taken any steps to overclock or underclock my device. Maybe it's going senile and I get to buy a galaxy s III soon
*phew* well my problem's been solved. Since I was able to get into download mode I flashed a baseline rom with Odin and found my way back to ICS. One surprise along the way was that from the same tutorial I had followed (and had happy results from) a few months ago, the step of using Odin to root the device wasn't working, it kept getting stuck at 'zImage' during the process! What's more, after that I was getting the BSOD image (the phone, exclamation mark and computer), which I found could be helped by using a 'One-Click Unbrick for Samsung devices'.
That was a XXJVU firmware. After some snooping around I found a different firmware than the one I had previously used and had switched from a XXJVU firmware to a XXJW4 firmware through a page on XDA-Developers. Did that. It worked. And now I'm back to ICS again, yay!
Thanks for the help along the way!
hay guys,
i bought my hd7 afew months ago and have had this happen afew times now and its really starting to annoy me.
so the phone just restarts itself and gets stuck on the HTC screen on bootup, then sometimes it will continue but will goto the startup pages as if this if the first time i have used the phone. if it doesnt continue i will have to remove the battery and leave it for abit then try again.
the last time it happened i had to do a factory reset myself using the volume + button on bootup to get it to work again.
so, all in all. phone resets itself and almost like formats the phone removing all photos, and settings etc.
i havent got and hacks or different rom's on the phone, i just update it through zune. its running mango at the moment.
any help would be great
THanks
curt
stagea09 said:
hay guys,
i bought my hd7 afew months ago and have had this happen afew times now and its really starting to annoy me.
so the phone just restarts itself and gets stuck on the HTC screen on bootup, then sometimes it will continue but will goto the startup pages as if this if the first time i have used the phone. if it doesnt continue i will have to remove the battery and leave it for abit then try again.
the last time it happened i had to do a factory reset myself using the volume + button on bootup to get it to work again.
so, all in all. phone resets itself and almost like formats the phone removing all photos, and settings etc.
i havent got and hacks or different rom's on the phone, i just update it through zune. its running mango at the moment.
any help would be great
THanks
curt
Click to expand...
Click to collapse
I can only think of 3 things :
Problems:
defective sdcard ( failing to read and write)
corrupted rom partition ( flash or zune upgrade process gone bad)
Failing hardware ( hardware parts are slowly dying)
Solutions
1) Try to flash the same rom again or another stock rom
2) replace sdcard
3) replace phone/ send for service
for the first 2 methods there are tutorials in these forums.
Follow them wisely and carefully
3rd solution is obvious
Take care.
Magpir said:
I can only think of 3 things :
Problems:
defective sdcard ( failing to read and write)
corrupted rom partition ( flash or zune upgrade process gone bad)
Failing hardware ( hardware parts are slowly dying)
Solutions
1) Try to flash the same rom again or another stock rom
2) replace sdcard
3) replace phone/ send for service
for the first 2 methods there are tutorials in these forums.
Follow them wisely and carefully
3rd solution is obvious
Take care.
Click to expand...
Click to collapse
I had the same problem, but after changing sim cards the problem seems to have sorted itself. I think it was the network. Can you try another sim and see if that is the problem? Hope this helps.
Hi Guys...
I got a Galaxy Note GT-N7000, and its been more than a week i tried to revived it using the any method i've found in this great forum.
So let me tell u guys the stories of my Note :
1. It was always updated OTA so the last ROM i used is Indonesian Note ICS 4.0.4
2. One day (last Friday) while i was browsing Internet using it, it suddenly got very hot, and the battery seems like draining very fast
3. In the mid day it reboot by its self, and entering countless reboot... a never ending reboot
4. So i tried to enter recovery, and yes sadly i've might triggered the emmc bugs by doing factory reset. But i'm not sure i've done it or not, coz i've a CWM recovery installed.
5. Anyway then i tried to flash stock room found in dr.ketan's thread...many thanks to him for those collection using PC ODIN and i got the "factoryfs" stuck problem
6. I also tried to flash countless kernel over and over, tried install Stock GB and ICS, tried RocketROM, CM10 and it all failed. In dowload mode i still got a Stock Firmware installed. So any ROM i've tried to install using Kernel didn't succed.
7. So i decided to take it to Samsung Service Center nearby, and i found that my battery is BAD, it wont charge (wonder would it because of the battery i got that problem in the first place). Since i got this Note for around 8 months, and the warranty for the battery is 6, the make me bought the new one, ordered and available in 2 days.
8. So I get back to the service center, put the new battery restarted the phone, and it stop on samsung logo (no yellow triangle there). So I complained, and they look into it, and said we may try to install new software, but there's a risk that your Note got damaged. They said the risk is mine and they wont have any responsible for it.
9. So furiously i bargain about my Warranty (12 month), coz the said that i've updated the ROM my self, so i explained to them that it was OTA's update, all i do was press YES, and they said even OTA official update will cancel my warranty. Its getting weird, i got angrier and they just said its their company procedure so there's nothing they can do to help me. So Samsung Indonesia will cancel warranty for every attempt to update the ROM OTA's, only their service center is allowed to do so. Wasted my valuable working hours there...
10. So i get back, determined i officially will do anything to get this Note life back. So i started to look at Forrest1971 (many thanks to him) thread about bricked note and tried many kernel and got one working with adb (T-Kernel V0.9) doing the checking and found faulty partition 9 and 10 and doing the step and finally got the partition fixed. Lost 3GB of space.
Then here came the real problem :
1. Still wont work with ODIN, stuck at Factoryfs with stock ROM GB N7000DXLC2_N7000OLBLC2_N7000DXLC1_HOME.tar and ICS N7000DXLR5_N7000OLBLR2_N7000DXLR1_HOME.tar. But working fine flashing Kernel so my guess it is not the connection problem. I've tried on 1 PC, 2 Laptops, 2 OS (Win7 32bit and WinXP 32 bit) still the same.
2. Then i tried to flashing via Kernel (CWM, Abyss, T-Kernel, CM9 Safe Kernel) i got to do trial and error coz not all ROM can be installed using any given Kernel. Seems that T-Kernel v0.9 is working for most of the ROM. Sorry i didn't keep note about the kernel-rom coupling. Here is the list of ROM i've tried :
cm-9.1.0-n7000 + gapps-ics-20120429-signed
cm-10-20121209-NIGHTLY-n7000 + gapps-ics-20120429-signed
RocketROM v2 XXLS7_stock_odexed
SuperNexus-N7000-BUILD5-20121017 + gapps-jb-20121011-signed
RocketROM_ICS_XXLPY_v1
3. All of those ROM came out with the same problem :
- Freezing on the Samsung/Mod Logo Screen (Got very HOT)
- Entering the "Andoid is Upgrading" and then updating Apps but stuck at random number (# of ###) (Got very HOT), i've tried to wait overnight but stay on the same number
- Succeeded boot up but Freeze after couple of minute (Got very HOT)
4.All those problem seems happened randomly, but most of the time it happened like this :
Stuck and Logo Screen - Reboot by me - Stuck and Upgrading - Reboot by me - Boot fine, but freeze very soon - Reboot by me, and back to the Logo stuck... (but still sometime its just random), the only thing same that it got very hot.
5. This is my last resort, i'll try to flash Supernexus, CM9 or CM10 without the GApps. Now i'm on Supernexus ROM, not yet freeze while i'm typing this. But without the GApps i wont have G-Play, and cant reinstall Apps that i bought in G-Play. Dilemma...
So any thoughts or advices will be greatly appreciated...
I really like this phone, wish i can revived this phone... :fingers-crossed:
Thanks B4 for any comment...
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
diasdroid said:
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
Click to expand...
Click to collapse
I would complain to the service center. It's absolutely rubbish that an ota update voids warranty, they're lying through their teeth and I wouldn't stand for it. So long as you have no trace of custom rom or root, they are required by law to fix the phone or replace it within 12 month warranty. If you'd left traces of root or Cwm that's a different story.
Try a second repartition, often a first scan will not find all bad sectors, run through it again just to be safe. Also, after repartitioning its usually the case that stock or tw based Roms won't work without freezes and reboots because they occupy too much space on the emmc. You're best with cm or aokp Roms.
Sent from my GT-N7000 using xda premium
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
trunoob said:
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
Click to expand...
Click to collapse
Jesus Christ, way to get yourself into a mess... The null keyboard just means you have to reflash the csc correctly. Extract the gb rom file and it should reveal a csc file, input that into the csc part of mobile odin and flash.
Screen problems... How old is your battery?
Triangle issue, just download triangleaway app from play store and run.
Hopefully you've learnt something about following directions to a t. Don't think you've done any lasting damage though, you're lucky.
Sent from my GT-N7000 using xda premium
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
trunoob said:
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
Click to expand...
Click to collapse
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Click to expand...
Click to collapse
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
trunoob said:
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
Click to expand...
Click to collapse
Good news, well done
Sent from my GT-N7000 using xda premium
Hey folks, first thread ever, I really need help with this troubled N910T, DOK2, Android 5.1.1
Whats wrong with this phone:
The contact app will stop everytime I open it, since contact app is combined into Phone app, so the Phone app will also stop everytime I click on it. However, the situation will be fixed if I change the locale to English. (The phone belongs to a Asian friend)
One of the instant message app, the Wechat, similar to Whatsapp Messager and Facebook Messager, will not receive any kind of notification, at all.
The phone's battery drop from 50% to 1% then turn off itself in minutes.
The last two problems may be unrelated issues to the first one, and that is not the main reason I'm really here. I have ODIN flashed the latest firmware over 10 times and all THREE of the problems still exist after all that.
And whats bothering me is that ODIN flash firmware WILL NOT FACTORY RESET this phone, that doesn't make any sense to me. Please let me know if I make a mistake about that, because every other phone or tablet I have worked on before will always be factory reset after flashing a OEM firmware.
I have also flahed TWRP and wiped everything from the System to the internal storage and reflash the firmware but the problem is still there.
sort of things have been done to the phone may have something to do with the problems:
installed the zips I got from this thread http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
it debloated the phone.
the phone was lost in a rainy day, found again two days later. Remote lock and wipe preformed via Android Device Manager but the wipe process never go through.
Please let me know if the phone is worth saving at all, I have spent days in this phone fixing and researching for solution. I found no similar issue around here, and the phone is out of warranty.
Thank you and please let me know should I throw this thing away.
Battery needs to be replaced. Are you sure you flashed right firmware for 910t not 910t3?
darekz said:
Battery needs to be replaced. Are you sure you flashed right firmware for 910t not 910t3?
Click to expand...
Click to collapse
It's a N910T, and the ODIN sucessfully passed everytime but will not factory reset the phone,.
Have you tried going into recovery and factory reset it yourself
tat2messiah said:
Have you tried going into recovery and factory reset it yourself
Click to expand...
Click to collapse
Many times already.
If you haven't done so, you may want to do a clean install which means wiping system, data, dalvik and cache at least three times in custom recovery such as TWRP. Then you can try ODIN baseband, bootloader, rom and kernel (if rom doesn't contain one), custom recovery. Next you boot into customer recovery again and do a factory reset and that should do it. Let me know if that helps.
raynaran said:
Hey folks, first thread ever, I really need help with this troubled N910T, DOK2, Android 5.1.1
Whats wrong with this phone:
The contact app will stop everytime I open it, since contact app is combined into Phone app, so the Phone app will also stop everytime I click on it. However, the situation will be fixed if I change the locale to English. (The phone belongs to a Asian friend)
One of the instant message app, the Wechat, similar to Whatsapp Messager and Facebook Messager, will not receive any kind of notification, at all.
The phone's battery drop from 50% to 1% then turn off itself in minutes.
The last two problems may be unrelated issues to the first one, and that is not the main reason I'm really here. I have ODIN flashed the latest firmware over 10 times and all THREE of the problems still exist after all that.
And whats bothering me is that ODIN flash firmware WILL NOT FACTORY RESET this phone, that doesn't make any sense to me. Please let me know if I make a mistake about that, because every other phone or tablet I have worked on before will always be factory reset after flashing a OEM firmware.
I have also flahed TWRP and wiped everything from the System to the internal storage and reflash the firmware but the problem is still there.
sort of things have been done to the phone may have something to do with the problems:
installed the zips I got from this thread http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
it debloated the phone.
the phone was lost in a rainy day, found again two days later. Remote lock and wipe preformed via Android Device Manager but the wipe process never go through.
Please let me know if the phone is worth saving at all, I have spent days in this phone fixing and researching for solution. I found no similar issue around here, and the phone is out of warranty.
Thank you and please let me know should I throw this thing away.
Click to expand...
Click to collapse