Hello -
I was wondering if someone could give me a hand for a second. I'm running an x10a, Firmware 2.-update1, Baseband 2.1.54, Build # 2.1.A.0.435, rooted, xrecovery, etc, etc
I carefully read all the instructions to many of the Roms out there, and checked to makes sure I am on the correct baseband, etc, now when I flash to any rom, it installs, boots, etc, but every single rom I have tried always gives me the error Phone Stopped Working Unexpectedly and keeps popping up every three seconds or so, it only stops when I enable air-plane mode.
I tried the Dev Tools > Crash System Server, etc, but it doesn't seem to solve the issue as many forum postings suggest..
would anyone have an idea how to solve this issue?
Did you make sure to do a full wipe and wipe cache, dalvik and battery stats before flashing the ROMs?
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Maybe one. Thing can help you out is flashtool try flashing the stock Rogers rom whit flashtool and afterwards flash custom roms just to make sure if its not the phone that is faulty.
Sent from my X10i using XDA Premium App
CMoney87 said:
Did you make sure to do a full wipe and wipe cache, dalvik and battery stats before flashing the ROMs?
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Click to expand...
Click to collapse
Yes I had done this each time. I also read in the posts that you are supposed to wipe the cache "after" the rom is installed, I tried all the methods and not having luck..
Also do I need to flash to a stock rogers rom? the phone originally is unlocked internationally...
Dont wipe cache after install. If you havent done anything with it yet you dont have anything cached. Reflash a ROM without wiping the cache afterwards and see what happens. If that doesnt work reflash the latest global generic FW, reroot, reinstall XRec and try another flash. There is no reason that you would need to flash a Rogers FW except if you were bringing the phone in on warranty.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Related
Hello,
I was wondering if someone could help me out. I checked the forums although I cannot find an answer.
Been trying to switch roms and get this issue with every rom, that my phone won't find the baseband. So I crash the server and it works, but I get the error phone stopped working unexpectedly. So I found that this problem only occurs when my sd card is inserted. If I remove it the rom picks up signal.and no crashes.
So I tried a different card, same issue, I format the card, same issue, etc...
Is there any fix? any help would be much appreciated
Thank you.
Sent from my X10a using XDA App
Try a clean flash and install. Reflash the latest FW, root and install XRecovery. Then make sure you do a full wipe, wipe cache, dalvik and battery stats before installing the ROM. That usually gets rid of all those odd little bugs. You can also unmount your SD card without physically removing it but hopefully the clean install will clear up your troubles.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Ok, I got that before going straight to a Froyo custom rom, try a EWJET 2.1 custom ROM first and see if you still have that problem. I did that and didnt have problem moving up but I went back again to 2.1 for other reasons.
CMoney87 said:
Try a clean flash and install. Reflash the latest FW, root and install XRecovery. Then make sure you do a full wipe, wipe cache, dalvik and battery stats before installing the ROM. That usually gets rid of all those odd little bugs. You can also unmount your SD card without physically removing it but hopefully the clean install will clear up your troubles.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Click to expand...
Click to collapse
Thank you for responding. I gave that a shot, well i tried in two methods.. i downloaded for xrecovery a clean rooted, xrecovery installed of the stock rom.. then followed the steps and got the same issue.. so i thought to do a full factory wipe using sony's tool, went back to stock rom, rooted, xrecovery installed, etc.. flashed the rom, same issue.. i tried this with several roms and cannot seem to bypass this error.. it almost seems like its just me due to limited info in the forums...
i guess i'll keep trying, thank you for your help.
sasukewa said:
Ok, I got that before going straight to a Froyo custom rom, try a EWJET 2.1 custom ROM first and see if you still have that problem. I did that and didnt have problem moving up but I went back again to 2.1 for other reasons.
Click to expand...
Click to collapse
I gave this a try, downloaded the latest EWJET 2.1, everything worked fine on that rom, no crashes, etc.. so i tried flashing several roms thereafter, without success..
could it have anything to do with being on a locked bootloader?
I know people are going to say i have to search before asking, but i cannot find a question regarding this problem that has an definitive answer!!
I have been on this forum for a while and have never posted due to not having any problems that didn't have an answer available, but recently i dropped my X10i and the screen broke :-( so i got a replacement phone from SE, i have flashed and rooted an installed xrecovery but when i restore my previous tripnmiui backup
I will detail my process
I received the phone with 1.6
I installed seus and updated to 2.1 (BB 46)
I then ran the x10flash tool to flash to BB52
I then rooted the phone an asked for root permissions to install xrecovery
I then booted into xrecovery
Full wipe, partition cache, dalvik cache, battery stats etc...
I then restored my previous back up
This has now booted up fine but i have no radio and it says unknown radio!
i have tried to crash the system and have tried the BB patches with no luck :-(
Does anybody know what else i can do ?
Reinstall the ROM and then use the 'Advanced Restore' option in XRec to restore the data from your previous backup. Make sure you reboot after the install and get radio working before restoring the old data. Hopefully that gets everything working for you.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
I have now resolved this issue but thank you for replying
What i had overlooked is that what i was doing was installing the old rom on BB52
but the original rom had been installed on bb54 with the bb54 patch
so i reflashed my phone to bb54 and restored the rom and this had resolved the issue,
so for future reference people!
when restoring a rom to a phone make sure it is on the original baseband that it was on when you took the backup!!
CeeJay
I bought device in Europe with German Vodafone 2.3.4/4.5.2A rom.
I get reboots with all roms i tried as well as all custom kernels i tried while these all stuff work on other peoples devices with no issues whatsoever..
Before flashing rom i wipe device with moto-fastboot and cwm like anyone else who is familiarized with the procedure.
I follow all instructions and all but somehow i end up with issues not many people have.
What the hell doing wrong if anything at all?
well this is the wrong section to post in, but have you tried factory resetting from the phone?
Wrong section. It might be that your CPU is getting very hot, so it keeps rebooting.
Tried factory reset off course but i don't have any single issue with stock software. Just with custom ROM's and kernels i want to play with.
Also, I haven't noticed it gets hot that much.
how come it doesn't get hot and reboot that much to other people?
What problems beside the reboots?
Sent from my MB860 using Tapatalk
@schwarzlichtkind, something like widgets missing after reboots, display staying turned on (when talking) when it needs to turn off.. annoying stuff like that..
Which CWM are you using?
Sent from my MB860 using XDA App
when you install a rom do u wipe data, cache, and dalvik cache before flashing the rom?
then do you fix permissions after flashing?
i recommend you do this when you flash a NEW rom, if you are installing an update just wipe cache and dalvik before flashing, then fix permissions after.
latest romracers..i always tend to run latest software, hence the topic
I'm having a similar issue since I got my phone back from repair, no matter what I do faux's kernel 0.2.2 and 0.2.3 cause random reboots and the phone not turning on and heating up. So far 0.2.1 hasn't caused me any problems, hopefully 0.2.1 fixes this and 0.2.4 (in the future) doesn't give problems.
First of all, please post question on the Q&A forum, not on the Android Development one.
Second, please organize your things before asking, and ask a serious question to get a useful answer. Based on your question, 90% of the answers will be guesses.
I reccomend you pick a ROM you like, try it without any custom kernels for a while and see if you get the same reboots. If so, then post a question on the appropriate ROM's discussion thread, don't create a new one just because.
Edit: Post reported btw
Sent from my MB860 using xda premium
Are you sure you fully wiped? data cache and dalvik? if you did you can try using rom manger and official CWM
everytime a flash a rom i use this tool without fail. option 10. then i do the appropriate wipe in recovery. have never had a bad flash. i am anal like that. : )
http://forum.xda-developers.com/showthread.php?t=1314607
I have problems with faux's latest kernels also. Just stick to the stock cm7/blur/MIUI kernels and you should be fine.
Sent from my MB860 using XDA App
try under volting using setcpu. i too had this random reboot issue. but did an undervolt of 100mV (for 1.45GHz). i use faux's 1.45ghz kernel v2.3
have fun!
a possible radio issue i think...
Which radio works better? I have N_01.100.00R
Hi,
I have a galaxy note i-717m. It is lagging very badly, even if i tried to clear cache, dalvik cache, and wipe data/factory reset.
I tried to restore it to a working rom, it succeeded with less lagging. However, the phone freezes screen when I try opening any apps and will reboot after sometime.
Could anyone please help?
Going back to stock cannot help either.
Flash the correct modem. That is a Bell phone originally, right?
rangercaptain said:
Flash the correct modem. That is a Bell phone originally, right?
Click to expand...
Click to collapse
Ok i will try flashing the bell stock modem as well.
flahsed stock bell modem by cwm, sucessfull, but cannot fix the lag
Just don't do anything flashing-wise. Let the rom and modem settle for a little.
I tried letting it settle for the whole afternoon.
I still experience freezes when i try opening some apps and everytime i press back to exit an app.
The phone reboots sometime, sadly i don't have a tjag box.
I have gone to recovery and show log.
Its shows: failed to open /sys/class/android_usb/android0/state: no such file or directory.
Dunno if that matters.
Valentino0918 said:
Hi,
I have a galaxy note i-717m. It is lagging very badly, even if i tried to clear cache, dalvik cache, and wipe data/factory reset.
I tried to restore it to a working rom, it succeeded with less lagging. However, the phone freezes screen when I try opening any apps and will reboot after sometime.
Could anyone please help?
Going back to stock cannot help either.
Click to expand...
Click to collapse
Is your rom stock? Or did you flash a rom from the development section?.. The lag your talking about?...why are members talking about your modem for lag? am confused?.....What exactly are you looking for? can you flash a rom? if so stay away from Jelly bean based roms right now,seems to have alot of bugs..I tried most of them.and users that arnt that experiencedvshouldbstayvaway from them and just stick to a good stable ICS rom right now...your lag will be gone and your phone should run alot faster you will see improvements right away
I restored to the bell stock rom and modem
The device can boot, but it freezes when i press the back button, trying to quit an app.
thank you for your advice, i will try getting the canadian custom i717 rom
I'm helping a friend with her S3 i9300. It was running very sluggishly and starting in the last couple months she's been having a sleep of death issue.
It works fine (albeit slowly) while she's using it but when it sleeps for more than 10 minutes it doesn't turn back on without a lot of trouble or a holding down the power button and hard resetting. Every once in a while it only boots if I go indirectly through download mode.
I've confirmed with the play store app that she does NOT have the "insane chip" involved in the SDS issue. I've also factory resetted, rooted, tried flashing a custom kernel, a custom TW ROM (S5 sensation) and now an AOSP ROM (resurrection remix) and the problem persists.
Looking at other users' suggestions I took it apart and cleaned/played with the power button, even replacing it with the one from my old t999. Still the same.
I'm at a loss at this point. Has anyone run into this issue and found a fix I'm missing? Thanks for the help.
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
TENN3R said:
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
Click to expand...
Click to collapse
Thanks for the reply. Before flashing any ROMs I've always made sure to do a factory reset and then individually wipe System, Data, Cache, and Davlik Cache even though I know I'm duplicating some of the wiping. Unfortunately that did not work in this case.
I'll give the MEGA/SUPER wipe a try and report back.
Thanks again.
Looks like MEGA wipe didn't do the trick either. The phone is on NA8; is there a newer baseband I can try? Not sure what else to try.
At this point I'm thinking it might just be a hardware issue.
Flash the latest stock firmware from sammobile then factory reset, remove sd card and sim then test with a different battery.
If still the same then it is a hardware fault, motherboard/cpu.