I downloaded a flashable zip of dsp manager, can I rename to update.zip and flash through stock recovery?
currently I am running (sprint) stock jelly bean rom JRO03U FH05 rooted (only rooted to flash dsp through cwm) and Ive been noticing data drops for long periods and want to unroot incase I need to go to the store but I want to keep dsp manager and any unroot method I see will wipe it out.
edit: ive found that when I have a lengthy data drop toggling wifi on and off re-establishes the 3g connection. Anyone think they know what my problem is?
No
Sent from my Galaxy Nexus using xda premium
airtime82 said:
I downloaded a flashable zip of dsp manager, can I rename to update.zip and flash through stock recovery?
currently I am running (sprint) stock jelly bean rom JRO03U FH05 rooted (only rooted to flash dsp through cwm) and Ive been noticing data drops for long periods and want to unroot incase I need to go to the store but I want to keep dsp manager and any unroot method I see will wipe it out.
edit: ive found that when I have a lengthy data drop toggling wifi on and off re-establishes the 3g connection. Anyone think they know what my problem is?
Click to expand...
Click to collapse
Stock recovery cannot flash, you need a custom one for that.
As for your data drops: have you tried verifying your APN settings? Tried a different radio?
Petrovski80 said:
Stock recovery cannot flash, you need a custom one for that.
As for your data drops: have you tried verifying your APN settings? Tried a different radio?
Click to expand...
Click to collapse
ive tried different roms, odining to stock, different radios, and different kernels. are the apns just like your "mobile network type",ip address, MEID, etc? thanks for the response.
Edit: So what you say about the recovery means I cant have dsp manager without being rooted? Or can I flash cwm or twrp by just changing the recovery files and flashing a recovery img without root?
Couldn't you just turn on USB debugging, connect to your PC, "fastboot boot (somecustomrecovery).IMG", and use it to flash the dspmanager.zip?
BTW, to unroot, all you have to do is delete "su" and "supersu.apk" (or "superuser.apk" if you're using that).
strumcat said:
Couldn't you just turn on USB debugging, connect to your PC, "fastboot boot (somecustomrecovery).IMG", and use it to flash the dspmanager.zip?
BTW, to unroot, all you have to do is delete "su" and "supersu.apk" (or "superuser.apk" if you're using that).
Click to expand...
Click to collapse
usb debugging is on by default on custom recoveries, and it's not needed for fastboot as well.
sent from my i9250
ive tried different roms, odining to stock, different radios, and different kernels. are the apns just like your "mobile network type",ip address, MEID, etc? thanks for the response.
Edit: So what you say about the recovery means I cant have dsp manager without being rooted? Or can I flash cwm or twrp by just changing the recovery files and flashing a recovery img without root?
Click to expand...
Click to collapse
Yes you can, if a flashable zip of DSP manager exists (I'm not sure). Just boot or flash a custom recovery (CWM or TWRP indeed), and use it to flash the DSP manager zip.
Couldn't you just turn on USB debugging, connect to your PC, "fastboot boot (somecustomrecovery).IMG", and use it to flash the dspmanager.zip?
BTW, to unroot, all you have to do is delete "su" and "supersu.apk" (or "superuser.apk" if you're using that).
Click to expand...
Click to collapse
ADB is not fastboot. ADB is an interface provided by Android OS and custom recoveries, Fastboot is an interface provided by the bootloader.
bk201doesntexist said:
usb debugging is on by default on custom recoveries, and it's not needed for fastboot as well.
Click to expand...
Click to collapse
Petrovski80 said:
ADB is not fastboot. ADB is an interface provided by Android OS and custom recoveries, Fastboot is an interface provided by the bootloader.
Click to expand...
Click to collapse
Derp... 'k, thanks.
Thanks for all the responses guys. I couldn't shake the data drops on the ota and sprint didn't know what to tell me over the phone so I just backed up odined fho5 complete and data is now working completely. As for not needing root yes I took your advice fast booted cwm, flashed DSP manager then just flashed the stock recovery back.
Sent from my stock jb machine
airtime82 said:
Thanks for all the responses guys. I couldn't shake the data drops on the ota and sprint didn't know what to tell me over the phone so I just backed up odined fho5 complete and data is now working completely. As for not needing root yes I took your advice fast booted cwm, flashed DSP manager then just flashed the stock recovery back.
Sent from my stock jb machine
Click to expand...
Click to collapse
Nice one. :good:
airtime82 said:
Thanks for all the responses guys. I couldn't shake the data drops on the ota and sprint didn't know what to tell me over the phone so I just backed up odined fho5 complete and data is now working completely. As for not needing root yes I took your advice fast booted cwm, flashed DSP manager then just flashed the stock recovery back.
Sent from my stock jb machine
Click to expand...
Click to collapse
just one thing: you didnt need to flash cwm, just boot it:
Code:
fastboot boot cwm_or_twrp.img
this way you keep whatever recovery is installed, allows you to try out stuff, without really flashing them.
sent from my i9250
bk201doesntexist said:
just one thing: you didnt need to flash cwm, just boot it:
Code:
fastboot boot cwm_or_twrp.img
this way you keep whatever recovery is installed, allows you to try out stuff, without really flashing them.
sent from my i9250
Click to expand...
Click to collapse
I didn't even know you could do that? Sooooo how do you just boot it?
Sent from my Galaxy Nexus using xda app-developers app
airtime82 said:
I didn't even know you could do that? Sooooo how do you just boot it?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
bk201doesntexist said:
fastboot boot cwm_or_twrp.img
Click to expand...
Click to collapse
:cyclops:
3rdstring said:
:cyclops:
Click to expand...
Click to collapse
Reading comprehension is hard
Sent from my Galaxy Nexus using Tapatalk 2
3rdstring said:
:cyclops:
Click to expand...
Click to collapse
Whoops didn't even notice it said that too. I skim a lot while using my phone. Sorry.
Sent from my Galaxy Nexus using xda app-developers app
Related
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.
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!
Installed a app to change transitions, chose my transition, and it asked to reboot, so i did it, but now, it stays on rebooting screen :'(
Can this be fixed? i unlocked bootloader and flashed recovery and can ge tinto recovery mode but i can´t access the phone.. I'm panicked rlly :'(
Sorry, i know I'm a noob in this topics.. If you could help me i can give you my skype also..
Thanks
Paul
paulo111 said:
Installed a app to change transitions, chose my transition, and it asked to reboot, so i did it, but now, it stays on rebooting screen :'(
Can this be fixed? i unlocked bootloader and flashed recovery and can ge tinto recovery mode but i can´t access the phone.. I'm panicked rlly :'(
Sorry, i know I'm a noob in this topics.. If you could help me i can give you my skype also..
Thanks
Paul
Click to expand...
Click to collapse
If you have a custom ROM installed just wipe cache and dalvik... reflash that ROM and gapps and reboot
EDIT: always make a nandroid backup when ever you flash something you are not 100% sure it will work on your device
Sent from my Galaxy Nexus using xda premium
NORCALkID said:
If you have a custom ROM installed just wipe cache and dalvik... reflash that ROM and gapps and reboot
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I didn't change anything in the roms, i have the original rom installed never done a backup or installed a other rom..
I didn't do it, should have known that before... is there no way out now?
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
Did you use a toolkit to unlock boot loader? You could use one to reflash a stock image ? Or push an update.zip over USB and flash from recovery ?
daz.g said:
Did you use a toolkit to unlock boot loader? You could use one to reflash a stock image ? Or push an update.zip over USB and flash from recovery ?
Click to expand...
Click to collapse
I used toolkit to unlock boot loader yeah, add me on skype that way i can tell you what i did, i'm not very good in this area idk how to do those things you said :\ Sorry
3rdstring said:
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
Click to expand...
Click to collapse
Can i do this without being able to go to homescreen? only from recovery?
Maybe somebody can assist me via skype and tell me what to do? I really don't know what to do :'(
I feel so stupid right now.. Hope some1 can help me.
Skype is: hoepaulo
paulo111 said:
Maybe somebody can assist me via skype and tell me what to do? I really don't know what to do :'(
I feel so stupid right now.. Hope some1 can help me.
Skype is: hoepaulo
Click to expand...
Click to collapse
read the link that was posted to you by 3rdstring
You have a couple options here. Two that pop into my head immediately are download a custom ROM make sure it is for whatever device you have I.e. maguro, toro, toroplus. Boot into recovery and follow the directions in the ROM thread to install. Or download the stock images for your device and boot into bootloader and fastboot flash those. There are guides everywhere to do this.
Edit: forgot to mention that in recovery if going the ROM route you need to get that ROM. zip onto your SD card. Do it by mounting SD card in storage and adb push the zip to /sdcard.
Sent from my Galaxy Nexus using xda premium
Going back to the stock may help you after wiping dalvik cache.
Sent from my Galaxy Nexus using xda premium
Beamer9408 said:
Edit: forgot to mention that in recovery if going the ROM route you need to get that ROM. zip onto your SD card. Do it by mounting SD card in storage and adb push the zip to /sdcard.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This doesnt work on our device. In recovery, push files with adb to /data/media/.
Sent from my i9250
I need some help, today sundally my Gnex turned off while I was using it as a camera, now it is on a boot loop, I'm o Cm10.1 whith AK256 Kernel. I tried to wipe data, cache.... Reeinstaled CM10.1 and nothing, Purity ROM and nothing, I really don't know what to do. I'm traveling and now using just the iPod for everything :/
GiulioPasini said:
I need some help, today sundally my Gnex turned off while I was using it as a camera, now it is on a boot loop, I'm o Cm10.1 whith AK256 Kernel. I tried to wipe data, cache.... Reeinstaled CM10.1 and nothing, Purity ROM and nothing, I really don't know what to do. I'm traveling and now using just the iPod for everything :/
Click to expand...
Click to collapse
Try to format system then flash custom rom.
If not, flash stock images.
Sent from my Galaxy Nexus using xda premium
May be a kernel problem.
Get correct kernel and flash it.
or
Get stock image and flash it from https://developers.google.com/android/nexus/images
Seems a kernel problem to me rather than a ROM problem. Try flashing another kernel like Franco or Fancy, and then dirty flash your current ROM over it. And ya, don't forget to wipe dalvik cache!!
Happened to me a long while ago and above method solved it for me.
Sent from my Galaxy Nexus using XDA Premium HD app
rajatpatel2009 said:
Seems a kernel problem to me rather than a ROM problem. Try flashing another kernel like Franco or Fancy, and then dirty flash your current ROM over it. And ya, don't forget to wipe dalvik cache!!
Happened to me a long while ago and above method solved it for me.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Huh? If you flash a ROM after a custom kernel, the ROM kernel will overwrite the custom kernel.. What's the point?
OP, it's probably data corruption OR messed up permissions. first option is fixing permissions in your custom recovery. Reboot. If that doesn't boot fully, format userdata or reflash stock through fastboot.
Sent from my Nexus
bk201doesntexist said:
Huh? If you flash a ROM after a custom kernel, the ROM kernel will overwrite the custom kernel.. What's the point?
OP, it's probably data corruption OR messed up permissions. first option is fixing permissions in your custom recovery. Reboot. If that doesn't boot fully, format userdata or reflash stock through fastboot.
Sent from my Nexus
Click to expand...
Click to collapse
I reflashed the stock rom using the Gnextoolkit and it win´t boot againg, now i will try to flash cm and see what happens
bk201doesntexist said:
Huh? If you flash a ROM after a custom kernel, the ROM kernel will overwrite the custom kernel.. What's the point?
OP, it's probably data corruption OR messed up permissions. first option is fixing permissions in your custom recovery. Reboot. If that doesn't boot fully, format userdata or reflash stock through fastboot.
Sent from my Nexus
Click to expand...
Click to collapse
I'm so sorry, made a typo there. Here I would like to clarify to OP that first dirty flash the ROM so that any files modified by your previous faulty kernel would be changed and than flash a new kernel over it!!
Again sorry for my previous misleading post. I apologize for that.
GiulioPasini said:
I reflashed the stock rom using the Gnextoolkit and it win´t boot againg, now i will try to flash cm and see what happens
Click to expand...
Click to collapse
Paste the exact fastboot commands you're using. I'm not helping a user that uses a toolkit to interact with his device, as I don't know where is it failing.
I installed CM yesterday, it boots but I can't stay with the screen on, if I use it for 3 minutes on my phone reboot. Tonight I will do everything again with the ToolKit, back to stock again but now cleaning all the data and I will relock the bootloader :/ That's really sad.
GiulioPasini said:
I installed CM yesterday, it boots but I can't stay with the screen on, if I use it for 3 minutes on my phone reboot. Tonight I will do everything again with the ToolKit, back to stock again but now cleaning all the data and I will relock the bootloader :/ That's really sad.
Click to expand...
Click to collapse
please stop with the toolkit. its prolly failing somewhere.
if you use the fastboot commands, me or bk201doesntexist will help.
Zepius said:
please stop with the toolkit. its prolly failing somewhere.
if you use the fastboot commands, me or bk201doesntexist will help.
Click to expand...
Click to collapse
Thanks very much. Now, should I do what efrant's guide for returning to stock says?
GiulioPasini said:
Thanks very much. Now, should I do what efrant's guide for returning to stock says?
Click to expand...
Click to collapse
Yes, please. Copy and Paste all the console commands and their output to a service like Pastebin and post the link.
Sent from my Nexus
bk201doesntexist said:
Yes, please. Copy and Paste all the console commands and their output to a service like Pastebin and post the link.
Sent from my Nexus
Click to expand...
Click to collapse
Thanks very much!! Now my Gnex is running the stock rom very well (but I will come back to CM, I can´t resist )
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