Database Info

[ROM] Stock deodexed, debloated w/ root, tethering (5/31 - 100% working for ALL!)

Features:
-Based on stock UCKD5 system image
-Rooted
-Busybox
-Fully deodexed and zipaligned
-Removed AT&T Code Scanner, AT&T FamilyMap, AT&T Navigator, Live TV, myAT&T, and YPmobile
-Enabled tethering
-Set the home page to google.com
-Made the included bookmarks removable
Flashing instructions:
1) Download the ROM and place it on your INTERNAL sd card.
2) Boot into ClockworkMod Recovery.
3) Open a command prompt and type the following commands (you must have adb set up on your computer):
Code:
adb shell
su
mount /sdcard
cd /sdcard
mv update.zip clockworkrecovery.zip
mv SGH-I997_UCKD5_rooted_deodexed_debloated_v3_no_wipe.zip update.zip
cd /
umount /sdcard
exit
exit
4) On your phone select apply sdcard:update.zip
5) That's it. Select reboot when it finishes and if you want a clean install you can just perform a factory reset after it boots.
Download:
SGH-I997_UCKD5_rooted_deodexed_debloated_v3_no_wipe.zip (165MB)
I do this for fun so you shouldn't feel any obligation to donate, but here's a link if you want to. Donations of any amount are very much appreciated.

you're the man.

To brick or not to brick ... is there a CWM you suggest i attempt from?
EDIT: not to brick ... waiting patiently.

Any way I can flash this via Odin?

sraitter said:
To brick or not to brick ... is there a CWM you suggest i attempt from?
Click to expand...
Click to collapse
Don't do it. I made the mistake of trying to force Captivate's on mine and I'm bricked now. Just hang around and wait for CWM to officially come out for Infuse.

Unkrash said:
Any way I can flash this via Odin?
Click to expand...
Click to collapse
No. If I had the device I could make it Odin flashable, but there's no way that I know of to create/modify rfs images without a Samsung device.

Much appreciated! Debating trying this on my own but it seems smarter to at least wait for CWM.

crawlgsx said:
Much appreciated! Debating trying this on my own but it seems smarter to at least wait for CWM.
Click to expand...
Click to collapse
you can mod3e recovery and it may flash through there. i will see if it is the same locations as the capitvae, it if is close then you can use a batch script in windows that will abd everything for you. otherwise it is pretty easy after you have root which is also done in a batch script from lost1 or with superoneclick root.

Dani897 said:
you can mod3e recovery and it may flash through there. i will see if it is the same locations as the capitvae, it if is close then you can use a batch script in windows that will abd everything for you. otherwise it is pretty easy after you have root which is also done in a batch script from lost1 or with superoneclick root.
Click to expand...
Click to collapse
Yeah I have root all set, the problem is with no CWM is if I flash this and something doesn't work I have no way home. No other rom or backup to flash.

One of you should email Koush. He will work with you to get the info he needs to make a recovery for the Infuse.

gtg465x said:
One of you should email Koush. He will work with you to get the info he needs to make a recovery for the Infuse.
Click to expand...
Click to collapse
Sounds like a good plan, will do. (done)

I have the device. I'm willing to make it if you provide me with the info to make it Odin flashable.

Yup I am pretty ambitious also.
Hoping for some progress on that front tomorrow.

lost1 said:
I have the device. I'm willing to make it if you provide me with the info to make it Odin flashable.
Click to expand...
Click to collapse
It's a pretty tedious process so probably better to just wait for CWM.

I'm bricked myself so really, to only thing I CAN do now is wait for an Odin image. That's about the only reason why I'd want it.

Unkrash said:
I'm bricked myself so really, to only thing I CAN do now is wait for an Odin image. That's about the only reason why I'd want it.
Click to expand...
Click to collapse
How did you brick it?

gtg465x said:
How did you brick it?
Click to expand...
Click to collapse
Tried flashing on a Captivate kernel/ROM.

Unkrash said:
Tried flashing on a Captivate kernel/ROM.
Click to expand...
Click to collapse
With Odin or did the Captivate CWM work for you?

I'm not worried about tedious, rather know the ins and outs. Let me know if you change your mind.

