Database Users

Guide to root Rogers G1's

***********Don't follow this method**************
THIS is what you want to do. This thread is an older method.
Do this at your own risk!!!....I'm by no means an expert on this. In fact it's the first time I have done this. There are probably tons of guide to doing this on the T-Mobile version but I made this to help people with the Canadian Rogers G1. So it only applies to that specific phone. This is also expecting you be using Windows (I use XP but Vista will work but I don't know where the command prompt is found....google it if it isn't in the usual spot). Also the commands would be the same using a Mac but yet again I don't know what or where the equivalent of windows command prompt would be found on a Mac.
First off you need the Android SDK which you can get from here (http://developer.android.com/sdk/1.5_r2/index.html).
Unzip the folder inside the .zip file to C:\Android so the final resulting file structure will look like C:\Android\android-sdk-windows-1.5_r2\
Now do the steps 2 and 3 found here http://developer.android.com/guide/developing/device.html
I have cut and pasted these steps here but if you are using a mac you may need to refer to the link. Actually refer to it anyways in case I missed something.
**************** Steps 2 and 3 *********************​
Turn on "USB Debugging" on your device.
On the device, go to the home screen, press MENU, select Applications > Development, then enable USB debugging.
Setup your system to detect your device.
If you're developing on 32-bit Windows, you need to install the 32-bit USB driver for adb. The USB driver is included in the SDK package. To install it, follow these steps:
1.Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software. Select No, not this time and click Next.
2.Select Install from a list or specified location and click Next.
3.Select Search for the best driver in these locations. Browse to the usb_driver/x86 in the SDK package (<sdk>\usb_driver\x86).
4.Click Finish. The system should install the driver files as necessary. Your machine may require a reboot.
********************************************​
Plug your USB cord into your phone and plug the USB cord into your computer.
Open a command prompt in windows by going to Start/Run and then type cmd. You should a dos like window open up. Now navigate to the directory C:\Android\android-sdk-windows-1.5_r2\tools
Type “adb devices” to confirm USB Debugging is turned on
Keep the command prompt open for later use
Get fastboot from here (http://www.htc.com/www/support/android/adp.html) and put it in the tools section of the SDK
Get these files http://drop.io/ii4t2ax and put them in the tools section of the SDK. Mount your sd card so you can copy update.zip to the root of your sd card.
Turn off your phone and then press the camera button and the power on button so it loads up to fastboot mode (or whatever it is called..lol). Once it gets to the screen with 3 androids on skateboards on the bottom you should press the “call” button to the farthest left. It should go to another screen that says “FASTBOOT USB”. If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
Now in the command prompt you need to type “fastboot boot recovery.img” don't touch your phone tile it gets to a new choice of menus in recovery mode. Once it gets there you should make a nandroid backup. I really urge you to make the backup. Make sure there is space left on your SD card.
So follow the menus and press the button combination to make the back up and once that is done press the other button combination to apply the update.zip file....Do not touch your phone at all....I'll cut and paste what Haykuro's directions were on this part to emphasize the importance of not touching anything....
(LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
Mine didn't take very long but if it does still do not touch anything. Please....just don't!
Once it is done press HOME+BACK to reboot the phone out of recovery mode.
Power off your phone and then press the camera button while pressing the power on button to go back to the fastboot menu. Press the “call” button (to the farthest left remember!) so you see it say “FASTBOOT USB”. Once again...If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
In the command prompt which you should have left open for convenience you have to type “fastboot flash boot boot.img”
Then type “fastboot flash recovery recovery.img”
Then type “fastboot reboot”
At this point you basically have root but you need to change permissions on a file that need to be on the phone so everything works as your would expect with root
Turn the phone on to be on the operating system.
Type “adb root” in the command prompt to confirm you have root access
Download this file http://www.magicandroidapps.com/su.zip
Unzip the file to the tools folder of the SDK
In the command prompt type “adb remount”
Then type “adb push su /system/bin/su”
Then type “adb shell” and you should get prompted with a # symbol
Type “chown root.shell /system/bin/su” right after the # symbol
Then type “chmod 6755 /system/bin/su”
That should be it...try running the market enabler or SetCPU which you can get here http://forum.xda-developers.com/showthread.php?t=505419
If they work then you have root....currently you CANNOT use any of the custom roms because they were made for T-Mobile versions of the G1. I'm waiting for conversions of these roms myself so have fun waiting just like me. This is the first time I have ever hacked/rooted any phone so be sure to research stuff yourself...I might have things wrong. Who knows....it's all a risk just like I took when I decided to try it without having a step by step guide to read from.

Remember guys...I JUST wrote this so be sure to read it the whole way through before jumping into things. Post problems you run into here so I can fine tune it.

so you managed to root the rogers G1?? great job!! did you figure this out yourself???

no...Haykuro did this. I just took all the available information and put it in order to help others do it. It was all in this thread here http://forum.xda-developers.com/showthread.php?t=522127

Can we get a tutorial of how to flash a new rom now I really want to try out the new hero rom.

there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.

XwXDv8XwX said:
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
Click to expand...
Click to collapse
Is Haykuro working with Cyanogen? Man I just want to play with the Rogers Rom. Oh well I guess I'll settle for getting rid of the Rogers crap and being able to buy stuff on the Market finally.

Yep, I made a 3.6 for the Rogers Dream. I haven't actually tested it because I don't have one, but I used Haykuro's tools to build the boot image. Let me know if it works for you guys!

Holy...where is that at? lol

My wife has gotta get her ass home with my phone damnit! lol

http://forum.xda-developers.com/showthread.php?t=518851

lol, I just finished restoring my phone too. Oh well I am downloading your files now cyanogen, here's to hoping I don't brick my phone on my first flash attempt.

Can someone point me to a guide to flash this rom to my phone?

XwXDv8XwX said:
Can someone point me to a guide to flash this rom to my phone?
Click to expand...
Click to collapse
After you have rooted, copy the file to your sdcard as "update.zip", boot into the new recovery mode, wipe your data if you are coming from the stock build, then flash the update! The first boot will take a bit longer than usual. Check my thread for a FAQ.

Just wanted to say "Thank You" I have been following the threads in the background for the better part of a week, and was hesitant to give it a shot as I am not too sharp on dealing with dos boxes. However followed it along and everything went off perfect, grabbed set CPU and installed it and works. So I guess I have root. Not really sure what I can do with root, but will look forward to browsing around and seeing what is cool.
The big thing is I want to be able to flash new roms. So I guess this is the first step in doing that. (already actively flash PPC roms on the Hermes)
Again thanks for everyones work on this.

well here it goes....it'll be the first time I ever flashed a new rom to my phone...at least I know some other people have tested this version of cyan's rom so I feel pretty safe doing this. I would just send it back and pretend I don't know what's wrong with my phone if I did brick it but things seem to be going pretty smooth so far.

I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.

XwXDv8XwX said:
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
Click to expand...
Click to collapse
No, you wipe before the update. Wiping doesn't erase your SD card, only the internal data partition.
Also, my ROM is a "Google" based ROM. You'll have to sacrifice the spiffy HTC dialer and Exchange support, but I include all the other HTC apps.

How's your flash going XwXDv8XwX? I tried, but was stuck on the Rogers screen for more than 10 minutes. I rebooted the phone and tried again using the "adb logcat" command to try and see what my phone is doing but as soon as it restarted I stopped getting stats. Is this like a 20-30 minute setup process perhaps?

This is taking ALOT longer than usual. It's staying at the rogers logo right now....how bad is this?

Nexus S4G might be bricked, please help

I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks

Go look in the developer section, one of the stickies, the one that talks about the nexus s 4g cdma. You might have flashed something that was meant for the gsm nexus s. It has links to correct files and guides for the sprint version of the nexus.

Pm me and I will help u over the I'm client of your choice.

Basically, I have no service, and no card, so since I can access Fastboot Mode, and unlocked, is there a way to push a rom direct onto Sprint phone.
I looked in Developers Forums, I am not ready to jump in with custom rom yet (I have used extensively on other phones) but would like to start with stock, go with root and programs as needed.
So how would I push to phone via computer? and what programs, again, no idea of commands to use.

Have you flashed CWM yet? You can use that to reflash the stock ROM. Worst case you can use this thread:
http://forum.xda-developers.com/showthread.php?t=1072698
That will bring you to 100% out of the box factory settings

If you can get into fastboot, then you didn't brick it. You'll be fine, you just need to get in touch with someone that can walk you through the process of fixing it. Or search around, read, and take your time to figure out what to do.
It's not hard. The worse thing you can do is panic or rush to fix it.

Basically what you did when using superboot was you actually installed a boot.img file not meant for your device on your phone. What you should do is, go through the guide for your specific phone...you will have to install a recovery image and then install a custom rom or stock rom.
I do not know if you know your way around with fastboot....basically you could also ask a dev to send you the original boot.img and flash it using fastboot but the first stepi described is easier.
Sent from my Nexus S using Tapatalk

nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
If you are going to waste your brand new phone by being stupid how about giving it to me instead! Ill take good care of it.
Sent from my PC36100 using XDA App

Here Try this and let me know if it work:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot flash boot boot.img'.
7.Type in the cmd.exe window 'fastboot reboot'.
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse

THANK YOU, for answer, but it didn't work.
I downloaded, opened, opened cmd from there.
My phone is unlocked, setting there with unlock screen, put it in bootloader mode, but when I type in instructions, it comes back "not recognized as internal, external command, program, batch file"
This is the problem I had when trying to unlock, so reading, used Superboot, probably wrong phone, so now it is wiped and empty.
I also read another thread suggesting Odin in this situation. Have downloaded that, SamsungSimpleDL, followed those directions, that doesn't work either. I have hacked and rommed Epic, very familiar with that, if it works, but cannot point to proper files (pda, pit, or bootloader).
So any other ideas, I am very good at directions, that is how I learned

My Phone is Fixed - YEAH
This did not work, but this link did
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
Basically used Odin (my old backup from Samsung Epic) and it worked when all these suggestions wouldn't.
I couldn't unlock easily, like all of these, therefore used Superboot. Would recommend no one touches that!!
I couldn't run any of the commands before this, and still couldn't use these.
So the instructions to dig thru the Developers section is correct, but so hard with so many customs, phones, carriers, to choose from. Makes it difficult
So use this link if stuck like me, I am just glad I con't have a brick, and I'm still pushing the Thanks button for all who helped, that's what will make this fun.

Kindle Fire bricked. Need major help

Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:

Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.

tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.

Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.

soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.

factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!

[Q] N73G stuck on Google screen

I was using my N73G at home this evening and it spontaneously rebooted to the Google splash screen... and stayed there for well over 5 minutes. I tried long pressing power to reboot again, and it went back to the same screen.
TWRP is installed, and I am able to get into that. I tried wiping cache and dalvik, and it booted straight back to the splash screen again, solid for 3 minutes before I went back into TWRP. In the file manager my files all appear to be safe and sound. I am currently running a nandroid backup before I futz with it any further. TWRP has not given me any errors over the course of the backup.
I should note that I have had some trouble connecting to TWRP over ADB although I can use ADB when booted into the OS. So if I need to go fishing for files over USB, I hope I won't come up empty. If necessary I could try flashing CWM recovery instead, as I may be able to get my files more easily that way.
Anyway, ideas are welcome. I was running a bake of the Modaco custom ROM, and the zip for that ROM is still on the device, so I was thinking I might try reflashing that. But first I should try and get my nandroid off the slab.
As fortune would have it, I have already ordered an RMA device swap due to issues with the speaker blowing out. So if I fail to resuscitate it, help is already on the way. But I would like my tab to work again by the time I go back to work Monday

Update: Figured out the ADB recovery driver problem. Nandroid backup was successful. I'm now pulling the backup image to my desktop. Will try a ROM reflash next.

UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices. So I typed in adb logcat and found some message about /system/xbin/busybox missing.
I browsed with ADB shell and found there is a busybox in /system/bin. So I did ADB remount, and then copied busybox from bin to xbin. Entered a reboot command, and bam! Five seconds on the Google splash, and then right to the booting X.
Why in the world would this have happened... maybe the busybox installer app got an upgrade and botched an attempt to upgrade busybox?

cmstlist said:
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices.
Click to expand...
Click to collapse
The adb daemon - adbd - is started by init as a service so long as you have previously enabled adb debugging. So, it happens before the whole android reboot sequence kicks off (checking that all .apks without odex files have up-to-date .dex entries in dalvik cache, permission checks, etc.) You can access it on devices that are "stuck" in the late stage of booting.
TWRP - for better or worse - does not claim the same USB vid/pid ID that is used by the N7's ADB facility, even though the exact same driver can be used for either adb mode ... so long as you manually went into the driver install package and add the "universal" vid/pid values used by TWRP to the driver's .inf file. I think this is done simply to minimize the effort keeping up with new device identifiers by the TWRP team. It does create the impression that separate drivers are needed - but only because neither of the two drivers (Google vs. Universal) have the "other's" vid/pid pair listed as matching devices in their .inf files.
Anyhow, you got it all sorted out - congrats.

Thanks! I had been worried maybe the whole file system was corrupted, so in comparison this was a relief.
Sent from my Galaxy Nexus using Tapatalk 2

LG G2 Fastboot

Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.

Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)

For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.

Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks

You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app

I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.

demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks

dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks

Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.