Related
I have tried a couple of custom roms and they have all worked fine at first but then after a while most of them would do something like force close whenever i try to open anything. This is getting really frustrating. I have a build 1009 and im looking at phoenix 3.0 and perception 10.0 both look really nice. Could someone tell me what im doing wrong and how to fix it. Every time i try to enable third party apps recently or something else ( I can't remember specificly what it was but it was rooting it or something) it will do the blah blah something apcore stoped working force close so right now im just going to use my phone on stock firmware and use it like normal and see what happens but could someone help me. I have used gingerclone, Assonance (force close problem), Darky 8.0 with the captivate workaround (force close problem), and maybe a few others but those are the only ones i can remember.
Custom roms are rooted with side loading enabled. So if you are trying to do this after you have the rom loaded, that could be a problem. I also would like to know what you are restoring on these roms. Should only be user apps.
To pin point your problem please provide more detail
I have put apps from custom roms onto the stock rom and other roms. Could that be the problem? And also this is what im going back to.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Im only doing the first part im not going to jh7. would that have something to do with it. Any help is greatly appriciated.
yamato2 said:
I have put apps from custom roms onto the stock rom and other roms. Could that be the problem? And also this is what im going back to.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Im only doing the first part im not going to jh7. would that have something to do with it. Any help is greatly appriciated.
Click to expand...
Click to collapse
What apps?
I do not think only going back to jh7 would cause your issue. Tell me more about what you are trying to do to enable side loading, and why you are doing it on as custom rom
I had the ones i downloaded and i sideloaded one wireless tether app a long time ago then i backed it all up with titanium backup and i would install a custom rom and it would have roms preinstalled on it. I would want to put on a different custom rom so i backed up again and the flashed back to stock the to the new rom. and i would restore all the apps including the one from previous roms. If you are asking for the specifics it would take a while and about the side loading i followed the guide http://forum.xda-developers.com/showthread.php?t=738376 and did the method 3 it seemed to work fine until i rebooted and then it did the force close thing. And i didn't go to jh7 i went to jh6 or jh2 or something like that but im going to try going to jh7 and see if that helps.
dont restore ALL apps in Titanium Backup. safest option is "restore missing apps+data"
all the custom 2.2 roms have tethering/wifi hotspot built into them...no need for another app for it.
for custom roms, you DO NOT need to root or sideload...they are enabled by default on all custom roms.
Thank both of you for your help. I will probably for now only install roms specificly for captivate and with specific instructions.
Hi there, im new to this forum and Im kind of a novice to flashing and rooting.
Firstly, my device is a Samsung Galaxy Tab Sprint version.
Secondly, when I bought this tab, I got fed up of the stock software so I decided to flash the rom. I researched allot on how to do this. Then I came across a custom rom called Modaco and flashed my galaxy tab using Clockwork Recovery.
Thirdly, I started to experience a particular problem - the AutoRotation broke. Whenever I rotated my tab portrait in a way that the homescreen, back buttons etc are in the normal position, the screen itself will be upside down making it difficult for me use the tablet conveniently.
Next, I started to develop another problem, i wasn't able to boot into recovery mode so i came accross another method to remove the modaco custom rom to install the stock rom. I used ODIN and download mode. This worked but the whole autorotation situation still persisted. I downloaded a file that would attemp fixing the autorotation problem but didnt work so I tried booting into recovery mode using ADB recovery and Clockwork Recovery but whenever it attempts to get there, it then shows me the samsung logo and remains frozen.
Lastly, I have come to a conclusion that I dont want to be using custom roms and I think it has to do with the Kernal. I want my tablet to be as I just bought it, untouched, not flashed etc.
If anyone can provide me with a solution, then I will be extremely greatful. Thanks
Seriously move this to the QUESTION THREADS. You will get more help there.
Check this thread out: http://forum.xda-developers.com/showthread.php?t=1009926
thanks, i will
been here
TCstr8 said:
Check this thread out: http://forum.xda-developers.com/showthread.php?t=1009926
Click to expand...
Click to collapse
Hey I've been here already but that SW Update doesnt work. It tells me "Cannot open Binary file" can you tell me why?
See post #34 in that thread posted by cdguider.
download the : New File With Odin, Sprint_P100_Samsung_GALAXY_Tab_USB_Drivers, Installation Instructions
read and follow the .txt file that is included step by step and it will work....
I used it but the first time I was in a hurry and did not read the install txt, didn't work. I opened the imstructions and went step by step the next time and it worked no problems..
hope it works out for you.
I am starting this thread, since it seems a lot of users are posting their problems in the Development section. It has become confusing for the other users who are new to this website to post thier queries in other thread. This thread will generally be answered by experienced users and we will continue to help as long as you guys do not create a mess here -:d
My phone have only 11gb internal memory. Is it normal? I though its 16gb phone
Crazy Ushi said:
My phone have only 11gb internal memory. Is it normal? I though its 16gb phone
Click to expand...
Click to collapse
Ya thats normal 11 gb for user...around 2 gigs is for apps...plus rest for system..
New user of a Galaxy Note, I remarked a strange thing with the way the Galaxy Note manage the wifi connexion. At my home, I've one Wifi network. One access point is into my desk and the second into my living room. When I connect my Note on the wifi into my desk room, I got the Wifi at 100% (of course as I'm at 2m of the antenna ;-) ). Now, if I move from my desk to my living room, the Galaxy Note still remain connected to the Wifi of my desk room witch is not good because I lost the 90% of my wifi power.
My question is now: Does it exist any solution to have my Smartphone switching automatically depending on witch room I am ?
For example, with my iPhone and/or iPad, both device automatically use the more powerfull signal (the one of my desk room when I'm in and as soon as I'm more closer of the antenna of my living room it switch to this antenna).
Last information, same problem with a Galaxy S2.
Is it a limitation of Android or a "specificity" of Samsung devices ?
Thx for your feedback !
Force shutdown every time I runs any application
Hello, newcomer's here. I've rooted my N7000 & installed stable CM 10.1.3 ROM, but I can't run any apps more than 10 minutes or less.
When I runs an app (especially games), even when the battery was 100%, the device will force shut. When I immediately turned it on after the
force shutdown, it will force shut at cynogenmod boot screen, but sometimes when I managed to (barely) get in, the battery bar indicates there's
only 1% charge left. So, I thought I should try BatteryCalibration, but still the same issue. Then I thought maybe it's the ROM, so I
installed the updated nightly version CM 10.2 ROM, and the same issue occurs again. I've searched in "All Forums" and found the idea on "wipe
battery stats" in recovery after install new ROM, but I can't find that option in CWM. Then, I read the idea of wiping battery stats has no effect at
all in the battery issue (http://forum.xda-developers.com/showthread.php?t=2256038). So, I flashed the stock ROM back and I didn't
face any issue on force shut and rapid battery drain anymore. But I've found a similar situation faced by other member in this thread
http://forum.xda-developers.com/showthread.php?t=2506468. Do I have to go that far just for remedy?
Is there any solution for this? Because I like custom ROM than using the stock, it's fast and swift RAM usage. Thanks for any advice on this.
Did you try a different battery to start with.?
my N7000 (factory firmware 4.1.2) was in charging, then suddenly its turn off automatically, then i switch on it, it stuck at boot screen..
cannot go recovery mode,
can go download mode with android logo, not ' ! " logo
flash back factory firmware, ordin stuck at boot.bin..FAIL
help
nokiamodeln91 said:
Did you try a different battery to start with.?
Click to expand...
Click to collapse
Nope, I don't have any spare battery for my device. Just bought it 2 weeks ago.
I'll consider your advice. Thanks.
N7000 screen
Hi, I'm not sure wether this is the right thread, but it is a question and I do need an answer..
Does anyone know wether the display of N7000 is the same as SHV-E160L?
I have one N7000 with a broken glass and LCD, and can get hold of a SHV-E160L for same price as the display only.. Would there be a way to frankenstein the LTE possibilities of SHV-E160L into the N7000?
Hope someone has hands on experience with this.. At least the screen part, since it is the main reason for the project..
LTE would be the icing on the cake..
Not sure of the screen but LTE is the compatibly dependent on SOC. The SHV has a snapdragon processor and Exynos doesn't have.
how to disable custom rom flashing twrp recovery? and just stay on cwmr?
First post ever on forum, sorry if i did something bad
You really can't. If the custom rom (may be you are referring to kitkat) comes only with twrp, you need to live with it till some kernel Dev makes a kernel with cwm compatible 4.4.
nokiamodeln91 said:
You really can't. If the custom rom (may be you are referring to kitkat) comes only with twrp, you need to live with it till some kernel Dev makes a kernel with cwm compatible 4.4.
Click to expand...
Click to collapse
Ah, then i get it, thanks for your help!!
Need Help...Plz
nokiamodeln91 said:
You really can't. If the custom rom (may be you are referring to kitkat) comes only with twrp, you need to live with it till some kernel Dev makes a kernel with cwm compatible 4.4.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559371
Please help me with my problem if you can. My mobile is seen by odin but i am unable to find a Stock Jellybean Rom for N7000, i.e either .tar or .md5 file in internet.
lord_pmvk said:
http://forum.xda-developers.com/showthread.php?t=2559371
Please help me with my problem if you can. My mobile is seen by odin but i am unable to find a Stock Jellybean Rom for N7000, i.e either .tar or .md5 file in internet.
Click to expand...
Click to collapse
Then install philz kernel using odin. Then boot into recovery. Flash any custom rom.
I now got another question, i have the 4.4.1 alysum omni and i just can't get the "standard email"(the one that is original on stock rom) app working, its giving me messages saying i cant login, i took it out from the "removed apks .rar file" and just installed it on new fresh rom, everything else works but not that.. what can the problem be?
its chewing and chewing for like 5 mins when i press next for login.. and then gives error "cant sign in to server"
thanks
Ate you talking about the Samsung Email app? Then it won't work without a TW framework.
My phone got stuck at boot screen and unable to go into recovery mode but can go into download mode.
Should i flash back stock gingerbread via odin? Do i need to i stall any kernel? Pls help.
My phone got stuck at boot screen and unable to go into recovery mode but can go into download mode.
Should i flash back stock gingerbread via odin? Do i need to i stall any kernel? Pls help.
shokokatana said:
My phone got stuck at boot screen and unable to go into recovery mode but can go into download mode.
Should i flash back stock gingerbread via odin? Do i need to i stall any kernel? Pls help.
Click to expand...
Click to collapse
Flash philz .tar file from download mode and you should have working recovery
Sent from my GT-N7000 using Tapatalk
Hi there
Firstly, let me state that I am a novice when it comes to rooting/flashing ROM,etc. I foolishly rooted my G note and found that it slowed my phone down to an astonishing rate. I was able to unroot after hours of trying (eventually finding an app on snappzmatket).
This seems to have cleared the root/super user, etc but something has been left behind that I cannot remove called CWM.
I just want my phone back to its perfectly adequate state, so anyone know how I can get rid of CWM? I think it has something to do with stock ROM, or is a replacement for it??
Like I said,I should not have been messing with it as its way over my head all this. if it helps, I'm in the UK and my note is with O2
Any help would be greatly associated
Cheers, Adam
Just flash any non rooted stock ROM from Dr Ketan's thread in the dev section. Use PC Odin.. Should be good!
Sent from my GT-N7000 using XDA
...take a look here...
http://forum.xda-developers.com/showthread.php?t=1329360:D
Hello, i have a problem with my galaxy gt i9000. i start the camera, couple sec. later it just crashes, it says "unfortunately, gallery has stopped." before that i was using android 2.3.3 then it said camera failed. but then i flashed jelly bean 4.1.1 and still crashes, do anyone knows what might help to get it working again?
mihkelramjalg said:
Hello, i have a problem with my galaxy gt i9000. i start the camera, couple sec. later it just crashes, it says "unfortunately, gallery has stopped." before that i was using android 2.3.3 then it said camera failed. but then i flashed jelly bean 4.1.1 and still crashes, do anyone knows what might help to get it working again?
Click to expand...
Click to collapse
go into the settings, app, all, gallery -----> clear cache and delete data
for safety still in recovery mode, wipe cache and dalvik.
then it should go back.
djceet said:
go into the settings, app, all, gallery -----> clear cache and delete data
for safety still in recovery mode, wipe cache and dalvik.
then it should go back.
Click to expand...
Click to collapse
Still nothing
says unfortunately gallery has stopped (
mihkelramjalg said:
Still nothing
says unfortunately gallery has stopped (
Click to expand...
Click to collapse
ok......hmmmm....
download this -----> http://goo.im/gapps/gapps-jb-20121011-signed.zip
go to recovery mode and wipe cache and dalvik.after that flash that zip.
this could help you. if not it would be better to re-install the rom after you have installed the stock rom + root kernel.
revert it to stock, re-root it, then install whatever ROM, then see, it solved it when i had that problem :fingers-crossed:
mihkelramjalg said:
Hello, i have a problem with my galaxy gt i9000. i start the camera, couple sec. later it just crashes, it says "unfortunately, gallery has stopped." before that i was using android 2.3.3 then it said camera failed. but then i flashed jelly bean 4.1.1 and still crashes, do anyone knows what might help to get it working again?
Click to expand...
Click to collapse
I see one or two possible causes of your problem:
1. Kernel more than 391MB usually breaks the 720p video and Gallery, make sure the bigmem patch of kernel is not activated.
2. Flashing directly from GB to JB usually causes post-installation problems, one of which maybe is your problem. Developers recommend a gradual ugrade of Android system to avoid any problems. From GB flash a CM9 ICS first then finally the JB Rom you wanted. In this way, you will surely get a trouble-free Rom.
smiley118118 said:
revert it to stock, re-root it, then install whatever ROM, then see, it solved it when i had that problem :fingers-crossed:
Click to expand...
Click to collapse
i dont remember the stock android and other sh*t can u tell me or post a link were i can get everything what i need to revert it stock ? tnx.
You can also try to fix permissions in CWM under "advanced".
prob.
i reverted my galaxy s gt i9000 to stock, and hoped to get camera working again but no. has still that problem, says camera failed or something like that.
well i seen some posts about copyng camera firmware, i tried that. but next problem was... that this copy failed. idk why, maybe i cant in stock ?
pls someone help me!
I think I have exactly the same problem.
It was caused by flashing Onecosmics ICSSGS RC 4.2 to CM10 Stable. (i have to admid the camera was semi broken at ICSSGS already, crashed somewhere in an hour after booting, had to reboot phone to get it running again, but well it was working...)
Camera has never worked since. (stock sammy gave me a black screen when opening the camera, making a picture just made it freeze. CM10 just gives gallery crashes upon opening. Tried nandroids, cleared cashes, tried stock sammy firmwares. I wanted to do a Samsung Kies repair, but i was unable to find stock firmware for my country...
Flashing the camera firmware might work. It didn't for me, but i have heard it could be the solution.
Can you see if you front camera is working (install instagram and make a front camera pic, will evade the gallery has crashed problem).
yea, my front camera works, i can take pictures and watch them later.
but my back camera doesnt work
maurico0o said:
I think I have exactly the same problem.
It was caused by flashing Onecosmics ICSSGS RC 4.2 to CM10 Stable. (i have to admid the camera was semi broken at ICSSGS already, crashed somewhere in an hour after booting, had to reboot phone to get it running again, but well it was working...)
Camera has never worked since. (stock sammy gave me a black screen when opening the camera, making a picture just made it freeze. CM10 just gives gallery crashes upon opening. Tried nandroids, cleared cashes, tried stock sammy firmwares. I wanted to do a Samsung Kies repair, but i was unable to find stock firmware for my country...
Flashing the camera firmware might work. It didn't for me, but i have heard it could be the solution.
Can you see if you front camera is working (install instagram and make a front camera pic, will evade the gallery has crashed problem).
Click to expand...
Click to collapse
yea, my front camera works, i can take pictures and watch them later.
but my back camera doesnt work
strange problem
Batistuta1 said:
strange problem
Click to expand...
Click to collapse
yes
still nothing
for now i tried to copy another galaxy s i9000 camera firmware and samsung wawe cam. firmware, but still that same problem... well 1 thing changed.
my galaxy s gt i9000 front camera is messing right now, i got like 6-7 me on that camera some lines are on the screen in camera :/
Well, if someone knows something what could help then please tell me!
ive tryed another roms, i been using android 2.3.6 and 4.1.1, back on stock, copyng files and messing around with that.
maybe camera is broken? i dont know what to do...
Have the same problem for a long long time.
been flashing a lotta roms kernels etc.. nothing.
I even changed the camera (I had another GT-i9000) and nothing, which makes me believe it's something of the Motherboard
Also, if I press the screen at the top half of it.. it shuts down.
I've had no back camera for a long time either. I've flashed back to eclair, tried about 4 different cam firmwares which all flashed successfully so they said, and lots of ROMs. I gave up. Im sure it must be hardware.
Seen people posting over time about the same thing. Firmwares helped a couple of people, but lots of people ended up with a dead camera. Buying a new camera unit from eBay fixes it. I think they're about £20....
Sent from my GT-I9000 using Tapatalk 2
I have exactly the same problem. Tried everything from changing many roms and kernels. Even bricked my phone for two weeks and then resurrected it using Darky's Rom Resurrection. But the camera even crashed in Darky's rom and it is still not working when I'm back to SlimRom 4.2.2 build 6. It was working all file and I cannot believe that it is a hardware issue. Please help.
YRS
same problem on my i9000. I will try with another camera from a friend's i9000.... if nothing happens probably will leave my precious