Related
Hi guys,
I am little bit tired of using many ROMs on my smart phone. It's been a long time that I started flashing it. I have tried all of the updated roms but recently I am having a kind of stressful trouble with my phone. Whatever is the rom doesnt matter after few hours phone crashes on black screen and doesnr response, after replacing the battery or long time pressing power button it restarts and seems ok but after few minutes or hours it does it again. this trouble has become a regular issue.
the second thing is phone says your internal sd card is umounted unexpectedly and the series of errors begin. all of the errors are blocking to reach the settings and even cant see which applications are runing.
I have suspicions on a virus or kind of spyware has inoculated to my phone or it's kernel file system (but after flashing it should be gone right? must not continue in new flashed rom)
this problem occur after even after the new rom is installed (i use odin 1.83 for flashing and i dont do any rooting/deodexing)
if you can help me on this I would be glad.
Better post on QandA thread.. What you are experiencing is SOD which is common in KP7 and in OC'd kernel of SGSL.. Did you flash and overclocked kernel? If so then that's the cause of SOD..
Sent from my GT-I9100 using xda premium
actually I am using XXKB3 rom but at this time I am trying to understand what is the cause of this problem, I red some discussions on HTC desire likely same problem called "aka black death" so they argue about the same problem but no solution and no exact reason is mentioned.
My phone is not rooted, not deodexed, any cpu overclock application is not installed, it's just flashed with XXKB3.
by the way same situation is valid in each rom without rooting, deodexing and cpu overclocking.
that's why I am confused
since you have tried "many ROMs", surely you at least have CWM, and made a full backup of your stock kb3 ROM before testing others, so you could easily go back to one that you know works, right?
if not, you at least ensured to do factory reset, wipe partition, and clear dalvik cache each time you installed a new ROM, right?
if not, then the reason you're having problems is because there's old stuff fighting on your phone, and you need to follow those steps properly next time
actually I did that things each time I installed those roms, except clearing dalvik cache via titanium backup, cause this thing needs root permission.
this time according to your advise I'll root my phone and write back about what happens. soon
trombosit2000 said:
actually I did that things each time I installed those roms, except clearing dalvik cache via titanium backup, cause this thing needs root permission.
this time according to your advise I'll root my phone and write back about what happens. soon
Click to expand...
Click to collapse
Uh? You would not have CWM without root? If you have CWM, you obvi. should have root?
I even didnt update CWM after loading new ROMs. (while I am living that troubles)
unfortunately
no development on black screen crash and still unmounts the internal sd card unexpectedly so problem goes on and still I am on investigation.
clearing dalvik cache and rooting and playing with cpu clock speed also doesnt effect this thing.
I need to report this that after phone sleeps when somebody calls me it's not responsing no melody, no signal on screen, even no light or awakening
but it rings at caller's phone.
looking for HELP
trombosit2000 said:
unfortunately
no development on black screen crash and still unmounts the internal sd card unexpectedly so problem goes on and still I am on investigation.
clearing dalvik cache and rooting and playing with cpu clock speed also doesnt effect this thing.
I need to report this that after phone sleeps when somebody calls me it's not responsing no melody, no signal on screen, even no light or awakening
but it rings at caller's phone.
looking for HELP
Click to expand...
Click to collapse
I am sure you have flashed the BOOTLOADER, PHONE and CSC of KP9 or KP7. Else, you would not have faced this problem. A factory reset and a CLEAN GB flash would do the solution!
trombosit2000 said:
unfortunately
no development on black screen crash and still unmounts the internal sd card unexpectedly so problem goes on and still I am on investigation.
clearing dalvik cache and rooting and playing with cpu clock speed also doesnt effect this thing.
I need to report this that after phone sleeps when somebody calls me it's not responsing no melody, no signal on screen, even no light or awakening
but it rings at caller's phone.
looking for HELP
Click to expand...
Click to collapse
"playing with cpu speed", as far as I know, means you installed a non-stock kernel, which may be known to cause SOD, among other things. trying to do stuff while in that case can cause other errors to occur as well. if that's the case, try flashing back to the stock kernel in the same thread you got the overclocked kernel rom, and if not, remove whatever app you installed that's allowing you to adjust your cpu speed and see if it helps
P.S., it's becoming obvious you've done more with your phone than you're revealing, which isn't helping us troubleshoot your problems:
trombosit2000 said:
...
My phone is not rooted, not deodexed, any cpu overclock application is not installed, it's just flashed with XXKB3.
by the way same situation is valid in each rom without rooting, deodexing and cpu overclocking.
that's why I am confused
Click to expand...
Click to collapse
is what you originally said, but as far as I know, you can't adjust cpu speed in the kernel provided, unless it's an overclocked kernel. providing inaccurate information makes it harder to get the proper answers.
try listing all the things you've done, send screenshots of your phone's "about phone" screen, showing kernel, build, etc.
Srry to break it to ya mate... But since your internal SD seems to be unmounting and your phone seems to be SOD-ing, you need to reflash to stock and send it to the service center for repair.
This isn't a support forum, although we are willing to help to the best of our knowledge. Hope you get this sorted out mate!
Cheerio!
Sent from my GT-I9003 using XDA App
Let me share the latest info...
after trying to use my phone without external sd card, black screen problem has gone, phone is waking after pushing power button,
but this unmounting internal sd card unexpectedly and application errors still continues. After unmounting it mounts sd card back (by itself) and scans, but then I can not start any of the settings or system applications cause it gives errors and closes. if I insist to open a system application it phone is freezing and not responding. and then I have to reset it to turn normal. and unmounting problem goes for a short time...
if there will be no solution as Erahgon said I will take it to the warranty service installed with a stock rom.
for now I am still using the
Baseband: I9003XXKB1
stock rom: FROYO.XWKB1
Kernel Ver. : 2.6.32.9 [email protected]#1
didnt root it,
didnt deodexed,
didnt cleared dalvik cache,
sod's happn wid me too ..!
while downloading gamedata thru gameloft the sods occur ..
the solution :
download screen off frm the market ..
its the only solution fr the sods !
Hi,
Does anyone have any insight as to whether CM9 phone encryption is working on the ChaCha rom described on XDA:
http://forum.xda-developers.com/showthread.php?t=1665828
Phone encryption is not listed there as one of the known problems, but CM9 phone encryption problems are mentioned elsewhere on the net.
I installed the CM9 for the HTC chacha without any hiccups. (I installed it after doing a factory reset via CWM from a rooted s-on stock HTC sense rom. I did factory reset, then wipe cache partition, then wipe Dalvik cache, then loaded then CM9 and gapps zip files).
When I tried to do the phone encryption, it seemed to hang or stall on a screen with a green outline of the droid with a sort of lock waistband. The text at the begin encryption screen says the process can take an hour or more, but I left the phone plugged in for about 6 hours. The green outline icon was still there (after entering my PIN at the lockscreen). When I pressed home, it took me to the home screen, but under settings/security the option to encrypt phone was still there so I am assuming encryption did not work.
The other thing to consider was that I was using a 64gb sd card, so perhaps that would make the process take longer (though several hours seems sufficient). I will try again with a 2gb card.
Also, I had not restored any programs or data via Titanium Backup, nor linked to google email/play before starting the phone encryption process.
Thanks!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Honestly that's untested at this time. And why didn't you use General section in the ChaCha forums?
I'm curios as to weather it's related strictly to CM9 or not, if it's working on other ports and if it's working on the RC1.
From what I can see the procedure is as following:
Touch Encrypt phone.
Enter your lock screen PIN or password and touch Continue.
Touch Encrypt phone again.
The encryption process starts and displays its progress. Encryption can take an hour or more, during which time your phone may restart several times.
When encryption is complete, you’re prompted to enter your PIN or password.
Subsequently, you must enter your PIN or password each time you power on your phone, to decrypt it.
Click to expand...
Click to collapse
And if CM9 phone encryption problems are mentioned elsewhere then it's mostly a CM bug.
OK, I'm not sure exactly where the problem lies, since there seem to be some reports of it working on some versions of CM9 (perhaps on only some builds and phones).
Also, I tried without the large sd card - same result, it just hangs on the outline screen, rather than continuing and displaying progress.
It would be great to have this, since one of the biggest advantages of the Chacha is its great keyboard, but if the phone isn't encryptable (except with more tedious operations, e.g. tasker) then that sort of defeats the purpose.
Actually, I can't find anything via google about phone encryption working on any CM9 build, though it seems to be working on many ICS phones.
Report of same stall problem with CM9 and Samsung captivate and galaxy, etc:
http://forum.cyanogenmod.com/topic/49617-cm9-and-phone-encryption/
http://forum.cyanogenmod.com/topic/49970-cm9-not-encrypting-phone/
http://forum.xda-developers.com/showthread.php?t=1477920#23742435
Reports of the encryption problem as a CM9-wide issue:
http://code.google.com/p/epictouchcm/issues/detail?id=73
https://plus.google.com/112172895831966524738/posts/YMHhAob6m6W
Hi bro, i need some help here, suddenly my GT2 (GSM) will auto reboot after every 15-60 minute. It was running fine for the past 10 month since have install cyanogenmod cm-10.1.3.
The weird part is, not only it reboot, it will do a rollback to a fix setting every time it reboot.
- Let say, as a normal you have many application install, many photo or file in your phone
How it happen, as a normal user, I went to uninstall any application via application manager or Delete some photo from my gallery. It show success deleted..... but soon after few minute my phone rebooted by itself. After this reboot i notice what i just delete/remove come back again. Seems like there is a restore being done.
I also try to reset to setting using phone manager, and it fail
I try to boot in to recover mode, such as
clear data/factory reset
clear cache
go to advanced>wipr dalvic
Install cyanogenmod cm-10.1.3, cyanogenmod cm-10.1.2 or even cyanogenmod cm-10.1.1
I have try clear data/factory reset, clear cache, go to advanced>wipr dalvic
or any other combine setting i can think of.... it fail too
once i reboot my phone, it still went back to this Fix Setting, every thing just come back.....
even i select install new OS
Any ideas what happen?
Thanks
Look here for similar issue. Maybe move conversation there and see if together a solution is found.
http://forum.xda-developers.com/showthread.php?t=2859471
Sent from my Nexus 4 using XDA Premium HD app
Yes, it look simular to my issue, can you help PM me the step, so that will give it a try. Now i just been force to bought a new smart phone as my current not working.
Read about these issues from various thread, this is happened due to broken emmc. The only step will have to replace it.
If someone can developed a kernel to prevent this issue which is happen to omap4 device
Unfortunately most kernel, maybe all current kernel, did not apply this.
jak978 said:
Read about these issues from various thread, this is happened due to broken emmc. The only step will have to replace it.
If someone can developed a kernel to prevent this issue which is happen to omap4 device
Unfortunately most kernel, maybe all current kernel, did not apply this.
Click to expand...
Click to collapse
So this is due to broken emmc, and i need to ask someone to replace it at some cost
is there a way to check the issue is emmc or just some software/firmware/rom issue
Till now, my phone still stay the same, it will reboot after sometime. I even try to flash it with other ROMS and even update my phone with the latest CWM or PhilZ, i even get the message of update success/status ok. But after a reboot, my phone still went back/revert to that same "OLD" setting with every thing still there. Restore to factory still fail, look like my phone is as good as a brick phone...
Anyone know of a way to resolve it?
Hey guys. Before I get to my issue and seek your help , please allow me to give you a bit of background about my self wrt Android OS and nexus devices. I have been a Nexus device user since the N1 days. OS flashing , Custom rom's , kernel patching , etc are nothing new to me. I can safely say that I am a custom rom addict , hence I know the mods for my devices intricately well. With this out of the way , I'd like to share the sequence of events that took place yesterday , which lead to this new thread , wherein I desperately need some expert advice.
- I was running the latest Bigxie 5.0 rom for my 32gb N5. It had root and TWRP and elementalx kernel
- I wanted to upgrade to the 5.0.1 without losing any data , so I first tried to sideload the OTA zip file , which failed with some error. I then followed this guide (http://bit.ly/1wNT36l) . I was able to therefore flash the 5.0.1 without losing data. I re rooted my phone , re flashed the recovery and the kernel
- At the same time I was upgrading my LG g3 to Lollipop. I wanted to try the "Tap & Go" data transfer feature , so I used that process to transfer the data from my current N5 to the new G3. Here is when the issue started. The data transfer didn't go through , as only the email accounts transferred to the G3. At the same time , I got this notification on the Nexus that Tap and Go was used to transfer my email accounts , and this notification couldn't be cleared from the notification panel. For some odd reason , I decided to jump back into recovery and wipe cache and dalvik cache to get rid of this notification
- As soon as I did that specific wipe and restarted the phone , the phone would just loop at the nexus image boot screen. 15 minutes later I went back into recovery and decided to use the "factory reset wipe". That too didn't solve my problem. Frustrated at the turn of events , I reflashed Bigxie's 5.0 rom from my internal storage , via twrp.
- The phone finally booted! But now the problem was that my Sdcard was showing no files. It was all blank. I checked with root explorer / es explorer and even when I hooked up my phone to my pc , the sdcard was showing no files. I could , however , see all my files in the root -- data -- media -- 0 folder. I tried my best to extract all my files from there , but each time I got an error that pretty much meant that no files could be moved from there. Interestingly , when I went into twrp , and went into file manager in the advanced options , it showed all my files on the sdcard as though nothing went wrong. So I could see everything on the sdcard in recovery , but nothing if i booted into the OS.
- Since I had made a backup of most of my data prior to any this happening , with the exception of certain whatsapp data , and after having spent almost 5-6 hours in figuring out where I had possibly gone wrong , I decided to wipe my device clean and just install the stock OS and pack this device away for good
- I downloaded the stock factory image for 5.0 from the official site and went back into bootloader and fastboot flashed each and every file. The phone booted , BUT , now my phone showed only 12GB as the size of the storage with 11GB available. This frazzled me beyond words! How did I reach this stage wherein my internal storage was screwed to this level?
- I again went back into bootloader , flashed 5.0.1 , wiped the device and now the phone is again stuck in a bootloop on the nexus bootscreen
I have finally decided to send the device to the LG service center near my office , but I wanted to share this experience with the community hear and seek their guidance on where I possibly went wrong and what I can do now to put things back together to some degree of normality. Have I somehow damaged something at the hardware level that a change of motherboard may be warranted or is this a pure software screwup?
Thank you for your patience in reading this loooooong story , but I had to explain each and every step in perfect detail.
after flashing stock image.. there is no need to wipe anything... just boot it... takes around 5-10mins max but comes up.....
When it does 12GB on a 32GB device, you just have to factory reset using the option from inside the ROM.
Sent from my Nexus 5 with the N5X LRX22C ROM
tip, just because you know and read rom´s instructions and such, dosent mean you are an experiencied user.this 99% would have save you
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
opssemnik said:
tip, just because you know and read rom´s instructions and such, dosent mean you are an experiencied user.this 99% would have save you
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
Well said , and understood. I followed a different set of instructions and flashed back to stock and fixed my device. Thank you for your help.
ecksreturns said:
Well said , and understood. I followed a different set of instructions and flashed back to stock and fixed my device. Thank you for your help.
Click to expand...
Click to collapse
haha no problem, i thoguth i was an experienced user too, but then i bricked mine by flashing lg g2´s rpm partition to get a different partition layout. lol. glad you got your n5 back
Hello I'm sending this post now because I'm going to need somebody's assistance. A quick story I have been doing this for about 3 months as far as my first root to a flashaholic. I have successfully got around my bootloader. The problem is I'm not 100% sure how. I have a good idea of what I did but I don't know exactly as I am NOT a dev and I am new to this. I catch on rather quickly though and have found a passion for modifying my android and this site has been my number one contributor. My goal is to give back and help others out as well. I started off by editing permissions in my system file along with floating feature, csc, features and the customer XML. It was somewhere right in one of those files that I did this.. I simply changed the permission or function and immediately when I did I was prompted by super user to let boot animations by JRummy apps creator of the toolbox to allow permission which I did. The problem is as I didn't realize what I did at the time until I reset it as I changed about 10 different things. About a week prior I tried installing the boot animation into different file folders which was the two options that they suggest. Nothing happened of course my bootloader is locked and i wasn't surprised. Well I changed the permissions that shouldn't have in the calling feature section and I got stuck with force close force close so I hard reset into the factory recovery and trief to clear the cache partition which was unsuccessful. I then decided to install philz custom recovery so I could do a good clean out because obviously the factory recovery is garbage but every time I tried to change it it would stick me in a boot loop after being successfully flashed and in use for at least 24 hours. After I wiped the dalvik cache and the cache partition with Phils I then decided to try one last flash with a custom ROM and everything flashed fine. But once it rebooted I noticed a completely different boot animation and to my amazement it ended up booting and upgrading all my apps it started up normal. The rom I installed was real rwilco's mostly stock version 1.2 G900PVPU3BOG1. After that I decided I was going to take another chance and flash a few modification files. Once again succesfull. This morning I decided I was going to try to do a backup and restore. I backed it up with Phil's recovery and then I restored it. Restoring gave me a bit of a problem as I had to delete the cache and the dalvik cache. I then restarted the system the first time it didn't work or I didn't wait long enough I'm not sure. The second time I hard reset it introduced a normal boot and it started back up and was upgrading all 590 something after they have. Before I did any of this I was working away at a stock rom that I managed to modify a file in. This would be the aboot.mdn i believe. I was able to open it up into a notepad and replace it with the older version in the text part only so the file name itself stayed the same. I don't know if that played a major part to it or not. But I have sense flash recovery and files without getting stuck into a bootloop and with this new firmware almost every time I turned it off and on it would put me in a boot loop just because I was rooted. I attempted to simply change a new battery that I ordered powered off replace battery powered back on and was stuck in a boot loop. I have been making it my goal to somehow crack this thing. This is where I need help because I am still a noob I always just happened to poke in the right places I could care less about reaching 10 posts so I can post links if you like after I upload my information you can go ahead and reset that. I am here because I can seriously help and this website has been a major contributor to me becoming a flashaholic. I am at work right now and have already attempted but I'll go down to a 3G signal if that. I have absolutely no reliable internet here but within 5 hours I will be home uploading to my Google Drive a copy of my manifest and CSC, permissions, and features files. I have also created a clockwork recovery which I am going to upload as well I need somebody to help me go through these and pinpoint exactly what I did so we can get a legit thread with the fix. I somehow basically flashed a new boot animation which i think is blocking my other boot. I have confirm this working I have 2 screenshots I'm going to upload. Anybody with real experience and actually knows what they're doing I would appreciate your help in this matter.. And actually knows what they're doing I would appreciate your help in this matter. I just need to get home to my laptop to upload. Thanks xda you guys are awesome and I hope this is finally my opportunity to contribute and give back.
i ran out of time and couldnt proofread. sorry about that lol'
in my drive account i have a 1) factory rom that i modded aboot.mbn. 2) The backup "philz" cwm recovery. its my full backup apps and all down to the boot image that replaced the sprint yellow screen and the samgsung boot logo. 3) The system files that i have modified.. csc, features, floating feature, customer xml... 3) screenshots of rom info and adding others of some of the mods as we speak. still need 15 mins to finish uploading the sys files
if someone can figure out exactly what i did we have a fix. i have since flashed 30+ mods with no bootloop. email is [email protected] just incase for contact purposes
h t t p s: // drive. google. com / drive / folders / 0B5AfudcH1XDQMVFZdFhVTFdYQ0U---has many spaces only way to fit link
the system files have been diificult to et into my drive. most did not want to copy and the size themself. the full custom restore is in my drive already along with some screens. i have also set my boot animations to random and have about 20 or so cycling. also after restore make sure to wipe dalvick cache and cache. also some of the apps might fc i didnt have them fully restored when i created backup. i added a backup file in drive that has full copy.