Develop Bugs

AT&T to JME boot/recovery fix

Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders

thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?

quickk said:
thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?
Click to expand...
Click to collapse
I can confirm that this works, but, since we don't have stock bookloaders for at&t, its a one way trip. If you go back to the stock at&t firmware that I built, it will boot blank and you wont be able to see the stock recovery screens.
Its not perfectly safe in that if you fail to flash JJ4 bootloaders you can brick your tab. But once you have them, your tab becomes perfectly compatible with the euro firmware.

So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Sent from my GT-P1000 using XDA App

alexnoalex said:
So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Click to expand...
Click to collapse
I only know the results. Anyone who has flashed them back, either through Odin, Heimdall or dd has created a brick.

alexnoalex said:
Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders
Click to expand...
Click to collapse
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?

Jeepsdaddy said:
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?
Click to expand...
Click to collapse
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment jj4_bootloaders.zip

rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment 496999
Click to expand...
Click to collapse
Yes I did the RotoBackup per your instruction.
I'd prefer to wait until it is no longer a one way ticket. I need to be able to return to stock. The way I understand it now is that I can easily return to stock from my current state. Is that correct?

From Chat. To test with JME v4

Jeepsdaddy said:
From Chat. To test with JME v4
Click to expand...
Click to collapse
What are we testing with the swype?

Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.

rangercaptain said:
Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.
Click to expand...
Click to collapse
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.

Thank you Roto-Amigo. The jj4 bootloaders flashed though odin in the pda spot, now the at&t tab has the logo restored, the black screen and white line is gone.

Failed to update
Hi!
I tried this with the attached file, and had no success. As I'm quite unfamiliar with Odin, I will post an image of the failure but I lack debugging know-how with this tool. I'm willing to do whatever, but don't know what "whatever" is.
I appreciate any advice, especially with the information-gathering process. (Note: I did download again, from a different computer, with the same result.)
{
"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"
}

Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.

