I recently bought a nexus s and once rooted the keyboard dissapered. It was fine until i flashed a rom unsuccessfuly, then turned the phone off. Once turned back on the keyboard was no more. If anyone could help me find a zip. to flash or a way to put a new keyboard on the phone I would appreciate it. the phone is basicly useless without the keyboard now, ive tried recoving to factory condition, flashing from an earlier point, and so forth. Please help!!!
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
jojoost said:
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Billchen0014 said:
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
Click to expand...
Click to collapse
Dictionary http://db.tt/3echUtSP and IME: http://db.tt/EUAXXcsR
re: i flashed gapps
Sent from my Nexus S using Tapatalk 2[/QUOTE]
I flashed a gapps zip from the site you linked me to and now when the phone turns on it says setup wizard is not responding and give me the option to force close. Nothing happens from that point its just stuck in a force close loop. I hope to god i didnt brick this thing. Is there a way to fix this problem? I didnt backup before flashing gapps and ive tried to restore the phone and wipe it clean but no luck. Any help would be greatly appriciated because i just got the phone, mainly to use it as a fun project seeing as smartphone customization has become my new hobby, and Im usually very good at it but now I am just afraid ive bricked the phone and I bought it unlocked so i paid a fair amount of money for i. Please help if there is a solution. Thank You,
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Thank you
Oogway13 said:
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Click to expand...
Click to collapse
Thank you very much, I followed and executed your instructions and now im running ice cream sandwich 4.0.4. not bad from going from almost a bricked phone to running one of the best versions of android. I downloaded offical roms this time instead of custom ones, first a version 2.3.4 and a 4.0.3, flashed the ics rom first and worked like a charm. Thank you very much, even got an update 5 min after i flashed the rom. You saved me 200$ and the embaracement of having a worthless phone. Im sure ill have more questions in the future, so glad there are ppl out there with the same passion for smartphone customization that i have. Much obliged. Omar
Related
Hey guys,
This is my very first post, just to let you all know, so please have some patience! Thanks!
Anyway, so I have a Nexus S 3G (Canada) and I have rooted it, unrooted it, installed roms and everything. I works...for the most part. It's giving me all sorts of different little errors and what not. So I was wondering, how can I COMPLETLY start ALL OVER, as in, factory new, like when you buy a new phone (without the carrier stuff). I wanted to start fresh, fresh out-of-the-oven kind of start, do you understand what I mean? FACTORY FRESH. Thank you all so much in advance!
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
[email protected] said:
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
Click to expand...
Click to collapse
Thanks for the reply, I've already done that, and I'm still getting errors and other weird things, like not going out of airplane mode, failing to download the OTA 2.3.6 Update (I'm on stock 2.3.1 unrooted, I think), and I don't know if this is normal, but ClockworkMod Recovery is still there. Am I still rooted or something? Plus, when I try to flash a restore, from let's say Gingerbread 2.3.6 Stock, it says MD5 mismatch! How about if it's an ICS AOSP Build, it gives me the normal white Google logo like normal, but then just stays stuck there.
Is the anyway to erase EVERYTHING and start over like NOTHING was ever done to the device? Like when they are first distributing the the device and no one has ever touched it? Is there anyway to do just that?
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
lodxcol said:
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thanks for your excellent reply, but I have also already done that, EXACTLY that, multiple times too. Dalvik, battery stats, factory reset/delete all user data, wipe cache partition and fix permissions. What else is there left to do?
Thank you all so very much!!!!
I have fixed my Nexus S!!!
HeroKhar said:
I have fixed my Nexus S!!!
Click to expand...
Click to collapse
how did you fix it?
lodxcol said:
how did you fix it?
Click to expand...
Click to collapse
I reinstalled the newest update with the vanilla recovery
Sent from my Xoom using XDA Premium HD app
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?
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.
what are you doing before flash the new rom?
juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app
Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.
Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.
So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(
I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.
Hi all, I've been rooting and installing custom roms on lots of devices for a couple of years now. I didn't consider myself a noob after successfully getting cyanogen 9 or 10 on tenderloin and cm10.2 on tate.
However, it seems that I have completely missed something while installing EOS4 20130705-199 on the Motorola Xoom.
I had no problems with SDK install, adb, fastboot, got TWRP running w/ root. All this is from stock, mind you, if that makes any difference.
So then I decided to grab teamEOS's EOS4 and run that as the newest Android OS (that is arguably stable) that has been ported to the Xoom.
Well, I think I must have rebooted at a point that I wasn't supposed to, because I lost the ability to load the EOS-stingray-20130705-199.zip via ADB.
So I went into TWRP recovery and attempted to ADB sideload the rom file. Seemed to work for transferring, but after wiping caches and rebooting, I'm stuck on MOTO dual-core logo. I can get back into TWRP, though so I tried doing factory reset, wiping caches, and installing from an 8GB microSD card (/sdcard). Wiped caches again and then reboot... Same result, MOTO dual-core logo.
Ok, so now to barebones... Boot into fastboot mode and flash boot.img from EOS-stingray-20130705-199.zip and then boot back into TWRP and install rom again.... Same result, MOTO dual-core logo.
As you can probably guess at this point I'm getting a bit frustrated. I'm about ready to see how a Xoom flies when launched from a skeet clay launcher. Pull!..... BLAM! Just kidding, but I really do need to get this device back running.
Does anybody have any suggestions?
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
airesch said:
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
Click to expand...
Click to collapse
Thanks for the reply. I shall give -197 a try.
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset). The advice alone is worth it's weight in gold.
Bad news.
I just downloaded -197 fresh from goo, in fact I did it twice because I couldn't believe the results.
It actually fails to install giving the error "cannot open zip file" -199 never did that.
I also tried -131 (cdma) just to prove to myself that I have the right model. Same results, MOTO logo no boot.
Can't actually believe i am saying this, looks like goo's version is corrupt (my md5 doesn't match theirs and I just looked up the cached version of the webpage and it has d81cded40671c9c0963f95273859dbdd (which is what mine is.)
I will try to pm you a link of the file I have on my dropbox in a bit.
Thanks for this AIRESCH
Your version of -197 is working perfectly.
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Thanks again.
punishermoose said:
Thanks for this AIRESCH
Your version of -197 is working perfectly.
Click to expand...
Click to collapse
Excellent
punishermoose said:
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Click to expand...
Click to collapse
Not sure this is necessary, goo has been replacing/upgrading hardware and may not have everything up yet (none of the files were there for a good week at the start of the month.) They may get the right files back up before too long. It does suck for anyone trying to get the files right now tho.
I'm glad your up and working.
Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.)
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset).
Click to expand...
Click to collapse
ah, but you don't learn if it's not explained
Reason is: the Xoom only has a 256MB system partition and unfortunately the OS+Gapps (which normally resides in system) as of 4.1 or 4.2 comes to well over this amount. The rom developers HAVE been (they are currently trying to change this) making it so that some of Gapps gets enough copied into the data partition to make everything fit and symlink the files back into system. This has the positive effect of being able to have everything work even without enough space. However the downside is that if you factory reset it will wipe out the files in the data partition, leaving broken symlinks pointing to nothing, and makes it so some of it doesn't work anymore (how much depends on what gapps your using.)
In short: We have awesome devs that are still trying to fix the problem, but their current solution requires you to re-flash gapps (at a minimum, i normally recommend re-flashing both system and gapps) after a factory reset (which is not the end of the world (unless you don't have them both anymore.))
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
SgtTeabag said:
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. Need a good download/copy of 197, please! The goo.im 197 download is borked!!
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