[request] Australian fast boot optus files for gsm xt910 - Motorola Droid RAZR

I have bricked my Optus aust phone, and need fast boot files, can anyone upload theirs for me?
In fact, would it work I'd I just flashed any gsm xt910 fast boot from another country? Would that cause problems with the radios?

or the radio iformation and which retail version?

Look into the EternityProject Official Motorola RAZR ROMs Thread.
If your software isn't listed in there, try to flash another country's software. You shouldn't have problems with radios.

I've bricked my beloved Optus RAZR too! Argh!
As far as I can tell there are no Australian fastboot files yet. Did you have any success using another country's.
If you managed to un-brick would you mind letting us know the software version you used to find freedom again.
Thanks very much!

I've managed to un-brick my Optus RAZR as a european phone, but would appreciate it if someone could upload the local OTA for Optus.
If you have root access you can find the file in the /cache folder and it should read something like "65.1.12.XT910.Optus.en.AU"
any help would be appreciated
SilverDragon

I have Blur_Version.65.1.12.XT910.Optus.en.AU.zip (176MB). What files do you need from the ZIP? Or do you need the whole thing?

i have a aus/optus version razr as well.
had to flash a EU version on the phone.
EU work's ok but i get errors n weird things happening all the time.
i too would love the AUS files to flash.
thanks.

mRazr,
It is the whole thing we'd need to flash. Any chance you could upload it, or message me for my email?
Thanks
SilverDragon

Ok I'll upload it now and post the link when ready.
---------- Post added at 01:04 PM ---------- Previous post was at 12:23 PM ----------
I uploaded it but the web page didn't refresh and give me a link
Anyone have an FTP server or a website that refreshes/updates reliably?

