Develop Bugs

[RECOVERY] Nexus S 4G CDMA recovery-clockwork-touch-5.8.0.2 [01-31-12]

Koushik Dutta's Clockwork Recovery:
Attention: Some people experience problems when flashing through Rom Manager. Flashing again usually fixes the issue. Use method below for best results. If on pure stock, your recovery will be overwritten unless you delete your /system/etc/install-recovery.sh file.
To flash recovery for Nexus S 4G, download recovery 5.0.2.0 or recovery touch 5.8.0.2 and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
or if you prefer the touch version:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo4g.img
If you'd like simpler and more organized menus see j_r0dd's mod.
rev 5.0.1.0 Fix android_ secure backup bug.
rev 5.0.2.0 Fix root loss. Correct message when choosing "no" when wiping dalvik.

Officiality

RSVP....
outstanding
Sent from my HP Touchpad using xda premium

Backups on 4.x going tto restore properly on 5.x?
Great work by the way.
Sent from my Nexus S 4G using XDA App

...or just go into the ROM Manager app and click on "Flash Clockworkmod Recovery", your version will update to 5 automatically.
Sent from my Nexus S 4G using xda premium

Also there's a app in the app section that flashes img files quicker than you can blink.
Flash_image by gui
Sent from my HP touchpad using xda premium

jakkz said:
...or just go into the ROM Manager app and click on "Flash Clockworkmod Recovery", your version will update to 5 automatically.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I had some issues doing it through rom manager. It was a no go so I flashed through bootloader.
I haven't checked if old backups are compatible yet. Anyone care to try and post?
Sent from my Nexus S 4G using XDA App

Every time I click on the update from inside ROM Manager, something terrible happens. I used think it was because I clicked on the link for the other Nexus S, but I was super duper careful this time.
If I try to reboot into recovery without being attached to my PC after flashing a new recovery in ROM Manager, I get stuck in fastboot. If I tell it to please boot me into recovery so can add a shiny new object to my Android, it tells me, "No ma'am." And, if im being honest, when I can't flash exciting new thingys on the go, existence begins to seem somewhat more futile. I'm sure you understand.
Might as well ask if there's a way I can fix it before I get home (in TEN HOURS) by fastbooting from a terminal or something. Okay, I'm begging.
p.s. I feel like I didn't get invited to most of Version 3 and all of Version 4.
Sent from my Nexus S 4G using xda premium

I had the same issue after using rom manager to flash 5. I just rebooted and tried flashing again from rom manager and it worked the second time
Sent from my Nexus S 4G using Tapatalk

jdkjgjjd said:
Might as well ask if there's a way I can fix it before I get home (in TEN HOURS) by fastbooting from a terminal or something. Okay, I'm begging.
p.s. I feel like I didn't get invited to most of Version 3 and all of Version 4.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Read the op. There is a reason why I gave instructions to flash through fastboot and not rom manager.

info[]box1 said:
Also there's a app in the app section that flashes img files quicker than you can blink.
Flash_image by gui
Sent from my HP touchpad using xda premium
Click to expand...
Click to collapse
This app worked great for me. Easy as 1,2,3

qbking77 said:
Backups on 4.x going tto restore properly on 5.x?
Great work by the way.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I can confirm they do work.

Trying to upgrade from 4.0.0.2 to 5.0.0.0, I keep getting stuck on "Waiting for device"..

If on windows...your driver is bad.
Try flash_image gui by Joeykrim

Well here is the thing, I can push/pull things from the device, I can adb shell to the device.. Everytime I try flash the recovery, I get the waiting for device

Well if on Windows, fastboot driver needs to be there along with adb.driver. Two different things

Didnt work through rom manager, had to do it via fastboot. I dig the new color!

so rom manager updated my cwm to this one and when i go to reboot into recovery it goes into bootloader and which i chose recovery nothing happens .... first line says FASTBOOT - NO RECOVERY OR BOOT IMG

For anybody having flashing/ pushing/ just getting the new cwm recovery use the flash_image by GUI app located in the ns4g app section. I can't stress it enough, but it your trying to computer up to speed for Android development I understand.
Sent from my HP Touchpad using xda premium

I updated through ROM Manager and it worked just fine. I believe as long as you are running the latest version of ROM Manager you shouldn't have any issues.

[HOW-TO] CMW on LTE Version through Rom Manager

If you have any questions, concerns or problems, please post in the CDMA post because I will no longer be checking here.

