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
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
Hello guys, I have to ask you a question that I can not resolve for months.
I have a HTC TOUCH PRO, and every kernel I try to always have problems.
At first the device works well and is also very fast, but hopelessly after a while it stops. When you first start can last hours and then crash, but already the second hangs after a few seconds.
I've tried almost every kernel, even the "msm-htc-linux-20101204_005141-package.tar" by the comments that seems to be the best for my device, but nothing. I'm desperate and I do not know what to do.
Can you tell me how to solve this?
Waiting for reply.
Thanks to everyone that I will respond.
I'm not sure what your problem actually is. Sounds like the system_server bug... Make a call to voicemail, phone should speed back up.
Also, the newest kernel is 1253. The autobuild service has fallen behind GIT, see this thread to get the most up-to-date GIT commits.
i must only update with this kernel?
master9 said:
i must only update with this kernel?
Click to expand...
Click to collapse
The kernel (zImage) goes hand-in-hand with the modules file.
Still not sure what you mean tho.
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
master9 said:
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
Click to expand...
Click to collapse
You say it's fast, but the phone freezes...?
Where does it freeze?
XDAndroid is far from 'stable'...
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
djdafreund said:
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
Click to expand...
Click to collapse
O___o I did not realize that. All RAPH's...? Do we have logs? I need information man!
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
djdafreund said:
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
Click to expand...
Click to collapse
Oh right, that. Screen shifting seems isolated to the RAPH800 and DIAM500. Probably RAPH500 as well, and I'm not sure what the other DIAM is... perhaps there is a DIAM800, not sure. Either way, seems to only be the CDMA devices.
But of course LOL. I personally love my Touch Pro, but WOULD love to upgrade if i had the money. But yeah, the dreaded shift problem til it's fixed. Not a BIG deal for now, since previous kernals will hold us off til that's fixed.
Nothing, i have the same problem
master9 said:
Nothing, i have the same problem
Click to expand...
Click to collapse
You still haven't properly elaborated on your actual problem. Vagueness will get you nowhere, except frustrate people.
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
master9 said:
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
Click to expand...
Click to collapse
Seems to be a pretty big language barrier here... "any kernel I mountains"...?
So has Android ever worked for you? What build(s) have you tried?
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
master9 said:
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
Click to expand...
Click to collapse
What about FRX03? I can't really help you with any build but that one - if you're using a different build, you'll need to get help in those threads. Generally if you just throw up a post like this, use FRX03 (or AOSP, whatever) as your base to test off of.
If it works in that build, but doesn't work in one of the others - then it's that build. If they fail in both builds, then it's a general issue with Android - or, you've just done something wrong .
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Keep in mind, most neopeek variants require two partiations to be setup as primary (one FAT32 and one EXT2). You might find it a tad difficult in finding someone to help you troubleshoot your process unless you seek help from with-in the thread that you downloaded superfroyo or any other neopeek variants. It is rare to find but then again, you could just as easy try out FRX04 and post your feedback in that thread too. See THIS post for info on downloading the FRX04 update file but you will probably need to downoad THIS package first, then update the system.ext2, rootfs and kernel package after the fact. Stinebd has links for the rootfs in his sig.
n-Joie! (Enjoy)
master9 said:
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Click to expand...
Click to collapse
Again, you're using funky version. As R^72 said, get help with those versions in that thread.
If you want help, at least try FRX03. You haven't even given it a shot. Then you can update to FRX04, and if that all works - then try something more complicated like a Neopeek build!
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.
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
Its been a while since I have rooted anything manually and i need some expert advice here.
I have someone unlocking my T399 and he gave me this guide -> http://rootmygalaxy.net/root-galaxy-light-sgh-t399-install-twrp-recovery/ the problem is the TWRP link is dead and i cant find another of that version anywhere. Does anyone have this or can I use http://androidforums.com/threads/recovery-team-win-recovery-twrp-2-7-0-0.836658/ or https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604 ? Im assuming yes but wanted to double check with you guys before off and doing something catastrophic to my phone.
Any help is much appreciated.
Thanks
Phonecapone
TWRP Themed Recovery
phonecapone said:
Its been a while since I have rooted anything manually and i need some expert advice here.
I have someone unlocking my T399 and he gave me this guide -> http://rootmygalaxy.net/root-galaxy-light-sgh-t399-install-twrp-recovery/ the problem is the TWRP link is dead and i cant find another of that version anywhere. Does anyone have this or can I use http://androidforums.com/threads/recovery-team-win-recovery-twrp-2-7-0-0.836658/ or https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604 ? Im assuming yes but wanted to double check with you guys before off and doing something catastrophic to my phone.
Any help is much appreciated.
Thanks
Phonecapone
Click to expand...
Click to collapse
There you go
I upload TWRP Themed Recovery on Android file host there you find (IMG,zip,tar) file choose what you want:good:
https://www.androidfilehost.com/?w=files&flid=157735
I used the second one you linked just a couple weeks ago, and it appears to work just fine:
https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604
A140 said:
There you go
I upload TWRP Themed Recovery on Android file host there you find (IMG,zip,tar) file choose what you want:good:
https://www.androidfilehost.com/?w=files&flid=157735
Click to expand...
Click to collapse
Hey A140 thanks a million! Hopefully I wont have any issues downloading it. For some reason I have had a lot of corrupt downloads from androidfilehost. I know they said they are in the process of moving servers? So perhaps that's why. Can you upload to one more place so we all have a backup here? So in the event others run into the same problem I am having we're all covered. =]
http://www.multiup.eu is good
I will try and download soon as I just got back around to this phone again and give it a try and let you know what I think. Right now I have TWRP ver 2.7.1.0 for Galaxy Light T399 ? which appears to be custom and themed? I just now noticed it when rebooting into Recovery from ROMs restart options. It is white, brown and orange with a list menu. I haven't seen this before though again I haven't flashed any other versions of TWRP besides the touch so maybe it's the standard? I did have TWRP ver 2.8.4.0 for this phone which was the grey, black and blue big button themed touch interface I loved so much.
Aside TWRP matters im also toying around with Lightwave-V3 Rom by user @root@ which I switched to from TigerLillly by user DJBoxer. Both seem to be pretty good although Lightwave was suppose to have came preconfigured with a bunch of useful utilities / mods and it appears they weren't configured in the Rom's configuration. I'll have to take a look and see what needs to be modified if they exist within the build seems same with TigerLilly also. I'd suggest these 2 ROMs to anyone with this phone. Smooth, no bloat and no problems so far. However I am always up for trying any others if anyone has some to suggest. Post and let me know.
First post back here in some months. Now back into androids more and attempting root on a few unknowns so hopefully I will have some good material to contribute in the near future. Still hitting that learning curve hard trying to get with the future. I'm still oldschool @ heart stuck with knowledge of the past flip / feature phones, java, crackberries, outdated unlocking boxes and about 100 pre android phones lol. Have the parts to the first android still but unfortunately incomplete. Some interesting times I tell ya. Thanks to XDA and HOFO I'm picking up where I left off quite quickly.
Lightwave - https://forum.xda-developers.com/galaxy-light/development/rom-lightwave-v1-t2825253
TigerLilly - https://forum.xda-developers.com/galaxy-light/development/rom-tigerlilly-v2-1-4-4-2-t3400659
I will post a TON of information on this phone, recovery, rooting, stock/custom rom links and much more in the appropriate thread when I get time free from work. Have done a lot of researching since this post. https://forum.xda-developers.com/galaxy-light - seems to have most of my work done lol. I keep forgetting how old this phone is and that it's been ran through by quite a few dev's already.
Upload it
I upload both themed 2.7 and 2.8 to your favorite site I am giving the link down you can download from it I upload zip file you can flash using costom recovery that you have right now if you want img file you can extract zip file you find Img file and if you want to flash through odin than use zarchiver on your Android phone and compress img file to tar and rename it tar.md5!?
Themed 2.7 link
http://www.multiup.eu/bd3fdc8bee0f678b90df62a1376ed1e6
TWRP 2.8.4 link
http://www.multiup.eu/en/download/9...14bc32/openrecovery-twrp-2.8.4.0-gardalte.zip
phonecapone said:
Hey A140 thanks a million! Hopefully I wont have any issues downloading it. For some reason I have had a lot of corrupt downloads from androidfilehost. I know they said they are in the process of moving servers? So perhaps that's why. Can you upload to one more place so we all have a backup here? So in the event others run into the same problem I am having we're all covered. =]
http://www.multiup.eu is good
I will try and download soon as I just got back around to this phone again and give it a try and let you know what I think. Right now I have TWRP ver 2.7.1.0 for Galaxy Light T399 ? which appears to be custom and themed? I just now noticed it when rebooting into Recovery from ROMs restart options. It is white, brown and orange with a list menu. I haven't seen this before though again I haven't flashed any other versions of TWRP besides the touch so maybe it's the standard? I did have TWRP ver 2.8.4.0 for this phone which was the grey, black and blue big button themed touch interface I loved so much.
Aside TWRP matters im also toying around with Lightwave-V3 Rom by user @root@ which I switched to from TigerLillly by user DJBoxer. Both seem to be pretty good although Lightwave was suppose to have came preconfigured with a bunch of useful utilities / mods and it appears they weren't configured in the Rom's configuration. I'll have to take a look and see what needs to be modified if they exist within the build seems same with TigerLilly also. I'd suggest these 2 ROMs to anyone with this phone. Smooth, no bloat and no problems so far. However I am always up for trying any others if anyone has some to suggest. Post and let me know.
First post back here in some months. Now back into androids more and attempting root on a few unknowns so hopefully I will have some good material to contribute in the near future. Still hitting that learning curve hard trying to get with the future. I'm still oldschool @ heart stuck with knowledge of the past flip / feature phones, java, crackberries, outdated unlocking boxes and about 100 pre android phones lol. Have the parts to the first android still but unfortunately incomplete. Some interesting times I tell ya. Thanks to XDA and HOFO I'm picking up where I left off quite quickly.
Lightwave - https://forum.xda-developers.com/galaxy-light/development/rom-lightwave-v1-t2825253
TigerLilly - https://forum.xda-developers.com/galaxy-light/development/rom-tigerlilly-v2-1-4-4-2-t3400659
I will post a TON of information on this phone, recovery, rooting, stock/custom rom links and much more in the appropriate thread when I get time free from work. Have done a lot of researching since this post. https://forum.xda-developers.com/galaxy-light - seems to have most of my work done lol. I keep forgetting how old this phone is and that it's been ran through by quite a few dev's already.
Click to expand...
Click to collapse
Thanks again! For conversions and archiving I have been using 7zip and a few simple batch files to convert .tar + calculate sum to .tar.md5 and and .img to .tar then .tar to .tar.md5 calculating sum.