HikenGruven
Member
Thanks for compiling all of this! I want it bad, but I think I'm going to sit it out until it stabilizes a bit more. My tinkering time is limited right now.
guess what dezy I had 1.9 stick at the google screen. I am going back to my previous jb rom and I am just gonna sit on it until source is released.
Strange, I'm on 1.9 and it boots in about a minute. Tried multiple times and all is good so far.
Sent from my Galaxy Nexus using Tapatalk 2
Mine bootlooped on me AGAIN! While I was out of the house for an hour or so, recovering now. Really don't think my phone likes jb roms....guess what dezy I had 1.9 stick at the google screen. I am going back to my previous jb rom and I am just gonna sit on it until source is released.
Think I'm gonna find a regular cwr to flash. I really do believe that cwr touch interferes or messes with the phone with jb roms.its weird cuz i did 3 wipes of data, cache, and wiped dalvik. I should have never booted up on 1.9 with my data and everything intact.:angry: Im glad i did cuz it saved me the hassle but still there is a problem with cwr touch.
No idea. Not even a battery pull helped this time. I'll give a JB rom one more shot, but if it freezes up again with a regular version of cwr, I'm going back to an ICS ROM. I can't afford for my phone to go down when I'm away from my PC.I think cwr touch could be an issue but why would it fail to boot. Unless it's failing to wipe something that doesn't show itself until after you run it for awhile and you go to reboot or change batteries.
Sent from my Galaxy Nexus using Tapatalk 2
Yeah I think I was on that version.Did you try 5.8.0.2 (or is it 5.0.8.2,..you get the point ) in CWR Touch? That's the version I used and have had JB 1.8 running at least 6 hours with multiple reboots done and a backup made, and a mod flashed. The only hiccup was the one time I had to wait longer than normal at the Google logo after restoring the device ID. Question, well you probably can't answer since you switched recoveries. Was going to ask you what happens when you manually go to mount the /data partition from within recovery. Sounds like maybe it's not getting mounted hence why your data as all there.