theboo7 said:
This is a guide on how to get ClockWorkMod onto your LTE Galaxy Nexus through Rom Manager
Go to market, search "Clockworkmod"
Install Rom Manager*
Open up Rom Manager and select "Flash ClockworkMod Recovery"
A pop-up will come up called "Confirm Phone Model," of course choose "Google Galaxy Nexus CDMA"
Now let it install etc, then with a File Manager** with SU access, Go to system, click "Mount R/W"(if using Root Explorer) and then scroll down until you see "recovery-from-boot.p" and rename it to "recovery-from-boot.p.bak"
Close out off your File Manager and go to Rom Manager and select "Reboot into Recovery"
There you go
You should be able to boot into CWM
* Free version works
**I used Root Explorer
Click to expand...
Click to collapse
For starters that file doesnt exist under the directory "system"

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
By "that file" I'm assuming you are referring to "recovery-from-boot.p" ?

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.

staticx57 said:
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.
Click to expand...
Click to collapse
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw

theboo7 said:
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw
Click to expand...
Click to collapse
I had to do this same thing on stock to keep the stock recovery from restoring.

jermaine151 said:
I had to do this same thing on stock to keep the stock recovery from restoring.
Click to expand...
Click to collapse
Yeah it's a known bug, that's hopefully getting worked on.

Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk

dc iz 2 legit said:
Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Then you would follow the steps in the OP

What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?

Xirix12 said:
What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?
Click to expand...
Click to collapse
Flashing through ROM Manager is just a simpler way to get CWM. And I'm not sure why you would have gotten the red triangle, unless you didn't rename/delete the file in system. And I haven't heard anyone say the couldn't do anything in recovery, so I'm not sure what the problem is there.

When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM

theboo7 said:
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM
Click to expand...
Click to collapse
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Okay, so glad that you got it sorted out
Sent from my Galaxy Nexus using XDA App

this step by step process was incredibly easy. thank you!!!

reflekt2099 said:
this step by step process was incredibly easy. thank you!!!
Click to expand...
Click to collapse
Your welcome
Sent from my Galaxy Nexus using XDA App

Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk

Xirix12 said:
Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yeah, that file can cause problems with CWM on LTE, although it's a quick fix, I'm sure it's being worked on for future editions. And since you've been able to flash things, when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.

theboo7 said:
when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.
Click to expand...
Click to collapse
Same here. You gotta go slow. I selected the wrong option many times.

JB OTA won't install- says install untrusted zip? in cwm

I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app

Your phone is rooted? If yes you can't install OTA updates

I'm rooted yes. So what do I do? Unroot?
Sent from my Galaxy Nexus using xda app-developers app

htc_woe_is_me said:
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
polimeno said:
Your phone is rooted? If yes you can't install OTA updates
Click to expand...
Click to collapse
Not true. Root makes no difference.

efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
So either way I will lose all my settings, home screens and what not?
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?

efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
It's exact. But root can only be done if you have bootloader unlocked, and with unlocked bootloader can not install OTA updates

htc_woe_is_me said:
So either way I will lose all my settings, home screens and what not?
Click to expand...
Click to collapse
No, updating using an OTA update file will NOT make you lose anything.
htc_woe_is_me said:
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
Click to expand...
Click to collapse
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.

efrant said:
No, updating using an OTA update file will NOT make you lose anything.
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
Click to expand...
Click to collapse
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.

htc_woe_is_me said:
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
Click to expand...
Click to collapse
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img

efrant said:
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?

htc_woe_is_me said:
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
Click to expand...
Click to collapse
Gnex Toolkit wasn't working because of some missing file... re-installed it and flashed the stock recovery via Gnex Toolkit (I think). Is there a way to check which recovery is running? Anyway, if it is indeed stock, I just got prompted again for the OTA JB update.. it's installing now.... fingers crossed!!!
..OK so now it rebooted... started installing, got about halfway through.. paused, then it went to the stock recovery screen and stayed with a red triangle around an exclamation point! What is happening here?!
I have now re-locked the bootloader and received the prompt for OTA again....

Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app

htc_woe_is_me said:
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Follow the instructions in the "update" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

Guys i am having this EXACT problem, except on a S4 (I337M to be exact)
Here is my thread with the details
http://forums.androidcentral.com/as...t-update-ota-failure-using-triangle-away.html
But basically, im just wondering how i can get stock recovery back and get this ota to work!!!
Thanks!

[Q] "Error: Device not found" in adb.

Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.

Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom

Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks

Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.

Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again