rangercaptain said:
Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.
Click to expand...
Click to collapse
Sheesh, I had not been in download mode. In my (weak) defense, I had only done this once - and that's to apply JME4. I'll get better. The patch is applied and all looks well! Thanks for your indulgence, and for the prompt!
I knew the drivers were correct since nothing has changed on this PC (haven't used it) since applying JME4 to the Tab. I'll have a quick search for chainfire's bootloader patch.

rotohammer said:
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.
Click to expand...
Click to collapse
Hello rotohammer, sorry to bother you but I'm having a problem that I cannot seem to fix. Can you kindly see my post to see if you can help me? You seems like the one who knows the a lot about the AT&T Galaxy Tab. Thanks in advance for your help!
http://forum.xda-developers.com/showthread.php?p=11333386#post11333386

fixed me up!
rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
....
I only recommend this firmware for AT&T Tabs that have the screen problems.
View attachment 496999
Click to expand...
Click to collapse
totally fixed my blank screen booting! thanks!!
ATT Galaxy Tab, stock to Roto JME v1
Fixed Blank Boot w/Line w/jj4 bootloaders

hi guys,, i have tab that stuck at galaxy tab logo,, it cant access recovery mode but download mode is still ok.. ive tried many thinks including flashing pit and rotov4. but no luck. it always 'pass' but stuck at galaxy tab logo..
so my question is, can my tab ( arabic tab) be flashed with this jj4 so it can be normal again?..
thanks

[NOW PUBLIC!] Team Codefire Presents: Project FreeGee!

Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/sprint/freegee/FreeGee-0.5_Sprint.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...

Thanks to all of u guys for all your hard work!

Here is some proof, this is fully working...
{
"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"
}
Sorry for the blurry images, took these from my old OG Evo... But can say its fully unlocked!!!
Nice work thecubed, and shellnut2 on this, thanks for keeping our freedom alive!!!

Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app

Tyederian said:
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've already run the OTA, and had no issues unlocking, or rooting after the OTA...

I am so excited! I cannot wait to get this thing unlocked! :victory:

Sweet super excited

Awesome! Will be donating to the team on pay day thanks guys!
Sent from my PG86100 using xda premium

That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!

Wow! Many thanks to all the devs for their hard work and to the beta testers for their willingness to let their phones be guinea pigs. Very much looking forward to this!
Sent from my LG-LS970 using Tapatalk 2

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
$55 they charged me $99 and some tax on top of it. how did you pull that off?

Super sweet you guys are awesome!!

Christmas came early this year.
Sent from my LG-LS970 using xda app-developers app

New build is up!
Fixed a typo in my code haha

awesome job, big thanks to everyone.
And I second that $55 question.

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
How on earth did you get it for $55?

tabormeister said:
How on earth did you get it for $55?
Click to expand...
Click to collapse
Had signed up for phone freedom to get $50 gift card back in February.

So I just ran this and had a couple little panic moment!!
1. While reading the script, SU poped up and I missed the "Grant SU" button on the phone. I still got the backup folder but nothing was in it. I then thought it worked, rebooted, and nothing.
The second time I ran this, I got to the "Grant SU" button in time and all went GREAT!!! This time I had files in the backup folder.
2. When I rebooted into recovery, I tried to make a backup. I hit the backup button and got some message that said "Can't mount backup path". So i tried the backup to internal SD and it worked.
Figured I'd write this in case anybody else had the same moment's I did.
The files on the backup folder are very differnt from what I'm used to so hopefully I did it correctly. I noticed there was an option in CWM to choose the backup format after I'd made my backup, so I'm not sure which format is correct for Restore. I guess I used the default which is .dup.
Thank you very much dev's for this!!!!!:laugh:
---------- Post added at 05:54 AM ---------- Previous post was at 05:25 AM ----------
DO NOT use the camera!!!! It'll crash your phone!!!
I read about it in the ATT section just now, but it's too late for me. So I guess we have this bug also.
OK...so not quite a crash. Held the volume down button and power together and got it to reboot.
Now we just need to have a way to recover our phones if/and/or when we do crash our phones. I know the devs are working on this, as obviously they are the bomb!!!

Tease: Two things brewing that hopefully will be up today. Both directly related to this

Shelnutt2 said:
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Click to expand...
Click to collapse
I'm sure hoping you're referring to my post above. I get alittle wiggy if I don't have a way to fix my phone myself.

[RECOVERY] ClockworkModRecovery 6.0.1.2 (From Source)

Ladies and gentlemen, humans and androids, I present to you...
CLOCKWORK MOD RECOVERY 6.0.1.2
{
"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"
}
​
Install/Backup/Restore/InternalSD/ExternalSD all working!
For all you blob haters out there, you can switch the format from dup to tar in backup options!
Procedure is as usual:
1. Open Odin and ensure your phone is in DOWNLOAD mode.
2. Place the recovery.tar.md5 in the PDA slot.
3. Check auto-reboot and hit Start.
4. Wait for it to finish. Are you waiting? Wait until it finishes!
5. Enjoy an up-to-date CWMR6.
Recovery files are attached, along with Odin.
I've bumped into a few errors trying to get this working, so I'll post the symptoms and the solutions:
1. If the MD5 breaks validation, you changed the name of the recovery.tar.md5 -- it needs to stay the same!
2. If your transfer hangs, your cord may be bad. Mine kept getting stuck at 10% or so, and then I noticed my dog had bitten through the cord a little earlier. The cord is only good for charging, now.
If you have any questions or comments, I'll help as best as I can.
Aquethys' Recoveries are UNSUPPORTED by me.
Aquethys' old TOUCH recovery (Touch Recovery CM6) can be found at: http://aquethys.cu.cc/Glide/recovery.tar.md5
Special thanks to:
utkanos
KemoNine

Nice dude
MIRROR:
DOWNLOAD HERE

I hate to say this, but I get the same error message as I did flashing Aquethys version he was building!
write data size too big[14|sos] [Data:5213532(8) -> Part: 2550/2550(2k8)]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xffffffff]
Click to expand...
Click to collapse

can we have a flash cwmr of this? i know we can update cwmr this way as well - did that before on i9100 device.

