Related
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Can you boot in to recovery or bootloader (holding power+vol down)?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
That I can
mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Put the stock odexed rom from my thread in development section in your adb/fastboot directory on your PC.
Enter Recovery, assuming you installed a custom recovery.
If not, do that first, using the links in Flyhalfs threads in our Verizon One Original Dev section.
In Recovery go to Advanced in TWRP I believe and do adb sideload > swipe to sideload.
Then you will need to enter in terminal: adb sideload filename.zip from within the fastboot directory with the stock file in that same directory.
Use the filename of the zip you are sideloading. Once its done pushing, it will flash the rom and then you can reboot.
I had tried straight off after the root to install CWM and it gave the option to do TWRP. I had a blank black screen and then kind of stalled so I forced it into the bootloader screen and just reset. In the present time if I attempt the recovery selection it just stalls again, a black yet obviously backlit screen. My new download of ADB does not look the same as it had when I did the last phone either. I don't know what I've fouled up here.
I'll send it out at this point to make the pain go away and have someone undo it.
mySStery_machine said:
I'll send it out at this point to make the pain go away and have someone undo it.
Click to expand...
Click to collapse
I can try and walk you through getting fastboot or adb set up so that you can try fixing it on your end.
It's also pretty well laid out in guides on Google.
If you really wanted to have it fixed for you, I'm about 12 hours or so south of where you are if you wanted to mail it here and back.
Up to you, hit me up via PM if you decide you wanna mail it.
Otherwise, myself and/or others will gladly help you undo it I'm sure man.
Then you wouldn't have to be without it for a few days.
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
mySStery_machine said:
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
Click to expand...
Click to collapse
Sounds good, I'll shoot you my gmail/Hangout info and we can get you squared away I'm sure.
Yeah, I'm up above there just a little, about 2 and a half hours or so from there.
Sounds good, I'm ready to tackle tonight whenever and for however long it takes.
Ok, have deleted and redownloaded the ADB files, yours as well as the TWRP. I have the recovery and your file chilling out in C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools . What now my new found savior?
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
mySStery_machine said:
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
Click to expand...
Click to collapse
Double check the md5 of the downloaded file.
Also shorten the path to the file, at least the folder names leading up to it, so that it's more direct.
Less chance of error or too deep of a path.
Something Like:
C:\Android\sdk\sdk\platform-tools>adb sideload 1.10.605.15_Deodex_Full.zip
Click to expand...
Click to collapse
You will have to rename a directory and a file or so to get it like that and this may not be the issue, but should certainly eliminate potential for issues.
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
mySStery_machine said:
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
Click to expand...
Click to collapse
Yeah try that, you may need to grab HTC Sync and install it if you haven't if your existing drivers aren't cooperating.
MD5 was corrupt, I finally got it to push.
Used pdaNet for drivers.
mySStery_machine said:
Used pdaNet for drivers.
Click to expand...
Click to collapse
Cool, glad that worked.
If you have any further issues or success, let me know.
Sounds like you should be good to go though.
Downloading another version to see if I can get the info across and get this One cooking again!
So should I do the other .zips below the post with your links for the firmware?
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Penley94 said:
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Click to expand...
Click to collapse
The key here is going to be getting back into recovery. Have you tried getting into Download Mode? If you saw the LG logo then you SHOULD be able to get into download mode. Make sure the phone is completely powered off. Connect the USB to your pc but before you connect the other end to your phone, hold volume up then connect it. You should see "Download Mode" on the screen. You will see other directions for download mode but for me this always works, usb to pc, hold volume up then plug the phone in while still holding the volume up. If you can get into Download Mode you can flash a teenybin to get back into recovery following the guide in this thread here.
Currently even if you can get into Download Mode adb might not recognize your phone(at least it never did for me). Once you flash a teenybin using LGNPST, you should be able to get into Recovery. Once in Recovery you can use adb to pull your files off of the phone and onto your computer. I use it from a linux terminal but there are guides available for Windows if that's what you use. The adb guide should be easy to find on xda(just search) so I haven't linked to it. Once adb is set up on your computer AND you can get into Recovery you can use the command 'adb pull /data/media' without quotations and it will copy the contents of your internal storage to your pc. However if you can get into recovery you do have other options for just getting the phone back up and running. This guide here should also help.
If you are familiar with irc(internet relay chat) you can hop onto freenode and enter the #lg-optimus-g channel. As soon as you enter the channel you will see "Need Help? You won't read this but..." followed by a link. All the files for LGNPST, teenybins, and in depth tutorials on fixing a soft brick will be found there. I hope this helps you and hooray for me because this is my 200th post!
PS - If you can't get into Download Mode then your secondary bootloader is gone and there isn't anything you can do(to my knowledge). However, like I said, if you saw the LG logo at all, Download mode should still be an option. Also keep in mind these instructions are for the Sprint(ls970) lg optimis g. I believe the keys are flipped on AT&T/International models(Volume Down when you plug it in to get to Download Mode).
HPTesla said:
The key here is going to be getting back into recovery. Have you tried getting into Download Mode? If you saw the LG logo then you SHOULD be able to get into download mode. Make sure the phone is completely powered off. Connect the USB to your pc but before you connect the other end to your phone, hold volume up then connect it. You should see "Download Mode" on the screen. You will see other directions for download mode but for me this always works, usb to pc, hold volume up then plug the phone in while still holding the volume up. If you can get into Download Mode you can flash a teenybin to get back into recovery following the guide in this thread here.
Currently even if you can get into Download Mode adb might not recognize your phone(at least it never did for me). Once you flash a teenybin using LGNPST, you should be able to get into Recovery. Once in Recovery you can use adb to pull your files off of the phone and onto your computer. I use it from a linux terminal but there are guides available for Windows if that's what you use. The adb guide should be easy to find on xda(just search) so I haven't linked to it. Once adb is set up on your computer AND you can get into Recovery you can use the command 'adb pull /data/media' without quotations and it will copy the contents of your internal storage to your pc. However if you can get into recovery you do have other options for just getting the phone back up and running. This guide here should also help.
If you are familiar with irc(internet relay chat) you can hop onto freenode and enter the #lg-optimus-g channel. As soon as you enter the channel you will see "Need Help? You won't read this but..." followed by a link. All the files for LGNPST, teenybins, and in depth tutorials on fixing a soft brick will be found there. I hope this helps you and hooray for me because this is my 200th post!
PS - If you can't get into Download Mode then your secondary bootloader is gone and there isn't anything you can do(to my knowledge). However, like I said, if you saw the LG logo at all, Download mode should still be an option. Also keep in mind these instructions are for the Sprint(ls970) lg optimis g. I believe the keys are flipped on AT&T/International models(Volume Down when you plug it in to get to Download Mode).
Click to expand...
Click to collapse
Thank you for the response, i just tryed to get in to download mode and it went in to it fine. I would try to do all that to repair it but I dont want sprint to see that its rooted and it I cant have it be fixed when the new phone comes in, the only thing that i want is to get my files from it. Is there any way that I can just do that but leave the phone the way it is? (Not booting up passed the lg logo) I want the new phone because my current Optimus G's battery is going pretty bad I think and I would like a new one.
Penley94 said:
Thank you for the response, i just tryed to get in to download mode and it went in to it fine. I would try to do all that to repair it but I dont want sprint to see that its rooted and it I cant have it be fixed when the new phone comes in, the only thing that i want is to get my files from it. Is there any way that I can just do that but leave the phone the way it is? (Not booting up passed the lg logo) I want the new phone because my current Optimus G's battery is going pretty bad I think and I would like a new one.
Click to expand...
Click to collapse
There are plenty of ways to get it stuck at the lg logo, sometimes it happens just from dirty flashing a rom, sometimes because you install a rom without wiping dalvik/cache. But you should know if you are on Sprint, one of the reasons I stick with them(even though their coverage is horrible in my area) is because rooting DOES NOT void your warranty with Sprint. They will warn you against it but they are the only carrier that allows rooting and will still fix your phone. Here is some info on that here. They won't advertise it but it's the truth. But bricking your phone intentionally is pretty easy I think. After getting back your data, just go into recovery and start deleting stuff you normally wouldn't. It's similar to opening up your car's hood and saying "This looks important" and ripping it out, lol. At this point that's what I would do, fixing your rooted phone is within their warranty, replacing it(which is what you want) I'm not 100% on. Although the post I linked to, says even ordering a replacement on a rooted phone is covered. Its in a reply on that page, you'll see another link. So you could get your info, use a different LGNPST file to set your phone back to factory(which will relock the bootloader and lose root) and then you can do what you did to get there in the first place or root it and start deleting important files with a root explorer to get it back to being stuck. Hope this helps.
HPTesla said:
There are plenty of ways to get it stuck at the lg logo, sometimes it happens just from dirty flashing a rom, sometimes because you install a rom without wiping dalvik/cache. But you should know if you are on Sprint, one of the reasons I stick with them(even though their coverage is horrible in my area) is because rooting DOES NOT void your warranty with Sprint. They will warn you against it but they are the only carrier that allows rooting and will still fix your phone. Here is some info on that here. They won't advertise it but it's the truth. But bricking your phone intentionally is pretty easy I think. After getting back your data, just go into recovery and start deleting stuff you normally wouldn't. It's similar to opening up your car's hood and saying "This looks important" and ripping it out, lol. At this point that's what I would do, fixing your rooted phone is within their warranty, replacing it(which is what you want) I'm not 100% on. Although the post I linked to, says even ordering a replacement on a rooted phone is covered. Its in a reply on that page, you'll see another link. So you could get your info, use a different LGNPST file to set your phone back to factory(which will relock the bootloader and lose root) and then you can do what you did to get there in the first place or root it and start deleting important files with a root explorer to get it back to being stuck. Hope this helps.
Click to expand...
Click to collapse
Oh wow I never knew that but that helps a lot thanks for the help, the sprint guy said theydid a master reset or hard reset or soemthing like that, does that mean it deleted all my pictures and everything? And i understand what you mean to rebrick it that's pretty simple. When i get my new optimus is there a new root out for the update? And what roms do you prefer?
Penley94 said:
Oh wow I never knew that but that helps a lot thanks for the help, the sprint guy said theydid a master reset or hard reset or soemthing like that, does that mean it deleted all my pictures and everything? And i understand what you mean to rebrick it that's pretty simple. When i get my new optimus is there a new root out for the update? And what roms do you prefer?
Click to expand...
Click to collapse
If they did a hard reset it is possible that it wiped everything but not a definite. I purchased my phone from Best Buy and was on zvb. When the zvc update came through it messed my phone up(which is why you don't take OTA's once rooted without further knowledge/modifications) so I took it to Best Buy and they said they did a hard reset to fix it. It worked, my phone booted back up and my internal was fine. However, that's Best Buy and they barely know what they are doing so it may have been a soft reset, I am not 100% sure. As for a new root for the update, I received another phone shortly after because the glass back on mine broke and Best Buy replaced it with a whole new phone. It was on zvc and I used an app named Framaroot with the Gandalf exploit option and it worked fine for me. I have heard of others having issues with that method but for me, it worked and has stuck.
Fiddy619's universal root method seems to be the preferred way for our phone, look in the general section here for a thread by engine95 to see what I mean. After I rooted with Framaroot I then used FreeGee and unlocked the bootloader then made a total nandroid backup of my stock in TWRP before going further. I also copied the backup to my PC just in case.
As for my preferred roms, if we are talking about Android 4.4 both Vanir and PSX are my personal favorites. However as you can tell from my signature I am still using stock zvc android 4.1.2. I have flashed just about every rom available for our phone but my daily driver is stock that I have modified manually(different kernel, removed bloat ware, minor modifications and tweaks, etc). For android 4.3 I have had the best experience with CM10.2 and cfxe. I have not tried CM11(based on 4.4) for awhile but it seems to have overwhelming support - Cyanogenmod usually does.
Really when it comes to roms it's personal preference. They are all very similar with different tweaks/additions. As for which one is the most stable that is also a tricky question. Even though we have the same model of phone, I have seen how picky they can be from one to the other. My roommates have the EXACT same phone, installing CM10.2 worked fine for two of us, but one lost GPS and I had to fix it.
My best advice for when you get your new phone is to backup your working stock and then have fun flashing different things making sure you follow the instructions per rom exactly. It's always a good idea after making your backup(if planning to install another rom) to wipe everything except your internal storage and do a clean install of the rom and gapps. Then, test it for a day or so because sometimes it takes time to settle in. It's a shame that Optimus DE gave you issues, it was rock solid for me, again, these phones are picky! But one of the main reasons I stayed with stock is because the AOSP based cameras leave much to be desired when compared to the LG camera. Again it's just personal preference because some don't like the lg camera.
If you have any other issues or questions I will be glad to help if I can. A lot of the people you see who are active on the forums are very knowledgeable, as long as you ask politely most will be glad to help.
HPTesla said:
If they did a hard reset it is possible that it wiped everything but not a definite. I purchased my phone from Best Buy and was on zvb. When the zvc update came through it messed my phone up(which is why you don't take OTA's once rooted without further knowledge/modifications) so I took it to Best Buy and they said they did a hard reset to fix it. It worked, my phone booted back up and my internal was fine. However, that's Best Buy and they barely know what they are doing so it may have been a soft reset, I am not 100% sure. As for a new root for the update, I received another phone shortly after because the glass back on mine broke and Best Buy replaced it with a whole new phone. It was on zvc and I used an app named Framaroot with the Gandalf exploit option and it worked fine for me. I have heard of others having issues with that method but for me, it worked and has stuck.
Fiddy619's universal root method seems to be the preferred way for our phone, look in the general section here for a thread by engine95 to see what I mean. After I rooted with Framaroot I then used FreeGee and unlocked the bootloader then made a total nandroid backup of my stock in TWRP before going further. I also copied the backup to my PC just in case.
As for my preferred roms, if we are talking about Android 4.4 both Vanir and PSX are my personal favorites. However as you can tell from my signature I am still using stock zvc android 4.1.2. I have flashed just about every rom available for our phone but my daily driver is stock that I have modified manually(different kernel, removed bloat ware, minor modifications and tweaks, etc). For android 4.3 I have had the best experience with CM10.2 and cfxe. I have not tried CM11(based on 4.4) for awhile but it seems to have overwhelming support - Cyanogenmod usually does.
Really when it comes to roms it's personal preference. They are all very similar with different tweaks/additions. As for which one is the most stable that is also a tricky question. Even though we have the same model of phone, I have seen how picky they can be from one to the other. My roommates have the EXACT same phone, installing CM10.2 worked fine for two of us, but one lost GPS and I had to fix it.
My best advice for when you get your new phone is to backup your working stock and then have fun flashing different things making sure you follow the instructions per rom exactly. It's always a good idea after making your backup(if planning to install another rom) to wipe everything except your internal storage and do a clean install of the rom and gapps. Then, test it for a day or so because sometimes it takes time to settle in. It's a shame that Optimus DE gave you issues, it was rock solid for me, again, these phones are picky! But one of the main reasons I stayed with stock is because the AOSP based cameras leave much to be desired when compared to the LG camera. Again it's just personal preference because some don't like the lg camera.
If you have any other issues or questions I will be glad to help if I can. A lot of the people you see who are active on the forums are very knowledgeable, as long as you ask politely most will be glad to help.
Click to expand...
Click to collapse
Okay Im going to try some new roms out when I get my new phone, I would like to try out an AOSP Kitkat Rom but I couldnt get one to flash last time I tryed but I will figure that out later when I get it. Now back to my Bricked Optimus, I want to try the teenybin method although I dont understand the directions... the second step tells me to flash but how can I do that without recovery? and it doesnt say anything about entering in download mode which is the only thing I can do, am I forgetting something? And thank you for the help Tesla I really appreciate it, Ive had more assistance from you than anyone else.
Penley94 said:
Okay Im going to try some new roms out when I get my new phone, I would like to try out an AOSP Kitkat Rom but I couldnt get one to flash last time I tryed but I will figure that out later when I get it. Now back to my Bricked Optimus, I want to try the teenybin method although I dont understand the directions... the second step tells me to flash but how can I do that without recovery? and it doesnt say anything about entering in download mode which is the only thing I can do, am I forgetting something? And thank you for the help Tesla I really appreciate it, Ive had more assistance from you than anyone else.
Click to expand...
Click to collapse
Are you a windows user? The teenybin isn't flashed from recovery it is flashed from a tool called LGNPST which is a Windows program. I am going to private message you a link. It will have links for downloading and installing LGNPST on your PC. It says that you will lose all your data but if you are using the teenybin you shouldn't. It's LG's tool for flashing firmware and gives that warning regardless of what you flash. And you're welcome, coming from an EVO 4G this phone is very different and plenty of people have helped me - just paying it forward.
HPTesla said:
Are you a windows user? The teenybin isn't flashed from recovery it is flashed from a tool called LGNPST which is a Windows program. I am going to private message you a link. It will have links for downloading and installing LGNPST on your PC. It says that you will lose all your data but if you are using the teenybin you shouldn't. It's LG's tool for flashing firmware and gives that warning regardless of what you flash. And you're welcome, coming from an EVO 4G this phone is very different and plenty of people have helped me - just paying it forward.
Click to expand...
Click to collapse
Hey I got in to recovery through the Teenybin although the reset that they did deleted all of my stuff so Im kinda bummed:/ but its okay cause I got my new Optimus today and its brand new so Im happy with it. Thanks again for all of the help. Thats funny that you used to have an EVO 4G because I had it for so long and thats the phone I switched back to when my LG got bricked, but let me tell you Im glad to be back to the Optimus haha the EVO 4G is just way to slow anymore. Now that I have this new Optimus which root method should I go with? Its currently runnning ZVB (4.1.2) should I update the software? It says theres a software update available but I know that sometimes they dont have roots out for those updates so how should I start with this process again with the new phone in your opinion? I havnt done this in forever (going on a year) so I cant really remember everything that I had to do.
Penley94 said:
Hey I got in to recovery through the Teenybin although the reset that they did deleted all of my stuff so Im kinda bummed:/ but its okay cause I got my new Optimus today and its brand new so Im happy with it. Thanks again for all of the help. Thats funny that you used to have an EVO 4G because I had it for so long and thats the phone I switched back to when my LG got bricked, but let me tell you Im glad to be back to the Optimus haha the EVO 4G is just way to slow anymore. Now that I have this new Optimus which root method should I go with? Its currently runnning ZVB (4.1.2) should I update the software? It says theres a software update available but I know that sometimes they dont have roots out for those updates so how should I start with this process again with the new phone in your opinion? I havnt done this in forever (going on a year) so I cant really remember everything that I had to do.
Click to expand...
Click to collapse
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly what he said, framaroot was quick and easy for me, but the lgog is so damn picky and fiddy seems to be the preferred method so use it just to be safe. I had zero issues with framaroot but I think I've just been lucky. And definitely update to zvc before doing either. I'd also update prl and profile for good measure.
That sucks that you lost all of your data, they must have actually did a hard reset where as BestBuy told me they did a hard reset and actually did a soft reset. But it's BestBuy so I never expect much. I softbricked my lgog the day after I got it using the GAIO tool(before finding out about FreeGee) and they fixed it with a soft reset. The guy called the manager over and the manager asked me if I tried unlocking the bootloader and I played dumb. My exact words were "What the hell is a bootloader?" and he immediately fixed it. But I was shocked anyone at BestBuy would even know that. Lmao.
As for my EVO, the micro usb port broke so I was charging it for two months like MacGyver, literally stipped the usb charging wire and hooked it straight into the positive/negative terminals in the battery while turned off! It was a fire hazard but it did the trick, lol. And luckily it had external sd(my one big gripe about the lgog) so I could still get my stuff off of it even without usb. I did love that phone, but you're right, it's incredibly slow now compared to the wonderful lgog.
And as always you are quite welcome!
---------- Post added at 07:39 PM ---------- Previous post was at 07:30 PM ----------
Penley94 said:
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
Click to expand...
Click to collapse
I think the reason I say framaroot is bc its also super easy, install the app, pick gandalf exploit and it will do it's thing - done without ever connecting to a pc. But @engine95 is right, fiddy is more stable so use that. As for TWRP, I love 2.5.0.0 but for KK roms you have to use the one that comes with updated FreeGee, TWRP 2.6.3.x because of the SELinux changes Google made with 4.4. TWRP 2.6 was unstable originally but has since become just as stable as 2.5 according to most. OpTimuS DE was rock solid for me, as for getting some of the G2 apps, I'm not certain. It's doable but I don't know how difficult it would be because I've never tried to install them elsewhere. And I already gave you my choice of best current KK roms but today I found out a few guys are trying to get OMNI official for us. When that happens I think I will be switching to OMNI because they have been producing some impressive commits/tweaks that you won't find elsewhere. Just look through xda news to see what I mean, OMNI is on a roll!
Penley94 said:
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
Click to expand...
Click to collapse
I prefer TWRP just because that has always been our best one since the beginning. Now that all the versions of the OG are coming together though both are fine.
I like stock, but Lrod's OpTimuS 5.0 is my daily. The G2 adds he made got me hooked.
If your gonna try to pull some stuff from DE, check with Lrod. He's made alot of changes to a lot of files making it difficult. For me at least.
I've ran all the KK Roms and I liked them all. PSX is probably my favorite though. I liked Liquid in its early days, pre KK. I'm not sure it's up to KK yet.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
I prefer TWRP just because that has always been our best one since the beginning. Now that all the versions of the OG are coming together though both are fine.
I like stock, but Lrod's OpTimuS 5.0 is my daily. The G2 adds he made got me hooked.
If your gonna try to pull some stuff from DE, check with Lrod. He's made alot of changes to a lot of files making it difficult. For me at least.
I've ran all the KK Roms and I liked them all. PSX is probably my favorite though. I liked Liquid in its early days, pre KK. I'm not sure it's up to KK yet.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again, I think you're right on all fronts. Liquid was smooth(heh) but it hasn't been long since we received an official 4.3 so I don't think they're up to 4.4. And same goes for the G2 apps, sometimes it's as simple as pulling an apk out of a zip and pushing it to system/apps and changing permissions but I think Lrod did a lot of work to get the G2 apps working on our phone because they required certain dependencies/modified frameworks.
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay so I rooted it through fiddys universal root but when I try to go on to FreeGee it just doesnt want to open for me? Ive tryed a lot of times and I get nothing it will either send me to the playstore to an app called busy box or will sometimes restart my phone, Im confised I have no clue what to do? I tryed to uninstall and reinstall and nothing I installed the busybox app but it said I didnt have root permission or there was a problem getting the root or something like that.
Penley94 said:
Okay so I rooted it through fiddys universal root but when I try to go on to FreeGee it just doesnt want to open for me? Ive tryed a lot of times and I get nothing it will either send me to the playstore to an app called busy box or will sometimes restart my phone, Im confised I have no clue what to do? I tryed to uninstall and reinstall and nothing I installed the busybox app but it said I didnt have root permission or there was a problem getting the root or something like that.
Click to expand...
Click to collapse
You have to root before unlocking.
Make sure your phone has at least 70 percent charge or more!!
Go to Settings: Settings>Security>Unknown sources checked: Settings>Developer Options>USB Debugging checked, Settings> Display>Screen Timeout - at least 5 min
from fiddy thread.
Directions
1. Unzip the zip file
2. Make sure USB Debugging is on, and you are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt. (Can now be run as admin if you wish, Still works running as regular user tho. Thanks robisodd)
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done.
You shouldn't have any issues.
If you do, then try Framaroot. http://forum.xda-developers.com/showthread.php?t=2130276 and follow those directions.
Follow this. http://forum.xda-developers.com/showthread.php?t=2050582 It has all the info on rooting and unlocking
Edit. You may have to root as admin/not admin, try both.
Edit #2 Also, do not use USB 3.0 ports. They are iffy for this stuff. LGNPST included
engine95 said:
You have to root before unlocking.
Make sure your phone has at least 70 percent charge or more!!
Go to Settings: Settings>Security>Unknown sources checked: Settings>Developer Options>USB Debugging checked, Settings> Display>Screen Timeout - at least 5 min
from fiddy thread.
Directions
1. Unzip the zip file
2. Make sure USB Debugging is on, and you are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt. (Can now be run as admin if you wish, Still works running as regular user tho. Thanks robisodd)
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done.
You shouldn't have any issues.
If you do, then try Framaroot. http://forum.xda-developers.com/showthread.php?t=2130276 and follow those directions.
Follow this. http://forum.xda-developers.com/showthread.php?t=2050582 It has all the info on rooting and unlocking
Edit. You may have to root as admin/not admin, try both.
Edit #2 Also, do not use USB 3.0 ports. They are iffy for this stuff. LGNPST included
Click to expand...
Click to collapse
Okay i will try this later when i have access to a computer, but the last root i tryed told me it was successful although it didnt restart my phone or anything it just said it was in the command prompt. I will try again cause i dont think it did anything. But i have a question about roms, i am most likely going to flash the DE 5.0 again because i like it with the g2 keyboard and i kind of like the lg feel to it but the only problem is google play music always gives me an error when im playing songs and it always has. I heard aosp roms dont have that problen so in your opinion what is the most stable aosp rom with all features working like gps and everything??
Penley94 said:
Okay i will try this later when i have access to a computer, but the last root i tryed told me it was successful although it didnt restart my phone or anything it just said it was in the command prompt. I will try again cause i dont think it did anything. But i have a question about roms, i am most likely going to flash the DE 5.0 again because i like it with the g2 keyboard and i kind of like the lg feel to it but the only problem is google play music always gives me an error when im playing songs and it always has. I heard aosp roms dont have that problen so in your opinion what is the most stable aosp rom with all features working like gps and everything??
Click to expand...
Click to collapse
AOSP SuperNexus has been getting good reviews here in the forums but I haven't tried it yet. I would give that one a shot though. I'd flash GAPPS standard with it instead of GAPPS core as well. This is just generally speaking with any of the AOSP roms.
The directions @engine95 gave you for fiddy are spot on(as usual ), specifically having the phone in charge only mode instead of mtp. I think a lot of people have missed that step and it won't work in mtp. Using usb 2.0 is another good tip.
And if your phone didn't reboot, you probably arent rooted. Easiest way to check that you are rooted is by going into the app drawer and seeing either Superuser or SuperSu app. If it's there, you're rooted, if not, it didnt work. If it said it worked but didnt reboot, Im assuming you rebooted manually? It sounds silly but sometimes it's as simple as that. But again, after rebooting if one of those apps arent there, you are not rooted.
EDIT: I've never tried rooting with fiddy without being in charge only mode, Im wondering if being in mtp may install supersu/superuser app but not the binary? Probably not but I could be wrong. Just wondering if there is any possible way that the app could be there but you still wouldn't have root privileges. For me, if the app is there, I'm rooted but I don't pretend to know everything(far from it, lol).
EDIT#2: Once you are rooted and recovery is installed, here is the link to SuperNexus.
EDIT#3: And I can't stress this one enough....after rooting and unlocking the bootloader, before flashing ANYTHING, make a full backup of your stock AND copy the TWRP folder(with your backup in it) to a computer, JUST IN CASE! That way you will always have a backup elsewhere, even if something goes wrong with your phone's internal storage. Better safe than sorry!!! And it's also best to copy the entire TWRP folder.
@HPTesla You're on a roll!
Go with everything he's said.
I don't use Google music ,so I'm of little help there.
Almost every ROM has its quirks, and it's just a matter of finding the one that does what you need/want.
Our devs have given us a lot of options. And I know, I sure appreciate them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Penley94 said:
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Click to expand...
Click to collapse
I ran OpTiMuS for a long time and every time I would try new roms, decide I didn't like or whatever and go back, I'd always have to 1. Dial ##72786# 2. Let it self activate sometimes twice, but usually just once before I would pick up 3g/4g. May have just been my phone but you may try that out if you go back to optimus De. Over all, my favorite stock like rom though.
Sent from my Optimus G using XDA Premium 4 mobile app
Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
mdphoenix said:
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
Click to expand...
Click to collapse
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
debianmain1 said:
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
Click to expand...
Click to collapse
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
mdphoenix said:
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
Click to expand...
Click to collapse
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
debianmain1 said:
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
Click to expand...
Click to collapse
I can always fire up an Ubuntu flash drive if necessary. I'll get working on Fastboot.
Thanks again!
@debianmain1 Hmmm, Fastboot doesn't seem to be functional. I've got download mode. Can I push something to it that way?
I managed to get somewhere yesterday. I tried flashing D85120e_00.kdz and it failed again. I got the "cannot communicate with server" error, then it rebooted and tried running initial setup and failed.
So I tried flashing D85110C_00.kdz. Much to my surprise, it worked! So I ran through initial setup and got the phone working to make sure all was well. I rebooted and got the Red 2. So now here I am. Guides show that I should be able to put it in download mode and reload factory firmware again. But all I get is the "Download Mode" graphic. It never switches over to the updating mode with the circular arrows. I fear the worst at this point, but I really don't know enough about the LGs to diagnose my own doom just yet.
Someone on Reddit pointed me in the direction of Board Diag. Unfortunately it doesn't appear to work on D851. Running out of options. Looks like it'll end up being an expensive learning experience.