Related
My phone is rooted and I have had many custom roms on my phone. I decided to flash Virtuous Unity rom today, did a full wipe first, flashed and did a reboot and now once I get past the lockscreen a bunch of system force closes come up and after about 30 seconds it reboots again! Is my phone bricked? I have managed to get into recovery mode a couple times and even tried flashing other, previous roms that I have worked before and the same thing happens! I honestly don't know what to do can anybody help?!
bellerophon90 said:
My phone is rooted and I have had many custom roms on my phone. I decided to flash Virtuous Unity rom today, did a full wipe first, flashed and did a reboot and now once I get past the lockscreen a bunch of system force closes come up and after about 30 seconds it reboots again! Is my phone bricked? I have managed to get into recovery mode a couple times and even tried flashing other, previous roms that I have worked before and the same thing happens! I honestly don't know what to do can anybody help?!
Click to expand...
Click to collapse
try wipe and flash the rom again.
Go into recovery mode and choose advanced, then Wipe Dalvik Cache; go back and choose factory reset, after this flash Full Wipe 1.5 ext 4 and i recommend to flash CoreDroid Rom, to have a running system, otherwise ARHD Rom; after this i think you will have success. I had a similar experience with another rom and this helped me.
Yes as Neo XL said you need to wipe everything and then install a fresh ROM. Sometimes things just get a bit buggy for no apparent reason and all it needs is a wipe.
Also double check the md5 matches, many problems are caused by corrupted downloads
I finally got it back to normal. it was very frustrating trying to hit the power button and restart into recovery mode when force closes are literally popping up every 2 seconds. I did a full wipe/factory reset and I wiped delvik cache. I then flashed MIUI (none of my Sense ROMs would load for some reason), and used rom manager to flash the new Unity ROM, which worked. For some reason, I am having difficulty flashing ROMs directly via Clockwork (mainly sense-based ones).. but If I go through ROM manager, it usually works..
Next time don´t wait, until you can hit the power button; remove short the battery and then restart by holding volume down.
You might want to try reinstalling clockwork. Dont do it via ROM Manager, get the latest proper release of CWM here: http://forum.xda-developers.com/showthread.php?t=1003723&highlight=clockworkmod
Follow the instructions on how to install it but do verify the MD5 and the SHA-1 tags using a program called Exactfile.
bellerophon90 said:
My phone is rooted and I have had many custom roms on my phone. I decided to flash Virtuous Unity rom today, did a full wipe first, flashed and did a reboot and now once I get past the lockscreen a bunch of system force closes come up and after about 30 seconds it reboots again! Is my phone bricked? I have managed to get into recovery mode a couple times and even tried flashing other, previous roms that I have worked before and the same thing happens! I honestly don't know what to do can anybody help?!
Click to expand...
Click to collapse
i just tried to flash this rom today and had the same issue on inspire 4g... did a full wipe and install through clockwork and i had your problem 3 times.. first time was when i tried to use htc sense acct... second and third the rom was fine for about 10 minutes then just had all these system force closes and reboots... i was under the impression that flashing a rom though rom manager wasnt really the proper way to flash roms.. im still new to all this coming from the iphone world... i was really interested in trying out the virtuous unity rom... have you had anymore FC issues since flashing through rom manager??
Posting here since I cannot yet post to the actual ROM forum.
I'm running the Synergy ROM, RC1 and have a couple of issues. First though, thanks to the DEVs for all of their time and efforts, this looks to be a very good ROM!
I've been through most of the 200+ pages on the ROM's thread and did not see any information that may help (except turning off auto rotate of the home screen), but it's possible I missed.
The main issues I have are slow response issues. They are:
Slow response when I pull down the navigation bar.
Slow response when hitting one of the soft buttons (i.e., the + button to launch the app specified by the settings in Rosie).
Very slow response when I come out of a game that was in landscape mode. It takes a couple of seconds for the screen to switch from landscape back to portrait (after flipping the phone to portrait) and then another few seconds for it to put all the icons back on the home screen (home screen is blank when I come out of the game). I did turn auto rotate off and that has helped, but was wondering why there was such slow response without it.
Google apps such as Maps and Calendar that are started by another application, but do not shut down the starting app exists. This, of course, drains the battery and was not an issue on the stock rom.
When I flashed the rom, I did do a factory reset and erased all other caches. My apps and app data (not system data) were restored via TB.
I have also frozen the following apps via TB:
Flash
All live wall paper apps
Stocks
Flickr
FM Radio
News
Stocks
Smoke & Visualization Wallpapers
Voice Dialer
Voice Search
Thanks!
Mike
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
ithrewitontheground said:
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Absolutely correct. On top of this, the other reason you may be seeing slow response would be the fact that this is a very large rom, and takes up more space in your usable memory than most roms. What I have done to *somewhat* alleviate this issue when I'm running the synergy rom is to move all of the apps that I can (except for those that I use widgets from) to the SD card.
Just my recommendation
ithrewitontheground said:
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
My thought was that when restoring an app, such as WSOP Texas Hold'em, I also wanted to restore the data so it restored games won, amount of money, etc.
Is that data what you are saying I should lose when flashing new roms?
Thanks,
Mike
0soPolar said:
Absolutely correct. On top of this, the other reason you may be seeing slow response would be the fact that this is a very large rom, and takes up more space in your usable memory than most roms. What I have done to *somewhat* alleviate this issue when I'm running the synergy rom is to move all of the apps that I can (except for those that I use widgets from) to the SD card.
Just my recommendation
Click to expand...
Click to collapse
Quite a few of my apps are on the SD card. I have 313MB free on the internal storage. Should that be enough to reduce some of the lag.
Thanks!
HELP!!! I flashed synergy rom last night and today, it goes to the boot animation screen and freezes. It just shows the synergy rom bouncing around and wont go anywhere from there. I tried doing a recovery through bootloader, but it wont let me move down from fastboot. Did I just brick my phone or is there any other way to get past this screen? can i plug my sdcard into the computer and delete this boot animation and if so, where would I find it? Please help, it would be GREATLY appreciated!!!
Give the phone a minute. It will let you move it. I just keep hitting volume down. It will work.
Sent from my ADR6300 using XDA App
dysfunkshun said:
HELP!!! I flashed synergy rom last night and today, it goes to the boot animation screen and freezes. It just shows the synergy rom bouncing around and wont go anywhere from there. I tried doing a recovery through bootloader, but it wont let me move down from fastboot. Did I just brick my phone or is there any other way to get past this screen? can i plug my sdcard into the computer and delete this boot animation and if so, where would I find it? Please help, it would be GREATLY appreciated!!!
Click to expand...
Click to collapse
If you can boot into recovery, you did not brick your phone.
I've had this problem before and I don't even use Titanium. I also had plenty of free space on internal. Ram never seems to free up though. It's the strangest thing.
Sent from my ADR6300 using XDA App
Does anyone else have issues with anything that requires data syncing (Facebook, Twitter, SMS, etc) stopping unexpectedly? It seems to happen at around 30% battery and the only way I've consistantly stopped the problem is to wipe and reflash Synergy Rom.
Any ideas?
Yea Idk what's going on with it after about an hour I would get android.process has stopped and needs to force close. I can't even use any app as that constantly pops up. Great ROM but unusable at this point.
Did you do a complete wipe before you installed it. Most of the issues I have seen arise because a complete wipe has not been performed. If you like the rom, do a complete wipe (factory, partition and dalvik) and reflash it.
jlokos said:
Did you do a complete wipe before you installed it. Most of the issues I have seen arise because a complete wipe has not been performed. If you like the rom, do a complete wipe (factory, partition and dalvik) and reflash it.
Click to expand...
Click to collapse
This is after a full wipe, twice. Once the battery gets to a certain point, everything starts crashing and never recovers no matter what I do. Battery pull, full charge, cold restart. Nothing works.
Edit: I've also noticed that the GPS is locked on and I cannot shut it off.
Chindogg said:
This is after a full wipe, twice. Once the battery gets to a certain point, everything starts crashing and never recovers no matter what I do. Battery pull, full charge, cold restart. Nothing works.
Click to expand...
Click to collapse
Yea I also did a full wipe two different times. I didn't notice it happening once the battery gets to a point I just know that after an hour or so of use it was unusable.
1. If you use DualRomX2 would that possibly speed it up? Because doesnt it install Roms on EMMC?
2. Im also really frustrated by the slow response on alot of things like right rosie button and notification pulldown.
3. Video recording for me is just awful. Im not sure about actual quality but the framerate for sure is horrible. I compared a video i shot on stock and with Synergy and there is a HUGE difference. Synergy video being much worse.
Great Rom just plenty of little annoyances.
Synergy ROM loading issue
Flashed Synergy ROM last week and was very impressed. However, saw where 3.0 Sense items were missing and realized after reading several other posts that the carousel +widgets.zip should have been loaded with the ROM. So I reloaded the ROM and widgets through AMON-RA Recovery (Followed all of the original instructions I had followed the first time I loaded the ROM). Everything looked fine until I rebooted the system. Now Synergy ROM start-up screen loops over and over. At this rate the fill battery I started with will run out, and I'm not sure what will happen at that point.
Anyone have any suggestions for this issue? Any help would be appreciated. Thanks.
Options:
a) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, & flash a different rom.
b) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, flash Synergy again, reboot.
c) Pull your battery then turn on your phone like normal.
d) Pull your battery then boot into recovery, wipe cache/wipe dalvik cache, then boot into rom.
Edit: I don't use Amon_Ra, when I refer to "recovery" I was referring to CWM. Hopefully someone with experience comments in regards to Amon_Ra recovery.
Yeah I don't have too many issues with it... last night it got kinda squirrely so I fixed permissions in recovery and re-flashed the Warm Theme without wiping any data, it's been all good ever since.
The ROM is my daily driver... I really do think that these issues are app-related. There is something that certain apps do that this ROM is not built for, I'm just not sure what it is. It's been real good to me overall though, battery life and all.
SlimSnoopOS said:
Options:
a) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, & flash a different rom.
b) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, flash Synergy again, reboot.
c) Pull your battery then turn on your phone like normal.
d) Pull your battery then boot into recovery, wipe cache/wipe dalvik cache, then boot into rom.
Edit: I don't use Amon_Ra, when I refer to "recovery" I was referring to CWM. Hopefully someone with experience comments in regards to Amon_Ra recovery.
Click to expand...
Click to collapse
SlimSnoopOS, as it turned out I pulled the battery and rebooted into Recovery after a few hours, but thanks for the direction. These were the exact things I did. The reason I used AMON-RA instead of CWM is that Synergy says in a number of places that it only loads with AMON-Ra (and I'm a coward!),
Awesome, glad everything is functional again!
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App
could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App
I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.
I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.
well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far
Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon
Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve
Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve
the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.
Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve
I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium
Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve
Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve
Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
TALBR said:
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
Click to expand...
Click to collapse
OK... so ODIN is working, eh? That helps the situation. Now...
1) If you can get ADB working, probably.
2) By flashing a pit file through either ODIN or (custom) recovery. (I prefer using recovery as it's safer.)
3) Not completely sure, though it (might) be a hardware issue.
P.S. You should NEVER flash stock ROM unless you have a bricked device. I rather you flash CM11 even if you have a bricked device. I never trust stock ROM.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
TALBR said:
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
Click to expand...
Click to collapse
I had that situation of storage earlier.
u have no choice but to wipe all.
if u still can connect ur device to a pc, i would suggest to copy ur data on ur internal storage to ur pc.
after that, earlier what I did was flash the zoot script from cwm and do a custom mega wipe. of course ur internal storage will be wiped. clean until all the folders nd files.
then reboot back to recovery to flash custom rom again.
if u r not rooted the only way is to factory reset full wipe system data nd cache.
wipe cache only won't solve the problem of internal storage.
to be frank, u jump from 4.3 to 4.4.2, u have to factory reset. too many users try to avoid this because lazy to resetup nd backup. but u have no choice.
Sent from somewhere under the sky, at the corner of this rounded earth.
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Irwenzhao said:
OK... so ODIN is working, eh? That helps the situation. Now...
1) If you can get ADB working, probably.
2) By flashing a pit file through either ODIN or (custom) recovery. (I prefer using recovery as it's safer.)
3) Not completely sure, though it (might) be a hardware issue.
P.S. You should NEVER flash stock ROM unless you have a bricked device. I rather you flash CM11 even if you have a bricked device. I never trust stock ROM.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
not all ppl like Cm / aosp.
and stock rom is not bad. it is just most ppl don't like to do a clean flash.
without stock rom, u can't use the full feature of spen, and it defeat the purpose of having spen.
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
I had that situation of storage earlier.
u have no choice but to wipe all.
if u still can connect ur device to a pc, i would suggest to copy ur data on ur internal storage to ur pc.
after that, earlier what I did was flash the zoot script from cwm and do a custom mega wipe. of course ur internal storage will be wiped. clean until all the folders nd files.
then reboot back to recovery to flash custom rom again.
if u r not rooted the only way is to factory reset full wipe system data nd cache.
wipe cache only won't solve the problem of internal storage.
to be frank, u jump from 4.3 to 4.4.2, u have to factory reset. too many users try to avoid this because lazy to resetup nd backup. but u have no choice.
Sent from somewhere under the sky, at the corner of this rounded earth.
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
not all ppl like Cm / aosp.
and stock rom is not bad. it is just most ppl don't like to do a clean flash.
without stock rom, u can't use the full feature of spen, and it defeat the purpose of having spen.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Or Ditto N3, stock ROM has loads of bugs (kitkat)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Irwenzhao said:
Or Ditto N3, stock ROM has loads of bugs (kitkat)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
I agree that DN3 is great rom.
I also agree that sometimes official firmware also have bugs.
but, I don't agree that custom rom will free of bugs that official have it.
certain bugs will still remain.
don't forget, custom rom is build on Samsung stock base with some enhancement to feel better in smoothness, functions, battery life, as well as user interface.
Sent from somewhere under the sky, at the corner of this rounded earth.
Not sure why there's an asop vs tw debate going on here... anyway, assuming the op's history is accurate, this sounds like hardware failure