Please read carefully what i write, i know exactly what to do !
You need a custom recovery !

Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.

If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.

And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.

Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?

Yes and plz post results
Sent from my GT-I8190 using xda app-developers app

robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.

Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.

Yay congrats
Sent from my GT-I8190 using xda app-developers app

And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot

Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.

Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app

[Q] Recovery Trouble, Please Help :(

I put TWRP Recovery on my LS970 and tried flashing the Liquid Jelly Bean ROM on and it ended up with just pure stress. Before I flashed it I had wiped the dalvik and normal cache and even factory reset it before flashing and it said it installed correctly. I restarted my phone (and I do have an unlocked boot loader and recovery of course) and it was stuck on the Google unlocked boot picture. I tried flashing it again and Ive used LGNPST and LG Flashtool and none helped. I was wondering if there is a possible solution to this perhaps I could send a flashable zip through my computer? Please help

ETR174 said:
I put TWRP Recovery on my LS970 and tried flashing the Liquid Jelly Bean ROM on and it ended up with just pure stress. Before I flashed it I had wiped the dalvik and normal cache and even factory reset it before flashing and it said it installed correctly. I restarted my phone (and I do have an unlocked boot loader and recovery of course) and it was stuck on the Google unlocked boot picture. I tried flashing it again and Ive used LGNPST and LG Flashtool and none helped. I was wondering if there is a possible solution to this perhaps I could send a flashable zip through my computer? Please help
Click to expand...
Click to collapse
So do you have recovery or fastboot now? If you LGNPST you should be locked and have stock recovery.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
So do you have recovery or fastboot now? If you LGNPST you should be locked and have stock recovery.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It has TWRP recovery and has fastboot. When I try LGNPST its stuck at 1% and it says verifying files. I waited 30 minutes and it was still there.

ETR174 said:
It has TWRP recovery and has fastboot. When I try LGNPST its stuck at 1% and it says verifying files. I waited 30 minutes and it was still there.
Click to expand...
Click to collapse
Do you have any other roms on your SD? If not, try to adb sideload a stockish ROM. Adb sideload is on first page of this. http://forum.xda-developers.com/showthread.php?t=2082084
Edit. Have you tried reflashing your ROM? This time wipe system, dalvic, cache, and data. NOT INTERNAL data. That's your SD.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
Do you have any other roms on your SD? If not, try to adb sideload a stockish ROM. Adb sideload is on first page of this. http://forum.xda-developers.com/showthread.php?t=2082084
Edit. Have you tried reflashing your ROM? This time wipe system, dalvic, cache, and data. NOT INTERNAL data. That's your SD.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I only have that and GApps. And for adb you have to have usb debugging on right? I dont.

ETR174 said:
I only have that and GApps. And for adb you have to have usb debugging on right? I dont.
Click to expand...
Click to collapse
You'd said you had liquid installed and LGNPST failed, so liquid should still be installed. So in recovery, wipe those 4, flash liquid then gapps and see if it works. Then we'll go from there.
Sent from my LG-LS970 using XDA Premium 4 mobile app

Ok. Ill give you pictures of the end processes too.
Edit: Well I cant give you pictures but I wiped the four and my phone is stuck on the Google unlocked boot.

ETR174 said:
Ok. Ill give you pictures of the end processes too.
Edit: Well I cant give you pictures but I wiped the four and my phone is stuck on the Google unlocked boot.
Click to expand...
Click to collapse
So you did the wipes, installed liquid, installed gapps, then rebooted and are stuck. Do you have ADB installed? If so DL this TWRP. http://www.androidfilehost.com/?fid=22909751817929287.
Extract the recovery image using 7zip.
Boot your phone into fastboot/bootloader Then cd to the folder the image is in. Then issue this command.
"fastboot flash recovery recovery.img"
You may need to do this first. "fastboot erase recovery" then "fastboot flash recovery recovery.img"
If your not comfortable doing this, just google fastboot and you'll find info on how to do it. This thread seems pretty thorough. http://forum.xda-developers.com/showpost.php?p=41374534&postcount=1
Then go here, http://forum.xda-developers.com/showpost.php?p=36270473&postcount=1 to ADB sideload a Stockish Rom
If this doesn't work then you'll probably end up having to use LGNPST

engine95 said:
So you did the wipes, installed liquid, installed gapps, then rebooted and are stuck. Do you have ADB installed? If so DL this TWRP. http://www.androidfilehost.com/?fid=22909751817929287.
Extract the recovery image using 7zip.
Boot your phone into fastboot/bootloader Then cd to the folder the image is in. Then issue this command.
"fastboot flash recovery recovery.img"
You may need to do this first. "fastboot erase recovery" then "fastboot flash recovery recovery.img"
If your not comfortable doing this, just google fastboot and you'll find info on how to do it. This thread seems pretty thorough. http://forum.xda-developers.com/showpost.php?p=41374534&postcount=1
Then go here, http://forum.xda-developers.com/showpost.php?p=36270473&postcount=1 to ADB sideload a Stockish Rom
If this doesn't work then you'll probably end up having to use LGNPST
Click to expand...
Click to collapse
Thanks but I really dont understand adb. What needs to happen on the phone end in order to use adb? And for the computer?

ETR174 said:
Thanks but I really dont understand adb. What needs to happen on the phone end in order to use adb? And for the computer?
Click to expand...
Click to collapse
Read that link above and it explains adb and fastboot
But if you're not comfortable with that then just LGNPST
Go to the teeny bin thread under "Additional info" and follow the LGNPST walkthru.

engine95 said:
Read that link above and it explains adb and fastboot
But if you're not comfortable with that then just LGNPST
Go to the teeny bin thread under "Additional info" and follow the LGNPST walkthru.
Click to expand...
Click to collapse
Oh I forgot to mension that I did flash teeny bot with LGNPST but this cane with the SBL. Should I download a different version and try flashing again with LGNPST?

ETR174 said:
Oh I forgot to mension that I did flash teeny bot with LGNPST but this cane with the SBL. Should I download a different version and try flashing again with LGNPST?
Click to expand...
Click to collapse
Ok now we're getting somewhere.
When you used teeny bins, it installed the wrong version of TWRP to use with KK Roms. In your recovery is the version 2.6.0.0?
The easiest way to change that recovery is to use fastboot and install a KK version 2.6.3.3. You can find those in the TWRP thread or the root guide under Working recoveries.
You can also use CWM recovery if you want
So follow what is posted above, install a KK recovery, then you should be able to install Liquid.

engine95 said:
Ok now we're getting somewhere.
When you used teeny bins, it installed the wrong version of TWRP to use with KK Roms. In your recovery is the version 2.6.0.0?
The easiest way to change that recovery is to use fastboot and install a KK version 2.6.3.3. You can find those in the TWRP thread or the root guide under Working recoveries.
You can also use CWM recovery if you want
So follow what is posted above, install a KK recovery, then you should be able to install Liquid.
Click to expand...
Click to collapse
I mean I used Freegee to unlock the bootloader and install TWRP Version 2.6.0.0 and from what it sounds like there is a lot of problems with it. Could I flash CWM or a newer version of TWRP with LGNPST?

If you use LGNPST you'll be back to Factory stock. Recovery included. There's no way to install another recovery until to root/unlock
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
If you use LGNPST you'll be back to Factory stock. Recovery included. There's no way to install another recovery until to root/unlock
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well do you know any reason why it stays at 1% verifing files? Or any fixes to it?

ETR174 said:
Well do you know any reason why it stays at 1% verifing files? Or any fixes to it?
Click to expand...
Click to collapse
Are you selecting the right DLL? Using either ZVB or ZVC bin?
Other than that, I don't know. Maybe you need to uninstall then reinstall the LG drivers or LGNPST.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
Are you selecting the right DLL? Using either ZVB or ZVC bin?
Other than that, I don't know. Maybe you need to uninstall then reinstall the LG drivers or LGNPST.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont know let me go check. I thought it had something to do with the phone not the dll or bin files.

It must be the bin file because I flashed teeny bin just fine with the dll

Im an idiot. Turns out that the firmware was in a cab file which was supposed to be extracted into a bin file. It got deleted to I downloaded a stock bin from your android file host profile and Im going to flash in just a minute and tell you the results.

ETR174 said:
Im an idiot. Turns out that the firmware was in a cab file which was supposed to be extracted into a bin file. It got deleted to I downloaded a stock bin from your android file host profile and Im going to flash in just a minute and tell you the results.
Click to expand...
Click to collapse
No worries. I can't remember where that bin file gets extracted to, but if you're downloading the bin that's fine too. I forgot to mention that ZVC is the most current, but if you have ZVB that's fine if you're gonna run CM/AOSP
Sent from my LG-LS970 using XDA Premium 4 mobile app