lost1 said:
I'm not worried about tedious, rather know the ins and outs. Let me know if you change your mind.
Click to expand...
Click to collapse
Same, I have an iPhone 4 as my 'production' phone if it comes to that.

[Q] Nexus S 4G won't boot past Google Screen!!

I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??

There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).

Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?

deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.

It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )

deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?

deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.

I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.

deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps

Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.

same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...

nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David

I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.

[OUDHS] CWM based recovery for AT&T Express

Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.3
for your AT&T Samsung Galaxy Express
Read this whole post before doing anything ​
Enjoy
Odin Flashable - OUDHS CWM-based Recovery 1.0.3.3
Odin 3.04
Drivers
Directions:
1) Download the above files
2) Extract Odin3-3.04.zip and copy the tar that you downloaded into the folder
3) Run Odin as an administrator
4) Power your device off
5) Press and hold volume down and power to enter download mode
6a) Connect your phone to your computer
6b) Wait for drivers to finish installing if they need to be
7) You should see Odin find your device by marking a blue square in the ID COM box
8) Click on PDA and choose the recovery tar you downloaded
9) Click start
-----------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now if you wish to root youll need to follow these instructions
-----------------------------------------------------------------------------------------------------------------
SuperSU+ 1.25
Directions:
1) Download the above file
2) Connect your phone and copy them to your phone
3) Once they are copied power down your device
4) Hold volume up and power to enter Clockworkmod recovery
5) Navigate recovery by using the volume keys and power to select
6) Choose install zip from sdcard, then pick internal or external (where you copied it to)
7) Scroll down to the SuperSU+.zip and select it to install
-----------------------------------------------------------------------------------------------------------------
Congrats you are rooted! this procedure will work on any firmware update you guys get
-----------------------------------------------------------------------------------------------------------------
If you enjoyed getting root/recovery and want to show appreciation you can always buy me a coke​​
Source​
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) For being the best we can for those whom need us
rdawson28 For being an awesome tester
BlindArtisan For providing the stock recovery, thanks man

I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.

Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?

BlindArtisan said:
Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?
Click to expand...
Click to collapse
www.shabbypenguin.com/OUDstuff/Samsung/ATT/Express/Express-OUDHS-CWM.tar

Thank you. An alternate way to install for those who are rooted and don't want to use Odin.
Create a copy of the recovery on your sdcard.
In the android terminal or adb with shell type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
To make the recovery permanent.
Find /system/etc/install-recovery.sh
Rename the file install-recovery.sh.backup
Reboot into recovery and enjoy the glory.
Sent from my rooted SAMSUNG-SGH-I437 using xda app-developers app

JDC2389 said:
I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.
Click to expand...
Click to collapse
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.

Sworder said:
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.
Click to expand...
Click to collapse
You could always uninstall the drivers then install fresh ones from Samsung. Or use the in phone method.
Sent from my rooted SAMSUNG-SGH-I437

I has to uninstall then put the fresh drivers on thats the easiest way
Sent from my SAMSUNG-SGH-I437 using xda app-developers app

Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.

invert_nexus said:
Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.
Click to expand...
Click to collapse
I have the exact same issue with the date.
I don't quite understand what you are saying, but It doesn't try to fix root on boot it tries to fix the recovery.img
Sent from my rooted SAMSUNG-SGH-I437

Thanks blind you came through for me, that way I didn't have to worry about my phone being recognized in download mode. Nice job on the recovery it looks fantastic.
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Someone needs to make a video about this root method to spread the word and upload it to youtube!

Worked flawlessly on a new phone. A 6 month old one, all appears ok, it sees the phone, odin loads the image, phone reboots ok. When I try try to reboot into recovery mode I get the stock recovery, not CWM.
Any ideas?

guys i am so sorry, i had to reinstall linux and thought i lost teh device t ree, anyways i compiled a new version of OUDHS recovery for yall. and finally uploaded source

Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?

invert_nexus said:
Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?
Click to expand...
Click to collapse
source is at the link
and there is a good deal different in the latest version. honestly i suggest everyone upgrades

Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.

invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
Havent updated yet but sounds like the same problem as before ill test tomorrow been really busy also gonna work on the cooked up rom more when I get a chance im sure the recovery issues will be fixed shortly
Sent from my SAMSUNG-SGH-I437 using xda app-developers app

invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
the time will always be off, recovery doesnt talk to the rest of the phone. crap, did that get fixed? or was it always broken?

shabbypenguin said:
the time will always be off, recovery doesnt talk to the rest of the phone.
Click to expand...
Click to collapse
Odd. Is that just an ussue with this phone?
crap, did that get fixed? or was it always broken?
Click to expand...
Click to collapse
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.

invert_nexus said:
Odd. Is that just an ussue with this phone?
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.
Click to expand...
Click to collapse
the time this is android wide afaik. twrp and official cwm have teh same bug :/
and crap that means some of the new features broke stuff for yall :/ ill put the old on back up in the OP i was really hoping to give you guys touch recovery

[FIRMWARE] Flash KitKat the EASY Way!!!! or Go back to JellyBean

KitKat the EASY Way!!!!
Or, go back to 4.2.2 JellyBean
If you are going to return your phone back to warranty, I would suggest this method in this thread as it does a COMPLETE wipe of your device and puts it back to 'Factory'. It removes Root Flags so it does not show having been rooted, and removes ALL data.
Disclaimer: This is not MY method, but a method I used. The information and files have been figured out over time by many individuals and it's been combined in this thread.
This thread is to help Noobs AND Veterans to flash their ATT D800 LG G2 to KitKat. This will be very spelled out, and I’ve even included a video (see below), so NO Mistakes. Yes, that means you!
PLEASE refer to the Video Below before asking questions, as too many questions get a little overwhelming.
Warning! Please Read!​
This WILL erase everything on your phone and put it back to FACTORY STATE, so be sure you’ve backed up!
Ok, first thing you need to do is download the version you want. I’ve got KitKat 4.4.2 version D80020c, and I’ve got JellyBean 4.2.2 version D80010o. These are VERY LARGE files, so be patient, although I am able to get as much as 6MB/s download speeds from this server.
BIG THANKS TO bigfau for the KitKat TOT and DLL files!!!​
Download Installer - KitKat 4.4.2 D80020c - This Flashes Stock KitKat, WITHOUT Root, and WITHOUT Recovery. - Use TowelRoot and AutoRec to get Root and Custom Recovery. - Single File LARGE archive. KK MIRROR DOWNLOAD
D80020c Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download.
Download Installer - JellyBean 4.2.2 D80010o - Single File LARGE archive. JB MIRROR DOWNLOAD
D80010o Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download..
Download Installer - JellyBean 4.2.2 D80010d - This is for those who want to install Custom Recovery and not update to KK... - Single File LARGE archive.
Now, for the fun stuff (You may want to print this out for reference and check them off as you go)
Pre-requisites:
1. Be sure your phone is currently running a Compatible based ROM. If not, please flash a Custom Compatible Based ROM onto your phone. (ie: If you have a D800, be sure you have a D800 ROM on it. If you have a D802, be sure you have a D802 based ROM on it.)
2. Be sure you have turned on USB Debugging before starting.
Step #1: Program Installation:
1. Save the installer to your desktop
2. Run the Installer by double clicking
3. Wait a while for everything to extract (It might look like nothing is happening. This can take a few minutes, be patient, it’s HUGE)
4. (On Win7 or Win8, Accept User Account Control)
5. Accept my License
6. Don't Change Anything and click ‘Install’
7. Wait some more… and more… Large files are extracting…
8. When it pops up, click ‘Next’ to install the LG drivers. Even if you’ve already installed them, install again! This is to verify you’ve got the right ones installed.
9. Click ‘OK’ to finish the Driver install
10. Click ‘Next to install the LG Flash Tool
11. Don't Change Anything and click ‘Install’
12. Uncheck ‘Run LGFlashTool 1.8.1.1023 and click ‘Finish’ (If you forget to uncheck this, just close the program when it opens)
13. Click ‘Next’ to start the LGFlashTool Patch. (This makes it so you don’t need to change the date back on your PC)
14. Click ‘Next’ again
15. Click the bullet to ‘Agree to my License’ and then click ‘Next’
16. Don't Change Anything and click ‘Next’
17. Click ‘Start’
18. Click ‘Next’
19. Click ‘Exit’ to finish Patch Installer
20. Congratulations, Program Installations are all DONE!
Step #2: Place Phone into Download Mode:
1. With phone NOT plugged into a USB Cable, Hold the Power button to turn off phone
2. Plug your USB cable into your computer
3. Hold the Volume UP Button on your Phone
4. While Still Holding the Volume UP button, plug in the USB cable to your Phone
5. Continue to hold the Volume UP button until your phone enters Download Mode
6. If this does not work, pull the USB cable and start from #1 of this section
Step #3: Change Com Port to 41
1. With your phone STILL in Download Mode and STILL Plugged into Computer
2. Go into Device Manager
---a. Press and hold your Windows Key (Between CTRL and ALT)
---b. Tap the ‘Pause/Break’ Key (Usually Top Right of Keyboard, might be different on yours)
---c. Click on ‘Device Manager’
3. In the Device List, scroll down to ‘Ports (COM & LPT) and double click to expand
4. Find the ‘LGE AndroidNet USB Serial Port (COM4)’ (Your COM Port Number might be different, that’s OK)
5. Double click to open the port
6. On the Tabs at the top of that screen, click on ‘Port Settings’
7. Click on ‘Advanced…’
8. Click on the Com Port number to drop down the list
9. Scroll down to ‘COM41’ and select it
10. Click ‘OK’ Button to save that
11. Click ‘OK’ Button to close the Com Port Properties
12. Close the Device Manager
13. Close the System Window
14. Go back to the Desktop
15. That’s it, You’ve Changed the Com Port to 41
Step #4: Run LGFlashTool:
1. Double Click the ‘LGFlashTool’ icon on the Desktop (Win7 or Win8 accept ‘User Account Control’)
2. In the ‘Model Config’ window, check the box ‘Select Manual Mode’
3. Next to the DLL space, click the Three Dots ‘…’
4. Select the DLL file named ‘LGD800_.....v160.dll’
---a. For 4.4.2 KitKat, select ‘LGD800_20130811_LGFLASHv160.dll’
---b. For 4.2.2 JellyBean, select ‘LGD800_20130904_LGFLASHv160.dll’
5. Click the ‘Open’ Button
6. Next to the S/W space, click the ‘Remove ALL’ Button
7. Next to the S/W space, click the ‘Add’ Button
8. Select the tot file for the version you are flashing
---a. For 4.4.2 KitKat, select ‘LGD800AT-01-V20c-310-410-FEB-02-2014+0.tot’
---b. For 4.2.2 JellyBean, select ‘LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot’
9. Click the ‘Open’ Button
10. Click ‘OK’ Button to save choices
11. In the LG FlashTool program, click the ‘Yellow Arrow’ pointing to the Right.
12. Wait for the program to verify your DLL and TOT selections (This takes a while)
13. If successful, you will see ‘READY!!’ on ‘Port 1 (COM41)’
14. If you DON’T see ‘READY!!’, you may need to start over
15. If you see ‘READY!!’ unplug your phone from the USB cable and Plug it right back in. DO NOT PRESS ANY BUTTONS ON YOUR PHONE. It should STILL be in Download Mode.
16. The LG FlashTool progam will now start flashing your phone!!
17. At around 80%, the program will restart your phone.
18. It takes a while for the phone to restart, but it will boot to Android. Wait for the flash program to finish and it will turn your phone back OFF. And give you a ‘SUCCESS”
19. Close FlashTool
IF for some reason, the LG FlashTool does not finish 100%, and you get a ‘Fail’, as long as your phone has now rebooted into Android, you don’t need to worry about this. Just close the program, and enjoy your Freshly Restored LG G2!
For anyone having issue with the device check not passing due to mismatched device (caused by flashing a Custom ROM with Different device model ID to your D800: ie, D801 to a D800 or vice versa.), try using the attached dll file instead of the device specific one. It has been reported to work for many... You will need to extract the zip file to get the dll.