Here is the file link rezipped as a 7zip to shave off 40MB (I'm on a slow connection at the moment)
http://www.fileswap.com/dl/P085IcsTU4/Blur_Version.65.1.12.XT910.Optus.en.AU.7z.html
Unzip using 7zip, then re-zip as a zip file.
The CRC value in Blur_Version.65.1.12.XT910.Optus.en.AU.crc is 1682947141

< crossing my fingers >
Thanks, mRazr.
I'll let you know how it goes
SD

Try this? http://www.multiupload.com/T012AX9PKH
The file name does have an "australia" in it.
SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip

@ Spectral - that does work, and saved me from a brick, but it isn't the Optus branded version I'm looking for
@ mRazr - it seems converting the files to 7z and back breaks the digital signature on the file and it won't run. Can you upload the original file?
thanks
SD

I just realized something, 65.1.12 is just an OTA update since the full ROM's are much larger at 500MB+. I'm assuming you need the full ROM that was originally shipped with the phone, a version earlier than 65.1.12.
But either way you can download 65.1.12 from here:
http://dlhg.eternityproject.eu/mtsp...ur_Version.65.1.12.XT910.AsiaRetail.en.03.zip

Thanks mRazr.
I used the Euro ROM to unbrick my phone.
Point being I want to get the Optus OTA to get the phone back to local and not the Euro ROM
I was hoping to get the Optus OTA and push it back to a local version ( if that is even possible )
Is it possible to upload the original zip file without being converted to 7zip?
Tah
SD

ok here it is:
http://www.fileswap.com/dl/wNuQCcsbhd/Blur_Version.65.1.12.XT910.Optus.en.AU.zip.html
Again, there's a CRC file with the ZIP which you may need.
Blur_Version.65.1.12.XT910.Optus.en.AU.crc
Containing 1682947141

Ah well, was worth a try...
Got an error < quote > E:Error in /tmp/sideload/package.zip (status 7) < / quote> and from further investigation I would need a copy of the Preinstall directory from the previous Optus ROM.
You wouldn't be up for loading that, would you? Can be found directly in root and using Root Explorer you can copy the current preinstall directory to your SD-ext, then export it as you like.
May just have to either wear the Euro ROM or get the thing professionally flashed for $50
< sigh >
Thanks for everything, mRazr
SD

Sure no probs. I found three files; recovery, logwrapper, and update-binary. I'll email them to you in a moment.

< sigh >
nope - no joy.
I guess I'll have to live with the Euro firmware until I can get my hands on a full local ROM
Thanks for the assist though, mRazr
SD

No probs. At least with the retail euro ROM you'll get the official ICS OTA earlier rather than waiting forever for Optus to brand the ROM.

Related

English Update Utility

Credits for finding/pointing to this solutution go to AirwolfUK.
This is also hidden somewhere in a thread, but I think it deserves it's own thread. We (G4 owners) don't need to flash all our roms in Italian language. In stead of copying all the Update Utility files just copy "ROMUpdateUtility_Wizard_NoID.exe" and it will stay in English.
So if you get this error on you're G4:
ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA phone. Please get newer Update Utility
Just replace the "ROMUpdateUtility_Wizard_NoID.exe"! (I'll attach it too)
If you want to turn an already Italian installer into English replace all the files from "English Update Utility Files G4.zip".
Great! Thanks a lot for these! Hepled me a lot
Guess it should be a sticky, as not many people know where to find these things.
I've tried ROMUpdateUtility_Wizard_NoID.exe but keep getting
"Error 208: File Open.
The update utility can not open the requested file. Please check your update utility".
Anyone got any ideas what I am doing wrong?
maybe you're not with the utility and the nk.nbf in the same folder(all in the root of the folder).
Thank you so much...this just saved my otherwise bricked phone!
thx worked perfect in flashing the radio rom on my g4 to 2.19 uk!
I can't figure out how to upgrade my rom. I keep getting the dreaded Error 300.
Can somebody provide instructions on how to run this?
How?
How do I do this?
What should I replace?
Where should I put the "ROMUpdateUtility_Wizard_NoID.exe" file?
I just normally run the updateroom from a folder on my laptop, so where should I place "ROMUpdateUtility_Wizard_NoID.exe"?
I am attemping to flash Superrom
orelse4054 said:
How do I do this?
What should I replace?
Where should I put the "ROMUpdateUtility_Wizard_NoID.exe" file?
I just normally run the updateroom from a folder on my laptop, so where should I place "ROMUpdateUtility_Wizard_NoID.exe"?
I am attemping to flash Superrom
Click to expand...
Click to collapse
If the rom is one exe file, unpack it first with winrar. You'll see the file afterwards.
Yes I knows it becomes a exe file after I have zipped it.
Ok here it goes:
I run a normal ROM update exe file, I get the
"ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA phone. Please get newer Update Utility"
Then what shall I do with the "ROMUpdateUtility_Wizard_NoID.exe " if I just run this one the message: ""Error 208: File Open."
Can someone set up a step by step guide please?
Seems you haven't upacked the rom executable. You should have multiple files afterwards (e.g. ROMUpdateUtility_Wizard_NoID.exe and nk.nbf). Just replace the ROMUpdateUtility_Wizard_NoID.exe! The file error tells it can't find your nk.nbf.
Damnnnnn Vippie Rocks!!!!!!!
How to do it ..
is it just click and run ROMUpdateUtility_Wizard_NoID .. and the application will do all .. or we just need to but all stuff in unpack flash ( any flash ) and install it to firmware ??
thanks allot in advanced
help still not working
I got the ROMUpdateUtility_Wizard_NoID.exe and I run it in the same folder as the rest of the files from the program and I STILL get error 300
Thanks Wes
Thank you men !!!
Thank you very much men, you saved my life !!!
Ok this file just bricked my MDA !
deathblooms237 said:
Ok this file just bricked my MDA !
Click to expand...
Click to collapse
Impossible.... it's you who did something wrong.
vippie said:
Impossible.... it's you who did something wrong.
Click to expand...
Click to collapse
No... I think your half-ass instructions confused everyone! you posted the update utility yet did not instruct that it should have been extracted in the same folder as the new ROM of the user's choice.
If you were to create a folder then extract the utility to that folder, then click on the extracted file, then for sure you will get the error msg.
Download first the ROM you want in a folder, All New ROMs will extract to two files. One of those files is the rom update utility file that you will need to replace with the Update Utility exe file in this post. To do this just extract the update utility tool ( posted here ) in the same folder of the downloaded and extracted ROM folder. You will then be up and running. Follow the instructions.
To follow up with my previous post, I would suggest you start with the 'Wizard_Love rom or the Button Rom as basis. This will reset your download prompts on your device to accept any Wizard compatible ROM of your choice. After the first update most likely you will not need this utility to update your favorite rom onto your device.
asfoor said:
No... I think your half-ass instructions confused everyone! you posted the update utility yet did not instruct that it should have been extracted in the same folder as the new ROM of the user's choice.
Click to expand...
Click to collapse
And even than it wouldn't brick the device. So your "no" should be "yes, you're right vippie"!
Did you notice the "developers" in the websites name? What are people doing on this forum if they don't know how to REPLACE a file. It isn't necessary to spoon-feed people.

Decrypting Roms

Hi All,
I seem to remember there being a guide to decrypting roms for the x10.
I've saved a backup of my oz optus firmware from pc companion and was hoping to make an unecrypted version of it to be used with flashtool.
I've tried searching and I simply cannot find the guide to unencrypt (That's if memory serves me correctly and it even exists.)
Could someone please point me in the right direction.
Cheers
dangerzau said:
Hi All,
I seem to remember there being a guide to decrypting roms for the x10.
I've saved a backup of my oz optus firmware from pc companion and was hoping to make an unecrypted version of it to be used with flashtool.
I've tried searching and I simply cannot find the guide to unencrypt (That's if memory serves me correctly and it even exists.)
Could someone please point me in the right direction.
Cheers
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=683793
This link might should be what your looking for - title has changed a few times
Does anyone know how to do it tho? I downloaded the "tool to partially decrypt" but it doesn't show any instructions or anything.. Just a bunch of files..
That tool won't decrypt the ROM. I will decrypt it soon (read: when I get access to my external HDD).
With that said lollylost, Do you need me to upload the two files somewhere?
Main reason I wanted to decrypt it was to extract the optus my account apk as its not available on either the market or the optus.com.au website.
And yeah i'd allready downloaded the decompression tools. Lollylost, have you got some sort of application or even a guide on how to decrypt the firmwares?
Would be nice if you could upload the firmware since all my firmwares are on the inaccessible HDD.
Hey guys, maybe u can help me...
i flashed my x10i with flashtool to the R2BA(shipped) Rom ok,
but now id like to flash it back to my old .16 Rom which i had before on ma device, it is a unbranded .16 version, id like to flash it back cuz i want to make later if hopefully the new R2BA for free devices comes out in SEUS to flash it officially,
ive saved my original files: 2 files :111Mb , the other : 16Mb
but how do i flash it back !? with flashtool its not possible i guess isnt it ?
ive tried flashing with seus by changing files in the db folder (by the way is there somewhere a description how to do that exactly ? )but it doesnt seem to work...
pls guys i need ya help
Reflashing back to different firmware
natedastate said:
Hey guys, maybe u can help me...
i flashed my x10i with flashtool to the R2BA(shipped) Rom ok,
but now id like to flash it back to my old .16 Rom which i had before on ma device, it is a unbranded .16 version, id like to flash it back cuz i want to make later if hopefully the new R2BA for free devices comes out in SEUS to flash it officially,
ive saved my original files: 2 files :111Mb , the other : 16Mb
but how do i flash it back !? with flashtool its not possible i guess isnt it ?
ive tried flashing with seus by changing files in the db folder (by the way is there somewhere a description how to do that exactly ? )but it doesnt seem to work...
pls guys i need ya help
Click to expand...
Click to collapse
Reflashing has been covered before but since I had trouble with it I feel for you so i'll post my lil guide
Hopefully its allowable to link to file on other sites (If not can a mod feel free to edit this post and I'll create a pdf guide if thats okay).
EDIT: Turns out as a new user I can't link to external sites and services. With that in mind if you do a google search for "download SEUS" and scroll down till you see the sony ericcson site, you should be okay.
Step 1
Download SEUS if you dont allready have it (NOT pcCompanion that a different program)
Step 2
Using SEUS, run your phone through a repair. That means let SEUS download firmware and install it to your phone.
Step3
When using SEUS the db folder will be in C:\Program Files\Sony Ericsson\Update Service\db\YOURIMEINUMBERGOESHERE\blob_fs
Find the two largest files in that folder select it so its highlighted & press F2 on the keyboard to rename the file. The filename will now be highlighted. Press <Ctrl> + <C> to copy the file name to your clipboard, press <ESC> to cancel the rename.
Now that you have copied the Filename to your clipboard, locate where you saved your original firmware files and highlight the largest one. Press <F2> again and this time press <Ctrl> + <V> . This will paste the new filename onto your firmware.
Do the same for the second largest file.
Step 4
With the file rename complete, you can now copy the two files you just rename into your C:\Program Files\Sony Ericsson\Update Service\db\YOURIMEINUMBERGOESHERE\blob_fs folder.
Step 5
Run through the repair again with SEUS however this time when SEUS says its downloading it will take a matter of seconds and then flash your original firmware back onto your phone.
Step 6
ALL DONE Enjoy your original firmware.
Lollylost: I tried to upload files and it crapped out about 50% of the way through.
I did notice that there was once an SEUS plugin that you had uploaded to hotfile that did the decrypt on the fly, is it still possible to get this plugin so i can finally extract the my account.apk and get on with rooting my phone?
Cheers
Me
Uploaded
LollyLost: I've uploaded the firmware for you it's here: http://www.multiupload.com/RAOCA34155
If you could do me a favour and extract the my account application on there so I can root and put back the usage counter would be great.
Cheers
dangerzau said:
LollyLost: I've uploaded the firmware for you it's here: http://www.multiupload.com/RAOCA34155
If you could do me a favour and extract the my account application on there so I can root and put back the usage counter would be great.
Cheers
Click to expand...
Click to collapse
I am also looking for this, but too noob to perform the extraction
I see only ICON_7756655... file...
Not understand... not working...
Help
(sorry my bad english)
Can someone please decrypt the Nordic image found in this thread for me? So I can flash via Omnius/flash tool if I ever need to do it. I am having difficulty figuring out how to do it myself.
http://forum.xda-developers.com/showthread.php?t=722657
I would really appreciate it, thank you.
Nordic_R1FB001
Here you have the Nordic Generic R1FB001 with flashtool included, just to install, dont forget to backup your data since this will be a clean install.
hotfile.com/dl/54774133/5a987e4/Nordic_R1FB001_FlashTool.rar.html

Original Firmware Restore Files for Springboard/Mediapad

On the Huawei site I was able to find a link to the original Honeycomb firmware for the generic Mediapad... does anyone have the links to the T-Mobile firmware?
Huawei Honeycomb Download Links
I would love to have these also.
Sent from my HUAWEI MediaPad using xda premium
Xanderful said:
I would love to have these also.
Sent from my HUAWEI MediaPad using xda premium
Click to expand...
Click to collapse
+1 This is a must have if we ever need to send the tablet back for warranty.
I am awaiting for my Springboard to arrive from USA in 10-14 days.
If (cross my fingers) I'll recieve it alive, the first thing in my todo list is to try backup images from all partitions (though warranty is not my case).
PS
If somebody can reguest SIM unlock code from TMO - I'm very curious, if there are a lot of binary differences between locked (before) and unlocked (after) nv_data.bin, or just a couple of bytes?
As promised:
www . 4shared . com/folder/WbaOrqKb/TMO_SB.html
www . filefactory . com/f/9296e687aa0253d5/
(sorry, too young to post links... extra spaces added)
Stock TMO SpringBoard S7-303uV100R001C201B027 partitions dump.
Except 4(extended), and those with individual data (5,13,14,16) partitions not being overwritten with known updates, 18 (recovery2) the same as recovery, 25 and 26 are empty.
Assuming "fastboot flash boot boot.img" etc for each partition.
Naming and filenames are in every huawei_partition.xml availiable - the only difference in partition table against MediaPad is mmcblk0p27 (/sdcard) which is intact during flashing.
Happy rooting and recovering!
PS
And for those who missed "4G" in general Huawei ROM's - just look at \hwcust\tmobile_us\resource\xml\cust.xml :
Code:
<!--begin DTS2011070602393 y00140144 add for TMO Data Icon Req-->
<boolean EDGE_shows_2G="true">
<boolean UMTS_shows_4G="true">
<boolean HSPA_shows_4G="true">
<boolean Roaming_shows="false">
<!--end DTS2011070602393 y00140144 add-->
Seems to me that T-Mobile treat all "except EDGE" as "4G" - one can decide for himself if this marketing bull**** worth thinking about.
thanks for posting this - would this follow the dload update process ? would you be able to type up how to restore this?
Bump. I downloaded Huawei's official 3.2 software update, then replaced all of the files in the update.zip folder with those posted. I was able to flash them onto my Springboard, and it said it completed successfully. Now, however, whenever I start the tablet, it just goes into a boot loop. Any thoughts?
There must be "log" and "sync_log" files on external sd card, which You used to update.
Can You post them anywhere?
jwhite326 said:
Bump. I downloaded Huawei's official 3.2 software update, then replaced all of the files in the update.zip folder with those posted. I was able to flash them onto my Springboard, and it said it completed successfully. Now, however, whenever I start the tablet, it just goes into a boot loop. Any thoughts?
Click to expand...
Click to collapse
I am not an expert but you might want to check on the file permissions.
Is it possible for someone to build a dload folder to install the above firmware?
Might it be possible to repack the T-Mobile system img with root, so that we can get root without changing firmwares?
Thank you so much for this. I needed it when I bungled up my system partition.
I was on a later OTA, so flashing your system img backup reverted me to an older firmware. This had some incompatibilities in terms of wi-fi and the front-facing camera, which I fixed by also flashing the kernel (boot img). In order to trigger it to propose an OTA update, I then had to also flash the cust img.
Having done that, I sniffed out in alogcat the URL of the OTA update:
http://android.clients.google.com/packages/ota/huawei_springboard_mediapad/009e6fd7c5ce.update.zip
im looking at the partitions xml and i cant figure out what is what, i know i can fastboot flash system, cache, userdata, boot, recovery etc, but what about the rest of the files - how do we flash them? what are the partition names? my springboard is totally screwed and stuck at the huawei logo i can only get to fastboot...any help would be appreciated

[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually

Manual Updating: How-To Preserve Root Access and Bootloader Unlock!
update... as of Nov 10 2014:
Official Lollipop for D855 and F400 has come out... following my instructions here you can still get bump'd - http://forum.xda-developers.com/showpost.php?p=56650179&postcount=59
So far, no anti-rollback in sight but I would still be careful of future updates.. and all other G3 devices models should be careful before taking an OTA (AT&T/Verizon... maybe).
Follow the steps above and you will ALWAYS have access to root/bump and flash anything you want.
​This thread assumes you are already rooted, have TWRP installed and can read English.
If you have those 3 covered the rest is EASY as long as you read.
If you are unsure of any terms used in this post please search XDA/Google instead of asking in here.
Background
I'll get this out of the way right now... if you do not care about having access to Bump or root you can ignore all of this and continue to take LG's OTA updates. One could argue that taking OTA updates is required to maintain any level of safety/security... but that goes out the window once you start rooting and installing recovery/roms anyway. Regardless, I am not telling anyone not to update. But if you do update... do it manually. As of Oct 18 2014, every single G3 variant has root and bootloader unlock.. either out of the box(D851) or thanks to Bump. There is no need to ever take an OTA from here on out. The latest D855 and F400 OTA updates have blocked TowelRoot, IORoot and even Stump.. pretty sure only PurpleDrake works on them for now... I would expect PurpleDrake to be patched soon enough. And with official Lollipop updates coming root will only get harder. But.. as long as we install everything through TWRP manually we can update while keeping root/unlock/Bump.
Yes, we can downgrade using LG FlashTool but that could be blocked at any time with an OTA update to prevent rollback(Samsung does this).
Yes, it's possible to complete an OTA upgrade and maintain root but there is no way to know for sure if root will stick. And the OTA is upgrading the bootloader. Why gamble? This post is just a suggestion on how to stay updated without locking yourself out of anything... but it's not a rule. Just one of many options you can take. But if you do lose root or bootloader unlock after an OTA... don't go asking any devs when then next root tool is coming out or if there's a magical way to downgrade the bootloader. ​Overview
With all that said... now that we're all rooted and unlocked I decided to make a thread on how to:
1. Block OTA updates and remove OTA packages and that annoying notification. Easy!
2. Download updates manually.. no OTA zip needed. Easy!
3. Manually flash updates without losing root or Bump. Easy!
Most of us have access to the same files found in the latest OTA.. either with a .KDZ or .TOT(Sprint and AT&T refuse to release KDZ files..it seems they would prefer you to not be ale to fix the phone yourself). We can extract the individual partition files from a KDZ/TOT and easily flash them through TWRP. ATT/Sprint users will need leaked TOT files... or something like a pre-patched System.img/Boot.img/Modem.img from a user who has run a modified OTA update... yet managed to keep/regain root. More on that possibly in the future.
The main things we want out of a new OTA update:
A. Radio/Modem.img - although newer isn't always better
B. Kernel/Boot.img - this is often where root is blocked in new updates. But update manually and it no longer matters since we can root system through TWRP.
C. Rom/System.img - this is where most of the "fixes" in updates happen.. and what most people want from an OTA.
D. *Optional: Bootloader stack/Aboot.img,SBL1.img, DBI.img, LAF.img, RPM.img, TZ.img - this is where downgrading and Bump could be blocked. Avoid updating for now unless you are 110% sure you know what you're doing.​How-To Block and Remove OTA Updates
If you are flashing custom roms in TWRP.. I'd expect OTA updates to already be removed. If you get an OTA update while running a custom flashable rom be sure to ask the dev why he can't make a proper custom rom that keeps you safe from OTA updates.
Block
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> Disable
*Replace "851" with your devices model number, 850, 852, 855 etc.
This seems to only work on D851, D851 and D855 versions (possibly D857/8/9 and F400). AT&T, Verizon and Sprint users have reported the Hidden Menu method does not work. If you have one of those devices you can use a RootExplorer-type app to find the OTA related APK and rename the file to ____.apk.bak or use Titanium Backup to freeze it. If using Titanium Backup look for com.lge.lgfota.permission, OTA or System Update and freeze it. If looking for apk and odex file to rename.. search for OTA or FOTA or LGDMSClient.. etc
If you see an "Apps update" that just might be the "LG Apps" and not a firmware update. Updating LG apps is safe.. firmware is not (if you want to be able to maintain root/mods).
Remove OTA Update(and notification)
If an OTA notification is on your device you most likely already have the OTA file on your phone. If rooted, you can remove the OTA files and get rid of that annoying notification.
Updates are found in the /cache/ folder on your phone. Using a RootExplorer-type app(or ES File Explorer) browse to the root of your phone(NOT the root of your internal storage, /sdcard/, but the actual phone). If using ES File Explorer you may have to use the "show hidden files" option and grant the app root. You will see the update .zip file in cache if you did everything correctly. If no one has already uploaded the OTA zip.. copy the update to your sdcard and then upload for everyone else. Now delete the zip file from /cache/.
Deleting the file in /cache/ will get rid of the OTA but will not get rid of the notification. To get rid of notification:
1. Pull the notification shade down on your phone
2. Long press on the OTA notification until you see the App Info option pop up.
3. Click App Info and uncheck the Show Notifications box.
​How-To Download Updates and Extract KDZ/TOT Files
1. Easiest way to obtain updates would be to look in this around XDA in your proper subforum for an update already posted by someone else. With Bump, many flashable rom zips will be popping up. Roms usually contain "system" and "boot"... which are two of the three things we generally want from an update. The third being the modem.. which is never included in a flashable rom and often not required to be updated. If you want the updated modem you will have to look around for the file or use the steps below to get it yourself.
2. If there is a new OTA update, no one has already posted the updated flashable files and you can't wait any longer... it is time to take matters into your own hands. Instead of giving in and taking the official OTA or begging others for help.. download the updated KDZ for your device yourself. And NO, we will NOT be not flashing the full KDZ.. we are just taking some files from it.
You can get your devices KDZ by visiting THIS LINK and entering in your MEID or IMEI.. it will give you a link to the latest available KDZ from LG. Sometimes KDZ files take a few days to show up after the OTA.. give it a little time. Do not beg in thread for KDZ files. Help yourself or wait for someone to post the files you were looking for.
It is encouraged to share not only KDZ and TOT files... but the extracted System/Boot/Modem images you extract from them as well. Only one person needs to download a KDZ per DeviceVariant/SoftwareVersion... that person can then share and everyone else just downloads from their link. You no longer have to be a "rom dev" of even know how to make a flashable zip to help share updates with others.
Anyway... to extract these partitions after downloading the KDZ/tot you can check out the following posts for scripts/tools to make things easy:
a. CLICK HERE [Tool][python] LG Compressed KDZ Extractor - by thecubed Script to extract partitions from KDZ.
b. CLICK HERE SystemMerger.py - by cybojenix Script to merge split system files from extracted KDZ.
c. CLICK HERE [TOOL]LG Bin Firmware Extractor - by xonar_ Script to extract TOT files and merge system.img's into one.
d. CLICK HERE [TOOL] KDZ and TOT Extractor - by bullghost Windows tool, adds all features of the scripts above with an easy to use UI.
invisiblek has updated xonar_'s LGBinExtractor to work with some more G3 devices - https://github.com/invisiblek/LGBinExtractor
If you have a question about an extraction tool be sure to read everything in the 4 threads. Post in the above threads if your question is still unanswered. Between the 5 extraction links above you can extract any G3 KDZ/TOT on Linux, OSX or Windows.
And remember, the main partitions we want from the TOT or KDZ: modem, boot and system.
Alternatively you can extract the KDZ directly on your phone -- click HERE.
Since more than a few people are having issues manually extracting... I will show an example that came from this thread and how to correct it:
KDZFileTools.py -f D85510L_00.kdz -x
[!] Error: Unsupported KDZ file format.
[ ] Expected: 0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80 ,
but received 0x28 0x5 0x0 0x0 0x24 0x38 0x22 0x25
Two things wrong here... first, the command is incorrect. when using the KDZFileTools.py "-x" is not used.. you want "-s 0" to extract the DZ.
Example:
Code:
python KDZFileTools.py -f D85510L_00.kdz -s 0
The second error is the "Expected.. but received" message. To fix this just open the .py script up in a proper text editor(notepad++ on windows for example).. find "x28x05x00x00x34x31x25x80" in the script...
replace it with "x28x05x00x00x24x38x22x25" (or whatever string is given after the "but received" output.. use logic) then save script.
rerun script. DZ will now extract into the "kdzextracted" folder. Once that finishes extracting you can use the Windows GUI tool to extract the .DZ file into individual partitions (and merge system). Or you can continue using the manual script methods.
To manually extract the DZ you're going to now use the DZFileTools.py script to split the DZ file (that's in the kdzextracted folder) into individual partitions.
Example:
Code:
python DZFileTools.py -f kdzextracted/D85510l_00.dz -x
that command will extract all your partitions into the dzextracted folder. Now drop the SystemMerger.py - by cybojenix file linked above into the dzextracted folder.. cd into the dzextracted folder and run that script to merge all the split system partitions into one system file.
Code:
python SystemMerger.py
All done.. you now have the boot, modem and full system.img to flash on your phone (along with every other partitions that comes with a kdz). :good:
3. Other methods for obtaining updated files would be grabbing the OTA update zip from the /cache folder and trying to pull files out of that.. or having an "in" and getting some leaked files or TOT. Sprint and AT&T users would benefit most from a leaked updated TOT.
​Where-To Download KDZ Files
In this section I want to start a collection of all the latest KDZ files for all G3 devices.
You can help me out by either posting your KDZ link with FULL info about the KDZ/DEVICE..
Example of a helpful post:
derp said:
Hi, here is my model info and kdz url below...
LGD855
A6NEWH
D85510L_00
16GB
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW978806432109876543213/D85510L_00.kdz
Click to expand...
Click to collapse
OR you can PM/Private Message me your IMEI so I can look up all the models and latest KDZ's myself. This would help me the most but I understand the security concern. If security is an issue.. you could leave the last 3 digits off the end so I dont have your exact #. If you trust me.. please consider sending me your IMEI if you own one of the devices I need listed below...
KDZ Links Below
Team Codefire had to come through once again and supply TOT files to the USA carriers that provide no public KDZ (AT&T, Sprint, Verizon)
AS985 (USA Regional) - NEED IMEI
D850 (USA AT&T) - 10D TOT (AT&T has no public KDZ files. Feel free to complain to them.)
D850PR (Puerto Rico Claro) - NEED IMEI
D851 (USA T-Mobile) - 10M KDZ
D852 (Canada) - NEED IMEI for D852 Bell, D852 Rogers and D852G
D855 (Europe) - 10L Netherlands 16GB | 10L Germany 16GB NEED MORE IMEIS
D855AR (Argentina) - NEED IMEI
D855K (Australia) - NEED IMEI
D855P (Brazil / Mexico) - NEED IMEI
D855TR (Turkey) - NEED IMEI
D857 (China) - 10C KDZ NEED IMEI STILL
D858 (China / Hong Kong) - NEED IMEI D858 and D858HK
D859 (China) - NEED IMEI
F400 (Korea)- F400L 20E,
LS990 (USA Sprint) - ZV4 TOT (Sprint has no public KDZ files. Feel free to complain to them.)
US990 (USA US Cellular) - 10C KDZ
VS985 (USA Verizon) - 12B​
Click to expand...
Click to collapse
​How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img
1. You downloaded a custom rom flashable zip a rom has made for the community. Roms contain "system" and "boot"
Flash these in TWRP and follow any instructions in the thread/post where you downloaded it. Rom questions belong in those specific rom threads.
You may have to wipe data/factory reset in TWRP, depending on rom.. or you may need to flash a gapps zip if using an aosp-type rom.. etc..
There's no need to worry about OTA's using this route. Proper custom roms will never include the bootloader stack or anything that could remove your bootloader unlock. And just about all custom roms come with a pre-rooted "system" so you don't have to worry about root either. Remember to make a backup in TWRP before flashing anything.
2. You obtained some boot.img,modem.img,system.img files... either extracting from TOT/KDZ yourself or downloaded files another XDA member has uploaded. This method is something you can do all by yourself... no help from a dev needed. To make this method just as easy as flashing a custom rom zip in method #1.. I have made 3 flashable zip files - [Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip]
Download them to your phone using the link below then follow the directions that follow...
DOWNLOAD FLASH2 FILES FROM CODEFIRE HERE
A. Make a new folder on your internal sdcard called: flash2
B. Download and place Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip on your phone. Internal/external sdcard.
C. Stick system.img, boot.img and modem.img into the /sdcard/flash2/ folder. Files must be named system.img, boot.img and modem.img
D. Create backup's in TWRP.
E. In TWRP, flash Flash2System.zip and/or Flash2Boot.zip and/or Flash2Modem.zip to install your updated images.
F. If you have flashed a stock system.img you will need root. After the flash completes press Reboot System and TWRP will ask if you want root. Go thru the process in TWRP then reboot. After booting you may have a notification to finalize root. Few more clicks and you're rooted... it's that easy. No more worrying if root is patched in the latest OTA update... or having to undo everything you changed in stock so that the OTA doesn't brick you.
Flash2*.zip didn't work? Make sure your system/boot/modem.img files are in the /sdcard/flash2/ folder. Internal sdcard!
​How-To Properly Share KDZ/TOT and other Update Files
If you have a new KDZ or have already extracted the KDZ.. please share it with the rest of us in this thread! Please post the KDZ link along with the exact model, region software version and size. Example: D855 Germany 10L 16GB KDZ.
If you want to share your extracted system.img, boot.img and modem.img files please upload them somewhere and share the link. Please specify if you would like others to mirror your files or not (if hosting them on personal server).
Please label all shared files properly! Name them appropriately with boot, modem or system in the name.. as well as the FULL model and software version. Entering my IMEI into the KDZ generator from the last section I can see my device info such as: LGD851TN and D85110M_00. Exact models and software versions are important so other users know which files they need to flash and which to avoid. You should only flash files for your exact device variant. An example name based on my info above: LGD851TN_10M_00_Boot.img (this can be renamed later to boot.img once downloaded or placed on sdcard).
​
Click to expand...
Click to collapse
More G3 Flash2 Threads:
[FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)
[EFS] LG G3 EFS Backup and Restore
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-12-11
Reserved
Nice. On the LS990 (Sprint), it appears that the APK responsible for OTA is titled "com.lge.lgfota.permission" version 4.4.2-LS990ZV41403169216
If I'm looking at the wrong app, someone please correct me, so that other users don't freeze this app and think they're covered, but I froze it and rebooted with no problems.
I also had to run the command line "am start com.lge.hiddenmenu ....[etcetera]" to get into the OTA enable/disable screen.
Block and remove instructions won't show, "spoiler" text reads "blocked"
Sent from my LG-D850
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
cali4nia831 said:
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
Click to expand...
Click to collapse
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
autoprime said:
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Click to expand...
Click to collapse
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
EDIT:
Ended up just renaming the LGFOTA.apk file listed in the first reply above. So I should be good to go...
cali4nia831 said:
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
Click to expand...
Click to collapse
Don't tap Enable.. Tap Disable... and that's it. OTA disabled... off.. all done.
Someone can provide me with img files? I dont have a PC, just using my phone PM if you can help me.
autoprime said:
word
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-10-18
Click to expand...
Click to collapse
Don't stick threads.. stick the man
He knows too much
Thanks for all your work
Edit: Can someone sticks his threads ?
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
First of all, thanks for the guide! It will help a lot of users in preserving bump and root
I don't think that leaving boot/etc .img out will help. LG engineers aren't stupid. The can, for example, do it like this: after "m" update all our phones will reflash aboot/etc partitions to patched versions on 1 jan 2015. The partition's images will be hidden in some big system file, while the waiting daemon will be hidden in, for example, healthd. We will never discover it until it's too late. GG WP.
That said, I really doubt that they will do it that way, but this is still a possibility. I guess i'll flash AOSP/CM/OMNI/smthing rom ASAP.
pRo_lama said:
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
Click to expand...
Click to collapse
link a, b ,c , d in the O.P. mate.. He provided all you need.... =)
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
L10nH34Rt said:
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
Click to expand...
Click to collapse
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
The hidden menu setting ever resets? Not after reboot, factory reset etc?
teddy0209 said:
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
Click to expand...
Click to collapse
I get an unsupported KDZ format error, that's my problem.
L10nH34Rt said:
I get an unsupported KDZ format error, that's my problem.
Click to expand...
Click to collapse
Well, I just extracted mine.... d855, v10i..
Check the command...
teddy0209 said:
Well, I just extracted mine.... d855, v10i..
Check the command...
Click to expand...
Click to collapse
I tried to extract v10l and it failed.
i deleted system updates with tibu should i delete LGFOTA.apk? under system,etc security there are a file named otacerts.zip should i delete that one to.

B170 update arrived

So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Any idea how the phone installs this OTA zip file?
Is the updater-script failing because of assert statements for cust and system?
Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?
Thanks for your efforts on this and answering my questions.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse

Categories

Resources