So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
kevinzone said:
So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
Click to expand...
Click to collapse
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
efrant said:
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
Click to expand...
Click to collapse
will this make my files be deleted? I would rather not have that happen please
kevinzone said:
will this make my files be deleted? I would rather not have that happen please
Click to expand...
Click to collapse
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
efrant said:
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
Click to expand...
Click to collapse
Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused.
If this is the ONLY way , then can you please tell me how to do this, i'm confused.
If there is another way on to get out of this boot logo aokp thingy, without losing data , please tell me.
Note: i dont know if i'm doing anything, but i backed up via the recovery CWM
then after i deleted cache and dalvik, then flashed aokp,franco and then g apps. And nothing happened
Bump please. i really don't want to wipe my phone
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Prod1702 said:
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Click to expand...
Click to collapse
Uhh i reflashed aokp, kernel and gapps. Nothing really. Two questions.
1. Anything else?
2. for the reflashing, i want to flash another rom, how do i put the files on the phone? Gnex doesn't have an sd card slot and i dont know how to access it on the computer if it is in recovery mode. So confused
EDIT: not entirely sure what flashing means, so what i meant by flashing in my case, was that i just re ran the zips. then reboot. Nothing . waited 5-10 minutes ish. Never had long bootups on my first try.
Bump please!
kevinzone said:
Bump please!
Click to expand...
Click to collapse
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
efrant said:
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
Click to expand...
Click to collapse
But there is a problem. I cant access the phone. Since it won't boot up i can't access it from the computer.. Or can i? There's no sdcard slot either
Related
OK, here it goes.
I have a R800x CDMA Verizon Xperia Play
I had bootloader unlocked successfully by alejandrissimo.
I am rooted.
Today I decided to try the MIUI rom for CDMA.
It required custom kernel, and recommended Kieren's darkforest kernel.
I installed that kernel via fastboot with no problems.
Upon turning on phone, i get a page that says Sony, then I get ANDROID page.
Then it just stays on ANDROID. I can tell that it is not frozen because I can see the waving lines going across.
SO, I decided to just go back to stock kernel then try again.
BUT, I cannot get into fastboot!!
I hold search while connecting usb, and the led blinks blue once, then continues with boot.
I am at a loss.
I Can get into CWM.
Please Help!
Edit: I just noticed that after holding search then plugging in USB, the light blinks blue once. Then about 25 seconds later, the light turns solid blue for about 3 seconds. Then just to orange for charging. During this time, I can not get fastboot to recognize device, nor does my computer recognize any devices.
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
netizenmt said:
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
Click to expand...
Click to collapse
ok, small problem with that.
when I click to install flashtool, it tells me that it is not available for my region (Central USA).
I do have a nandroid and titanium backups made just before flashing.
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
still stuck
netizenmt said:
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
Click to expand...
Click to collapse
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
zeeky120 said:
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
Click to expand...
Click to collapse
Yeah, that seems to be the wrong boot.img. It should be called boot-v2.img.
EDIT: WOW - I just reread your post after posting mine and realized I pointed you to the same spot!
Try this ROM which is a version of CM9 that Chevyowner got working for our R800x. I know it works because I'm using it. http://www.mediafire.com/?1xnh54i6lvnnh73
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
zeeky120 said:
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
Click to expand...
Click to collapse
just an fyi, you can name kernels whatever you feel like (I'm not sure about spaces, I use linux, so I never have spaces in names anyways )
Sent from my R800x using Tapatalk
Flashing now
OK, I just downloaded and flashed the ROM about 3 minutes ago.
I cleared everything just like you told me to.
It installed with no errors.
You may be right about long boot times for first boot, otherwise I have a really bad kernel.
It has just sat on Sony screen for the past 10 minutes.
It hasn't even went on to the android page that I got before.
Hoping that it will Work.
Assuming that it doesn't, what would be my best next move?
Can I flash a kernel (Such as doom_lord's CDMA Kernel) via clockwork?
I think I saw a video about it for the Samsung fascinate, however I seem to recall something about needing an s2 file or something??
I will update as soon as I get something. (hopefully good news)
Update: It has been about 20 minutes now and still on Sony screen.
Now it has been 30, im starting to get worried. Should I plug in? Should I just let it be? Should I let it die? Should I battery pull?
Major Edit: I got impatient and just battery pulled. I then tried to get into CWM, but failed. THen I got a bright Idea, why not try fastboot with the new rom. IT WORKED. I WILL NOW TRY TO FLASH A NEW KERNEL AND SEE IF THAT HELPS.
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
chevyowner said:
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
Click to expand...
Click to collapse
is this your kernel, or someone else's? If it's yours/you have a working copy, could you post an md5 so the op can double check it?
Sent from my R800x using Tapatalk
nope not my kernel, and i doubt i have an original working copy as i added 2 lines so i could mount my sdext partition.
Finally!
OK, I am now back up and running.
I went through every kernel and rom for CDMA play, and got nowhere.
I ended up getting Doom's kernel to run. It worked, and booted to android... Then stayed at android.
Then I decided to flash my nandroid i made, and am now working on stock rom W/ DoomKernel.
The ROM seems to be lagging a lot.
Since everything is *working* now, what kernel/ROM combo can anyone verify working for the Play R800x CDMA.
I would really like CM9 or ICS based roms.
Thanks for your help getting me out of this mess!!
EDIT: Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
If you're using keiran (darkforest) cm9 kernel the md5sum for it should be: 74a5be2bf95322b8c45780d9daeda4fa
Sent from my R800x using Tapatalk
zeeky120 said:
Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
Click to expand...
Click to collapse
This site has some of the stock FTFs, just extract the kernel.sin from the R800x one http://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html
kernel.sin: http://www.mediafire.com/?e29j13d9wpgdvoj
md5sum: 45116201967408d70895ef63c500ed1e
@zeeky120 - I'm sorry you're having so many problems. For me when everything seemed hosed, I started over by using Flashtool and flashing the ftf file I gave you links for. Then once it came back up as stock, I started again from scratch. Depending on what your goals are, you need to flash the proper kernel for that. Then get into CWM. Clear DATA, CACHE, DALVIK CACHE before you do anything else. Then load via zip file the rom you want to install, making sure it matches the kernel you loaded. And, whether necessary or not, I always wipe the big 3 again, just in case. (Call me paranoid, but it helps! )
Ok now up and running on stock everything working great just like out of box. The only thing I have done so far is to root. I want to do it right this time. I would like to flash cm9 based miui for r 800x. Could anyone provide detailed step by step instructions and links for download. Thanks in advance.
Sent from my R800x using xda premium
Closing Notes
This thread has reached its end, because my problem has been fully solved. Advice to future users, always clear the big three, and when in doubt: use flashtool to reboot the ftf. Right now I am up and running on CM9 (use the link in Chevy's signature to download. I can verify that it works great on CDMA. (faster download speeds than stock!!!) Thanks for everyone for all of their help, and I hope to be contributing to development in the near future.
I've practically tried everything, I posted in the thread for the Team Vicious ROM about this problem, a received many responses. But so far all the proposed ideas to fix this problem have come to no success. I am left with the Google X boot animation every time I tried flashing.
I'm curious what would be the best plan of action for getting to Jelly Bean successfully?
Status of GN:
verizon ROM 4.0.4 stock (unlocked and rooted)
What I'm flashing?
Team Vicious 4.1 Jellybean ROM v3 + faux kernel
My process of flashing:
factory reset in stock ROM
superwipe, or do a format to (/dalvik-cache, /cache, /data, /system)
flash jb ROM
wipe cache again (sanity check)
umount /system and /data
reboot
wait up to an hour at least 15 minutes
The Result:
Google boot animation (X)
Frustrated user
restore nandroid backup
try again
unknownzero said:
I've practically tried everything, I posted in the thread for the Team Vicious ROM about this problem, a received many responses. But so far all the proposed ideas to fix this problem have come to no success. I am left with the Google X boot animation every time I tried flashing.
I'm curious what would be the best plan of action for getting to Jelly Bean successfully?
[note: I'm kind of new here, hope I posted in the right place]
Click to expand...
Click to collapse
Well what process have you been using?
What's the current stat on your phone? What ROM?
And as far as I know... your in the right place :cyclops:
Well...
I'm going to assume that you've waited a good 10-15 minutes during the first boot after installation? I haven't experienced it but I've read that pulling on first boot before getting to the opening screen may cause the phone to not boot fully. Again, I haven't experienced this, but FWIW.
Next I guess I would validate that you're not doing a dirty install (installing directly over a ROM without wiping). I've had good success using the 'super wipe' script prior to loading up a new ROM.
If you haven't gone through all of the dev forums I'd suggest at least starting here: http://thesuperusersguide.weebly.com/everything-jelly-bean.html
You'll find quite a bit of relatively up to date material for getting started.
Hopefully this helps, but what I would suggest is trying super wipe, then loading up your ROM. On first boot - walk away. Don't come back for 20 minutes. If it still hasn't booted at that point maybe try reverting back to 4.0.x, making sure your phone is working and then start over step by step.
I saw this morning that there is a one-click restoration script out there now, check this out for more info:
http://forum.xda-developers.com/showthread.php?t=1743939
Good luck!
Wolfbeef123 said:
Well what process have you been using?
What's the current stat on your phone? What ROM?
And as far as I know... your in the right place :cyclops:
Click to expand...
Click to collapse
The current state of my phone is restored to 4.0.4 stock, as always unlocked and rooted. The one I'm attempting to flash is the Team Vicious v3, I have already tried v1 and v2.
The processes I've been using are a combination of following directions, then trying to the superwipe, and some other scripts. Wiping /system /cache /dalvik-cache / data, then flashing, then wiping the aforementioned and flashing again. I've practically done almost every combination possible with no success.
windexh8er said:
Well...
I'm going to assume that you've waited a good 10-15 minutes during the first boot after installation? I haven't experienced it but I've read that pulling on first boot before getting to the opening screen may cause the phone to not boot fully. Again, I haven't experienced this, but FWIW.
Next I guess I would validate that you're not doing a dirty install (installing directly over a ROM without wiping). I've had good success using the 'super wipe' script prior to loading up a new ROM.
If you haven't gone through all of the dev forums I'd suggest at least starting here: http://thesuperusersguide.weebly.com/everything-jelly-bean.html
You'll find quite a bit of relatively up to date material for getting started.
Hopefully this helps, but what I would suggest is trying super wipe, then loading up your ROM. On first boot - walk away. Don't come back for 20 minutes. If it still hasn't booted at that point maybe try reverting back to 4.0.x, making sure your phone is working and then start over step by step.
I saw this morning that there is a one-click restoration script out there now, check this out for more info:
http://forum.xda-developers.com/showthread.php?t=1743939
Good luck!
Click to expand...
Click to collapse
I wait usually 20-30 minutes, but I notice that the device heat is not fluxuating ( to me that indicated very low usage) I have reverted to 4.0.4 stock after each attempt from a nandroid backup.
I have also md5 verified all the files against the ones listed one the page, in the case you wonder about dirty data. I'm tempted to try the superwipe, flash, factory reset, then flash, wait an hour. I don't do dirty installs also, I might be a little new here but I know not to do that. What else is there?
Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA
Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?
There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
danny_dv8 said:
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
Click to expand...
Click to collapse
What version of TWRP are you using? I heard 2.6 may have some issues?? Also, did you do proper wiping procedures, such as factory reset, cache wipe, dalvik cache wipe, etc before modding a new ROM? Which new ROM are you flashing, and did you flash a new radio with it?
danny_dv8 said:
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
Click to expand...
Click to collapse
First, what is it flashing procedure? I should be downloading rom to ur external/internal SD card, then boot to recovery and make a backup of data, boot, and system partitions, then wipe dalvik cache, system, data, and cache 3x each, then go back to main menu and choose install, find the rom and flash it, if aosp also flash gapps, then reboot, shouldn't be having any issues if u follow that procedure, and upon first reboot let the phone sit for around ten min or so to let everything settle, the first few days or so things will still be settling in so give it 3 full battery cycles before u start guaging performance, I'm on twrp 2.6 and never had an issue yet an I'm a flash addict, u could also try reverting to stock with Odin and then starting over, Odin give a more complete system wipe so u may have some corrupt files somewhere, but like I said if u follow that procedure u should be ok
Sent from my SGH-T989 using xda premium