Related
Before getting started I need to thank some people who have hlped me with this project or offered help to me. These people can be seen as contributors to this project, and I am grateful for their help.
Contributors:
JesusFreke (XDA)
Rogue7474, thanks for the help even though we never got it to work right. Hopefully we can continue to work together!
Coyote711
Also, before we get started, you will need root, and Jesusfreke's Mod rc30 installed(pref. v1.2), or RC8.
THIS COULD BRICK YOUR PHONE!
While I highly doubt it will, it still could!
If you are going to do this, I very highly URGE you to install the G1 engineering bootloader. With this installed, if something does go wrong, your phone is salvageable!
JesusFreke's Mod RC30 update V1.2: http://forum.xda-developers.com/showthread.php?t=443713
G1 Engineering bootloader: http://forum.xda-developers.com/showthread.php?t=455860
One more thing! Let it be known that this update will wipe your phone! (This means all your apps, data, etc. will be gone and you will have to sign into your gmail account once more.) This has to happen to install the theme correctly!
However, after you have done this once, and providing you still have the theme installed, you will not have to wipe your phone for future updates, I will provide another update which will install updates to the theme and will not wipe your phone.
With all that said an done I can get rid of that bold font.
This is a very simple process thanks to Jesusfreke helping me understand how to make an update.zip file which will work with his mod rc30 update.
Simply download the file, place it on your sdcard, boot your phone into the recovery mode(power+home), and hit alt+S.
Once it says its done, reboot the phone and enjoy!
Let me know if you run into any problems at all!
Let me know what you want to see in the next release, be reasonable I'm not a master image maker, and android does some strange things to some images.
Let me know if something seems out of place, or wrong.
I will try to resolve all issues as quick as I can.
The non destructive updates are for those that already have the theme installed and wish to upgrade to the newest version.
The destructive updates are for those that have never before installed this theme. This update will wipe the phone as is required the first time this update is installed.
Ok, well I applied it....
Here goes nothing.
US G1 running JF RC30 1.2 and dev bootloader.
I just backed up all my apps using astro too.
Welcome to T-Mobile G1...
See you in a minute.
I don't wanna get off topic here, but we need an all inclusive (how to back up your stuff) thread. Something that hits on Astro, My Backup, TXTract etc... and I need to pull up that thread about backing up your desktop layout and read that...(just can't remember which forum it was on...thing it was AC.com)
Thanks so much for doing this. I'm glad we finally got something different to look at. I'm glad someone is out there defending the pretty.
PS: FIRST!!!
Stericson said:
Before getting started I need to thank some people who have hlped me with this project or offered help to me. These people can be seen as contributors to this project, and I am grateful for their help.
Contributors:
JesusFreke
Rogue7474 (AndroidCommunity), thanks for the help even though we never got it to work right. Hopefully we can continue to work together!
Coyote711 (AndroidCommunity)
Also, before we get started, you will need root, and Jesusfreke's Mod rc30 installed(pref. v1.2)
THIS COULD BRICK YOUR PHONE!
While I highly doubt it will, it still could!
If you are going to do this, I very highly URGE you to install the G1 engineering bootloader. With this installed, if something does go wrong, your phone is salvageable!
JesusFreke's Mod RC30 update V1.2: http://forum.xda-developers.com/showthread.php?t=443713
G1 Engineering bootloader: http://forum.xda-developers.com/showthread.php?t=455860
One more thing! Let it be known that this update will wipe your phone! (This means all your apps, data, etc. will be gone and you will have to sign into your gmail account once more.) This has to happen to install the theme correctly!
However, after you have done this once, and providing you still have the theme installed, you will not have to wipe your phone for future updates, I will provide another update which will install updates to the theme and will not wipe your phone.
With all that said an done I can get rid of that bold font.
This is a very simple process thanks to Jesusfreke helping me understand how to make an update.zip file which will work with his mod rc30 update.
Simply download the file, place it on your sdcard, boot your phone into the recovery mode(power+home), and hit alt+S.
Once it says its done, reboot the phone and enjoy!
Let me know if you run into any problems at all!
Let me know what you want to see in the next release, be reasonable I'm not a master image maker, and android does some strange things to some images.
Let me know if something seems out of place, or wrong.
I will try to resolve all issues as quick as I can.
Update.zip: http://fightforthepits.com/update.zip
Stericson
Click to expand...
Click to collapse
good job man keep continues
Looks good, except I'm having a bit of a problem. I don't have my browser icon. Kind of weird. So, thinking I could get to my browser by doing a search through the widget, "android.process.acore has stopped unexpectedly." I'm going to flash Jesus's V1.2 back on, and then try this again. Will post back.
WOW
this is remarkable! I haven't been here for a while. but that just gos to show that in time anything is possible. keep up the great work. will report if i catch any bugs. THANK YOU
very cool
But you'd think they would have made it easier to skin/theme, I mean what's the first thing most of us look for as soon as we get a new phone, myself its walls, themes and ringtones in that order and I don't think I'm that diferent than the average g1 owner, and the average g1 owner is very different than the average mobile user.
But everybody wants to personalize a new phone, that's why we don't all wear the same clothes...
To the OP, thanks for all this hard work you have given to the community.
Bhang
See I knew it. I always had my faith in the awsome ppl here @ XDA-Developers.com. Just can't wait to see what's in store for the future, I know it will be more things to come that'll make you wish we never should of doubted the G1 and Android. Keep up the g00d work guys
I7oobie said:
Looks good, except I'm having a bit of a problem. I don't have my browser icon. Kind of weird. So, thinking I could get to my browser by doing a search through the widget, "android.process.acore has stopped unexpectedly." I'm going to flash Jesus's V1.2 back on, and then try this again. Will post back.
Click to expand...
Click to collapse
Got it to work. Looks great! Except i now have to re-enable my browser Auto-Rotate. No biggy though, great work!
I've had a small amount of trouble with this, although I'm not convinced 100% that it's at fault.
I've attempted to install this on my uk t-mobile g1 and it seemed to flash ok, however I couldn't get past the sign up screen as it force closed before completing. I re-flashed back to my original modded TC5-RC8 and the problem persisted until I then forced a hard reset ALT-W in the bootloader.
On my second attempt (I know I'm an optimist) I just got a hang on the g1 splash screen (Which I managed to recover via adb). I'm thinking it's related to my being on TC5-RC8 as opposed to RC30.
Any ideas, or has anyone else had more luck with TC5-R8?
All the apps for the base rom have to be resigned separately /system/app. So if you use the UK rom some apks will not be signed and cause a looping android or crashes. I had actually done this to the UK rom(skinning) but I am a mediocre image manipulator so i just changed hues.
This will work with with RC30 JF image. not the uk. If its needed I can remake his work with his permission for the UK rom.
Ive modified it for use with the uk rom here is the download link
http://rapidshare.com/files/175199050/update.zip.html
let me know if works
To All:
About Koush's auto rotate browser, if you replace the browser in that update with his, one of the status bar images will change I believe, no biggy, you will just need to replace it the image if you like. I may do this then post his auto rotate browser.
Thirdly for those missing icons, it is likely maybye something did not get copied. If this is the case, and you are missing programs, please let me know which one as I can send them to you and you can manually push them to your phone without having to do another wipe.
Bhang: Google made this really difficult.....I agree you would think that themes would have been a first to settle....SHRUG
EDIT: afbcamaro, Thanks so much for taking the time and doing this. With the rc8 update does everything look the same?
Stericson
Excellent job !!!! Patience is the key !!!
Stericson said:
To All:
About Koush's auto rotate browser, if you replace the browser in that update with his, one of the status bar images will change I believe, no biggy, you will just need to replace it the image if you like. I may do this then post his auto rotate browser.
Thirdly for those missing icons, it is likely maybye something did not get copied. If this is the case, and you are missing programs, please let me know which one as I can send them to you and you can manually push them to your phone without having to do another wipe.
Bhang: Google made this really difficult.....I agree you would think that themes would have been a first to settle....SHRUG
EDIT: afbcamaro, Thanks so much for taking the time and doing this. With the rc8 update does everything look the same?
Stericson
Click to expand...
Click to collapse
When I go to do the auto-rotate browser, there is no room left. Oh well.
To push file to the dir /system NEVER do it while the phone is on, running normally. You need to boot into recovery mode and push it from there.
when you get into recovery mode you will need to type the following to mount /system
adb shell mount /system
adb push /whereveryoufileis/Browser.apk /system/app
This will eliminate the problem you are having.
Stericson
i found a bug
Everythings good. But I found something. When you make a folder and open it the res is off
Hope you can fix this its not a biggie but I told you I would report any bugs. Thanks again
So when you make a folder in the file manager or what? You have to be specific as to what program you were using, etc. I have to know exactly what your looking at....maybe you can take a screen shot?
Stericson
nice work stericson!
some things i noticed:
-opening a folder (shortcut) on the desktop. label is not displayed, and folder contents are not superimposed enough when its in the foreground.
-can't see the highlight when pressing an entry (inbox, sent, etc.) in the gmail app.
Ok. first, thanks for reporting back.
What do you mean the label isn't displayed? I put items on my desktop and I can see all of theie labels. I am also not catching what you are trying to tell me about the folder contents not being superimposed enough when in the foreground, maybe a screenshot would help.
Also the highlight, when pressing an email, etc should turn a bright white, as it does for me, does it do this for you? Also, what suggestions would you have for the colors or solutions to these problems?
Stericson
TheDudeOfLife said:
Ok, well I applied it....
Here goes nothing.
US G1 running JF RC30 1.2 and dev bootloader.
I just backed up all my apps using astro too.
Welcome to T-Mobile G1...
See you in a minute.
I don't wanna get off topic here, but we need an all inclusive (how to back up your stuff) thread. Something that hits on Astro, My Backup, TXTract etc... and I need to pull up that thread about backing up your desktop layout and read that...(just can't remember which forum it was on...thing it was AC.com)
Thanks so much for doing this. I'm glad we finally got something different to look at. I'm glad someone is out there defending the pretty.
PS: FIRST!!!
Click to expand...
Click to collapse
I agree with thedudeoflife. I didn't even know you could save apps on sd card? (wtf? really?) I think a how to back up stuff before a wipe out would be great!!!
P.S. you want to start a thread thedudeoflife since you brought up such a good point?? pretty please haha?
hbguy
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Thanks dude!
Here is the touch version of 6.0.1.5 http://d-h.st/1Kk. I built this last night using the recovery builder found here http://builder.clockworkmod.com/ with the 6.0.1.0 version as a base.
EDIT/ I FORGOT TO MENTION. I AM NOT RESPONSIBLE FOR ANYTHING WORKING OR NOT WORKING WITH THIS RECOVERY. I ASSUME NO RESPONSIBILITY FOR BROKEN DEVICES. USE AT YOUR OWN RISK. THANK YOU
myepicyear said:
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Click to expand...
Click to collapse
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Yes it has that option
Sent from my Galaxy Nexus using xda premium
TransWarp said:
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Click to expand...
Click to collapse
Yes, this version includes both tar and dup (data blob) backup formats. Tar formatting was re-added in 6.0.1.2.
So you can have either quick, large backups; or slower, slimmer backups with this version.
There's also an interesting adb sideload option as well. Not useful for most casual users, however, the more adventurous users will have a purpose for it from time to time.
10characters
FrostyF7 said:
Thanks dude!
Click to expand...
Click to collapse
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
myepicyear said:
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
ezeuba said:
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
Click to expand...
Click to collapse
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
myepicyear said:
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
Click to expand...
Click to collapse
Top notch response. Thanks...
---------- Post added at 05:30 AM ---------- Previous post was at 05:22 AM ----------
One question. How does the sideload thingy work? What's it all about?
Anytime
myepicyear said:
Anytime
Click to expand...
Click to collapse
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
The same way you installed twrp? Boot into fast boot mode and fastboot flash recovery name-of-recovery.img. Replace name of with the actual name of the image. Or you could download and install flash GUI and flash the image through the app.
Sent from my Galaxy Nexus
crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
myepicyear said:
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
Click to expand...
Click to collapse
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Definitely try to learn fast boot man. The toolkits are cool, but a minor mistake can make using one a nightmare. If you learn fastboot, you will always be able to fix your device. Plus it is the proper and preferred method for flashing a recovery, radio, or bootloader. It is an invaluable tool for for flashing.
Sent from my Galaxy Nexus using Tapatalk 2
crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm happy to be able to help man.
If you want a quick fix until I have some time to more time to explain fastboot thoroughly, I can do that for the moment.
The toolkit that mkskip has put together for everyone is very handy. It is basically like having all the essential tools, like fastboot, installed for you in their most lean form, without needing the whole android SDK installed. It also gives you a logical interface to interact with all that stuff. The toolkit installs all these tools within a folder on the root of your C drive. If you go to the root of your C drive, you'll see that folder, which is called 'Galaxy Nexus Toolkit'(or something). If go inside that directory, there's a folder called put imgs to flash here. There are several ways to do things in the toolkit folders, but basically, this is one folder you can insert imgs in to fastboot flash them.
Let me know if you're with me so far. I'm going by my memory of all this stuff because I don't use toolkits or Windows anymore. I can guide you through this, and during the process, hopefully broaden your understanding of fastboot at the same time. I'll need you to do some searching of your own during the process, or it wont make any sense at all, but I can definetly guide you through.
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
063_XOBX said:
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
Click to expand...
Click to collapse
Dude, I'm not stupid. I'm trying to explain it in a way he is already familiar with.
Jesus.
Update twrp 2.7, see Dhackers link for the img. Use Recovery Tools from Play to flash from home.
Seems that only Dhackers latest TWRP is the one to use.
Thanks to cyanidium for making it evident to me anyway.
Dhackers msm8960 goodies: http://androidhosting.org/Devs/Dhacker29/msm8960/
BTW Does anyone know what "twrp263-M44.img" is?
Attachments: the ...M44 is 1 day newer & works.
Just extract these to get the fastboot img.
More details
http://forum.xda-developers.com/showthread.php?t=2612883
More conformation http://forum.xda-developers.com/showpost.php?p=49978993&postcount=79
This one is not Dhacker latest anyway :
http://forum.xda-developers.com/showpost.php?p=45688558&postcount=1
Md5 starts with 791.
Want to try Philz.
http://forum.xda-developers.com/showthread.php?t=2545120
Want The latest 2631? w/ SDext usb mount. What is the rub?
This Photon Q TWRP, with full SD mount & more, works on the M! See attachments for the flash-able ver. Now for the rub: screen input requires the mirror of the buttons. I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL.... It is really not that hard to use. Think of it as a game also.
Md5 : 7630baf88ec9d6c2a144a2ee86ec9bb7
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
No settings, just bad! Thanks for the conformation Watson! We on a train with a new engine!!!
Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
How long have you known about it?
aviwdoowks said:
How long have you known about it?
Click to expand...
Click to collapse
I came across this issues first time trying to flash Paranoid and Pacman.
Which left me soft Bricked or in Bootloops. At the time i was just too fed up and went back to stock
second time i encountered that, was with the first stable KitKat by Dhacker.
That's when i decided to start clean and deleted all my Pre downloaded files and I was forced to download the new E33 from Dhacker.
And along with that all my other Roms and Files. I kind of figured something was bad with my TWRP file. But never thought of it since 791 wasnt found by my search engine.
And this December when I was flashing my GFs phone that's when I confirmed that the 791 didn't work for any of my roms.
Because I couldn't find Dhackers E33 through Google.De search (Some odd way searches come up differently if you search from different country)
And it did the same issues I had the First time around. That's when i dug around more and found Dhackers TWRP.
After using that I was able to flash Roms like a mad man until I found a Rom that my GF was comfortable using and liked.
Germanese said:
I came across this ....GF was comfortable using and liked.
Click to expand...
Click to collapse
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Ohh well now we all know!
Thanks again for the history.
This screwed up my data partition & I could not determine if it was philz or this. Then I decided the stop one, as I would go to the other & then data restore failure, so I used just philz & the problem went away!
aviwdoowks said:
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Click to expand...
Click to collapse
Nah i didn't post about it back then and recent we were side tracked ahahaha.
And I actually just got back couple days ago ... work ugh hate it already ...
There maybe a post few months back, me asking somewhere about which TWRP people are using,
because I had my doubt on which one to use; but no one really bothered to respond.
Then i just decided to flash away with what ever, since most errors resulted in an Harmless SoftBrick.
Since i figured a way around to that soft-brick, my thought was, what worse could happen, I did worse before LOL
I won't take credit, just stumbled upon it... That's all you. Just here to Confirm that i did have issues with that version.
Since then I been trying to see CWM for KitKat LOL
Hmm...
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Twilla said:
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Click to expand...
Click to collapse
Yes or the e33.
Not sure which is better. Philz is newest & I have an ini file to help you set it up see #2 post.
Update.
Haha. But not a joke. PHOTON Q twrp 2631 up.
twrp 2631 maybe provided by arrrghhh!
http://forum.xda-developers.com/showpost.php?p=49857073&postcount=176
If you want to be synched to his Q versions, go thank him!
That means a good screen version for our m.
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Coronado is dead said:
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Click to expand...
Click to collapse
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
aviwdoowks said:
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
Click to expand...
Click to collapse
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Coronado is dead said:
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Click to expand...
Click to collapse
May I suggest philz new version just out.
Allows you to format many /'s now.
I use only it now.
Not pocket proof like twrp. Beware
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
aviwdoowks said:
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
Click to expand...
Click to collapse
It works fine (I have flashed Dhackers *img) but if we want to flash any ROM we must change updater.script and add moto_msm8960 to device list on it.
I have success flashed BeanStalk after I add moto_msm8960 to updater.script
P.S. Also unified ROMs flashed great!
P.P.S. Gummy is most stable for me from unified ones
Flash TWRP-2.7.0.0-moto_msm8960-hdpi.img with Recovery Tools. See OP.
Would anyone know if Dhacker's TWRP works on the XT905 model as well?
Yes. But that is just good advice. I do not have one.
ATTN: I NEED EVERYONE'S HELP!!! PLEASE!!!Here's what I need you to do!Find and Search through your PC's and look for any complete or decently stable ROM's, RECOVERY's, KERNEL's and any possible missing links / files / documents for the LG Optimus V regardless of it's version or kernel and Send me WORKING links, files, of anything you got. All the links for this phone are dead... I've checked all over the web. This is still a great phone, and can still be used either with Boost Mobile or simply with a Credit or Debit card. A friend and I plan on revamping this phone to see if we can't bring it back to it's glory. But in order to do so.... Got to have the Archives! Every link is dead.... PLEASE PLEASE PLEASE search around for anything LG Optimus V, VM670, Thunderc Optimus S is also appreciated.
THANK YOU FOR YOUR TIME AND PATIENCE
Send them to me, in a PM and or share them with me to my Google Drive via email.... PM for email... thanks
You may post links here only as long as the owner hasn't pulled the files for TOS Violations.
To be honest.... if your unsure, just PM the links.
I'm taking any and all files that are DEAD links
anything I can redownload as of today's date, will be unwanted.
But don't let that discourage you from SHARING THEM AWESOME FILES AND RE-UPLOADED LINKS!
THANK YOU THANK YOU THANK YOU!!!
:good::laugh:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Here's some Optimus S stuff I used to use,was able to download from here today, https://archive.midnightchannel.net/zefie/files/cell/LGLS670/
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
timjames474 said:
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
Click to expand...
Click to collapse
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files
Click to expand...
Click to collapse
you have to crack open the boot.img and replace just the kernel with a working one. it's "fun."
and finding a working kernel for the newer screens now as a standalone download is really iffy. (actually, see next post. I found /one./)
if you have another jb rom with working screen you can split that boot.img and yoink its kernel for the one that doesn't have more than a backlight. you can also plop that picasticks kernel from below into any blackscreen recovery images too, they split and recombine just like a boot image.
a lot of people call the boot.img a kernel, but it's actually a combination of kernel and ramdisk.
you can use osm0sis AIK tools to disassemble and reassemble boot.img relatively painlessly.
I'm happy to promote osm0sis's work. he does great things. drop him a donation if you're so inclined, he certainly deserves it.
by the way, don't try to insert the 3.0 kitkat kernel into anything else... it probably won't boot. jb is the best bet to try it on though, thekraven nudged me into porting that kernel from the p500 for his jb roms. I'm glad he did, because the experience has been very useful on other devices.
ok, here's my gift to y'all.
https://www.androidfilehost.com/?w=files&flid=317344
archive of the primary goodies from my old failing NTFS external drive. We'll see how long it takes for androidfilehost to arbitrarily delete them like they did every other file I ever uploaded there for the optimus S/V with no warning or acknowledgment. they never even answered multiple support requests trying to find out why... I'm guessing they decided to clean their servers of things uploaded before a certain date, but no telling since they wouldn't answer.
in the kernels subfolder is a picasticks kernel i built for the old/new screens.
multiple recoveries. some are old and may blackscreen on newer devices, fair warning. some roms will be the same way. the twrp's may or may not have reversed system/userdata like my os2sd twrp, try and see. they should at least be good on any model optimus s/v screen.
several roms, including one harmonia, and PAC-rom from thekraven.
others folder has V drivers... and swype flashable zip, ripped probably from GB stock, maybe from froyo stock.
also multirom recoveries and installer if you like multiboot. thread here
have fun.
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
Click to expand...
Click to collapse
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
timjames474 said:
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
Click to expand...
Click to collapse
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
bigsupersquid said:
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
Click to expand...
Click to collapse
if you manage to find it,do let me know! TIA
timjames474 said:
if you manage to find it,do let me know! TIA
Click to expand...
Click to collapse
I can pull the one from the rom on my V and switch the keys.
no flashable zip, you'll have to use adb to install it, I'll post the commands
it's home and menu that are swapped if I remember right, is that correct?
it's actually a .kcm file, I've messed with so many devices I mix things up sometimes.
Sorry for being gone so long,yes those are the keys,my Optimus S had been dropped one time too many but i finally replaced it and am still interested in getting those files and commands
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
bigsupersquid said:
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
Click to expand...
Click to collapse
Seems that it always goes to /system/usr and the two folders are keylayout and key(something else idr) the one that i cannot remember the name for is where the .kcm files are at
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
bigsupersquid said:
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
Click to expand...
Click to collapse
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
timjames474 said:
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
Click to expand...
Click to collapse
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
bigsupersquid said:
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
Click to expand...
Click to collapse
MicroG has a broken login,the login box is all the way off screen for me,but ive since gotten a modern phone at the gentle prodding at Tello anyway