dbrannon79 said:
I hate to say this, but I get the same error message as I did flashing Aquethys version he was building!
Click to expand...
Click to collapse
You shouldn't have any problems. Are you sure you downloaded and tried to use the right one? I have tested it, for sure, and it worked great on an I927R (mine, Rogers/International variant) and a I927 (girlfriend's/AT&T variant).
You'll get that error if your partition size is too small for recovery -- our recoveries *are* limited -- to about 5,200,000 bytes -- this is just under that and should work fine. You should not be screwing around with it.
Ensure you are using the recovery.tar.gz I included. Then attempt to do it again -- I have a feeling you may have flashed Aquethys' again.
And just noticed -- the recovery you used is larger than mine -- mine is 5,02x,xxx length in bytes -- so yours is not mine, since it went to 5,213,xxx.
taiber2000 said:
can we have a flash cwmr of this? i know we can update cwmr this way as well - did that before on i9100 device.
Click to expand...
Click to collapse
Well, I think I know how to do that -- but it's a little more risky. Involves manually using commands to write to the partition -- which is less stable/ideal than Odin. I was talking to some folks (when my cable was bad) and they said we could do that method as a LAST OPTION. They didn't seem to be too happy of the thought -- but it is something I could potentially research. It may have just been because I was potentially sacrificing my phone, when I didn't know for sure if it was correct/good.

Works well with i927 (AT&T) Version..