good stuff bud!

Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies

Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.

epapsiou said:
Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies
Click to expand...
Click to collapse
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
BAM1789 said:
Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.
Click to expand...
Click to collapse
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.

You my friend are a very nice person lol. Taking the time to put this together.
Sent from my LG-D800 using Tapatalk

SuperSport said:
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
I haven't had my G2 very long so I haven't been able to test myself, but just looking around the forum seems the 10o firmware causes boot issues with some custom ROMs. I could be wrong though. Maybe the problem doesn't exist anymore and I'm reading old info.

SuperSport said:
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.

epapsiou said:
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.
Click to expand...
Click to collapse
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.

SuperSport bro u made my life so much easier. Thank u for your hard work bro.
Sent from my LG-D800 using Tapatalk

SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.

epapsiou said:
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.
Click to expand...
Click to collapse
I'm having the same issue flashing any stock based rom on 800o. It throws me in a bootloop. How would I get the 800d fw?
Sent from my LG-D800 using Tapatalk

SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.

Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.

Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app

Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?

Sorry Everyone, I've been out of town and only on my phone, but mostly busy with family stuff.
freebee269 said:
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.
Click to expand...
Click to collapse
Thank you for the clear info. I will build a 10d version. Hopefully tomorrow.
strose09 said:
Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.
Click to expand...
Click to collapse
I'm sorry, I have been away from home. Just read this. Yes, you are fine if your phone is rooted. This Flash will remove Root. As mentioned in the First post, there is currently no way to root KitKat, (Unless I've missed something since last night). So root, then go to KitKat.
mjgspr95 said:
Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Some people have issues with Internet Explorer on Mega Website. You might install Chrome or Firefox and try it that way, or use a Download Manager of your choice.
humblehyper said:
Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?
Click to expand...
Click to collapse
That is Correct, no Custom Recovery. Not unless something has appeared since last night when I last went through the forums.

