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?

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.

Stop using one click crap. If you don't know what you're then you should not be messing with your device.

Sent from my DROIDX using XDA App

I can. Just won't.

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.

albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for

The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.

csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.

Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.

Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App

Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process

After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.

@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.

In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

[Q] Atrix Special "Brick" Problem with touchpad - reset

So, guys...here's a real challenge for all of you.
I taught my friend how to enable multitouch on Atrix 4G and I did mine correctly, but he tried editing the touchpad.cfg file using the Atrix, removed the READ permissions of file and restarted the phone. Obviously, the phone can't read the touchpad.cfg anymore and touchpad is not working at all.
Gladly (yeah, this is sarcasm), the Android won't let he do a factory reset because the Froyo version needs an extra step of TOUCHING the screen to complete the recovery command.
I tried accessing it via ADB too, but it requires you to TOUCH the screen and choose your USB connection type.
So, touch is out of question. Is there any way to access this cell phone and make the files readable again (or replace the files, whatever makes it working). The phone has USB Debugging enabled, if it helps.
p.s: sorry if it's been posted before, but I search the forum A LOT and could only find two similar posts that were unanswered. (Please, let's not make this one be the third. We don't need that.)

Have you tried fastboot? try turning off the phone and holding power + volume down until you see the word Fastboot then press volume up. You should be able to do whatever from adb now. Try that or an official update.
this should be in Q&A btw
Sent from my MB860 using XDA App

Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance

chapter81 said:
Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance
Click to expand...
Click to collapse
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.

Alcapone263 said:
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
Click to expand...
Click to collapse
Well, he's running Froyo 2.2, so I guess this option is not available for us to try. Even though because I'm not really sure I can go throught all these steps.
Alcapone263 said:
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.
Click to expand...
Click to collapse
Can you please explain me this idea of yours in more details? I think that all I need is to be able to communicate with the device without using touch. I read somewhere that using Fastboot, I could do anything via ABD, but even putting the phone on this mode, I still get "device not found" on ADB console. Maybe I'm missing some extra step. But again, if you could please explain me about this permission thing in Recovery Mode, it would be great, Alcapone. Thanks!!!

Flash a pudding 2.2 sbf

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

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.