Database Users

[GUIDE] Flashing with Heimdall

Heimdall is an alternative, cross-platform tool to flash firmwares for the Galaxy S series of devices, including the Tab.
Heimdall
Some of you might not have heard but a brilliant guy one day woke up and thought 'damn it Odin' and started working on Heimdall. The guy reverse-engineered the protocol to flash our Galaxy's and turned up a piece of software called Heimdall that can do exactly the same as Odin.
This tool is open-source and runs on Qt for its GUI and libusb to communicate over USB making this tool completely cross-platform. This basically means flashing your Galaxy is not just limited to Windows anymore.
This guide will walk you through the steps to work with Heimdall. I'm a Mac user so the screenshots you'll see will be Mac-y. However, since the app and GUI are cross-platform the same apply for both Windows and Linux.
Disclaimer:
Flashing your device through anything but Kies can be a dangerous business and can brick your Galaxy S.
That said, Samsung seems to have engineered the Galaxy S series in a way that makes it relatively difficult to brick even if you **** up.
Proceed with caution and at your own discretion, both the developers of Heimdall and I can not be held accountable for the possible damage you do to your device by following this guide or using Heimdall.
Flashing with Heimdal
Flashing with Heimdall is a little bit different than with Odin. With Odin you usually select a PIT, if necessary, add the PDA.tar.md5, Modem.tar.md5 and CSC.tar.md5 to the locations, put the phone in download mode and hit go.
Heimdall takes a different approach. In the Heimdall GUI you need to select all components you want to flash. This means extracting the TAR-archives and pointing Heimdall to their respective files. This allow relative fine-grained control over what you flash and doesn't depend on files being named correctly.
In order to install Heimdall head over to the guy's website and download and install Heimdall.
Do yourself a favor, even if you're on Linux or Mac, just reboot after the install. On OS X the installation includes a kernel extension and though this can usually be reloaded by logging out and back in again the reboot is safer and can't hurt.
Mac OS X specific
For Mac OS X the 1.1.0 version of Heimdall includes some nuked Qt binaries which means the GUI won't start. This can be fixed by afterwards installing Qt from here.
The above should not apply to the latest Heimdall release anymore according to the release notes. If however you still get errors about Heimdall failed to start, just install the Qt binaries linked above anyway, should take care of the error.
There is a second problem unfortunately on OS X. Due to a bug in older versions of the bootloader the device doesn't register correctly in download mode. If you then try to flash without having fixed the bootloader you'll nuke the Galaxy S and end up at a "black screen of death". Trust me, I tried, it broke and it scared the crap out of me.
Don't worry, this isn't the dreadful black screen of death meaning your device is busted, it just means your firmware is. You can just put it into download mode again and flash another firmware over it with Odin (Windows)
In order to avoid this we need to fix the bootloader first. Everyone who has installed the official Froyo update through Kies will already have a fixed bootloader and so you can ignore the next bit. If however you hocus-pocused around with Kies / Odin to flash Froyo like I did you probably don't have the updated bootloader.
Unfortunately we're going to need Windows for this and Kies so either get a VM ready, bootcamp into Windows or find a friend who'll lend you his pc for an hour.
See the second post, "Fixing the bootloader" for instructions.
Click to expand...
Click to collapse
Linux specific
As far as I'm aware there are no Linux specific problems, not even the bootloader issue mentioned above for OS X. However, it might be wise to follow the instructions anyway since an updated bootloader can't hurt.
Click to expand...
Click to collapse
Windows specific
As far as I'm aware there are no Windows specific problems, not even the bootloader issue mentioned above for OS X. However, it might be wise to follow the instructions anyway since an updated bootloader can't hurt.
Click to expand...
Click to collapse
Now, time to get busy.
I'm going to assume that you have downloaded a firmware, for example from samfirmware, and have extracted the .RAR and the .TAR inside and now have a folder with at least the following:
factoryfs.rfs (PDA > FactoryFS)
param.lfs (PDA > Param.lfs)
zImage (PDA > Kernel (zImage))
Additionally you might have:
cache.rfs (CSC > Cache)
modem.bin (Other > Modem)
Be aware, there are other configurations possible. For example, when you're rooting by flashing a rooted kernel there will probably only be a zImage.
Start Heimdall or Heimdall-frontend, you should get a screen similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, unless explicitly stated that you need a .PIT to flash this firmware you can leave this field blank. If you load a PIT, be sure to see if you need to repartition. The general rule is that you won't, unless you flashed with a firmware that had a different PIT than what samfirmware is indicating you need.
After that, start hitting the browse button for the components you want to flash with Heimdall and add them. Your screen will probably look something like this:
Now, it's time to put your phone in download mode. Power off the phone and wait for it to completely have shut down and unplug it from USB / charger. Hold down the Home and Volume Down buttons and then press Power. Keep holding those three buttons until you get into download mode (you'll know when you see it).
If you can't get into download mode / nothing seems to happen, you probably have a Galaxy with the broken 3-button combo problem, see here for a fix:
http://forum.xda-developers.com/showthread.php?t=785201
Now, connect the phone over USB with your computer. If you're on on Mac and Linux you can proceed immediately. If you're on Windows you'll probably need to wait for Windows to install a driver or two.
Now hit the Start button and watch it go!
If all goes well you'll see the progress bar on both Heimdall and in your phone filling up (might take a while for one to appear on the Galaxy S). Once it's done it'll probably say everything went OK and the Galaxy will reboot into recovery. Let it do it's thing, it will reboot again and begin booting the new firmware.
After having installed a new firmware the first boot might take a while. You'll just seem to be stuck at the glowing S, just let it run it will boot eventually.
If however Heimdall says "Failed" your phone will (probably) reboot or when you try to reboot you'll get stuck at the "black screen of death":
This isn't a "my device is bricked" screen, just that you ****ed up the firmware. Just follow the instructions again, put it in download mode and try again.
If, after having seen the above screen, you can't get your phone into download mode, then you're toast.