Usefull guide thanks
but i think there is not a difference between those Flash DLL i had 20130904 and just freshy flashed KitKat
also if anyone cares about a LG Flash tools "PASS" then while it stops on 80-94% and boot into OS itself, do a Factory Reset of phone and it will check a Factory Flag (it sets to 5) and gives message a PASS

Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk

pcoruganti said:
Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Oh but indeed it is.
Sent from my LG-D800 using Tapatalk

OTA downloaded, and captured... It begins || update 5/7/16

ADDED INSTRUCTIONS AT END OF POST*****
Got it.... Rooted, twrp, the whole deal. On 6.0. I'll post instructions in the middle of the week for everybody.
Unfortunately if you already did the other method, you are screwed for now. Because the method I used required me to flash a stock 5.1.1.
Standby
_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|
So there I am sitting on my computer last night, when a notification pops up on my V10 .... The old "congratulations, you've won first prize in an update contest!"
Lo and behold, the MM update had downloaded (at record speeds I might add).
Without wasting a minute, I navigated to the cache partition and copied it to my internal folder (see attachment), then backed it up on drive.
So... We'll just skip to the good part...
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
I'll save you all the curiosity and let you know that I am going to look into this option to flash the OTA this weekend. I'm going to assemble a compatibility analysis and if everything checks out, I'll flash it.
Standby for carnage.
****INSTRUCTIONS
OK... I really owe everybody here an apology for taking so long to get an official instruction up. Work has been crazy this week. But I wanted to be able to take some time to do this. So here we go...
But wait... Before we even start, please for the love of God do your homework here. Please go read through chains thread about his app, how it works, etc. The interface is straight forward enough, but there are other things to understand. Please just understand what you are doing, and please verify checksums of anything you download. This is very important.
And thank chainfire, not me.
PRE-FLASH REQUIREMENTS:
1. First and foremost, you MUST be on the latest version of MM TWRP. There is a thread in the development section for this, with instruction on how to flash it, find that thread. Get it installed. This is a must. You must also verify adb and fastboot are working fully on your device.
2. You must be 100% Stock (but rooted) on the latest TMO V10 5.1 1 firmware and ROM, no custom kernels, nothing. Stock, with the exception of working root, and the latest 3.0.2.0 Marshmallow TWRP. When I say stock I mean no deodex, no system apps removed, this is an absolute requirement. The reason for this is mostly to avoid the update.zip from aborting as it does checks for presence of apps within system, etc. If you have to flash a stock ROM before doing this, don't do it as an "in line" queue before you flash the OTA in flashfire. Do it separate.
3. You must have the official OTA downloaded and on your internal SD card. Also, put the latest superSU version 2.67 on an external card, and remove the SD card from the device. The md5 for the OTA is 280ad51eb96457df097df5a088a535af9
Once you have checked those 3 boxes. You are ready to proceed.
4. Install flashfire. I was on version 32.
5. Open flashfire, grant it root
6. Go into the setting of the app, check the "Flash boot loaders" and "Freeload" box.
7. Find the OTA package, queue it up with "flash zip or ota" (small + sign at the bottom right of the screen)
It is important to note that after the flashing process completes, you will want to power off the device, and boot it into fastboot mode to unlock the boot loader.
8. Execute the update.
9. After it finishes, power off the device.
10. Boot into fastboot by holding down the volume down button, and with the button held down, plug the USB cable into your computer.
11. Once in fastboot, type the following command and hit enter:
Code:
fastboot oem unlock
Let it run for a bit, it is going to wipe your data.
12. After it completes (your terminal should give you a time displayed for the operation).... Unplug the phone, and yank the battery.
13. Pop in your Micro SD card (with superSU 2.67 flashable on it) then manually boot the phone into recovery mode. You are going to flash superSU again as a sanity check. I did this because if for some reason FF didn't flash superSU, and then the system wrote over your recovery during your first boot... You'd be absolutely dicked stuck on stock MM with no way of getting root back for now. I like verification...
To boot the v10 into recovery mode manually, simply have the device powered off, then hold the volume down and power button at the same time. AS SOON as you see the boot screen (not to be confused by the boot animation) released the power button for just a little less than a second then press and hold it again (keep the volume down button pressed the whole time). It may or may not be absolutely critical that you don't screw this part up. You need to get into recovery at this point to validate root being installed.
This should take you into 2 sequential screens, both asking about clearing data, select yes for both (don't worry, it won't, it will take you into TWRP.
Once in twrp... Mount your SD card in the twrp settings, and flash superSU.
Reboot afterwards. Done.
After you do this, you will be in 100% stock, rooted MM.
You might need to flash twrp again (do it the normal way, you are done with flash fire now), but root, you will have, and full functionality, you will also have, with everything working.

Dont do it. No root for MM at the moment.

Double0EK said:
Dont do it. No root for MM at the moment.
Click to expand...
Click to collapse
Unless you use Eliminator74's rooted rom which is the official MM update from T-Mobile.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.

markbencze said:
what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.
Click to expand...
Click to collapse
I'm debating that myself
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

Standing by!
Sent from my pretty nifty brand new LG V10

Ok. Im actually interested in the outcome.

I think a lot of us are curious to see if it works. For all we know this is the solution that we've had the entire time. the question is, is anyone brave/crazy/foolish enough to try it? It might work great, but then again it could brick your phone given LG devices are untested trying this. there are several devices that were also untested that it did work on so who knows. But the app does have the capabilities to flash a stock update.zip and maintain boot root and recovery. I would think you'd have to reunlock your bootloader after flashing though in order to boot.

anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache

In for results

dimm0k said:
anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache
Click to expand...
Click to collapse
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

A think tank.
If the update is zip, can the flash be done with TWRP plus superSU?!

truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip

truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
so is mine

dimm0k said:
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip
Click to expand...
Click to collapse
That's weird. Wonder why your's went there?
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

See OP... got it.

warBeard_actual said:
See OP... got it.
Click to expand...
Click to collapse
Got what? Is in you used Flashfire and updated via ota and were able to retain root and TWRP? Sorry, I"m running g on almost no sleep cause my truck broke down and is in the shop and it's hard to sleep in the customer lounge of a Freightliner dealership.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.

crashnova said:
Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.
Click to expand...
Click to collapse
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

truckerdewd said:
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
I woke up to the OTA this morning. I find it odd tho because i thought OTAs were disabled on siraltus rom. I would try FF but don't eant to risk bricking until OP shares the steps he took.