So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.
Related
hi,
in this thread
http://forum.xda-developers.com/showthread.php?t=1401633
it references the kernel by imoseyon. i would like to download that kernel so i have it in case i want to come back to it later while i try a franco kernel. but when i go to imoseyon git files, there are so many files, i don't know where to find it.
if i hit the download button, the file it wants to download is like 120megs. seems like kernel zip files are usually like 4 or 5 megs so 120mb doesn't seem right.
anyone know how i can get the CWM install ready kernel?
thanks
Unzip the rom and take the boot.img out.
This is the kernel, you can flash it using fastboot.
thanks. these look to be the commands to do that
adb reboot bootloader
fastboot flash boot boot.img
http://rootzwiki.com/topic/13299-kernel-leankernel-minimalistic-kernel-171-12012/
Google is your friend.
Edit: If you go to his git, you download his source and all the associated repos. That's why it's 120mb. Download it from rootzwiki there. Those ones are CWM-flashable.
glhelinski said:
thanks. these look to be the commands to do that
adb reboot bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
This may not be enough as often kernel requires some suplement files to be stored in /system. CWM flashable bundles of leankernel are the best way to go. Main development goes on rootzwiki, head there for this kernel. 0.6.6 uses leankernel 1.7.1 I believe
thanks to both of you. good info. google is definitely a friend...rootzwiki password resets are not
Coming from a T-bolt, I got in the habit of wiping data, cache, and dalvik cache every time I threw a new rom on.
If I'm going from 0.6.5 to 0.6.6 do I need to wipe ANYTHING? I've heard no, but it just feels weird flashing a rom straight over an existing rom.
Thanks in advance for your help!
Seedster said:
Coming from a T-bolt, I got in the habit of wiping data, cache, and dalvik cache every time I threw a new rom on.
If I'm going from 0.6.5 to 0.6.6 do I need to wipe ANYTHING? I've heard no, but it just feels weird flashing a rom straight over an existing rom.
Thanks in advance for your help!
Click to expand...
Click to collapse
Nope, don't wipe anything
Sent from my Galaxy Nexus using xda premium
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
have you ever flashed a rom and kernel before? also are you till in stock rom?
x1rocket said:
have you ever flashed a rom and kernel before? also are you till in stock rom?
Click to expand...
Click to collapse
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
game_guy said:
Yes I've flashed a ROM before. Following these same steps, I was able to boot CM9. I've also managed to get AokPlay, Paranoid Android and a few other ROMs running on my device. I always flash back to stock before attempting to flash a new ROM.
Click to expand...
Click to collapse
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
x1rocket said:
on the thread you have downloaded the file are the users facing the same problems or just you? must be not supported by your model or the compiled file was not a success to let you boot... if you do check, make sure you read all the pages on that thread...
Click to expand...
Click to collapse
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
game_guy said:
It's definitely compatible with my device, it even says it is. I read through the thread and it looks like one or two people are having the same issues.
Click to expand...
Click to collapse
wait a couple of days and see if those users have a fix for it... as no one else posted on this thread they wouldn't know the problem the same as I don't know...
at least I tried to help
game_guy said:
I've been trying to flash CM 7.2.0 and every time I do it, it either A) freezes on the kernel or B) freezes on the boot animation. My bootloader is unlocked. Here are the steps that I've tried.
1. Flash R800x_3.0.1.E.0.88_Verizon.ftf
2. Activated phone, wifi, and whatnot. Play around with it for a few minutes.
3. Flashed the kernel that came with FXP CM7.2.0 zeusc.
4. Boot up into recovery. Wipe user data, cache, dalvik cache.
5. Flash CM7.2.0 zeusc zip.
6. Reboot and the boot animation freezes. I've waited up to 30 minutes and no change. Pulled the battery out, turned on, still freezes on boot animation.
I've done the same thing with R800x_4.0.2.E.57_Verizon.ftf and still no luck. Any ideas?
Click to expand...
Click to collapse
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of http://get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Leraeniesh said:
If you are still having trouble flashing CM7, I would suggest downloading from zeusc section of get.cm
Or, you can try one of the many CDMA optimized ICS/JB ROMs.
Click to expand...
Click to collapse
I might switch back to CM9 or Paranoid. I've tried the JB ports. One has working data but no sound, and the other CDMA has everything working except I couldn't get data to work.Thanks for that URL, which one would you recommend? RC1, 2, 3 or stable?
agraceful said:
You may have to wipe everything a few times. Of course you can always use my modified cm7 which has autorotation unlike any other cm7 for zeusc lol
Click to expand...
Click to collapse
If the get.cm doesn't work either, I'll go ahead and try the one in your signature. If all else fails, I'll probably go back to CM9 or Paranoid.
Thanks for all of the help you guys, this is a pretty nice community. :3
Sorry to double post, but I tried the ones from get.cm and the modified one from agraceful, but both froze on the boot animation then crashed and froze on the kernel. I think I'm just gonna give up on this particular ROM.
Check what kind of kernel you using.
I had simillar problem whed used kernel from XDA downloaded file. When used from file downloaded from CM project site it runs with no problems.
I have no idea why that happen, maybe on XDA forum is different modificated version for 800x or 800i etc. and not working with all phones.
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
brettbee said:
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
Click to expand...
Click to collapse
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
try beanstalk 1.300
brettbee said:
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
Click to expand...
Click to collapse
I have been using beanstalk 1.300 with the b-team CM kernel.it has 4.2.2 and everything works! its fast and smooth with great battery life the 4.3 roms have some issues so I am gonna stick with this one
AFAIK everything in the newest Evervolv works.
phillibl said:
AFAIK everything in the newest Evervolv works.
Click to expand...
Click to collapse
Are you using a nightly? Which one?
Does 3G come back after WiFi is turned on?
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
kahlil88 said:
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
Click to expand...
Click to collapse
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Thanks!
brettbee said:
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Click to expand...
Click to collapse
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
brettbee said:
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
Click to expand...
Click to collapse
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
brettbee said:
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
Click to expand...
Click to collapse
What version of gapps are you installing? Try flashing the ROM without installing gapps and see if it will boot, then if you're successful go back into recovery mode and flash gapps-jb-20130813-signed.zip from here.
funny question, does docking mode work with these roms?
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
flinzak said:
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks - found it and downloaded it! I'll give it a try when I can have my phone out of service.....
I flashed Evervolv 10/30 nightly yesterday and it looks like they have the 3G/WiFi toggle issue resolved. The quick settings were missing but, I'm guessing that'll be corrected in the next build. Also, flashed B-Team Kernel. 4.3-s2w version resulted in bootloops but, the 4.3-v2 version worked just fine. No sound issues as far as I can tell.
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
jonatcer said:
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
ArslanQureshi said:
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
Click to expand...
Click to collapse
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
jonatcer said:
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
Click to expand...
Click to collapse
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
ArslanQureshi said:
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
Click to expand...
Click to collapse
Alright thanks a bunch.
Would you, or anyone else still reading this thread, care to weight in on whether Evervolv or CB's rom (Which? Beanstalk?) is more stable?