Fixing the bootloader
Fixing the bootloader
In order to fix the bootloader we need to flash some firmware. There's always the risk of data loss so make a backup first!
First we need Kies available on Windows, so grab it and install it. See the XDA wiki about this.
Once Kies is done installing don't launch Kies or exit it first, then connect your Galaxy S. Let Windows purr for a while as it gets busy installing your device drivers. Once it says it's done, you can start Kies.
Now, it's time to get the Kies registry patcher. We'll use this tool to fool Kies into thinking an older version is running on the Galaxy S so that it presents us with the option to grab the Froyo update.
Once you've started Kies and Kies has recognised your phone, start the Kies registry patcher. Set the Fake mode to True and select your product code. As I'm Dutch, I selected XEN from the dropdown. There is a list on the XDA wiki to tell you which product code is suited for your country, I suggest you use that one.
Now hit the "Write registry" button and then inside Kies, select the update firmware button in the bottom right corner (the phone with the arrow). Kies will now probably tell you it has an update for your phone which should be in the JP* series or GJK3, meaning it is the Froyo update.
Tell Kies to update your phone. Kies will get busy downloading the firmware and flashing it. Your phone will reboot into download mode, once that done you'll see recovery mode and then it will start booting.
Now that you have installed the official Samsung Froyo Galaxy S update you'll have the fixed bootloader you need in order to be able to use Heimdall on OS X.

crystal clear and helpful. thank you.

Many THANKs for this Guide!! Great work

great guide !
... added to the wiki

AllGamer said:
... added to the wiki
Click to expand...
Click to collapse
Thanks. Figured it might help some people .

No Windows
The reason why I'm using Heimdall is because I'm on a mac and don't have access to a Windows pc. The whole bootloader step kind of makes it impossible for me to use Heimdall. Is there a workaround?
Ps. When I say I don't have access to a windows pc, I mean it. I'm approx. 10 hours north of any major city, in the wilderness.

If you had working 3-BR prior to flashing & getting the phone computer icon with a ! in the triangle, I think there is hope.
If you really blotched your flashing, & get that semi-bricked icon when you try to into download mode, Heat the phone a bit & press Vol down + Menu + Power button for a very long time. This has happened to me thrice on my SGS with working 3-BR, & the longest it took me to go into download mode was something like over 30 seconds.
Hope this helps.

My Heimdall doesn't let me flash if I select a PIT file... And already tried with 3 diferent PIT files. Do you know why?

i followed the guide, but heimdall says "Failed to start Heidall"
i've a mac intel 10.6

hi
what does the following error mean?
Failed to access device. Error: -12

Failed to access device is quite literally what it means, failed to access device.
This usually means something is wrong in download mode or the USB kext is acting up. A reboot should solve it, put your phone back into download mode and you should be good to go.

baul87 said:
i followed the guide, but heimdall says "Failed to start Heidall"
i've a mac intel 10.6
Click to expand...
Click to collapse
I only got that error with the problematic QT binaries. Did you install the "normal" QT binaries after installing Heimdall? (See the Mac OS X Specific part of the opening post).

I'm on a Samsung Fascinate is it completely necessary to update to the Samsung Froyo Bootloader for this to work? The Fascinate doesn't even have Froyo yet. Thanks in advance.

daenney said:
If, after having seen the above screen, you can't get your phone into download mode, then you're toast.
Click to expand...
Click to collapse
Well, I got that screen message and can no longer go into download mode. Not sure what happened, but I apparently did something wrong.
QUESTION: if I take this into a Verizon store, will they be able to tell that I had rooted the device? I'd like to take it in under warranty.

Get yourself a USB JIG (see toopic about unbrick JIG), when you plug that into your phone (when its offline) it will go into download mode no metter you did had BSOD or not (I have it all the time with odin, I'm starting to think my device is ****ed up though )

I receive "Failed to detect compatible device" I have Heimdall running. The only way I can get into the Download screen is to take my battery out completely and plug into USB while holding Vol Down and power.I put the correct Modem.bin file in the correct place and hit start but I keep getting an error.
Im on a rooted Fascinate coming from a Stock DL09. I installed a Rom and Kernel w/ Rom manager.But I had issues w/ SMS learned it was because of the Radio/Modem

I keep getting failed to access device error 12. I'm not sure why. I've restarted the SW and get same response. Odin detects the device as well as my OS. Is this not compatible with the Sprint Galaxy tab or do i need specific drivers?

Bxsteez said:
I keep getting failed to access device error 12. I'm not sure why. I've restarted the SW and get same response. Odin detects the device as well as my OS. Is this not compatible with the Sprint Galaxy tab or do i need specific drivers?
Click to expand...
Click to collapse
Check the readme in the heimdall directory. For the windows version you must install the drivers attached.

kunjar said:
Check the readme in the heimdall directory. For the windows version you must install the drivers attached.
Click to expand...
Click to collapse
Yup. I did that but it appears i installed the wrong driver. I tried to delete the driver but that didn't work. I had to switch to another computer and it worked perfectly.

May'13 - Unlock Bootloader, Flash Recovery, Install ROM on Atrix 4G AT&T 4.5.141

The best feature of Android - It's open. You can modify Android to have the best performance from your phone. My previous Atrix's hardware had some problem. So I didn't root my/unlock my Atrix. However, after seeing the upcoming CM10 for my set &; a battery friendly ROM yet 100% stable ROM, I finally decided to flash a custom ROM. What's great? I'm successful.
Yesterday, I was determined to unlock my bootloader & flash MROM on it. But I was afraid if I do anything wrong, my phone will not boot. I've not any other phone other than this & it's very precious to me. It's my beloved Atrix. I was unrooted, unlocked. Meant - I didn't do any modification at all. If you're on AT&T 4.5.141 (OTA Upgraded) then this tutorial is for you. (Bell/International users close your tab now!)
I'll not be responsible if you do any harm to your device
(You know the drill )
How to Unlock Motorola Atrix Bootloader (4.5.141) AT&T
I'm a noob. So I was searching for a perfect & easy tutorial. The automatic bootloader unlock seems really confusing to me. So I decided to do it manually. It's more easy &; clear than the automatic version.
I'll be writing this tutorial only for AT&T Atrix running 4.5.141 - Android 2.3.6 version. This tutorial will also work for AT&T 4.5.91 version.
But don't try this on AT&T 4.5.145/Bell/other international version. Once you flash CM7, don't flash Motorola's ROM with SBF. It'll brick the phone..
(Means your phone is dead!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We'll be flashing a custom ROM directly after unlocking the bootloader. So please download a custom rom &; it's Google Apps to your internal memory/SD Card. The main purpose of unlocking bootloader is to flash roms. So I don't care whether Motorola's buggy, laggy, sluggish, default blur ROM works or not.
Pre Requirements
We'll be needing a couple of tools.
We need the drivers for Atrix 4G. Download &; install it from here*(31.60 MB)
We'll need fastboot to unlock. Download fastboot from here (4.73 MB)
We'll need RSDLite. Download RSDLite 5.3.1 (4.33 MB)
Only for AT&T Atrix running 4.5.91/4.5.141 -*We'll need the 1.1 MB Unlocker Only SBF for AT&T Atrix. This tool will make ready your smartphone to unlock via fastboot command.
How to Unlock Bootloader Now?
If you've rooted already, take a backup of your apps with Titanium Backup. If not, then you're gonna loose all your apps.
Unlocking Atrix 4G Bootloader 4.5.141 Step-by-step
First of all, install RSDLite & extract the file*4547-fix-try2.sbf on your desktop.
Extract fastboot to C://fastboot.
Open RSDLite.
Power off your phone. Press power button+volume down together. You'll see a text "fastboot". Then start pressing the volume down again &; and again until you see "RSD". Once it comes, press volume up button. It'll say "Starting RSD Protocol"
You'll see that RSDLite has detected your phone in the menu. (SE Olympus or something like that)
Now Click the "..." button in RSDLite &; navigate the*4547-fix-try2.sbf file from your desktop.
Click Start.
Wait 5/6 minutes It'll restart your phone. You'll maybe see a boot error. (Just ignore it. Cause we're gonna flash a new ROM anyway).
After waiting some minutes, it'll say it's saying "starting fastboot protocol"
We're half done. We've extracted our fastboot files in C://fastboot
Open Command Prompt with Admin Privilege
Code:
Type "cd.."
Code:
Type "cd.."
Code:
Type "cd fastboot"
Type "
Code:
fastboot devices
".You'll see if your devices gets recognized or not.
Now type "
Code:
fastboot oem unlock
it'll give you a unique ID to unlock your phone.
Type "
Code:
fastboot oem unlock "XXXXXXXXXXXX (Unique ID)"
BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!
Flashing ClockWorkMod Recovery
(I've downloaded the latest recovery from romracer from here & placed it into the fastboot folder already)
Reboot your phone into fastboot mode again. (If power button doesn't do it, do a battery pull. To get into fastboot, Press power button+volume *down together until you see fastboot &; then press volume up)We're in the command prompt still.
So write*
fastboot erase recovery
Then write
fastboot flash recovery recovery.img
YAY!!! BOOM! We've flashed unlocked the bootloader & flashed recovery!
To flash a rom now, go to recovery mode (Press power button+volume *down together until you see*fastboot*&; then keep pressing volume down &; until you see "Android Recovery". Once you see it, press volume up.
The ROM flashing guide is easy. Choose install zip from SD card &; select your rom package &; it'll be installed. Reboot to enjoy your first custom ROM
Previously Published on my site http://saifhassan.info!

Emergency AT & T Atrix 4g (2.3.6) 4.5.145 Original 4547-fix-try2.sbf
Friends, let me urgent need to file 4547-fix-try2.sbf. Phone "failed to boot one" has failure. then the first term is no longer soft.As I understand it from RSD lite rom (4547-fix-try2.sbf) need to install. I'm searching, but I could not find. Links are broken. URGENT PLEASE HELP
(I'm sorry for my english is bad.)

saiftheboss7 said:
...BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!...
Click to expand...
Click to collapse
Finally) I'm done! 10ks!

Help please
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks

ukmed said:
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks
Click to expand...
Click to collapse
try "fastboot devices" to make sure your device is connected and recognized.

lehjr said:
try "fastboot devices" to make sure your device is connected and recognized.
Click to expand...
Click to collapse
Tried that, nothing happens...
Help!?

ukmed said:
Tried that, nothing happens...
Help!?
Click to expand...
Click to collapse
Make sure you download the USB Driver for WIndows. I posted the link in the OP. Read it thoroughly.

i need help
all my volume buttons are not functioning, how can u help me unlock........

If you have root, you might be able to use adb and the internal reboot command to reboot into various modes (recovery, fastboot...).

Tonyanaky said:
all my volume buttons are not functioning, how can u help me unlock........
Click to expand...
Click to collapse
Just flash TWRP after download, rename it to recovery & replace with the one that comes with fastboot extracted folder.

help
my 4547-fix-try2.sbf failed to work......what do i do???

Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?

Xfire68 said:
Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?
Click to expand...
Click to collapse
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!

Xfire68 said:
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!
Click to expand...
Click to collapse
there is a set of drivers that are for win 7 64 bit that i found early this morning via the droid x forum. I'm not at home right now, but i will post the link here when i do get home. hopefully it helps with issues with this os setup
Edit
File uploaded. even thought it says droid, it should still work

Works for 4.5.141 ?
Hi! Does this method work for Atrix 4G AT&T 4.5.145 as well? I want to get bootloader unlocked of my phone and install any ROM which supports 2-way Call Recording. Kindly suggest a stable ROM also that supports call recording function.
I am bit confused as the thread title says for 4.5.141 only.
Thanks in advance!!! :good:

Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Enviado desde mi MB860 usando Tapatalk 2

andresrivas said:
Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Click to expand...
Click to collapse
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.

sony108 said:
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.
Click to expand...
Click to collapse
yes, its called read post #1 and delete the recovery.sh in your phone before flashing cwm

[Q][Request] NVFlash Tool + APX drivers to flash bootloader

Hi Guys,
This morning my Nexus 7 turned Off and util now i couldn't turn it on again. when pressing the power button for 30s or more it turn on in APX mode with black screen.
I've tried many times pressing the power on button for 30s to 1min, but doesn't work.
I've tried to unpin the battery wait 1 or 2 hours, but it doesn't work.
I've tried to charge it but seems like it's not charging because the screen keeps black, so doesn't work.
Diagnostic
When connecting it to my computer its recognized as APX device. I've done some research and found that it's a way to hard unbrick devices, i've found cases called SOD (sleep of death) and i think my Nexus 7 is in SOD or hard bricked.
Cause
Seems like the bootloader becomes corrupted and without it my devices goes to APX mode by default. other way to enter in this state is erasing the bootloader with fastboot. so be careful.
Solution
Reflash the bootloader.
The Easiest way is flash it on fastboot mode there are a lot of tutorials to do that. but you need the bootloader to start the fastboot mode or boot android and as it's corrupted i can't go in that mode.
The Hardest way is on APX mode, using a tool called NVFlash (http://forum.xda-developers.com/showthread.php?t=1773323) with a Naked APX driver, the correct tool and some knowledge i think it's possible, but some people said that there isn't a NVFlash tool for Nexus 7. I don't know if it's true but if it is this process wouldn't be possible yet.
The last solution and the most adopted by users is resend it back to google and claim the warranty, but as i'm a Brazilian and I bought it on USA. i can't do that.
Request
As i know many people are stuck in the same state. We need a NVFlash Tool for our device, but as i don't have enough knowledge to do it my own, the last chance is request help. and i need help as many others.
if someone know how to proceed please contact me.
Thx! anyway!

the same
Rafael Aparecido Camilo said:
Hi Guys,
This morning my Nexus 7 turned Off and util now i couldn't turn it on again. when pressing the power button for 30s or more it turn on in APX mode with black screen.
I've tried many times pressing the power on button for 30s to 1min, but doesn't work.
I've tried to unpin the battery wait 1 or 2 hours, but it doesn't work.
I've tried to charge it but seems like it's not charging because the screen keeps black, so doesn't work.
Diagnostic
When connecting it to my computer its recognized as APX device. I've done some research and found that it's a way to hard unbrick devices, i've found cases called SOD (sleep of death) and i think my Nexus 7 is in SOD or hard bricked.
Cause
Seems like the bootloader becomes corrupted and without it my devices goes to APX mode by default. other way to enter in this state is erasing the bootloader with fastboot. so be careful.
Solution
Reflash the bootloader.
The Easiest way is flash it on fastboot mode there are a lot of tutorials to do that. but you need the bootloader to start the fastboot mode or boot android and as it's corrupted i can't go in that mode.
The Hardest way is on APX mode, using a tool called NVFlash (http://forum.xda-developers.com/showthread.php?t=1773323) with a Naked APX driver, the correct tool and some knowledge i think it's possible, but some people said that there isn't a NVFlash tool for Nexus 7. I don't know if it's true but if it is this process wouldn't be possible yet.
The last solution and the most adopted by users is resend it back to google and claim the warranty, but as i'm a Brazilian and I bought it on USA. i can't do that.
Request
As i know many people are stuck in the same state. We need a NVFlash Tool for our device, but as i don't have enough knowledge to do it my own, the last chance is request help. and i need help as many others.
if someone know how to proceed please contact me.
Thx! anyway!
Click to expand...
Click to collapse
I got the exact same problem..:silly:.

Yeah me too, anyone has succeeded in unbricking a Nexus 7 yet? Regards.

Hi, i've had a similar situation, trying to flash the new 4.3 on my nexus 7, after erasing some parts I was ending with bootloader failed using Nexus Root Toolkit. So I try every posibilities but no luck, Then I reinstall the adb driver, restart my computer change the usb slot open again Nexus Root Toolkit and click the unlock button from the program, it will unlock your Nexus 7, and after that I was able to update my Nexus 7 to 4.3
Hope this help!

duronu said:
Hi, i've had a similar situation, trying to flash the new 4.3 on my nexus 7, after erasing some parts I was ending with bootloader failed using Nexus Root Toolkit. So I try every posibilities but no luck, Then I reinstall the adb driver, restart my computer change the usb slot open again Nexus Root Toolkit and click the unlock button from the program, it will unlock your Nexus 7, and after that I was able to update my Nexus 7 to 4.3
Hope this help!
Click to expand...
Click to collapse
Did your Nexus 7 boot when you had the bootloader damaged? Or nothing on the screen at all?
Sent from my SGH-M919 using Tapatalk 2

Stuck in APX MODE / Maybe Bootloader erased
Yeah sadly but its true.
First of all ive flashed androdi 4.3 on my Nexus 4 manualy using the adb fastboot method.
like this:
1.unlocked the bootloader with NCry for Windows
2.rebootet into fastboot mode and executed the flash-all batch file from the official rom.
3.relocked the bootloader.
SO FAR SO GOOD
Hehe easy going....... here we go with the NEXUS 7 32 GB (WIFI)
1.unlocked the bootloader with NCry for Windows
2.rebootet into fastboot mode and executed the flash-all batch file from the official rom.
3.Something went wrong.
4.Crying like a little toddler :crying:
I hope there is some kind of genius out there who will bring us a fix.

Too many threads !!
Looks like many N7 owners have crashed their baby while flashing android 4.3.
Yeah of course we all have the same problem a broken bootloader.
But it doesnt mean that we have to start a thousand threads about the the same ugly thing.
Please fellow sufferer make this the main thread.

Me too my nexus 7 won't turn on . Any one who solve this?
Sent from my ALCATEL ONE TOUCH 5020E using xda premium

You must upgrade the bootloader and the radio to the latest version before upgrading to 4.3

I've tried many times pressing the power on button for 30s to 1min, but doesn't work.
I've tried to unpin the battery wait 1 or 2 hours, but it doesn't work.
I've tried to charge it but seems like it's not charging because the screen keeps black, so doesn't work.
Click to expand...
Click to collapse
charger animation is ok
but loop bootloading with google image
i just flashed radio on my working 4.3 !!!!
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
eternal70 said:
You must upgrade the bootloader and the radio to the latest version before upgrading to 4.3
Click to expand...
Click to collapse
no!!! this is not the reason why i have boot loop
i clear all and install android 4.3 and started it - ok
i flashed bootloader and start android - ok
- flashed radio - and i am having bootloop with only Google image
------- the radio have regional differences (IMHO) ----------
--------------------------------------------------------------------------------------------------
---------- Post added at 03:24 PM ---------- Previous post was at 03:13 PM ----------
wizzx said:
Yeah sadly but its true.
2.rebootet into fastboot mode and executed the flash-all batch file from the official rom.
Click to expand...
Click to collapse
i can not - it freeze on Google logo (not color) white word GOOGLE and bootloop arter restart
i can - it freeze on logo and reboot after pressing on power and volume

I've been looking all day for a solution but it doesn't seem like it's possible with Nexus 7
My Nexus 7 stopped booting to stock firmware, seemed like the OS went corrupt. I went to reload from fastboot but when installing I was met with failed to write errors when reloading the bootloader from fastboot. The device froze and now it's bricked.
I can get the device into APX mode and I actually found drivers to speak to the phone with nvflash for asus transformer but there is no bootloader image or blob available to reload the bootloader for Nexus 7 when in APX. I keep hearing that the flash tool to reload the bootloader is encrypted and not released from google or asus for N7. I hope this is not true and it would be awesome if someone could provide some assistance.
Thanks.

Asus`s drivers not for nexus!!!
you can try Nvidia mobile device boot drivers and ASM developer with working nexus 7
i can see in device`s list at my linux my device - but like unknown Tegra device
but if somebody can make full dump of any partition of nexus 7 - the flashing due APX mode can be real too.
-------------------------------

I just tried to flash the stock 4.3 ROM with Nexus Root Toolkit and some errors popped up.
Now i can't even boot my N7... Not even the Google logo. Is this the same problem???

jellymelly said:
I just tried to flash the stock 4.3 ROM with Nexus Root Toolkit and some errors popped up.
Now i can't even boot my N7... Not even the Google logo. Is this the same problem???
Click to expand...
Click to collapse
It's the same problem only if you can no longer get to the fastboot menu (or any menu at all) and when you plug your device into your computer, then hold the power button for 15 seconds and the driver says "APX". If your device can be turned on to the fastboot menu or any menu at all, then it's not the same problem.
Reading through the forums, it's an absolute joke that Asus and Google have not released the tools to resolve this problem given how many ppl have this issue.

Aethelwulf said:
Asus and Google have not released the tools to resolve this problem given how many ppl have this issue.
Click to expand...
Click to collapse
it`s cruel world and Google/Apple/Samsung/etc want to sell-sell-sell
our problems - belongs only to us
by the way - my new nexus 7 FHD come to my Town and tomorrow i can get it
(very quickly - 8 days from amazon (us) to russia)

Today started up Nexus 7 16GB Wifi 2012 version after a long time, so a software update came up.
Downloaded, applied it and stuck about at 80% of installation. So after 4 hours of waiting, pressed the power button until tablet shut down. Then tried to power it up, but nothing happened.
Tried bootloader mode, power button + volume up, power + volume down, all 3 pressed, EVERY combination you can think and i get the following:
Every way i get black screen. Like it never has never powered up. Just black screen, no powered up and showing black coloured screen, but simple black screen. The tablet is working in the background and showing absolutely nothing.
If i connect it to a pc, I can get in 2 modes. In an unknown mode and in APX mode (i also installed some drivers for APX).
When first connected to pc, it get in the unknown mode (I assume fastboot mode???) but cannot install any driver
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
10 second press of power + volume down buttons get me into APX mode
without drivers
with drivers
I assume we need this nvflash tool, to use APX mode in order to flash a bootloader and then recover everything via fastboot.
ANY ideas before contacting service?

Koyfo said:
Today started up Nexus 7 16GB Wifi 2012 version after a long time, so a software update came up.
Downloaded, applied it and stuck about at 80% of installation. So after 4 hours of waiting, pressed the power button until tablet shut down. Then tried to power it up, but nothing happened.
Tried bootloader mode, power button + volume up, power + volume down, all 3 pressed, EVERY combination you can think and i get the following:
Every way i get black screen. Like it never has never powered up. Just black screen, no powered up and showing black coloured screen, but simple black screen. The tablet is working in the background and showing absolutely nothing.
If i connect it to a pc, I can get in 2 modes. In an unknown mode and in APX mode (i also installed some drivers for APX).
When first connected to pc, it get in the unknown mode (I assume fastboot mode???) but cannot install any driver
10 second press of power + volume down buttons get me into APX mode
without drivers
with drivers
I assume we need this nvflash tool, to use APX mode in order to flash a bootloader and then recover everything via fastboot.
ANY ideas before contacting service?
Click to expand...
Click to collapse
Hello, i have the same problem !
Only the difference is, my nexus 7 discharged, and i pluged in over night to charge. (i charged in off mode). Then morning i wanted to power on and nothing. I tryed all button combinations, but the screen remains dark / dead !
Only when i plug in the Pc, it says APX device, and i can do nothing ( .
Please, someone have found a solution for this?
Thank you ( sorry for my bad english)

Too bad! Solution not yet found

Same problem
Same problem to my Nexus7 (2012) :crying:
Waiting for any solution, before to send it to assistance
Bye. Ivan

Well guys, today i dispatched the tablet to asus service. I hope everything will go ok. I will inform you if I have any news.

LG G2 Stuck with grey lines after using auto rec. please for god sake help me.

ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device; LG G2 D802 32GB

Some one please?

DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.

This is why I worry messing around with my G2

Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk

Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.

This is a known problem. Have LG send you a new one

blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?

did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?

stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.

walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.

Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.

walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.

walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.

Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files

wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?

stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk

So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.

Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!

Possibly bricked device, need D80020y image? (URGENT)

Hi, I was trying to update my LG G2 D800 to Lollipop using this guide:
http://webtrickz.com/how-to-update-lg-g2-to-official-lollipop-os/
However, after the device rebooted, it went to the LG logo screen, displayed this message in the top left corner, and went to an indefinite black screen.
boot certification error
secure booting error
cause: boot certification verify
Holding down the power button for about 15 seconds turns the device off, but sometimes it turns itself back on and does it again. Turning it off, then quickly holding volume down and power button, releasing on logo, then holding again brings it to a "Factory Data Reset" screen, however, doing a reset does nothing and puts me immediately back to the same problem.
Holding volume up and plugging it into my PC does the same thing, and when plugged in, windows recognizes about 20 "unformatted drives", and shows it as QHSUB_BULK in device manager, under other devices.
Before this, I was running stock 4.4.2, D80020y, rooted with towelroot. I had attempted to create a TWRP recovery, and it said it succeeded, however it was unable to boot to recovery.
I was going to try to fix it using this thread: http://forum.xda-developers.com/showthread.php?t=2582142
However, I am unable to find an img for D80020y.
I have access to a Win 8..1 desktop, and I can run whatever OS necessary in a VM.
Does anyone know where to find one? Or, can anyone provide me with one? Or, is there another way to fix this?
I'm just worried that my device is totally gone at this point, and considering I bought it used, I have no warranty, nor a phone to replace it, currently.
Thanks so much to anyone who can help me!

First off, why didn't you just do an OTA update to Lollipop (via settings/about phone) instead of trying to manually do it? It's a lot easier and you could of avoided all of this...
Anyways, I am not sure what exactly happened (maybe it was a bad flash or maybe you screwed up somewhere), but it looks like you've gotten yourself in a real mess.
Did you triple check that you followed the article step by step? Did other people state in the comments about any problems they faced when using the method?
I have tried that method you linked before, and I used Ubuntu, which is best for that method. However, it did not work for me. I remember going on and on with that and ultimately just flat out replaced my logic board when I had a bricked G2.
And I can totally relate to to the twenty unformatted drives, I have been in same exact situation with the endless windows popups when I plug in my phone, but I never really figured out the issue. I remember before I was stuck in fast boot mode, and after awhile I couldn't even get to fast boot.
Can you get into recovery? Is the phone still alive? If so, you can use this to get back to stock http://forum.xda-developers.com/showthread.php?t=2432476
Hope this helps a bit, I have never been in your situation but if you want a real, simple solution to this: I would purchase and replace your logic board (phone's motherboard). It is a definite fix. If you are not comfortable with that, then I would advise to go ahead and do some research about this. Unfortunately, I have no idea where you can get that img (I do not have a D800, but rather a VS980), but I am sure with some Google searches you can find it.
I have bricked a couple phones in the past, and we all learn from our mistakes!
Best of luck!

fischer12345 said:
*snip*
Click to expand...
Click to collapse
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.

Jtpetch said:
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Click to expand...
Click to collapse
Gotcha. I haven't ran into the issue you have been describing at all before, but I just wanted to try to understand this situation a little better, I wish I could tell you what exactly happened.
As far as your problem, here's what I would do. The phone is still alive correct? Contact LG and send that bad boy in. Tell them you used it for a couple of months and all of a sudden it does not work anymore. I think that would be your best bet. However, do not tell them you modified it or whatever you tried to do with it.
Be aware if you do send it in to LG, make sure you have not tried to open up the phone and screw around with it internally. They will not fix it if that is the case. Also, it can be quite pricey depending on your current condition.
Oh, and LG will not provide you with those files, they are there to help you with any kind of phone issue, but not these kinds of issues.
This my friend is the best advice I can give you! Again, another option would be replacing the logic board, but that is ONLY a last resort.
BTW, you didn't hard brick it so that's a plus

I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Jtpetch said:
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
Click to expand...
Click to collapse
can you enter download mode? pressisng VOL UP and then plug your phone and keep button press. does it goes to usb icon with curved arrows?

No download mode for me. Trying to boot to it just brings me the same error, and black screen.

Jtpetch said:
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Click to expand...
Click to collapse
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.

raptorddd said:
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
Click to expand...
Click to collapse
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.

Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
do the QHUSB_BULK Fix when u try it (its in 4)
anyway i got my g2 in a much heavier brick,
i have a third party lab that can possibly fix my g2...
its not that expensive....
so I just need to hope they can fix it

Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ

raptorddd said:
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
Click to expand...
Click to collapse
Yes, I am sure. I just tried it again, though, to confirm. Held volume up, plugged in USB, and it went to the LG logo screen, showed the same error text in the top left, and went to a black screen.
I am downloading the SRKtool right now, and will try as soon as i have it.

Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?

Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Click to expand...
Click to collapse
am not sure but there isnta kdz for lollipop right? you may need to go to KK KDZ
ooo you have d800 same as me. you need to download this and use the kitkat
Download Installer - KitKat 4.4.2 D80020c
http://forum.xda-developers.com/showthread.php?t=2663369 do that and once you in KITKAT ill tell you
if you need helps just ask

Ah, ok, will do. And thanks so much for all the help!

Jtpetch said:
Ah, ok, will do. And thanks so much for all the help!
Click to expand...
Click to collapse
no problem just hit thanks it i helped, once you in KK ill tell you how to go from there.

Wow, it flashed and everything without a hitch. I'm in KK now, and everything seems all good. So how would I go about upgrading to lollipop?

Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great

Jtpetch said:
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Click to expand...
Click to collapse
am glad you liked it, just pass the knowledge when someone is in the same shoes as you were..

i have the same problem as you please help
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
please guide me through what you did to get back to download
Click to expand...
Click to collapse