I have read the entire forum on this ROM and haven't been able to find any info on my issue....
My network still shows HSDPA
My network coverage (icon) flips between H+, 3g & E...with no coverage at all sometimes.
I've received a couple calls where only a couple numbers show up in the caller id? Once it just showed the number 6 and another time just 107?
It's also been freezing up and have to reboot...the back button won't work.
Thanks in advance for everyone's help...I'm new to this
Have you tried reflashing the ROM? Make sure you do a full wipe, dalvik.. etc... before flashing the ROM.
I know I wiped everything the first time around. I've thought about doing that...I guess that may be the end result. thanks
jimiyarb said:
I know I wiped everything the first time around. I've thought about doing that...I guess that may be the end result. thanks
Click to expand...
Click to collapse
Do you flash it from rom manager?
The thing is, even though that's the dev's preferred way of doing it, and the way I did it, I've since come to learn from a post by Mudknot2005 in his guide that's stickied to this section, that rom manager has a bug where even though you choose to wipe, it doesn't actually wipe.
This is the first I'd heard of it, and I don't have additional info yet, but it's kind of left a question mark in my head about the integrity of my flash, via the suggested rom manager route.
Maybe someone with more insight will visit this thread and shed some light on this.
Inspired Ace 1.0.1¦ XDA Premium
I did flash from ROM manager...It makes me a little less nervous to do it that way! I did read somewhere that you may need to flash back to an older version of ROM manager to avoid some of the bug possibilities. But like I said, I'm new to this and it can be a bit intimidating to a beginner. I def hope some more experienced members can get on here and help us out. Thanks Scott!
Scott_S said:
Do you flash it from rom manager?
The thing is, even though that's the dev's preferred way of doing it, and the way I did it, I've since come to learn from a post by Mudknot2005 in his guide that's stickied to this section, that rom manager has a bug where even though you choose to wipe, it doesn't actually wipe.
This is the first I'd heard of it, and I don't have additional info yet, but it's kind of left a question mark in my head about the integrity of my flash, via the suggested rom manager route.
Maybe someone with more insight will visit this thread and shed some light on this.
Inspired Ace 1.0.1¦ XDA Premium
Click to expand...
Click to collapse
I try to avoid Flashing from ROM Manager, it just seems to be (for me anyway) cleaner to boot into recovery and flash from there that way i know for sure that Dalvik and cache got wiped and if required i know that a full wipe has actually been done.
For me the method listed below works best
1. boot into recovery
2. choose advanced and the wipe dalvik cache
3. choose go back and then do a factory reset delete data
4. optionally go into the mounts and storage menu
5. format system and format data and format cache
6 flash ROM of choice.
cstayton said:
I try to avoid Flashing from ROM Manager, it just seems to be (for me anyway) cleaner to boot into recovery and flash from there that way i know for sure that Dalvik and cache got wiped and if required i know that a full wipe has actually been done.
For me the method listed below works best
1. boot into recovery
2. choose advanced and the wipe dalvik cache
3. choose go back and then do a factory reset delete data
4. optionally go into the mounts and storage menu
5. format system and format data and format cache
6 flash ROM of choice.
Click to expand...
Click to collapse
Thanks for this. It always helps to have concise steps, and I for one am still a bit intimidated by cwr.
Inspired Ace 1.0.1¦ XDA Premium
Yes...many thanks!
Sent from my Inspire 4G using XDA App
Related
Sorry if this isn't the right forum ahead of time
I just loaded Android Revolution 5.1.9 on my Inspire, I keep getting errors from Rom Manager, Twitter, Facebook, and it force closes everytime it tries to load. I've tried updating to no avail. Help would be great because I'm tired of seeing these FC messages
Try flashing the ROM again and clearing everything....factory reset and wipe dalvik-cache
Sent from my Desire HD using XDA Premium App
what would be the best method of flashing a new rom, since isn't rom manager the way to do it? (I'm really new on the rooting scheme since I migrated from the iPhone)
That was probably your problem, as it's a known bug that wipes don't work when initiated from ROM Manager. Put the ROM's zip file on your SD Card. reboot into recovery. Choose factory reset. Then choose advanced>wipe Dalvik cache.
After that, choose 'install zip from sd card'. Just navigate to your zip and select it.
kiesan88 said:
what would be the best method of flashing a new rom, since isn't rom manager the way to do it? (I'm really new on the rooting scheme since I migrated from the iPhone)
Click to expand...
Click to collapse
Check the stickied guide in this general section, by mudknot2005, it has an excellent step-by-step, with pictures even, of the "non ROM manager" way of flashing roms.
http://forum.xda-developers.com/showthread.php?t=1033353
It doesn't look like that link is linking, or something. I'm using XDA app, so links are a PITA.
You'll find it.
Thanks guys. Will try to get into recovery. I think when I tried switching roms from Core Droid, it went straight into bootloader, and didn't let me choose to go into recovery
edit: still having the issue of not being able to go into recovery. It loads the first screen, won't let me select anything, then goes into fastboot
Found a work around, taking out the SD card, then going into recovery. Works great so far. Did the cache clearing also.
Thank you for reporting the fix! Getting ready to pull the trigger here. Lurked n read n lurked n read ...gotta evidently update net.framework ... anyway you did good. Stuck with it and then reported the work around. I try to operate that way.
Sent from my Desire HD using XDA App
Running Android Revolution is nice....except that it freezes constantly on me. Bout to dump this rom and move onto the next
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
ant_wailes said:
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
Click to expand...
Click to collapse
You or anyone wouldn't happen to know off hand if the kernel is UVed or OCed? This sounds like a UV or OC problem. Its an easy thing to fix if it is and I find that's is always best to rule out the easy stuff first! Some phones don't like to be UVed or OCed at all and freezes like this sometimes are caused by exactly that, UV or OC.
edit: and oh yeah, WELCOME! If you really like CM ROMs, give absolution a try (at the very least, if you or someone doesn't know if the kernel is UVed or OCed, you're be using a ROM I'm familiar with and if the problem persists on this ROM, diagnosing the a UV or OC problem should be fairly simple and I'll know how to get that fixed quickly for you since I haven't used the straight CM ROM in quite some time!) Actually come to think of it, did you check the md5 number? you could have downloaded a bad link causing a bad flash. It's rare most of the time but I have seen it happen..
If you havent downloaded any apps and dont mind reflashing the ROM just down load the full wipe place in ROOT (No Folder) of SD Card go into recovery.
Full Wipe (DO NOT RENAME AFTER DOWNLOAD)
http://www.megaupload.com/?d=CJPE5CB7
1. Choose zip from SD Card (Full Wipe 1.5) and Install
2. Choose zip from SD Card (Cyanogen ROM) and install
3. Reboot system and enjoy.
I dont like to do the wipe cache, wipe dalvik whatever method, the zip 1.5 does a full wipe all on its own. Its an EXT4 Wipe so I use it for all EXT4 ROMS that I like to try out.
!!!WARNING: When you flash the full wipe do not exit recovery without installing your ROM. So make sure that when you enter into recovery thru Rom Manager to reflash make sure that you have both (Full Wipe Zip) and (Your ROM Zip) on your SD Card before installing.
I tried cyanogen and completed hated it. Absolution is the Bomb!!! But to each their own flavor.
ENJOY
@reponse
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
ant_wailes said:
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
Click to expand...
Click to collapse
Not a problem man! Be aware though with the 1.5 wipe that it DOES format your system and data to EXT4, and if I'm not mistaken if you make a back-up on EXT 4 and then format back to EXT 3, it will not work and the same applies for vice versa. If you do end up trying Absolution just drop on by the Q & A if the freezing problem persists, I or one of the devs will try to give you hand the best we can..feel free to PM if you go with Absolution
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
ant_wailes said:
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
Click to expand...
Click to collapse
No, if you use the full wipe it pretty much just does the wipe data, wipe cache and wipe dalvik cache in one flashable zip. I typically use the 1.5 then wipe data, cache and dalvik cache. It is completely overkill and really not necessary but I do it just the same. No, EXT4 should no cause a problem. I'm pretty sure that almost all the ROMs are now EXT4 supported. I believe it would say it if it wasn't at this point. I know the major ROMS (ARHD, CD, Bindroid, MIUI) are all compatible with EXT4. The only issues you will find with EXT4 is the issue I mentioned in my first post and if you want to use gene's tool to unroot.
Welcome to xda and yes I had the same problem I was setting up setcpu and I sneezed and I accidentally pushed it all the way over to 1.9 and my phone didn't like it it just froze...I was worried :/ so I turned my phone back on and went into setting and forced setcpu to close (mind you it took a few restarts lol) but yes I had let it reset itself and now it's working again I just need to remind myself to do a nandroid once a day xD hehe
Sent from my Inspire 4G using xda premium
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Reinaldo33897 said:
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I believe there is a 1.3 wipe that formats to ext 3 again, just in case the OP wanted to format to ext3 before flashing a new ROM as opposed to flashing a new rom and then having to wipe and then flash again.
Cool Thx I'll do s search for the 1.3. It be good to have.
Sent from my Inspire 4G using xda premium
Hi smart people!
Just to throw it out there, I am not very tech savvy so excuse me if I misuse terms and such.
I believe I completely bricked my phone (I hope I'm wrong). After I downloaded Cyanogen through ROM Manager, my finger stumbled on the "continue" or "next" button or whatever WITHOUT checking the boxes to clear data, etc. I believe this is where I went wrong as I think I followed all other steps correctly (fyi I used the one click recovery flasher and made a back up).
Now when I turn on my phone, it goes from the stock LG loading screen to a modified LG loading screen (Cyanogen's I'm assuming) but it gets stuck there.
I've been searching on the different threads for quite a while and pressing the different combinations of volume up/volume down/power don't seem to do anything. I cannot get to the recovery screen.
Please help! I will forever be indebted to all of you. I am stupid and shouldn't have tried to do this on my own. Thanks in advance
What you will need to do is flash CWM via NVflash then boot into CWm and install your ROM.
If you flash CWM via ROM Manager it causes problems like what you're describing, I know from my own experience of following a friends instructions and doing that then having that exact issue. After getting my phone working again I then started to frequent the boards here.
As soon as I read the first couple lines I saw rom manager and saw the problem, you to search something that you have typed out all within this thread... I'm not near a computer but you should just search through these threads and you find your solution in detailed description. You need to get recovery from nvflasher just search that
Sent from my LG-P999 using xda premium
thanks for your replies
thank you to both of you for your prompt replies. i will try doing this within the next couple hours and post any results. this is the thread i found with the information you guys gave: http://forum.xda-developers.com/showthread.php?t=1058649
thanks again
No, that's not for G2x. Go here: http://forum.xda-developers.com/showthread.php?t=1056847
Ya it needs to be the one that gunnman wrote out for people.
Sent from my LG-P999 using xda premium
Hey guys...on step #10, it says to "select 'have disk'" but i do not see that option in the list.
Thanks
okay now i realize i should have been doing the cwm recovery. sorry guys and thanks again
reboot error
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
justintheshark30 said:
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
Click to expand...
Click to collapse
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
P.S. for future reference, you did not brick your phone, you got stuck in a boot loop, you know your phone is bricked when you don't see anything on the screen when you turn it on, usually it's just a software issue, but sometimes it could be hardware, for example I burned the motherboard on my previous android phone trying to customize it lol
jj_z1 said:
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
Click to expand...
Click to collapse
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Волк said:
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Click to expand...
Click to collapse
I really hate posting anything that doesn't have to do with anything phone related but I just couldn't stop myself from replying to your post!
1) I actually read all posts in the thread!
2) I did not in any way suggest that he didn't flash CWM the right way, I merely asked if he had done a full wipe before restoring his backup!!
3) Your reply was submitted while I was typing mine, so I'm sorry I didn't check the thread again before submitting my reply!!!
4) I'm well aware of what he tried to do already, but thanks for repeating it!!!!
5) If YOU read all previous posts you'll notice that my post does not exactly replicate any other, there's some new information in there that the OP might find useful!!!!!
6) From what I can tell, you need to work on your english and comprehension skills!!!!!!
To the OP, sorry for trolling your thread with this post, but I just couldn't help it, and to Bonk I hope you'll be the mature one and not reply to this post.
Is that to say you're immature? If one were to judge by the number of exclamation marks you have I'd say yes.
The only "new" thing was asking if he wiped before the restore, which, at this point, would be useless to ask as I already told him to make sure to wipe.
To the OP: How goes everything thus far?
thank you
that's what i ended up doing and it worked. thank you so much for all your help!
Волк said:
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
Click to expand...
Click to collapse
And dalvik cache for good measure, even though it is stored on the cache partition and will probably get wiped when you wipe cache. Sometimes it's good to overdo thing's.
Unable to do anything!
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Start over. Do what it states here: http://forum.xda-developers.com/showthread.php?t=1248644
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Did you battery pull and start over?
Sent from my LG-P999 using xda premium
UNROOT help
Hello again smart people,
I was hoping we would never meet again (for the better) but unfortunately i must unroot my phone to receive work emails. I have tried unrooting my LG G2x multiple times but to no avail thus far.
Here is the process I have tried:
1) boot into recovery - wipe cache/data factory reset, wipe cache partition, wipe dalvik cache
2) restore - using stock rom i found online
3) flash stock recovery image using nvflash
4) (attempt to) unroot using superoneclick - AFTER GOING THROUGH MULTIPLE STEPS, IT SAYS "TRUE" UNDER "CHECKING IF ROOTED". (also, i know it is rooted because it says the phone already appears to be rooted when i try to root again).
Do you guys have any idea what the issue could be?
Thank you in advance...
Had a bit of trouble trying to do this last night, which resulted in a few hours lost sleep. I went formatting everything in CWM and realized after the fact, I also formatted the internal SD card. Luckily ADB worked in transferring the zip (learn something new every day).
Anyway, after all said and done, all my apps were still on the phone. This is after formatting and new ROM...
How can I truly start from scratch to make sure this new ROM is 100% fresh and free of any unnecessary apps from previous ROMs?
Also, what would be the best current radio and link to said radio?
TIA
EDIT: I had just realized the issue with Factory Reset/Wipe Data. This one I had forgot to mention as I could never use it as all options said no and the menu was not scrollable. Just decided to try and use the volume buttons and sure enough there was more to scoll to.
That said, would the following be a proper procedure to follow;
Wipe Data/Factory reset
Wipe Cache
Format: System, Data, Cache, Boot
Wipe: Dalvik then Fix Permissions
Install order: Rom first, Gapps second, Kernel last
Reboot
???
nimrod.sixty9 said:
Had a bit of trouble trying to do this last night, which resulted in a few hours lost sleep. I went formatting everything in CWM and realized after the fact, I also formatted the internal SD card. Luckily ADB worked in transferring the zip (learn something new every day).
Anyway, after all said and done, all my apps were still on the phone. This is after formatting and new ROM...
How can I truly start from scratch to make sure this new ROM is 100% fresh and free of any unnecessary apps from previous ROMs?
Also, what would be the best current radio and link to said radio?
TIA
EDIT: I had just realized the issue with Factory Reset/Wipe Data. This one I had forgot to mention as I could never use it as all options said no and the menu was not scrollable. Just decided to try and use the volume buttons and sure enough there was more to scoll to.
That said, would the following be a proper procedure to follow;
Wipe Data/Factory reset
Wipe Cache
Format: System, Data, Cache, Boot
Wipe: Dalvik then Fix Permissions
Install order: Rom first, Gapps second, Kernel last
Reboot
???
Click to expand...
Click to collapse
The method I follow is
1. Wipe Data/Factory Reset (this takes away all your downloaded apps?
2. Wipe system/cache/dalvik (this wipes everything else)
3. Flash ROM, Gapps, Kernel
The thing with android is, even if there are some files left over from the previous ROM, they'll get overwritten with the ones from my new ROM, taking them away regardless. The reason you wipe everything to make sure there aren't any files that won't get overwritten. So basically, wipe everything and flash, and you'll have a fresh new ROM also you don't need to fix permissions after you wipe everything because they'll be no permissions to fix! Lol
Sent from my Nexus S 4G using Tapatalk 2
beneath-a-burning-turtle said:
The method I follow is
1. Wipe Data/Factory Reset (this takes away all your downloaded apps?
2. Wipe system/cache/dalvik (this wipes everything else)
3. Flash ROM, Gapps, Kernel
The thing with android is, even if there are some files left over from the previous ROM, they'll get overwritten with the ones from my new ROM, taking them away regardless. The reason you wipe everything to make sure there aren't any files that won't get overwritten. So basically, wipe everything and flash, and you'll have a fresh new ROM also you don't need to fix permissions after you wipe everything because they'll be no permissions to fix! Lol
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Thank you, good sir! Now running nice and clean!
Still need that newest radio if ya know it.
nimrod.sixty9 said:
Thank you, good sir! Now running nice and clean!
Still need that newest radio if ya know it.
Click to expand...
Click to collapse
I don't know it offhand but its probably somewhere on the development forums. I just noticed I said "my new rom" in my original post, I meant "the new rom" just in case you were a little confused (probably not but that would've annoyed me if I didn't address it)
Sent from my Nexus S 4G using Tapatalk 2
beneath-a-burning-turtle said:
I don't know it offhand but its probably somewhere on the development forums. I just noticed I said "my new rom" in my original post, I meant "the new rom" just in case you were a little confused (probably not but that would've annoyed me if I didn't address it)
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Newest radio I can find is from last year. Maybe that the newest. I know for certain signal and data is a million times better. However, I still have no 4g
And Im having an issue I ned to report about the ROM but XDA wont let me post... :crying:
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