Ok title say lots!.... I have all the lg drivers on my comp the adb sdk and java but it keeps saying java isn't in my path even after i have put it there.....windows 7.....anyone that can help it would be appreciated....oh and no i dun have any backups...i don't think....unless my nand is in my root somewhere.....been researching and messing with this for a week now... phone is operating fine but i would like a recovery and root back.. oh yeah gingerbreak doesn't work...stays on running exploit...rebooted multiple times same result
Try a different version of GingerBreak. Make sure you download it using WiFi so it doesn't have as much chance of becoming corrupt. After 12 min if it doesn't reboot your phone pull battery and try again. It might take as many as 5-6 tries.
The Following User Says Thank You to AndyOpie150 For This Useful Post:
oh and no i dun have any backups...i don't think....unless my nand is in my root somewhere
It doesn't quite work that way. If you did have a backup, it would be on your sd card in a folder called clockworkmod.
Originally Posted by defensitive
phone is operating fine but i would like a recovery and root back.. oh yeah gingerbreak doesn't work...stays on running exploit...rebooted multiple times same result
How did you lose your recovery? Or, how did you flash BACKside without a custom recovery? As for Gingerbreak, it will work, but some people have had to run it upwards of thirty times. That isn't very common, but has happened. Just be patient and keep trying. It's like throwing a sticky waffle at the ceiling, you need to just keep throwing it until it sticks. Remember to reboot your phone between every attempt, and don't try anything crazy to "speed things along," as you run the risk of doing very bad things to your phone.
here is my path C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoo t%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowe rShell\v1.0\;C:\Program Files (x86)\EgisTec\MyWinLocker 3\x86;C:\Program Files (x86)\EgisTec\MyWinLocker 3\x64;C:\Program Files (x86)\Windows Live\SharedC:\Users\Benjiro07\Downloads\SDK (1).zip\SDK\platform-tools;C:\Program Files\Java\jdk1.7.0_03\bin\java.exe.
underclockword mod i have...... .saltedhash... has a star on it and it is an executable file. .settings has a star but is not executable. backup has boot.img. recovery.img and system.img and under download folder in cwm is a bunch of -numbered files with stars on them....no option to execute.... this is using root explorer... also does anyone have a link to a diff. version of GB? i have been using the one in how to root without a computer
Last edited by defensitive; March 12th, 2012 at 08:37 AM.
used home vol. up and pwr to get to black recovery....installed new backside and gapps...waiting to see what happens....cool beans i installed my recovery through the updater....thanks! this has been a nightmare
Last edited by defensitive; March 14th, 2012 at 01:11 AM.
Defensitive, maybe you could elaborate on the exact step you took and the updater you used so that another new member that's having the same problem can understand enough to fix there problem based on what you did to fix yours.
The Following User Says Thank You to AndyOpie150 For This Useful Post:
Alrighty then.... First off....BACKUP before flashing anything! Tis true you can save yourself alot of headaches and time by backing up. It all began when I somehow hit a wrong button in clockwork recovery... I was stuck with a black recovery menu...well genius I am decided to un-root via gingerbreak. Not a good idea! So now i have no root, recovery and a custom Rom(Backside) Well after a while of debating whether or not to get another phone I decided to attempt fixing it. Gingerbreak would not re-root... like 20 times at 10 min. each and nada(diff. versions too). Then I decided to try the adb sdk for windows... after fooling with the java jdk path and installing adb and setting the platform tools path I d/l'd droid@screen.. set the adb executable path for it...and wala i can see my recovery. I first flashed the next to last backside rom then gapps then quicksilver. Somehow this gave me root back. I then attempted to flash_image from terminal enumerator... no go...tried from adb... no go. then Brother Swing told me the new backside had a flash recovery option. Downloaded it went into recovery through adb and droid@screen and flashed just the new backside....Good to go. Then went and flashed g apps. quicksilver seems to give me the same issue when i flash it...the boot loop issue. so i'm theme free right now...any ?'s happy to help. Thank you to Brother Swing and Andy Opie. Brother Swing any idea whats up with the quicksilver?....i kinda liked the theme
What Android OS version did your phone come with:2.2.1 or 2.2.2 ,this will help determine weather you have a Hitachi screen or a Novatek screen (some recovery's give the Hitachi screen a black screen in the recovery menu). What specific recovery:Name and version did you install the first time (so members who have you screen version can avoid it). Also, most recovery's will give you a black screen if you use the wrong button to make a selection (just hit it again to go back to the recovery menu and try another).
OK. That's the proper recovery for the Hitachi screen.
Next time you hit the wrong button and you get a black screen just hit it again and it will get you right back to the recovery menu.
I'm thinking this is what really happened to you the first time. You just didn't know that you just had to hit the same button again. I had this very same problem on my first recovery ( kept hitting the wrong buttons to make a selection) drove me crazy for a whole day until I saw a post about the same thing.
Our themes need to be built on the framework of the Rom, therefore they are version dependent. Look at the four digit number in the file name, that's what build of BACKside it's for. I just finished the update for 0313, I'll be uploading it sometime today. The apk version will work with any build, but isn't as complete.
I have a theme from the market that never needs re-doing. Have flashed numerous different ROM's and Updates with no problem getting the theme to take hold. Maybe you could pull it apart and figure out what they did to make it work across all the ROM's and updates that I've flashed. This would allow you to only have to make one particular theme, instead of the same theme over and over again. Honeycomb 3D-SB
I'm using my theme for more than six months with every single Backside build, no need for update. It is ICS theme from the market that I heavily modified to meet my needs.
And I don't update ROMs with full wipe. No any problems here.
I've been reverse engineering a theme called Elegant Steel I found on XDA. I've already learned a tremendous amount from my experiment, and once I have a proper Linux installation on my new laptop work will continue.
UOT Kitchen themes, and those found on the market are two different beasts.
Market themes work on the default Android theme system. They use what's already built into the system, and are limited by that system.
UOT Kitchen themes are basically hacking the frameworks-res and SystemUI apks. People have been doing this manually using apkmanager before UOT Kitchen was established. (btw- UOT Kitchen uses apkmanager as a back-end).
Since UOT Kitchen themes are built from the specific ROM's files, they will only work with that ROM and most often only the build they were made for (so long as no changes were made to frameworks-res or SystemUI, they will work across builds, but almost every build of BACKside has changes to those files ).
The Following User Says Thank You to JerryScript For This Useful Post: