Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Back up and Ready for more :banghead:
I guess back to the status 7 version. No brick at least. Then removing the audio symlinks from updater since there not in etc in that version. dunno
When you got the status 7 were you able to easily reboot your phone? Meaning no brick.Back up and Ready for more :banghead:
When you got the status 7 were you able to easily reboot your phone? Meaning no brick.
Cool. From what I remember, you can just reboot after status 7 without wiping or anything.I didnt try to reboot. since i was still in CWM when that popped up while it was trying to install CM. I just re wiped everything and restored with no issues
How to flash ROM:
Select Factory reset in recovery
Wipe cache
Wipe dalvik cache
Flash ROM
Flash gapps if you wanna.
I thought someone said installing was different
Dont wipe /system when flashing. Thats the problem here. On the motion cm10, we dont wipe /system. Most people that do end up bricking.
Lol your too funny.How to flash ROM:
Select Factory reset in recovery
Wipe cache
Wipe dalvik cache
Flash ROM
Flash gapps if you wanna.
This is what confused me
!doh! Just realized those build.prop entries I mentioned earlier were supposed to be empty. PG kept it classy and didn't want to correct me. lol
all I did was wipe data/factory reset then flashed everything installed complete, reboot--- -rebooting seems to be working second lg logo screen..then 3rd lg logo screen [security error] stuck their...didn't even flash gapps,wanted to check if it booted up first. (I did notice when I was bricked I removed my battery put it back in then I connected phone to my pc not holding or pressing any buttons,i got a message in violet color/=missing battery file 3.png battery charging....
percent..%
Don't feel so bad about bricking guys. I've bricked this phone about 20 times, most of which was getting the edify script to work for flashing roms.
This phone is picky wit that sh!t. It's also weird having CWM as an app and not flashed. lol
Anyways I'm almost certain it's just the edify script that needs adjusting for this to boot.
I downloaded motion CM only to compare and aside from amount of files in folders, everything was the same.
I gotta hand it to ya, you unbrick faster than a mofo with a gun to his head. lol :rofl:I don't mind bricking and having to restore. Its what I can do to contribute. I'm not skilled in writing or moding ROMs. But I can test
welp I guess there went that idea. lol
Yea we both realized that was all moot for the time being. lolSo, been talking to PG. Looks like we might have a different kernel and ramdisk address. That would cause the build not to boot.
I just finished downloading the sauce, and I'm ALMOST ready to start my own build. I think PG is going to build me a zip with the changes I found. Maybe we'll get a working ROM!
Hey life goes on for us all. Gotta get a ecumacation yanno.Sorry for going MIA for awhile. School has a tendency to make me do that.
I noticed your device tree for the Spirit. Is it mostly the same from the Motion's tree? I'm trying to get caught back up where you guys are.
The Motion and the Spirit are not the same in terms of prop blobs. I dissected our stock ROM to figure out what's-what, and I'll post my prop-files list. It'll be up on my Github (ikarosdev).
The build you posted. Is it a kanged prebuilt off the Motion or is build from scratch?