Related
I have transformer tf101 (Honeycomb 3.2.1 + 16GB + Dock) that I purchased in August 2011. For first 6 months I was on stock ROM and everything was working fine. After that I flashed Android Revolution HD 2.2.0 on my tablet and then it started behaving crazily . Whenever I open browser it will automatically start zooming in/out, scrolling. It will totally go haywire and will start clicking left/right.
I searched on net and found that some of other unlucky guys are facing the same issue . I have attached a .txt file that contains the link to you tube video depicting the problem.
I have tried many ways such as using superwipe script and then reinstalling the ROM's. Even, I have tried with new ROMS(ICS one's) that are there but still the problem does not seem to go away. I have searched a lot but could not find the solution to this issue. Can somebody please guide me how to get rid of this problem. I believe this is the best android forum where I am hoping that someone will help me with this problem.
This is really basic but have you tried cleaning the screen?
Other then that, have you tried going back to a HC rom and see if you don't have any issues. I understand you want the latest and greatest version rom but to determine a fix and narrow down the problem maybe you should try all the alternatives.
Thanks for replying. I had cleaned up my screen and there was not a single app/widget on my homescreens. I flashed back to HC ROM but still the problem persist . I have tried all ways of flashing th ROM's but still the problem doesn't seem to go away. I have not tried the stock ROM for HC that came with my tablet (i didn't take the backup when I flashed new ROM).
Looking at the issue it seems to me as if this problem is software related rather than the hardware.If this would have been hardware related then I should have got this on day1 of my purchase.
stryke504 said:
This is really basic but have you tried cleaning the screen?
Click to expand...
Click to collapse
I think he meant literally "clean the screen." Like with a towel and some cleaner.
typci said:
I think he meant literally "clean the screen." Like with a towel and some cleaner.
Click to expand...
Click to collapse
And dont forget to wash your hands (Im serious, that actually affects the responsiveness of the screen)
I cleaned my screen (Literally ). The problem is still there . Can it be because of the browser. I am currently using Dolphin HD browser for my browsing. I will probably install stock browser and will check with it.
Your text file is rubbish too...no link, it's actually the HTML code for an error 404..which is funny.......not only is it not a working link, or even a link at all, it's a 404 in HTML..LMAO
Sorry for the bad attachment. I have the link.doc containing the link.
Yesterday, I tried with the stock ROM and everything was working fine till the point I connected my tablet to Wifi and upgraded my Google Market to Play store. As soon as the app was updated the same problem started recurring. Now I have uninstalled the updates for google play store but the problem is still there. But the good part is that the frequency of the random zooming/clicking has decreased and it happens in browser only. Earlier it was happening in all the apps. Can somebody please direct me to the link to US stock ROM (for HC 3.2.1). As of now I am running WW_ stock rom. I just want to try out the same with US_ stock ROM as well.
First of all, don't use super wipe script. Just wipe normally with CWM.
Do these options in CWM
1. factory reset/wipe data
2. clear cache partition
3. wipe dalvik cache
4. mounts and storage -> format /system
5. mounts and storage -> format /data (this is done by factory reset but just to be sure)
Get the official ICS rom from Asus' website. US or WW doesn't matter.
Flash it with CWM after doing the wipe procedure above.
Don't let google sync or anything restore any kind of back up.
If the same problem happens again, you got a problem that requires RMA.
Honestly it already sounds like you need to RMA but you should make sure before wasting money and time on RMA.
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
I have a big problem with RMA. I purchased my tablet in US and so it has North American Warranty. I am not residing in US. Thus for RMA, I have to ship my tablet back to US which will be expensive as well as an overhead . So I am planning of trying all the possible steps before I have to ask the Asus support in my native country. Please let me know if you know any stable version of Stock ROM. I read and found that some of the stock ROM's are having serious issues with Wifi/GPS etc.
harshbedi said:
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
Click to expand...
Click to collapse
Something could have gone bad during flashing.
What version of CWM are u using?
---------- Post added at 07:55 AM ---------- Previous post was at 07:51 AM ----------
harshbedi said:
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
Click to expand...
Click to collapse
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
harshbedi said:
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
Click to expand...
Click to collapse
i would first get on the newest version of recovery:
http://forum.xda-developers.com/showthread.php?p=16557195
it is touch based, but i just went into cwm and the regular method of volume and power keys work fine. AND you have to store the rom on the internal sd card in order to flash, it can't access the external card once you update.
and personally i'd wipe EVERYTHING like 3 times seems kinda of the standard.. i'm super ocd so i wipe it all 5 times before i flash.. might want to pick up an ASOP rom like
EOS:
http://forum.xda-developers.com/showthread.php?t=1520764
or KANG:
http://forum.xda-developers.com/showthread.php?t=1542302
see how that works.. could always pick up the stock ASUS rom though
FYI: to flash those new EOS and KANG roms you NEED to be on that version of cwm i linked
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
harshbedi said:
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
Click to expand...
Click to collapse
All this could have been caused by you never wiping cache and dalvik cache.
Yea, download the ICS firmware from Asus website. It will be in a zip. You extract it once. It will have another zip. That's the flashable zip.
You flash it in CWM like you would do for any other ROM.
Yes, I never wiped cache and dalvik cache.
I will check this today and will post my observations. I am keeping my fingers crossed and hoping that this should solve the problem.
Thanks for the info.
Thanks horndroid for the lovely info...It worked.
I cleared the cache and dalvik cache and then I flashed the new revolution 3.2.0 (ICS) Rom and as of no complaints. I have been using the tablet continuously for last 3-4 hours and no issues as of now. I am hoping that it continues to work the way it is functioning right now. I am loving my transformer again . I will use it for few more hours and will update my observations. I am still keeping my fingers crossed.
Moreover, Revolution 3.2.0 is awesome(Thanks to Mike and his team). Very stable and the GPS is awesome. Sitting in my room it acquired my position(No Wifi) within seconds.
horndroid said:
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
Click to expand...
Click to collapse
Yes. This is worth pointing out again and again.
Most roms (in my experience) wont even boot unless you wipe cache and dalvik.
And the roms that do boot runs like ****.
Now I have used my tablet for 16 hours..No issues..Running perfectly fine. I believe wiping cache has solved the issue.
I was reading about dalvik cache and came to know that during boot Android always create this cache (if it is not there). So if this problem comes again, can I wipe the cache and dalvik cache without flashing a new ROM. Is this advisable?
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
kailehu said:
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
Click to expand...
Click to collapse
o-l-a-v said:
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.*An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine*(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
I'm sorry to hear that but I'm also glad it's not just me, and wouldn't be a huge stretch to call me a newb.
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
Click to expand...
Click to collapse
Unfortunately, I've tried both recoveries already. I've gone through each step every time and I've never done it that specific order consciously, but I feel like I must have just by chance in all the times I've tried this. I'll try again though exactly like you listed and see what happens. Thanks.
No dice. I'd like to give more info than that but I don't know what else to try.
I recently tried to root my Galaxy Blaze under ICS 4.0.4. I downloaded files from a thread that explained step by step how to do from k0nane. When I ran Odin it said PASS. Now the only thing the phone does is vibrate, Samsung screen comes up, and the stays loading in the Tmobile screen. What do I need to do? Please help.
centenj said:
I recently tried to root my Galaxy Blaze under ICS 4.0.4. I downloaded files from a thread that explained step by step how to do from k0nane. When I ran Odin it said PASS. Now the only thing the phone does is vibrate, Samsung screen comes up, and the stays loading in the Tmobile screen. What do I need to do? Please help.
Click to expand...
Click to collapse
You need to read.. All you need to do is go to the ROM BIBLE Thread and read on how to root your phone..
http://forum.xda-developers.com/showthread.php?t=1574556
What!
Thanks for the reply. Im not good at this stuff or know codes lol. What do you mean by ROM BIBLE.
Well I got it working finally. The only thing IM trying to get working is to go around TMo mobile tethering. I downloaded barnacle and can't get it to work.
Sent from my SGH-T769 using xda app-developers app
Are you on ICS? If you have titanium backup go into it and look for tetherprovision and freeze it. Gets around T-Mobile tethering restriction.
Sent from my SGH-T769 using xda premium
Done!
Im done, running CM10 and 4.1.2.
Weird!
As a couple of days pass I noticed my phone turning off a couple of times a day. Could it be that I have the wrong kernel. I never changed the kernel after installing the new ROM.
centenj said:
As a couple of days pass I noticed my phone turning off a couple of times a day. Could it be that I have the wrong kernel. I never changed the kernel after installing the new ROM.
Click to expand...
Click to collapse
Its a bug in CM10
Sent from my CM10 Blaze
im_awesome_right? said:
Its a bug in CM10
Sent from my CM10 Blaze
Click to expand...
Click to collapse
I haven't had a random reboot since Dec.lol you guys need to perform full cleans when flashing.
What Happened
As a couple of months enjoying the advantages of CM10, this morning I receive a call and the stayed vibrating. I shut it off and the phone would not turn back on. I booted in CWM and wiped my cache and davlik, also did a factory reset and the phone did the same thing. The only thing it does is show the Samsung sign and thats it. Someone help please.
centenj said:
As a couple of months enjoying the advantages of CM10, this morning I receive a call and the stayed vibrating. I shut it off and the phone would not turn back on. I booted in CWM and wiped my cache and davlik, also did a factory reset and the phone did the same thing. The only thing it does is show the Samsung sign and thats it. Someone help please.
Click to expand...
Click to collapse
Wipe everything again including system in mounts and re flash ur rom and gapps and it should fix ur problem
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
johnb380 said:
Wipe everything again including system in mounts and re flash ur rom and gapps and it should fix ur problem
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
Click to expand...
Click to collapse
Do you mean in the mounts and storage screen in CWM, format the system?
how long did you wait after rebooting?? It will take up to 5 minutes or more to rebuild the cache
centenj said:
Do you mean in the mounts and storage screen in CWM, format the system?
Click to expand...
Click to collapse
Yes. Wipe that (system), cache, davlik cache, and factory reset. Wipe each of them atleast 2 times, since your having issues. Then flash ROM, then gapps, reboot and wait 10 minutes, then reboot and complete the start up.
centenj said:
Do you mean in the mounts and storage screen in CWM, format the system?
Click to expand...
Click to collapse
Yes sir make sure to wipe that too and what I do after flashing a rom is wipe cache and dalvik again then flash gapps and kernel (if needed) then reboot
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
Got It
Thanks alot guys got it back running.
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?
Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.
Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.
jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?
All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app
Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1
I am Having the same prob with galaxy tab2 7.0(gt-p3100)
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.
alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk