[OTA] Moto G3 Marshmallow OTA Links - Moto G 2015 General

Hi everyone, here is the thread for all captured OTA update files for the Motorola Moto G3.
After seeing @hp420's thread being overloaded with off-topic posts and its subsequent closure, I have decided to close this thread to all replies, as the intended purpose is to share links only. If you are looking for the discussion on the Marshmallow update, then go to this thread: [DISCUSSION] Android 6 Marshmallow Update
DO NOT FLASH AN OTA THAT IS NOT FOR YOUR SKU
Here are the links:
Code:
[B][U]XT1540:[/U][/B]
(1GB US OTA): [URL="https://drive.google.com/file/d/0B4GMV21ztsFBemF6cDFHTmxuZUk/view?usp=sharing"]Download[/URL] - thanks to @eterlux
(2GB US OTA): [URL="https://drive.google.com/file/d/0ByE999IDa0JnYnUzdjJKQ3Y3a3c/edit"]Download[/URL] - thanks to [user=4196521]@hp420[/user]
[B][U]XT1541:[/U][/B]
(1GB Retail UK OTA): [URL="https://drive.google.com/open?id=0B4TeS4rMavqxWEtZT0FWVkhQRXc"]Download[/URL] - thanks to @dd98
(1GB Retail EU OTA): [URL="https://drive.google.com/file/d/0ByyaN9elpLEyNGlqelNhRUJPS1U/view?usp=sharing"]Download[/URL] - thanks to @hakenhand
(2GB Retail EU OTA): [URL="https://mega.nz/#!vhZyjJQK!O2SXvxcxeKf94Oh5lPGwiYPkg5KpS-sGiR7e0j8cABU"]Download[/URL] - thanks to @Osid
[B][U]XT1542[/U][/B]
(1GB Latin America OTA): [URL="https://mega.nz/#!GQIjURzK!_gXp-W2lawrvUfGXasINOZDEZpZC1NdDquEKOnGnJdQ"]Download[/URL] - thanks to @comishi
(2GB Latin America OTA): [URL="https://drive.google.com/file/d/0B5Uensnd_nd2aC1HLUwzR3hXMTg/view"]Download[/URL] - thanks to @pdloud
[B][U]XT1543:[/U][/B]
(1GB Brazil OTA): [URL="https://drive.google.com/file/d/0B0tUh2HiN0C1S0pVMTNGQUxZU1k/view?usp=sharing"]Download[/URL] - thanks to @SoulReaperAzrael
(2GB Brazil OTA): [URL="https://drive.google.com/file/d/0Bz24pAZ6_fzFb3YzMWZ2WUxIWlE/view"]Download[/URL] - thanks to @leuofiridia
[B][U]XT1544:[/U][/B]
(1GB Brazil OTA): [URL="https://mega.nz/#!cxkBiKAI!3I9M0JM28N7tywlRFki9I6p4BOfQzVXzyk9Wkyl2VSE"]Download[/URL] - Thanks to @drico_649
[B][U]XT1548[/U][/B]
No OTAs captured yet.
[B][U]XT1550:[/U][/B]
(1GB India OTA): [URL="https://mega.nz/#!wBEUCTwS!SvEuNkkqXZKYXOdEtXNTg1hFeKomAwSAl_ks3TN2fhE"]Download[/URL] - thanks to @lexer98
(2GB India OTA): [URL="https://drive.google.com/open?id=0BxepRksF8JIKcnpVRlRyMFk0UFk"]Download[/URL] - thanks to [user=6504205]@d4c7[/user]
If anybody captures an OTA, please PM me with the following:
Code:
Link:
SKU Number: XT15xx
RAM Size: 1GB or 2GB?
If you are uploading an OTA, do not use Dropbox as they will eventually remove the link. Google Drive, Android File Host and Mega.nz are preferred
Thanks to @hp420 for the original OTA link thread

Added 2GB Brazil OTA (XT1543) thanks to @leuofiridia

Added proper US 2GB XT1540 OTA thanks to @hp420

Brazil 2GB XT1543 OTA Link Fixed

2GB XT1550 India OTA added thanks to @d4c7

Added 1GB Brazil XT1544 OTA thanks to @drico_649

Added 1GB Brazil XT1543 OTA thanks to @SoulReaperAzrael

Added 2GB Latin America XT1542 OTA thanks to @pdloud

Added 1GB Latin America XT1542 OTA thanks to @comishi

Added 1GB XT1541 MM OTA for Retail UK thanks to me
Added 2GB XT1541 MM OTA for Retail EU thanks to @Osid

Added XT1550 India 1GB OTA thanks to @lexer98

Added 1GB XT1541 Retail EU OTA thanks to @hakenhand

Tried flashing 1g retail UK put back to stock 5.1.1 wont flash says something about test kkeys mine still reads omni never even had an omni rom on this phone any ideas
Thanks in advance

How do I flash this ota on my stock moto g 3rd gen 2gb ??

skooter32 said:
Tried flashing 1g retail UK put back to stock 5.1.1 wont flash says something about test kkeys mine still reads omni never even had an omni rom on this phone any ideas
Thanks in advance
Click to expand...
Click to collapse
If you're really sure that system is pure stock, you can extract updater-script file from OTA and comment out (# char) lines which checks for correct fingerprint
Example (lines truncated for clarity):
# getprop("ro.build.fingerprint") == ....
# getprop("ro.build.fingerprint") == ...
# abort("Package expects build fingerprint of ...
Of course at your own risk.

Osid said:
If you're really sure that system is pure stock, you can extract updater-script file from OTA and
Of course at your own risk.
Click to expand...
Click to collapse
What would account for such a discrepancy? I have a Irish phone on Meteor network running the EU pure stock. I know some have received the OTA for this on my network.
Package expects: motorola/osprey_reteu/osprey_umts:5.1.1/LP23.72-47.4/4:user/release-keys
This device: motorola/osprey_reteu/osprey_umts:5.1.1/LPI23.72-47/5
Difference being LPI instead of LP and 45/5 instead of 47.4/4
What is the significance of these differences?

conpower said:
Difference being LPI instead of LP and 45/5 instead of 47.4/4
What is the significance of these differences?
Click to expand...
Click to collapse
Big significance.
Probably most of the files in /system partition have different contents (=different SHA1 hashes), so it's not possible to apply update.

Osid said:
If you're really sure that system is pure stock, you can extract updater-script file from OTA and comment out (# char) lines which checks for correct fingerprint
Example (lines truncated for clarity):
# getprop("ro.build.fingerprint") == ....
# getprop("ro.build.fingerprint") == ...
# abort("Package expects build fingerprint of ...
Of course at your own risk.
Click to expand...
Click to collapse
I have the same problem with my xt1541 2gb eu. I have the 23.72.33 build and if I try to install the update it fail. How can I do? What I have to comment in updater-script? thanks

matlear said:
How do I flash this ota on my stock moto g 3rd gen 2gb ??
Click to expand...
Click to collapse
Download the correct OTA file for your device, then copy it to the root folder on your phone.
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Press the Volume Down button to highlight "Recovery mode"
Press the Power button to restart into Recovery mode.
You'll see an image of an Android robot with a red exclamation mark, and the words "No command" underneath.
While holding down the Power button, press the Volume Up button.
Use the volume buttons to scroll to "apply update from sdcard" and press the Power button to select it.
Use the volume buttons to scroll to the OTA file and press the Power button to select it.
Wait until the OTA file has finished installing on your phone.
Use the volume buttons to scroll to "wipe cache partition" and press the Power button to select it.
Optionally, if you want a clean install instead of an upgrade:
Use the volume buttons to scroll to "wipe data/factory reset" and press the Power button to select it.
Scroll down to "Yes - erase all user data" and press the Power button to select it.
Source: https://motorola-global-portal.cust...prod_answer_detail/a_id/105537/p/30,6720,9390
Source: https://www.youtube.com/watch?v=4RUsspI1CrU (Moto G 2014)

I have XT1541, 23.41.47.osprey_reteu_2gb.reteu.en.EU retfr.
Should I use XT1541 (2GB Retail EU OTA) by @Osid? It doesn't mention retfr anywhere so I'm too scared to flash it.

Related

[HOWTO] manually flash Samsung Galaxy S with JVQ firmware ** WORKS ** UPDATED 20.07.

This Howto describes whole procedure to install Android 2.3.4 Gingerbread to Samsung Galaxy S I9000/I9000M
BEWARE: Following theese steps can be potentially dangerous. You are going to undergo potentially risky operation. In bad case, or if you do something wrong, you may brick your phone. Feel free to ask, if you are unsure.
First try to boot your phone in Download Mode (described in the howto, so look for it). If it works, follow Instructions in [Block 2]
If it does not work, ie. you can't boot your phone in Download Mode, then start with Instructions in [Block 1]
First of all, download I9000XXJVQ_by_Virnik.rar and extract it somewhere (for example on your desktop). All files mentioned in this howto are compressed in this package. Enter FLASH directory you have extracted. All things needed are categorized in it's specific folders.
You will get following folders from it (Inside extracted FLASH folder):
- Kernel
- Odin
- ROM
- Theme
And for the Theme, there are two Theme versions in the big RAR archive. DeepBlue and DeepPurple. Both can be outdated, so check their threads, to have latest one.
We will use all of them in [Block 2] of this howto.
Please understand, that Ficeto's Deodexed JVQ ROM zip package in this big archive is not same as official Ficeto's ROM, I have changed installed kernel and modem, to suit my needs. I have also removed few unnecessary apps from it.
[Block 1]
If you have problem with button combo, which means that your phone ignores Download mode and startup normally, follow theese instructions:
Preparations: Make sure you have the drivers installed (i.e Kies is recognizing the phone), adb available and "USB Debugging" turned on in "Settings -> Applications -> Development" menu. Type *#0228# in the dialer and check Voltage value (without USB plugged in) is atleast 3800(mV).
1] Unplug the phone from the computer (if connected)
2] Kill all Kies related software (tray agent, etc)
3] Start Odin
4] Plug in the phone to the computer
5] Start a new command prompt and navigate to the folder / drive where adb is located. If you haven´t downloaded adb yet, get it here.]
6] Type "adb reboot download" to the command prompt and press enter.
7] Switch to Odin and select the Aries_P-SBL.tar.md5 as PDA file. Make sure "Phone Bootloader Update" is ticked and re-partition is unticked. Do not select any other files but "Aries_P-SBL.tar.md5".
8] Press "Start" button to launch the update process. It will take around three seconds to complete. After the update phone will reboot automatically.
Thanks Richthofen for this part of my howto]
[Block 2]
If your phone is NOT branded and SIM-Locked, your way to new firmware is much more shorter. Follow theese instructions:
01] Enter Odin folder and startup Odin.
a) Click PIT Button, select s1_odin_20100512.pit file
b) Click PDA Button, open ROM/Stock folder and select CODE.tar file.
c) Click PHONE Button, open ROM/Stock folder and select MODEM.tar file.
d) Click CSC Button, open ROM/Stock folder and select CSC.tar file.
e) Tick "Re-Partition and if you were using Froyo previously, "Phone Bootloader Update" tick boxes
02] Power off your phone and make sure you have SIM card out, SD card out. Disconnect USB.
03] Press and hold 3-button combo, to boot your phone in Download mode (Volume down, Home, Power)
04] Connect your phone to the PC via USB cable.
05] In odin, ID:COM field shall change color to yellow, and in Message window, you will see message "Added"
06] Now press Start button.
07] Go and take cigarette, coffee, etc. This will take up to 5 minutes.
08] Phone will reboot itself. Disconnect USB. Pull out battery, once it is booted, and place it back.
09] Press and hold 3-button combo, to boot your phone in Download mode (Volume down, Home, Power)
10] Switch back to Odin, and press "Reset Button"
a) Click PDA Button, open Kernel folder and select CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.tar file
b) Make sure Re-Partition Button IS NOT ticked
c) Connect your phone to the PC via USB cable.
d) In odin, ID:COM field shall change color to yellow, and in Message window, you will see message "Added"
e) Now press Start button.
11] After successfull flash, phone will reboot itself, and Odin will write Success message.
12] Let your phone boot, meanwhile disconnect USB.
13] Once you'll set your language (you can skip all other configuration wizzard's steps), go to the Settings->Applications->Development->USB Debugging and tick it.
14] Connect USB to the phone now. You will notice information "USB Connected" in the notifications. Click it. Mount internal storage. Phone's internal SD card will become visible for the windows as a flash drive.
15] Delete everything from the SD Card, or move it somewhere to your desktop as a backup.
16] Copy XXJVQ_Deodexed_Zipaligned_MultiCSC_signed.zip file from ROM/Deodex directory to your phone's internal SD card.
17] Now it is time to choose. Are you boy, or girl? Because boys will most likely want their phone to be in blue color, girls will prefer Ping/Purple color. After you're decided, copy file of your choose from Theme directory to the internal SD card. You can take a look how it will look like in DeepBlue Theme or DeepPurple Theme threads. It is definitelly worth to look there, because Theme packages in the big RAR archive is not up-to-date as Theme zips in those threads are.
18] Time for another kind of magic. We will use another button combo, this time recovery mode. Press Volume Up, Home, Power
19] In the Recovery Mode, use Volume Up/Down to move in the menu. Select "Install zip from sdcard" and then press Power. Then select XXJVQ_Deodexed_Zipaligned_MultiCSC_signed.zip to install and confirm by pressing Power.
20] Progress bar will show up for a while. After that, select "Reboot system now"
21] Once It'll boot (this will take few minutes, because dalvik cache has been wiped, and needs to be regenerated from new files, and then filesystem conversion will start, so be patient), power off your phone again, and start in recovery.
22] Back in recovery Mode, use Volume Up/Down to move in the menu. Select "Install zip from sdcard" and then press Power. Then select DeepBlueTheme_JVQ_By_Virnik_v099-5.zip file or DeepPurpleTheme_JVQ_By_Virnik_v090-5.zip file to install and confirm by pressing Power. Reboot your phone once it's finished.
OPTIONAL:
Install Neldar's BLN app (paid) from the Market, and enable BackLight Notifications for incomming calls, SMS, emails, and so on.
Performance tips:
Download Tegrak from the Market, and try to overclock your phone to 1100MHz (which is absolute safe on every SGS). Test it a little with games and such, and then try higher value, for example 1200MHz. If your phone freeze, then stay with lower values, if not, you can try even higher value (1400MHz).
Most phones will handle 1200MHz maximum without any bad side effects. My own phone for example, can handle 1152MHz without freezing, and 1200MHz makes my phone freeze from time to time, so you can test it yourself.
You can test with Quadrant or Linpack, to see how your overclock affect overal performance of your phone ;-)
Vocabulary:
Button COMBO:
- Button Combo is trick, in which three buttons are pressed simultaneously, to force some action on the phone.
- Typically, phone can reboot in Download Mode, and Recovery mode. Some providers are disabling this. For this reason, first part of the howto has been created.
a) Download Mode Combo - Power off your phone. Now press Volume Down, Home, Power. If you did everything right and your phone dont have this disabled, your phone will start in Download Mode. You can verify it very easily, because you will have yeallow triangle in the centre of the screen with green Android robot with shovel in hands in the centre. Download Mode is used to flash your phone. Simply, it instruct phone to await data load from your computer. Dont worry, if you start download mode accidentaly, simply restart. It does not break anything.
b) Recovery Mode Combo - Power off your phone. Now press Volume Up, Home, Power. If you did everything right and your phone dont have this disabled, your phone will start in Recovery Mode. You can verify it very easily, because you will have text menu on the screen. You can move between each line by Volume Up (for moving selection UP), Volume Down (for moving selection DOWN) and Home to enter (start chosen action). In Recovery mode, you can apply update from sdcard (typically root kit, or anything inside update.zip, which have to rewrite/update something in the system), Factory Reset, or fix problems (some old versions of One Click Lag Fix broke system up, because it failed to create/delete ext2 partition, which ****ed up internal storage), such as clear phone app cache, reformat internal sdcard, and such.
{
"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"
}
Answers and questions:
Q: Can I use this for updating my Indian/Mexican/Japan phone?
A: Yes. But do not forget that this is european firmware, which means it will allow you to choose from european languages. If you want your phone in your own languages, you will need to choose different firmware from samfirmwares, depending where are you from. Then you can use that firmware, it does not change anything in the howto, except for the firmware nationality.
Q: I have my phone SIM-Locked, what can I do?
A: Follow second part of the howto first.
Q: I have my phone branded/download mode ignored, what can I do?
A: Follow second part of the howto first.
Q: Will it rewrite my files to Korean ones?
A: No. It will use european firmware, if you stick close to this howto.
Q: Will different nationality firmware change anything in this howto? Do I have to follow little bit different instructions?
A: No. You may miss some language support or Swype in your language, but that changes nothing.
Q: Can I hug you?
A: You can - if you are disease free, but I will not travel from my home town. In adition, you will also need to find me yourself ;-)
Q: Where are the files I need to proceed with this howto?
A: Few lines after this sentence Just choose your mirror, and enjoy.
(will be updated, once somebody asks something important)
PS: Once everything finished, install Quadrant from Android Market. Quadrant is very good benchmark. Write here your score please. Better than that, download Quadrant before whole procedure, write down your score, then start upgrade procedure. After finished, compare both numbers - before and after. Now you can feel the difference, aren't you? :-D
PS2: Tired of baterry live time? Here is another tweak. Download SetCPU from Android market. Give it root permission (simply agree, when it asks upon app start), set it to start at boot. Set frequency (min, max) to 1000MHz and policy to ondemand. Create new profile, set it to underclock phone's CPU when display is off to 200MHz. Done. To be sure, restart your phone. From now on, when your phone goes to sleep (simply laying in your pocket with display off), it underclock itself, which save batterry a lot.
PS3: Another baterry eating problem is number of running apps in the background. From Android Market, download Advanced Taskkiller (paid app, but worth it).
Install, setup it to start at boot, to kill unneeded processes every 30 minutes. BEWARE! You will have to set Settings and few other apps u like to be ignored in the Advanced Task manager!
PS4: Want to have nice UI, like the HTC's one? Download Launcher Pro (and pay for it to upgrade to Plus version). Then download Beautiful Widgets (paid too).
Play a little with its settings. Again, it is well worth it.
UPDATE:
Before you proceed, you shall install Busybox from the Market. Run it, and let it download and install busybox environment (to tell it straight - linux commands for the commandline, many apps for the root users uses them).
If you are concerned about Product Code and it's changing, here are procedure to do this. Keep in mind that JPY WILL NOT OVERWRITE your product code. It is fault of older firmware flashed previously. And as whole howto, it will be manual procedure again:
Check you actual Product Code by writing *2767*4387264636# in your dialer.
Then there will be a line that says:
[2] PCode:"your phone model type"
Due to previous flash, it can be wrong. So now we will change it to the proper value:
Text Mode Method:
Download Terminal Emulator from the Market
- Open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with HxD Editor and search for ''KOR'' - change this to the product code matching your country (red marked text should be changed). Im czech, so mine is XEZ. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿ[COLOR="Red"]KOR [/COLOR] GT-I9000HKD[COLOR="red"]KOR[/COLOR]
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin /efs/nv_data.bin
Also enter: rm -rf /efs/nv_data.bin.md5
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
GUI Medthod:
Download Android Mate from the Market
- Open the Android Mate, and switch to File Explorer bookmark at the top
- navigate to the /efs folder
- by ticking, select nv_data.bin, and from the bottom menu, choose copy.
- navigate to your sdcard directory (/sdcard for internal SD, or /sdcard/external_sd for external SD, does not matter)
- press Paste from the bottom menu.
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with HxD Editor and search for ''KOR'' - change this to the product code matching your country (red marked text should be changed). Im czech, so mine is XEZ. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿ[COLOR="Red"]KOR [/COLOR] GT-I9000HKD[COLOR="red"]KOR[/COLOR]
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Android Mate again, select File Explorer, find and tick your changed nv_data.bin, and press Copy from the bottom menu
- navigate again to the /efs directory, and press Paste from the Bottom Menu.
- tick "nv_data.bin.md5" file, and press Delete from the Bottom Menu (it will be autocreated after reboot)
- exit Android Mate, and reboot your phone.
Available Country Product Codes are here:
ATO -Austria (A1, bob, T-Mobile A, Orange AT, tele.ring, 3, yesss!, aon)
AUT - Switzerland (sunrise, Swisscom, Orange CH)
CNX - Romania (Vodafone RO)
COA - Romania (Cosmote)
COS - Greece (Cosmote)
CRO - Croatia (T-Mobile)
CYO - Greece (MTN, CYTAVODA)
EUR - Greece (WIND GR, vodafone GR, COSMOTE)
HAT - Romania (RO Orange, Vodafone RO, Cosmote)
IRD - Slovakia (Orange, T-Mobile SK, 02 - SK)
KOR - Korea (SEC Test)
MET - Ireland (Meteor)
MOT - Slovenia (Mobitel)
MOZ - Switzerland (Sunrise, Swisscom, Orange CH)
MSR - Serbia (Telenor)
MTL - Bulgaria (MTEL)
O2C - Czech Republic (O2 - CZ)
O2I - IE (02.ie)
ORO - Romania (RO Orange)
SEB - Baltic (LMT GSM, LV TELE2, LV BITE, LT Omnitel, LT Bite, LT TELE2, EE EMT, EE ELISA, EE TELE2)
SIM - Slovenia (Si.mobil)
SMO - Serbia (mt:s, Telenor, Vip SRB)
SUN - Switzerland (Sunrise)
TMZ - Czech Republic (T-Mobile CZ)
TOP - Serbia (Vip SRB)
TPH - Portugal (P TMN, P Optimus, vodafone P)
TRA - Croatia (T-Mobile HR, HR VIP, TELE2)
TSR - Serbia (mt:s)
TWO - Croatia (TELE2)
VDH - Hungary (vodafone HU)
VDI - Ireland (vodafone IE)
VIM - Makedonia (VIP MK)
VIP - Croatia (HR VIP)
VVT - Bulgaria (vivacom)
XEH - Hungary (T-mobile H, pannon, vodafone HY, vodafone HU VMAX
XEO - Poland (Plus, Era, Heyah, Orange, Play)
XEZ - Czech Republic (T-Mobile CZ, O2 - CZ, Vodafone CZ
XFA - South Africa (Vodacom, Vodacom Lesotho, MTN, Cell C, Virgin)
XFC - South Africa (Vodacom, Vodacom Lesotho, MTN, Cell C, Virgin)
XFE - South Africa (Vodacom, MTN, Cell C, Virgin)
XFM - South Africa (Vodacom, Vodacom Lesotho, MTN, Cell C, Virgin)
CPW - UK & IRE (O2 UK, Orange UK, T-Mobile, Virgin Mobile, Vodafone UK, TESCO, BT Mobile, H3G, Asda, O2 IRL, Vodafone IE, Meteor, H3G IE, Tesco Mobile Ireland)
DBT - Germany (T-Mobile D, Vodafone.de, E-Plus, o2 - de)
ITV - Italy (TIM, Vodafone, WIND, H3G)
XEF - France (Orange F, F SFR, BOUYGTEL, NRJ (SFR), Virgin, Tele2, Auchan, Carrefour, NRJ (ORANGE), Orange (340 01), Orange (647 00), Debitel, Leclerc, Digicel)
XEO - Poland (Plus, Era, Heyah, Orange, Play)
XEU - UK & IRE (O2 UK, Orange UK, T-Mobile, Virgin Mobile, Vodafone UK, TESCO, BT Mobile, H3G, Asda, O2 IRL, Vodafone IE, Meteor, H3G IE, Tesco Mobile Ireland)
BMC = Bell Mobility Canada
SER - United Kingdom (O2)
XEE - Nordic Countries (Telenor and others)
XSO - Singtel
MOB - Austria A1 (Mobilcom)
TMH - T-Mobile Hungary
XEN - Netherelands
If you like this thread and if it helped you, please vote for it with five stars, and to be at front page ;-)
If I did help you, please do feel free to thank me by Thanks button.
Works for me!
Thx dude, now thats what I call a How-to !
MagicOnline said:
Thx dude, now thats what I call a How-to !
Click to expand...
Click to collapse
No problem. You know, I can call myself professional in IT, but I know what are people asking, what they want. I know that feel, when you do not understand something and somebody still forces you to find out everything yourself. It is really stupid, because such behaviour can make things worst. If noob is forced to do something risky without any experience, without any concrete help, he can break his own device. This is why I have created this. To help such noobs. And please, do not take word "noob" badly - I have full respect to such people, because even if I am IT expert myself, I am actually noob in many other things.
Will this work on the Canadian GT-I9000M? I've been very reluctant to flash the European firmware onto my SGS, because I've seen how it is just different enough to cause "problems" (read: brick).
Thanks.
mymanchris said:
Will this work on the Canadian GT-I9000M? I've been very reluctant to flash the European firmware onto my SGS, because I've seen how it is just different enough to cause "problems" (read: brick).
Thanks.
Click to expand...
Click to collapse
please read carefully again. Just download canadian firmware instead. all other steps are OK and will work for you
PS: When I bought my phone, I wanted to flash it. It was branded and locked. So I edited Kies registry to canadian firmware info, to update via Kies (and unlock it), which reflashed my phone with canadian firmware. I didnt used it for long (five minutes maybe), because I have used it only to access Download mode. It worked.
But again, If you fear, do not flash. It is simple, risk is high, as you said - you can brick it. But due my experiences, if you can access Download mode or Recovery, there is everytime way back without bricking. Completelly bricked phone means that you have Button Combo's disabled. Then there is no way back except for waranty procedure.
So first make sure you have unlocked and unbranded firmware. If you don't, then unbrand and unlock first.
Nice and comprehencive how-to, but unfortunately, the first part about getting the 3 button combo does not work, at least not on my phone. Kies "upgraded" my phone to JM1.
Any ideas? TIA
KingOfSola said:
Nice and comprehencive how-to, but unfortunately, the first part about getting the 3 button combo does not work, at least not on my phone. Kies "upgraded" my phone to JM1.
Any ideas? TIA
Click to expand...
Click to collapse
Use Kies again, this time regedit to theese values:
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEU"
"HIDSWVER"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
upper post updated. Sorry, my misstake. Older FW provider disabled download mode too.
KingOfSola said:
Nice and comprehencive how-to, but unfortunately, the first part about getting the 3 button combo does not work, at least not on my phone. Kies "upgraded" my phone to JM1.
Any ideas? TIA
Click to expand...
Click to collapse
I'm not sure what you did with the 3BR to try and fix it, but I followed this advice here: http://forum.xda-developers.com/showthread.php?t=785201 ... and I have mine working fine running JM1 too.
Virnik0 - I came here from the other thread you had 'hijacked' and wanted to follow up the brief discussion.
I switched from KOR to XEU simply by the built-in feature (where it lists all the codes), after backing up my device (contacts etc...). My phone is now running the XEU version so I'm happier now than when I was.
I'm slightly annoyed that even after backing up my contacts etc... it doesn't save the groups I had saved my contacts in! In fact, after the normal reset that changing the country code does, there was no groups to choose from so I had to create these manually, and go through every contact one by one which was very time consuming. Do you have a better way of doing this? I currently have groups; Family, Friends & Work. Although I 'only' have 25 contacts, I've yet to add another 100 and don't want to do this until I'm happy with the way things are.
I'm still yet to try this method you posted, but I do see myself trying this out in the next few days. However, I've heard that the 2.2 update that you're able to get still contains some bugs, and the update that is due to be rolled out is still being worked on before release, which means I may be better off waiting. Your thoughts?
SamuraiHQ said:
I'm not sure what you did with the 3BR to try and fix it, but I followed this advice here: http://forum.xda-developers.com/showthread.php?t=785201 ... and I have mine working fine running JM1 too.
Virnik0 - I came here from the other thread you had 'hijacked' and wanted to follow up the brief discussion.
I switched from KOR to XEU simply by the built-in feature (where it lists all the codes), after backing up my device (contacts etc...). My phone is now running the XEU version so I'm happier now than when I was.
I'm slightly annoyed that even after backing up my contacts etc... it doesn't save the groups I had saved my contacts in! In fact, after the normal reset that changing the country code does, there was no groups to choose from so I had to create these manually, and go through every contact one by one which was very time consuming. Do you have a better way of doing this? I currently have groups; Family, Friends & Work. Although I 'only' have 25 contacts, I've yet to add another 100 and don't want to do this until I'm happy with the way things are.
I'm still yet to try this method you posted, but I do see myself trying this out in the next few days. However, I've heard that the 2.2 update that you're able to get still contains some bugs, and the update that is due to be rolled out is still being worked on before release, which means I may be better off waiting. Your thoughts?
Click to expand...
Click to collapse
I am not sure what bugs are you talking about. I didn't run into single one, JPM should be final 2.2 Froyo release from Samsung. About your contacts grouping problem, try this:
Move your contacts to groups as you like them to be.
Then backup your contact to Google
Then switch airplane mode on, disable wifi, and delete your contacts.
After then, switch airplane mode off, and wait for google sync.
Once done, export your contacts to sdcard.
then import them again.
Now it should be ok.
About the XEU and KOR problem - some people reports (and I ran in the same problems) that after flash, first boot, KOR makes problems creating internal storage. It simply refuses to format sdcard, recovery mode do not help. I am unsure if this is because of firmware itself, or different folder tree format...
ARGGGGHHHH!!!
I've just run into another problem. I just started Kies, and it required an update (which went fine). It's now version 1.5.3.10093_82 but upon connection with my device, the phone screen flickers like it's having an epileptic seizure. The 'MTP Application' on my phone flickers between that, and my home screen. Everything is closed down as normal - and a reboot of my device hasn't fixed this.
I'm thinking the new update has just screwed something up here, as I've never had a problem connecting before. Why does Samsung have to be so bad at everything???
Edit - Thanks for the contact info. I'll give that a try in a bit.
SamuraiHQ said:
ARGGGGHHHH!!!
I've just run into another problem. I just started Kies, and it required an update (which went fine). It's now version 1.5.3.10093_82 but upon connection with my device, the phone screen flickers like it's having an epileptic seizure. The 'MTP Application' on my phone flickers between that, and my home screen. Everything is closed down as normal - and a reboot of my device hasn't fixed this.
I'm thinking the new update has just screwed something up here, as I've never had a problem connecting before. Why does Samsung have to be so bad at everything???
Edit - Thanks for the contact info. I'll give that a try in a bit.
Click to expand...
Click to collapse
Is it your KOR to XEU switched firmware? As I said, KOR firmware should not even boot, but obviously you have managed to make it work...somewhat.
If your download mode works, use my instruction steps to flash it to JPM (JPK first, then JPM, because we need CSC and modem to be used first), and see if it works. It should. If you run into problem where it cant format internal storage after flash (here it comes - KOR firmware to XEU makes this), reboot to recovery, and press factory reset, clean cache, and then internal storage format. then reboot again.
It should work now.
Well I'm assuming it was originally a KOR firmware that was installed, after following the advice here to fix my missing 3BR mode last week. I have since changed the KOR to XEU by using the *#272*HHMM# code. The device reports that it's XEU as does the registry after connecting to Kies the other day.
I think it's the new update, and I've just emailed Samsung now to see what the hell they've done.
I'd rather have this issue fixed before I plan on trying your guide, as I will need to use Kies at some stage, and if I can't use it - I'll be in a world of hurt.
SamuraiHQ said:
Well I'm assuming it was originally a KOR firmware that was installed, after following the advice here to fix my missing 3BR mode last week. I have since changed the KOR to XEU by using the *#272#HHMM# code. The device reports that it's XEU as does the registry after connecting to Kies the other day.
I think it's the new update, and I've just emailed Samsung now to see what the hell they've done.
I'd rather have this issue fixed before I plan on trying your guide, as I will need to use Kies at some stage, and if I can't use it - I'll be in a world of hurt.
Click to expand...
Click to collapse
Hey, hold on!
Are your Download Mode accessible? If yes, than you are clean!
If you have Download Mode available right now, you do not need Kies!
Kies is needed only if somebody have their Download Mode disabled by provider/vedor!
Kies detects firmware by itself, so it is possible that you have gotten into mixed state, in which KOR switched to XEU firmware is detected by Kies as KOR, and overwritten something...
So I am suggesting you to try Download Mode first. If You can access it, you can flash rightaway, and have a pleasure with new JPM
Virnik0 said:
Use Kies again, this time regedit to theese values:
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEU"
"HIDSWVER"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
upper post updated. Sorry, my misstake. Older FW provider disabled download mode too.
Click to expand...
Click to collapse
Still no go with the 3BR unfortunately.
My initial values where:
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
GT-I9000HKDNEE
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
And after the "upgrade":
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
GT-I9000HKDNEE
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
Virnik0 said:
Hey, hold on!
Are your Download Mode accessible? If yes, than you are clean!
If you have Download Mode available right now, you do not need Kies!
Kies is needed only if somebody have their Download Mode disabled by provider/vedor!
Kies detects firmware by itself, so it is possible that you have gotten into mixed state, in which KOR switched to XEU firmware is detected by Kies as KOR, and overwritten something...
So I am suggesting you to try Download Mode first. If You can access it, you can flash rightaway, and have a pleasure with new JPM
Click to expand...
Click to collapse
Yes it's accessible - it's what I did last week to fix my 3BR
I'm reinstalling Kies now (old version), in any case as I'd like it to work as it should.
Well if I don't need Kies to complete this process then I may as well start this shortly... after I've made myself a drink haha.
Looks like I need to start downloading some files. I already have Odin 1.3 installed, so it's just the smaller files. Thanks for your help.
KingOfSola - See my post on the other page. It works, trust me!
SamuraiHQ said:
Yes it's accessible - it's what I did last week to fix my 3BR
I'm reinstalling Kies now (old version), in any case as I'd like it to work as it should.
Well if I don't need Kies to complete this process then I may as well start this shortly... after I've made myself a drink haha.
Looks like I need to start downloading some files. I already have Odin 1.3 installed, so it's just the smaller files. Thanks for your help.
KingOfSola - See my post on the other page. It works, trust me!
Click to expand...
Click to collapse
Download just one...it is marked by blue font at the bottom of my howto. It has 1GB, and you can find both firmwares in it, root kit, OCLF, battery MOD, and such.
Virnik0 said:
Download just one...it is marked by blue font at the bottom of my howto. It has 1GB, and you can find both firmwares in it, root kit, OCLF, battery MOD, and such.
Click to expand...
Click to collapse
Thank you
WOW! I don't speak Czech, but even I understand a 119 minute wait if I don't register (300kB/s), and a 17 minute wait if I do. I'm not sure about speed on this one aha. I think you should provide your login name and password
KingOfSola said:
Still no go with the 3BR unfortunately.
My initial values where:
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
GT-I9000HKDNEE
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
And after the "upgrade":
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
GT-I9000HKDNEE
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
Click to expand...
Click to collapse
What are you exactly trying to do?
Is your Download Mode accessible?
Have you tried regedit tweak?
To be successfull with kies (and enable Download Mode), you have to:
Startup Kies, press Update Button, then switch to regedit (DO NOT CLOSE KIES)
regedit, change appropriate values, close regedit.
Back in Kies, press upgrade Button
After reboot, you will have to switch your phone off (it vibrate shortly, once it is finally powered off)
Then press Volume Down, Menu, Power and hold all three buttons till it powers itself up. You need to press theese buttons in precise order and hold, which means that first you will press volume down and during the time you are holding it pressed, press menu (now you are holding two buttons), and then press power, while still holding all three buttons. After phone powers itself up, you shall se yellow triangle on the screen. Now you are ready to continue with Odin (second section of my howto)
Virnik0 - I recommend more download links. The one you're using requires payment for a 'quicker' download and shorter waiting time, or it's 2 hours for free and slow speed.
I do have a list of file hosting sites, but http://www.filedropper.com/ is very good.
I'm also learning Czech the hard way
SamuraiHQ said:
Thank you
WOW! I don't speak Czech, but even I understand a 119 minute wait if I don't register (300kB/s), and a 17 minute wait if I do. I'm not sure about speed on this one aha. I think you should provide your login name and password
Click to expand...
Click to collapse
I dont have any login from uloz.to server. It is completely free, even for uploaders. And if you want to understand what is written there, you can use google translator.
Or, if you know some other server where I can upload it to, just let me know. I can even upload it to your server, if you have fast line enough.
Just wait till download is finished as a free guest access
Go take coffee, cigarette, girl or any other entertaiment you want, I think it is worth it.
PS: Uploading took me 3 minutes :-D I am sitting at 1Gb/s optic wire
I wasn't joking, when I wrote that I am admin
EDIT: OK, uploading to file dropper now. Will give new link to the first post once it is uploaded.

[ROOT] Rooting for SGP611 with giefroot (Bootloader Locked)

WARNING: This instruction may brick your device permanently. I am not
responsible for any your loss or damage.
The following is the instruction to get root for SGP611 with giefroot(http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598)
Requirement:
Bootloader Locked Z3 Tablet Compact Wi-Fi 16GB (SGP611)
D6603(Generic GLOBAL 23.0.A.2.93) firmware (You can got it from XperiFirm)
Flashtool
Install driver included in Flashtool
Patched version of giefroot_v3 (View attachment giefroot_v3_sgp611_fix1.zip)
Download:
View attachment giefroot_v3_sgp611_fix1.zip
Small Instruction:
1.Backup
2.Flash SGP611 firmware (23.0.1.A.0.167) if other version is installed
3.Flash D6603 system partition (23.0.A.2.93)
4.Enable [USB Debug] and [mock locations] and [Unknown Source] , then run install.bat in (View attachment giefroot_v3_sgp611_fix1.zip)
5.You got root!
6.Backup TA, Back to SGP611 firmware
Instruction:
1. Backup all your data (including application data and internal storage)
2. Get SGP611(23.0.1.A.0.167) firmware
3. Get D6603 firmware(Generic GLOBAL 23.0.A.2.93 ftf) from somewhere
4. If firmware version of your device is not 23.0.1.A.0.167, then flash all
contents of ftf to back to 23.0.1.A.0.167
(Start Flashtool and click "flash device", then choose "Flashmode".
On "Firmware Selector" select SGP611 firmware.
Uncheck APPSLOG, CACHE, DATA in Wipe menu.
Check all checkbox in Exclude menu.
Unckeck KERNEL in Exclude menu.
Then click Flash button.
Shutdown your device and connect USB on holding volume down.
Wait 20minute or more to finish.
)
5. Flash only system partition of D6603 (23.0.A.2.93)
(Open "Firmware Selector" with same instruction above.
select D6603 firmware.
Uncheck APPSLOG, CACHE, DATA in Wipe menu.
Check all checkbox in Exclude menu.
Unckeck SYSTEM in Exclude menu.
Then click Flash button.
And flash with same instruction above.
)
6. Power on your device, then enable [USB Debugging] and [Allow mock
locations] in Developer options. And enable [Unknown sources] in Security
setting.
Added:
Disable [Verify apps over USB] in Developer options, and disable [Verify apps] in Security setting.
Thanks kvi!
7. Install usb driver included in Flashtool
8. Download giefroot_v3_sgp611.zip and extract zip
9. Run install.bat in extracted folder, then wait for about 1minute
10. You got root!
11. Backup TA
12. Restore stock firmware by following insruction of this thread http://forum.xda-developers.com/z3-...-to-rooted-stock-sgp621-firmware-drm-t3015494
(replace SGP621 to SGP611 in the instruction)
Thanks to zxz0O0 for giefroot and some other tools.
zxz0O0 spend so much time to make giefroot work on SGP611 kernel.
Thanks to lowtraxx for root instruction for SGP621.
(http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534)
Thanks to CubicU07 for instruction to restore stock firmware.
The old version (giefroot_v3_sgp611.zip) does not work.
Please try new version (View attachment giefroot_v3_sgp611_fix1.zip).
I'm sorry.
For me its not working:
Got a Z3TC 16GB WIFI, installed the Z3TC ftf, then flashed the system from the Z3, then used the tool but always get a device not rooted error
moritz31 said:
For me its not working:
Got a Z3TC 16GB WIFI, installed the Z3TC ftf, then flashed the system from the Z3, then used the tool but always get a device not rooted error
Click to expand...
Click to collapse
It may not succeed in one time.
Plaese try again 3 or 4 or more times.
If you still fails, please let's me know results of commands below.
Code:
adb shell cat /data/local/tmp/giefrootlog
adb shell cat /data/getrootlog
adb shell ls -l /data/local/tmp/scsi_wait_scan.ko
rurie said:
It may not succeed in one time.
Plaese try again 3 or 4 or more times.
If you still fails, please let's me know results of commands below.
Code:
adb shell cat /data/local/tmp/giefrootlog
adb shell cat /data/getrootlog
adb shell ls -l /data/local/tmp/scsi_wait_scan.ko
Click to expand...
Click to collapse
hey, i got it the problem seems to be on one site windows10,
on my mac i had to unplug replug the device after reboot before pressing continue
I noticed a mistake.
I fixed and upload again. (giefroot_v3_sgp611_fix1.zip)
Please try new file.
This file fixes both exploit itself and install.sh(for Linux/OS X).
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
kvi said:
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
Click to expand...
Click to collapse
Thanks for confirming
kvi said:
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
Click to expand...
Click to collapse
Thank you for reporting and information!
I added your information to the instruction.
FtF global z3 or z3 tablet?
edited:
I was asking if need to build de ftf firmw using z3 as device or z3 tablet, but It works with z3
Works for me, actually running stock android with root and TA partition restored.
THANKS A MIL!
I do not speak English, I use google translator
Do not know which section you mean, 5 or 12. If I did 5 you see in this picture
http: // oi59.tinypic.com / 2my85qc.jpg
Root with the bootloader intact, that is amazing! Will this also work on the WiFi 4G version? That's the one I have and I don't want to mess it up.
Angelusz said:
Root with the bootloader intact, that is amazing! Will this also work on the WiFi 4G version? That's the one I have and I don't want to mess it up.
Click to expand...
Click to collapse
Just scroll one line up in general forum you have the post for the SGP621 (LTE version) here
enjoy!
Oh, I missed that one, thanks!
Does it void warranty? As the DRM keys and still there and how to do you restore the DRM keys
Copy apps in SDcard.
If you already gained root access, can you copy all apps to SDcard? What apps you guys recommend? Thanks in advance.
Does this method erase all data in internal card?
Has anyone got this working with SGP612 yet? (32gb Wifi only version). I have't seen this mentioned anywhere, but it should be similar to SGP611?
I'm a bit confused at step 12 : first thing to do when following CubicU07 instructions is to follow ... lowtraxx instructions...
If we follow CubicU07 thread, we first have to back up TA, but that was step 11 of this current thread. sso I guess we should follow lowtraxx instructions, but this one specifies that it won't work for SGP611, and sends us to this thread. Back to square one, then.
My guess is that we have to follow CubicU07 thread, no matter what he says first (so, I won't follow lowtraxx instructions).
Could you please be more specific for step 12 ? Do we finally have to use Advanced stock kernel, PRFCreator, SonyRICDefeat, ... as described in CubicU07 thread (which also involves unlocking BL) ?
Thank you.
Where can I get the firmware from step 3?
It's written : install XperiFirm and download it with this software.

[Ascend W1-U00] Huawei SD Upgrade [available!]

Huawei Ascend W1-U00 SD Upgrade
The update method via SD Card. I do not know, maybe this subject already existed.
Found in the software mentioned below. I think this is a good additional function.
How to use this tool, you can read in the article made by a member djtonka.
Available in the software:
-- W1-U00_1030.5614.01000.20900
Launch keys:
hold pressing the keys “volume up” + “camera” and hit the key “power”
Click to expand...
Click to collapse
A similar example:
-- [Ascend W2-U00] ROM flashing + GDR3 ROM's
Have Fun!

DUK-L09C432B182 released

in case someone is interested, i just saw an update in huawei firmware finder: L09C432B182
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full/filelist.xml
but it was not approved
not approved firmwares drives device into NRD test keys
venugopalu007 said:
but it was not approved
not approved firmwares drives device into NRD test keys
Click to expand...
Click to collapse
i don't think so ..
OldDroid said:
i don't think so ..
Click to expand...
Click to collapse
ho thanks for this
Hi guys, I tried downloading the correct firmware (Update) unpacked and placed in the folder created on sd card dload. Then I tried to get into the Upgrade software mode. The phone reboots, seems to update the firmware but shortly afterwards it fails because incorrect firmware appears, and yet it's ok. I do not think it's updating because the firmware is not approved. Has anyone tried it?
nino64 said:
Hi guys, I tried downloading the correct firmware (Update) unpacked and placed in the folder created on sd card dload. Then I tried to get into the Upgrade software mode. The phone reboots, seems to update the firmware but shortly afterwards it fails because incorrect firmware appears, and yet it's ok. I do not think it's updating because the firmware is not approved. Has anyone tried it?
Click to expand...
Click to collapse
as i said before, it runs perfect here, but the update process is kinda complicated :/
changelog?
beltxo said:
changelog?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90810/f2/full/changelog.xml
That's B130 / B132 changelog. Weird. Maybe the changelog info has been not updated yet.
beltxo said:
That's B130 / B132 changelog. Weird. Maybe the changelog info has been not updated yet.
Click to expand...
Click to collapse
see this for full ota http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full/changelog.xml
Same
beltxo said:
Same
Click to expand...
Click to collapse
i think the database have some to update
OldDroid said:
as i said before, it runs perfect here, but the update process is kinda complicated :/
Click to expand...
Click to collapse
Please, explain how to upgrade firmware
ferrarif1 said:
Please, explain how to upgrade firmware
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886
no need to when i already wrote a guide for it ?
OldDroid said:
https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886
no need to when i already wrote a guide for it
Click to expand...
Click to collapse
Thankyou for the reply, you confirm that at the end of the process I have a factory erased locked bootloader phone ?
upgrading Honor 8 pro B310 to B 182
questions:
Do you have to have boot unlocked?
Do you need root y TWRP?
OldDroid said:
https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886
no need to when i already wrote a guide for it
Click to expand...
Click to collapse
nino64 said:
Tutorial
1. download the firmware for your model
2. extract the fw_DUK-<model number>.tar.gz file
3. format your MicroSD as ExFAT (Fat32 is limited to 4gb file transfer size)
4. copy the extracted dload folder in the root directory of your MicroSD
5. shutdown the device, insert the MicroSD and disconnect the USB cable
6. boot device using VOL+, Vol- and POWER and keep this combo pressed until the recovery process starts
7. once finished your device should reboot and be back in a working state
questions:
Do you have to have boot unlocked?
How do you extract the tar.gz file from Upadate?
Do you need TWRP?
Click to expand...
Click to collapse
Part 3 of the tutorial, not part 1
Looks like there's a B183 out there, but still same changelog as B130...
Accumulative changelog from B130 to B182 for Honor V9 (chinese version of 8 Pro)
* Adds the call encryption feature for China Telecom for better security.
* Optimizes prompts to enable Wi-Fi hotspot when Data saver is enabled.
* Integrates Google security patches for improved system security
* Improves system performance and stability for smoother operations.
* Optimizes power consumption for extended use.
* Fixes an issue where your device would occasionally fail to power on.
* Fixes an issue where sliding to answer calls would occasionally not work.
* Optimizes the response speed when viewing WeChat messages using WLAN.
* Enables the feature to add Honor watermarks by default.
* Optimizes touchscreen sensitivity.
* Optimizes GPS performance for more accurate positioning.
beltxo said:
Accumulative changelog from B130 to B182 for Honor V9 (chinese version of 8 Pro)
* Adds the call encryption feature for China Telecom for better security.
* Optimizes prompts to enable Wi-Fi hotspot when Data saver is enabled.
* Integrates Google security patches for improved system security
* Improves system performance and stability for smoother operations.
* Optimizes power consumption for extended use.
* Fixes an issue where your device would occasionally fail to power on.
* Fixes an issue where sliding to answer calls would occasionally not work.
* Optimizes the response speed when viewing WeChat messages using WLAN.
* Enables the feature to add Honor watermarks by default.
* Optimizes touchscreen sensitivity.
* Optimizes GPS performance for more accurate positioning.
Click to expand...
Click to collapse
Waiting for this update in India!

DDR type

In order to flash a full OOS set of partition images you need to know your DDR type so that you can choose the correct XBL* images to flash.
On OOS 11 you can find the phone's DDR type using getprop ro.boot.ddr_type. A result of 0 means DDR4 and 1 means DDR5.
Unfortunately that property is no longer present on OOS 12. But, thanks to @Qnorsten's investigation into the matter, he found the solution by looking through the code of update_engine (the Android code that process updates).
You can find the device's DDR by running cat /proc/devinfo/ddr_type from a terminal session. But you will need root permission to do this.
Here's what it looks like on my phone:
Code:
bgo8t:~ # cat /proc/devinfo/ddr_type
Device version: DDR5
Here is another way to check your ram type if you are unrooted on OOS12.
Your phone saves update_engine logs for your latest updates so you could check these.
here is how to access them without root.
In your dialer type in *#800# this opens the feedback app.
Select Other->Other general issues
Press Start
Press Continue in the window that pop up (restart is not needed)
Press next
Navigate to this folder on your internal storage Android\data\com.oplus.logkit\files\Log\<currentdateandtime>@other\recovery_log\ (replace <currentdateandtime> with the folder name that exist in that folder.
Open this file with a text editor update_engine_log
In this file you can find this if you have ever done a OOS 12 update
update_attempter_android.cc(355)] ddr_type is: Device version: DDR4
update_attempter_android.cc(361)] ddr5 is false
update_attempter_android.cc(553)] the ddr type of dev is ddr4
Qnorsten said:
Here is another way to check your ram type if you are unrooted on OOS12.
Your phone saves update_engine logs for your latest updates so you could check these.
here is how to access them without root.
In your dialer type in *#800# this opens the feedback app.
Select Other->Other general issues
Press Start
Press Continue in the window that pop up (restart is not needed)
Press next
Navigate to this folder on your internal storage Android\data\com.oplus.logkit\files\Log\<currentdateandtime>@other\recovery_log\ (replace <currentdateandtime> with the folder name that exist in that folder.
Open this file with a text editor update_engine_log
In this file you can find this if you have ever done a OOS 12 update
update_attempter_android.cc(355)] ddr_type is: Device version: DDR4
update_attempter_android.cc(361)] ddr5 is false
update_attempter_android.cc(553)] the ddr type of dev is ddr4
Click to expand...
Click to collapse
Unfortunately that doesn't work *EDIT* on my oos12 fw (thanks for the feedback below).
*#800# ends up in an error.
I've posted there how you can succeed in doing this on an unrooted phone with OOS12 firmware:
[FIRMWARE] OnePlus 8T [kebab][DDR0/DDR1][Release Updated!]
Providing the latest firmware updates for OnePlus 8T custom users. OnePlus Flashable Firmware (OnePlus 8T All Models) #include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war...
forum.xda-developers.com
crazyVII said:
Unfortunately that doesn't work as oos12 has restricted / broke / removed factory mode.
*#800# ends up in an error.
I've posted there how you can succeed in doing this on an unrooted phone with OOS12 firmware:
[FIRMWARE] OnePlus 8T [kebab][DDR0/DDR1][Release Updated!]
Providing the latest firmware updates for OnePlus 8T custom users. OnePlus Flashable Firmware (OnePlus 8T All Models) #include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war...
forum.xda-developers.com
Click to expand...
Click to collapse
i saw that post and that is also a good solution if you have an unlocked bootloader.
the *#800# method is working fine on my rooted KB2003 running EU C.33 at least.
*#800# works fine for me on oos-KB2005_11_C.33
Qnorsten said:
i saw that post and that is also a good solution if you have an unlocked bootloader.
the *#800# method is working fine on my rooted KB2003 running EU C.33 at least.
Click to expand...
Click to collapse
Hey there, thanks for the 'correction' and clarification. Googled and tested a lot the last days as this was broken on my phone and found many references telling, that it's broken everywhere.
Good to hear that it's wrong.
Edit>>
wrong post my bad.
Qnorsten said:
Here is another way to check your ram type if you are unrooted on OOS12.
Your phone saves update_engine logs for your latest updates so you could check these.
here is how to access them without root.
In your dialer type in *#800# this opens the feedback app.
Select Other->Other general issues
Press Start
Press Continue in the window that pop up (restart is not needed)
Press next
Navigate to this folder on your internal storage Android\data\com.oplus.logkit\files\Log\<currentdateandtime>@other\recovery_log\ (replace <currentdateandtime> with the folder name that exist in that folder.
Open this file with a text editor update_engine_log
In this file you can find this if you have ever done a OOS 12 update
update_attempter_android.cc(355)] ddr_type is: Device version: DDR4
update_attempter_android.cc(361)] ddr5 is false
update_attempter_android.cc(553)] the ddr type of dev is ddr4
Click to expand...
Click to collapse
Hello
I using your method
But i am confused
It says ddr4
But also saying its partition is xbl_lp5 which is for ddr5 ?
also saying compitabl
Qnorsten said:
Here is another way to check your ram type if you are unrooted on OOS12.
Your phone saves update_engine logs for your latest updates so you could check these.
here is how to access them without root.
In your dialer type in *#800# this opens the feedback app.
Select Other->Other general issues
Press Start
Press Continue in the window that pop up (restart is not needed)
Press next
Navigate to this folder on your internal storage Android\data\com.oplus.logkit\files\Log\<currentdateandtime>@other\recovery_log\ (replace <currentdateandtime> with the folder name that exist in that folder.
Open this file with a text editor update_engine_log
In this file you can find this if you have ever done a OOS 12 update
update_attempter_android.cc(355)] ddr_type is: Device version: DDR4
update_attempter_android.cc(361)] ddr5 is false
update_attempter_android.cc(553)] the ddr type of dev is ddr4
Click to expand...
Click to collapse
Hello
I used your method
It says ddr4
But I am confused about this
It also saying its compatible with ddr5 (see figure)
also saying its partition is xbl_lp5 when its for ddr5 how that
Please tel me
Is the os current is ddr4 but device ram is ddr5 ?
TechForEver said:
Hello
I using your method
But i am confused
It says ddr4
But also saying its partition is xbl_lp5 which is for ddr5 ?
also saying compitabl
Hello
I used your method
It says ddr4
But I am confused about this
It also saying its compatible with ddr5 (see figure)
also saying its partition is xbl_lp5 when its for ddr5 how that
Please tel me
Is the os current is ddr4 but device ram is ddr5 ?
Click to expand...
Click to collapse
Your screen shots clearly show that your device is ddr4: update_attempter_android.cc(355)] ddr_type is: Device version: DDR4.
That's all you need to know.
All the other things you're looking at are details of what actually happens when the Updater runs, which includes how it processes the *_lp5 image files in the update (it will skip them as you're DDR4).
BillGoss said:
Your screen shots clearly show that your device is ddr4: update_attempter_android.cc(355)] ddr_type is: Device version: DDR4.
That's all you need to know.
All the other things you're looking at are details of what actually happens when the Updater runs, which includes how it processes the *_lp5 image files in the update (it will skip them as you're DDR4).
Click to expand...
Click to collapse
Thanks
But why most if app which i used saying its DDR5
TechForEver said:
Thanks
But why most if app which i used saying its DDR5
Click to expand...
Click to collapse
Those apps are working off spec sheets for the device. They aren't reading the actual device configuration.

Categories

Resources