So, after playing around with this some more, this morning, I've discovered that the most important part -- being able to backup/restore -- is not working. Not sure if it is because it may be from an unstable branch of CM10 trying to integrate the newer Jellybean or what -- but I intend on fixing it and finding out what the problem is.
I didn't worry about testing the backup/restore, since I have no data/etc -- but I did test whether or not we could flash from internal or external SD cards, which does 100% work.
So, just a word of warning (I've included it in the topic) to be careful if you flash -- you may not be able to recover/backup as you would like to. I'll try to get this working within a week.

terinfire said:
So, after playing around with this some more, this morning, I've discovered that the most important part -- being able to backup/restore -- is not working. Not sure if it is because it may be from an unstable branch of CM10 trying to integrate the newer Jellybean or what -- but I intend on fixing it and finding out what the problem is.
I didn't worry about testing the backup/restore, since I have no data/etc -- but I did test whether or not we could flash from internal or external SD cards, which does 100% work.
So, just a word of warning (I've included it in the topic) to be careful if you flash -- you may not be able to recover/backup as you would like to. I'll try to get this working within a week.
Click to expand...
Click to collapse
Will be recovery type be Blob type ?

If it is CWM6, it will be. I may be able to see if there's a flag or two I can set to change it away from blob -- I know people seem to not like that.

thanks a million this will make development so much easier .. and it can even mount the external

terinfire said:
You shouldn't have any problems. Are you sure you downloaded and tried to use the right one? I have tested it, for sure, and it worked great on an I927R (mine, Rogers/International variant) and a I927 (girlfriend's/AT&T variant).
You'll get that error if your partition size is too small for recovery -- our recoveries *are* limited -- to about 5,200,000 bytes -- this is just under that and should work fine. You should not be screwing around with it.
Ensure you are using the recovery.tar.gz I included. Then attempt to do it again -- I have a feeling you may have flashed Aquethys' again.
And just noticed -- the recovery you used is larger than mine -- mine is 5,02x,xxx length in bytes -- so yours is not mine, since it went to 5,213,xxx.
Well, I think I know how to do that -- but it's a little more risky. Involves manually using commands to write to the partition -- which is less stable/ideal than Odin. I was talking to some folks (when my cable was bad) and they said we could do that method as a LAST OPTION. They didn't seem to be too happy of the thought -- but it is something I could potentially research. It may have just been because I was potentially sacrificing my phone, when I didn't know for sure if it was correct/good.
Click to expand...
Click to collapse
my apologies! after going back and looking at my download folder, realizing it's time to clean!! I reflashed your recovery and works!
Thanks,
I would like to see the recovery without the blobs that way single backups can be made and archived! also I do enjoy the "touch" version if there is a possibility putting all that together!
Thanks again and have a blessed thanksgiving!

I'll put the touch recovery back up. And...
I'm going to try to build TWRP in the next couple of weeks. Terinfire, you interested in helping me?

Aquethys said:
I'll put the touch recovery back up. And...
I'm going to try to build TWRP in the next couple of weeks. Terinfire, you interested in helping me?
Click to expand...
Click to collapse
TWRP! Wonderful! Million Thanks!
TWRP and physical keyboard is a great combo because you have a comfortable shell in recovery mode

Terin did you build in Ubuntu? ;/
I might have to cm sync again.. Takes forever xD like 2 hrs
Sent from my SGH-I747 using Tapatalk 2

Aquethys said:
Terin did you build in Ubuntu? ;/
I might have to cm sync again.. Takes forever xD like 2 hrs
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I setup a VM. Thankfully, my laptop is a monster so I have it virtualizing 8 cores without an issue. Don't ask the specifics, but to give you an idea -- it has two full-sized 5870's in it -- it's a monster.
Yeah, I have it working on Ubuntu. I'll see what I can do to help you out -- I can potentially build it if you help me find all of the details I need. I have a MUCH better understanding about how the entire systems work entirely, now.
So TWRP or whatever it is -- sure, I can see about helping you out with it. I'll probably finally need to get a github account or something, haha. Or get added to an existing TeamGlide one or something, hah.
Has anyone else tried to do a backup/restore with this? It didn't work for me -- but I'm curious if it worked for anyone else and maybe my SDCard's are formatted poorly?

I attempted to test the backup and restore! I found a setting for backup options, set it from "dump" to "tar" backed up to external sd. went well...
attempted to restore and got an error message "md5 mismatch"
opened the folder on my pc and saw where it made 2 .img files one boot and the other recovery. and a "system.ext4.tar" and "system.ext4.tar.a"
tried to open both if the archive files and both gave errors with archive manager in ubuntu, could not open! havn't tried the "dump" style backup yet!
Thanks.

terin,
Here's a permanent link for the touch recovery:
http://aquethys.cu.cc/Glide/recovery.tar.md5
Might want to add it to OP?

Aquethys -- done.
dbrannon79 -- Thanks for giving it a try and confirming. I have the same issues, regardless of dump-type on mine as well.
I'm wondering if it has something to do with CM's Jellybean source incorporating the latest and greatest from 4.2 Jellybean. It might not be an issue. Maybe it is. Regardless, I'm still trying to figure out the kinks with it. I'll be scheming with the good folks who helped me build it in the first place tomorrow -- and maybe I can at least get CWM5 working with an external card -- I haven't really seen much in terms of difference between 5/6, aside from organization structure... and we're kind of gimped (a little) on the size of our recovery partition, anyway...

terinfire said:
Aquethys -- done.
dbrannon79 -- Thanks for giving it a try and confirming. I have the same issues, regardless of dump-type on mine as well.
I'm wondering if it has something to do with CM's Jellybean source incorporating the latest and greatest from 4.2 Jellybean. It might not be an issue. Maybe it is. Regardless, I'm still trying to figure out the kinks with it. I'll be scheming with the good folks who helped me build it in the first place tomorrow -- and maybe I can at least get CWM5 working with an external card -- I haven't really seen much in terms of difference between 5/6, aside from organization structure... and we're kind of gimped (a little) on the size of our recovery partition, anyway...
Click to expand...
Click to collapse
sound good! I switched back to ver 5 mainly for the non bump backup! makes things easier to archive backups not to mention the ability to use them tweaking roms!!
I'll look forward to helping you test and any other way I can...
Thanks.

Hopefully going to be able to spit out a new version today for you folks. Will keep you posted!
EDIT:
And that was quick! Tested and working!

[KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel

Thanks to simonsimons34 we now have a kernel compatible with Virgin Mobile's recent FOTAs (new radio and new hboot) AND supports overclocking!!
This kernel is for Sense-based ICS ROMs, however one for AOSP-based ICS ROMs (i.e. CM9) can be found in this post.
In fact, this is the exact same kernel - I just used the RAMDISK from Virgin's most recent FOTA to make it compatible with Sense-based ROMs.
So, if you use it, PLEASE give Simon a thanks in the post I linked.
What the FOTA?!?
Firmware Over-the-Air (FOTA) is used for upgrades to mobile phones and tablet computers. The feature goes by several names including Software Update, Firmware Update or Device Management. Originally, firmware updates to a device required visiting a specific service center, with every mobile brand having their own service center. Another method of receiving updates has been by connecting the device via a cable to a PC. Both of these methods were considered inconvenient by consumers and also relied on consumers actively seeking out updates. Therefore the majority of mobile device manufacturers and operators have now adopted FOTA technology for their handsets. If the mobile device has FOTA capability, firmware updates are issued directly "over the air" from the mobile phone service provider to the device. FOTA also allows manufacturers and operators to "push out" firmware upgrades to ensure that mobile consumers have the latest software improvements, which reduces potential customer support costs and increases consumer satisfaction.
From Wikipedia
Instructions for flashing (kernel only)
Download attached boot.img
Flash boot.img in fastboot "fastboot flash boot boot.img"​
Instructions for flashing (ROM & kernel)
Follow the instructions of the Sense-based ICS ROM you want to install with the following amendment:
When flashing the boot.img in fastboot, use the one attached.
Credits and Thanks:
simonsimons34: for compiling the kernel and implementing the necessary changes to make it support VM's updates. (Basically all the heavy lifting) You ROCK!
russellvone: for testing and supplying the updated modules from the FOTA.
All the people developing for this device: You're why we're here.
Known Issues*
Bluetooth is spotty at best and won't always pair with devices.
Phone won't display "Charging" status when plugged in (though it will actually charge)
Changelog
5/07/2013: Rebuilt Kernel+Ramdisk so it no longer needs a flashable ZIP (thanks again to Simon for the instructions).
5/02/2013: First Release
*Important Notes
This Kernel is essentially provided "as-is".
Fixing the items under known issues would essentially require someone who possess the knowledge recompiling the kernel from source and I do not possess that knowledge.
This is simply a port of the AOSP kernel Simon made for this device to be usable on Sense ROMs and those issues could exist in both kernels or just simply be caused by "porting" the kernel.
@demoport has posted a work-around for the Bluetooth issue in this thread. It can be found here.​

Haha.. just did a instructional reply on Curiousn00b's myOne thread. Thanks for doing this -Duir-

I've been running this kernel/modules combination since you first asked me to test and its absolutely been stable for all the hard usage i put my phone through.
Thanks a million simonsimons34 and
-Duir-

46 downloads on the flashable zip and no comments? I'm gonna take that as a good thing LOL :victory:
OP has been updated. Hopefully removed the need for a flashable zip, just fastboot flash the boot.img. If for some reason it's not working like it was/should let me know, I'll put the original flashable zip back.

The kernel works ok, the only issue I've noticed is a very slow charge rate. Even when plugged into AC, it charges at the slow USB rate.

riggerman0421 said:
The kernel works ok, the only issue I've noticed is a very slow charge rate. Even when plugged into AC, it charges at the slow USB rate.
Click to expand...
Click to collapse
I wouldn't be surprised if that's somehow tied into the charging status not showing.
Sent from my hTC One V.

Updated op fix the non charging display?
Sent from my HTC One V using Xparent BlueTapatalk 2

russellvone said:
Updated op fix the non charging display?
Sent from my HTC One V using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No. Just removed the need for flashable zip.
Sent from my hTC One V.

getting half the battery life i got on jmz ics:\

-Duir- said:
46 downloads on the flashable zip and no comments? I'm gonna take that as a good thing LOL :victory:
OP has been updated. Hopefully removed the need for a flashable zip, just fastboot flash the boot.img. If for some reason it's not working like it was/should let me know, I'll put the original flashable zip back.
Click to expand...
Click to collapse
Would you be able to put the .zip back up again? I think there might be some modules in the .zip that are needed to get bluetooth working correctly. With this kernel, I can get the head unit in my car to pair, but it will never connect. I've tried it with both the myOneV and x3reme Sense v5 ROMs.
Both of those ROMs do connect fine with bluetooth if I use the OTA kernel and modules from the x3reme Sense v5 ROM, but I prefer being able to overclock with this kernel, and choose a governor other than ondemand.

I'm doing some play testing right now with the kernel and different ROMs and running stock, once done I'll post full findings.
I just ran the RUU and flashed the kernel to see what happens.
I gotta say, was rather surprised by them.
Charging Status: Working
Bluetooth: Working
{
"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"
}
Also after using myOneV for so long now it was nice to see that 3G icon again - oh how I've missed you. :laugh:
(Can't see it in the pic as I was testing to make sure Wi-Fi worked.)
MormegilND said:
Would you be able to put the .zip back up again? I think there might be some modules in the .zip that are needed to get bluetooth working correctly. With this kernel, I can get the head unit in my car to pair, but it will never connect. I've tried it with both the myOneV and x3reme Sense v5 ROMs.
Both of those ROMs do connect fine with bluetooth if I use the OTA kernel and modules from the x3reme Sense v5 ROM, but I prefer being able to overclock with this kernel, and choose a governor other than ondemand.
Click to expand...
Click to collapse
Attached to this post as requested, please let me know your results.

Well upgraded to new radio, Bluetooth is working and as expected the charging status is wonky. Only the notification LED changes to indicate a charging status, all the software-specific indicators (battery icon, power option in settings) think phone is discharging still. Gonna have a look at what files get changed by the FOTA.

-Duir- said:
Attached to this post as requested, please let me know your results.
Click to expand...
Click to collapse
Using the modules and kernel from the .zip didn't seem to help my bluetooth problem. I read in the other thread that clock speed (or lack thereof) can affect bluetooth pairing/connecting, so I tried all 6 of the following combinations with identical failing results: [245/1024,1024/1024,1200/1200] x [ondemand,smartassV2]
Changing back to the x3reme OTA kernel and modules, bluetooth connects immediately with clock speeds of 245/1024 and 1024/1024.
In case it helps, the bluetooth module is a Dual BTM60, and the vendor identifier portion of the bluetooth MAC is 00:13:7B

I'll be looking into the Bluetooth next, my attempts with charging status have determined it is something to with the kernel and the radio (or some other hidden nugget) in the FOTA. Every file the FOTA changed I flashed back the original versions off and it made no difference. The kernel displays charging status with the .0521_2 no problem but not with the .0928 and the stock kernel of course displays a charging status.
So yeah, given up on that and moving on to Bluetooth now, will report back if I find anything out.

-Duir- said:
I'll be looking into the Bluetooth next, my attempts with charging status have determined it is something to with the kernel and the radio (or some other hidden nugget) in the FOTA. Every file the FOTA changed I flashed back the original versions off and it made no difference. The kernel displays charging status with the .0521_2 no problem but not with the .0928 and the stock kernel of course displays a charging status.
So yeah, given up on that and moving on to Bluetooth now, will report back if I find anything out.
Click to expand...
Click to collapse
Hey, I just RUU'd and updated to the newest update... I'm still on whatever stock kernel it comes with after the RUU and everything is working fine.
My question is: Is there a way to get this stock boot.img so I can flash it later if I want to flash this kernel so I can overclock, but I may want to go back to this kernel someday.
Can I pull it from a nandroid backup through TWRP?

lilrob1213 said:
Hey, I just RUU'd and updated to the newest update... I'm still on whatever stock kernel it comes with after the RUU and everything is working fine.
My question is: Is there a way to get this stock boot.img so I can flash it later if I want to flash this kernel so I can overclock, but I may want to go back to this kernel someday.
Can I pull it from a nandroid backup through TWRP?
Click to expand...
Click to collapse
The easiest way is something you need to do in advance. Which is copy the FOTA zip file off your SD card before you run the update (because it gets erased afterwards) and then you can pull the stock boot.img from there.
For TWRP it will backup the boot.img if you instruct it to, but I'm unsure of what needs to be done to make into a fastboot flashable format (i.e. a simple rename).
That being said I have a copy of both FOTA zips and can supply it if needed, and they can also be found here

-Duir- said:
The easiest way is something you need to do in advance. Which is copy the FOTA zip file off your SD card before you run the update (because it gets erased afterwards) and then you can pull the stock boot.img from there.
For TWRP it will backup the boot.img if you instruct it to, but I'm unsure of what needs to be done to make into a fastboot flashable format (i.e. a simple rename).
That being said I have a copy of both FOTA zips and can supply it if needed, and they can also be found here
Click to expand...
Click to collapse
What FOTA zip was on my sdcard? I don't remember using one? why are there two fota zips?

lilrob1213 said:
What FOTA zip was on my sdcard? I don't remember using one? why are there two fota zips?
Click to expand...
Click to collapse
When your phone downloads the update it stores it on your SD card. There's two because the first one is the radio update, the second and most recent is the one that updates the hboot and makes using the RUU impossible.

-Duir- said:
When your phone downloads the update it stores it on your SD card. There's two because the first one is the radio update, the second and most recent is the one that updates the hboot and makes using the RUU impossible.
Click to expand...
Click to collapse
Oh... that makes sense... dang it! I wish I knew I could update the radio with the first update and skip on doing the second update so that I could still RUU if in trouble... now I'm screwed but yeah, can you PM me the FOTA zip for the second update so I can have the kernel?

lilrob1213 said:
Oh... that makes sense... dang it! I wish I knew I could update the radio with the first update and skip on doing the second update so that I could still RUU if in trouble... now I'm screwed but yeah, can you PM me the FOTA zip for the second update so I can have the kernel?
Click to expand...
Click to collapse
Done.
Ok so my attempts with Bluetooth haven't yielded any problems. I installed both the current versions of myONEv_RC9.5_FX+CDMA and x3remeSensev5_OTA and Bluetooth worked on first try with each. I'm streaming music to my BT speakers as I write this. I've only updated to the newest radio, not the newer hboot, but I can't imagine that update breaking Bluetooth somehow.

[ROM][D802]80220B EUR Open KITKAT Flashable ZIP With Custom Recovery Working!

This is only what has worked for me i take no responsibility for anyones phone catching fire after following my guide/advice. Tested myself on a UK D802 16GB on Three Network! Confirmed working on 32GB devices now too!!
This needs formatting to make it easier to read. I will get around to it but here is the basic info needed!
Please READ this entire first post before asking questions that are already answered.​
Today i have managed to flash the European Open Kitkat rom and root it and keep TWRP recovery. It worked for me but can't guarantee the same results for you.
Prerequisites. (Skip this if you already have rooted JB rom with custom recovery)
First i downgraded to Jellybean using this guide. I downgraded to "UK Open 16GB D80210B_00.kdz" i'm not sure if that's required though.
Then I rooted it using IORoot.
Then i installed TWRP using Freegee from the Play Store.
From here you are ready to flash or you can start from here if you already have root and recovery on Jellybean.
You need these three files.
1. My modded Stock rom zip.
Mirror 1 | Mirror 2
2. Savoca Modded Boot.img.
3. SuperSU ZIP.
Now to flash! (Take out your simcard first.)
1. Boot into TWRP and flash the modded stock rom DOWNLOAD 1. It will take a while and the screen may turn off during this, just press power button. Ignore the failed error!
2. Now go to main TWRP screen and select Reboot Recovery. (Wouldn't mount system otherwise!)
3. Now go to Mount and make sure System is ticked. (Not sure if required but do it anyway!)
4. Now flash Savoca's modified boot.img DOWNLOAD 2.
5. Again go to Mount and make sure System is selected.
6. Now flash SuperSU ZIP DOWNLOAD 3.
7. Now i wiped data here not sure if it's required as the rom wipes system but do it anyway!
8. Replace sim and reboot and all should be well!
If you have NO MOBILE NETWORK i got this error and that's why i recommended removing sim card. I had to repeatedly toggle wifi on and off, and airplane mode and restarted a few times. Not sure what fixed it but don't panic it DOES work.​
Bugs and Fixes!
Audio Hissing/Crackling on Headphones.
This is present on all Kitkat roms currently. Some users don't get it most do. Type of headphones seems to be a factor. The following fix is temporary and will revert after a reboot. So needs to be repeated if your phones reboots for any reason.
Type in phone dial pad 3845#*802# and it will show Hidden Service Menu.
Click on "ELT Test", select "Manual Mode" and select "Test Start".
With headphones plugged in select "Audio Loopback" and than select "Test Start".
Blow gently into the microphone and keep on this test 20 seconds or more.
Once done back out and play music. Enjoy!
No LTE/4G anymore?
It seems to require a change of bands for some to get LTE working. There is a value to edit in build.prop. You can do this manually with a root explorer and setting correct permissions after changing, I've found the easiest way is to download JRummy Build.prop editor from market.
Open the Build Prop Editor app.
Find the value "ro.telephony.default_network" and select it.
Notice the property value will be set to "9". Change this to "11" and let the app reboot phone.
If you still don't have LTE try again but change the value to "13" and let the app reboot phone.
Bluetooth Battery Drain
This is NOT real battery drain so please don't worry about it. It is a falsely reported statistic. I get battery life on a par with 4.2.2. Around 8 hours screen on time which is fantastic! If you have battery drain please try a full wipe, don't restore apps from another rom do it manually. Take a look at your apps.
How is it done?!
The modded zip is stripped down to include only the System, Modem and Cust partitions. These are all that is required for Kitkat to play nice with Savocas modified boot.img. I edited the updater-script to remove the entries for all partitions except those listed above and repacked it up nicely to flash. So it is possible to do this with any future updates too. The Cust partition is necessary in case your partition has old carrier stuff still on there, this flashes a clean Cust partition.
Thanks to:
LenAsh for the flashable zip i modded.
Savoca for the modded Boot.img and modules.
Chainfire for SuperSU.
Jesus for blessing all the little children.

it would be great if you also make one for the 32gb version
anyways, great work, dude!

I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?

superbonto said:
it would be great if you also make one for the 32gb version
anyways, great work, dude!
Click to expand...
Click to collapse
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
paniczklos said:
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
Click to expand...
Click to collapse
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!

ephumuris said:
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
Click to expand...
Click to collapse
I'm preparing a dead fish to throw it on your doormat ;p
I'm on 12th minute of booting - LG logo and led flashing green-to-blue.
And yes I'm 16GB
How to use the standard recovery ?

Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot

Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris

Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated.
{
"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"
}
Sent from my LG-D802 using Tapatalk

SPBoss said:
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated. View attachment 2630159
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
What rom are you running? I get the option for gsm/wcdma/lte auto. Although no 4g for me on Three in Hull yet.
badchip said:
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Click to expand...
Click to collapse
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...

ephumuris said:
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Click to expand...
Click to collapse
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?

paniczklos said:
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
Click to expand...
Click to collapse
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"

ephumuris said:
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
Click to expand...
Click to collapse
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/

ephumuris said:
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
Click to expand...
Click to collapse
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device

paniczklos said:
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
Click to expand...
Click to collapse
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!

badchip said:
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
Click to expand...
Click to collapse
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?

ephumuris said:
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
Click to expand...
Click to collapse
I'm downloading the UK open EUR and I'll start over.

ephumuris said:
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
Click to expand...
Click to collapse
I would very much appreciate that. I have used the tool to extract the kdz and dz. I have the files in screenshot now.
Whats the proper next step?
Thanks for your help
edit: The meta-inf folder is from the KK template provided in that thread, I suppose I don't need that.

Hi!
Firstly thanks for this!
and secondly i have to say that i already flashed to my LG G2 32gb and works like a charm... btw i also did it with another way:
1-Downgrade to 4.2.2.
2-when your in v.4.2.2 root and recovery.
3-i used lastest CWM version from Philz.
4-FLash your Rom.zip
5-reboot to recovery. (Dunno if this is really necessary but just in case i did it too)
6-Flash Savoca Patched
7-Flash Root
8-Reboot
9-ENjoy EUR 20b =)
Thanks!

Great to confirm working on 32gb too. Badchip you might have to wait til later unless you can use that existing meta inf folder. I've just left for work so not at laptop.
Try deleting every file but only keep.
Meta inf folder.
System.IMG
Modem.bin
Custom.bin
Zip those up and flash them. Should work if the update script is right in meta inf folder.
@iall5tar What base jellybean rom did you downgrade to?
And regarding custom recovery it should work with any cwm philz or twrp. I just referenced twrp as that's what I use.
Sent from my LG-D802 using Tapatalk

What you mean about folder meta-inf? im not a expert i just want to give a try and it worked xD