Related
Hi guys.
I've got a China-bought Galaxy Tab S (T705C). The current ROM doesn't allow Google Services. Hence, no Gmail, no Google Play store on my Tab.
Can anyone throw me a bone here?
Where do I begin with installing European firmware for the Tab?
1. Do I need to root the device?
2. Do I have to install Cyanogenmod / some other firware loader?
3. Will LTE firmware work on this model? (It's 4G)
Thanks
For reference, would this ROM be correct for the 8.4" Tab ?
http://forum.xda-developers.com/galaxy-tab-s/development/firmware-galaxy-tab-8-4-lte-t2837428
Galaxy Tab S 8.4 (LTE) SelambA ROM NH1 V1.2.1 20140921
emfields said:
Hi guys.
I've got a China-bought Galaxy Tab S (T705C). The current ROM doesn't allow Google Services. Hence, no Gmail, no Google Play store on my Tab.
Can anyone throw me a bone here?
Where do I begin with installing European firmware for the Tab?
1. Do I need to root the device?
2. Do I have to install Cyanogenmod / some other firware loader?
3. Will LTE firmware work on this model? (It's 4G)
Thanks
Click to expand...
Click to collapse
1)yes. http://androidxda.com/root-samsung-galaxy-tab-s-8-4-sm-t705c
2) you need a recovery ( TWRP) to install Rom zip file.
3) If the HW is the same I would assume yes. Does support main LTE frequencies
4) yes, Selamba Rom is correct
:good: Dude, you're my hero.
I'll give it a try.
emfields said:
:good: Dude, you're my hero.
I'll give it a try.
Click to expand...
Click to collapse
I have the exact same problem, very curious if you are able to solve the issue and how.
Partial progress - Update 11/26
dqs23 said:
I have the exact same problem, very curious if you are able to solve the issue and how.
Click to expand...
Click to collapse
dqs23: If it will be of help to you - here's where I've gotten so far:
My understanding, to this point, is:
1. I need to install a European ROM to use Google services, and Google Play store on the Tab S.
2. I think that the SM-T705C is the same as the T705, just from China. So, I assume that this ROM (French-based) should work:
3. I'll need a tool such as Odin or Heimdall to install a Root program.
Recommended in the above link is this one: CF-Autoroot
4. Upon flashing CF-Autoroot, I'll then be able to install a ROM manager such as TWRP, from whence I can backup and install the custom ROM.
Where I'm currently hung:
I'm using an Ubuntu 14.04 machine, which can't run Odin.
I don't have a Windows machine, or access to one conveniently.
There's a Java based version called JOdin, which I've used, but it hangs at "Cannot extract PIT file."
Using Heimdall alone, I have the same problem - Cannot retrieve PIT file. (Which I presume is necessary to proceed with flashing the Root package. So, it's apparently an Ubuntu/Heimdall issue, perhaps with this particular device.
I understand it's possible to get PIT files from other means, but I'm a bit out of my depth, and don't want to f*$# things up. So, at this point, I'll probably wait and try to get a Windows machine going, and test from there.
Please kindly add any additional information you find here to this thread.
Thanks for the update emfield.
As this is the first time I'm doing a root everything is very new to me. Luckily I have an expert nearby to consult with on the basics.
What I've done so far is rooted the tablet with cf-autoroot but after installed gapps manager I was unable to download the proper gapps (4.4.1-2) as it gave me download unsuccessful error every time.
I guess what I'm looking for is some kind of confirmation from others how they were able to flash it to a EU rom and the steps they followed.
emfields said:
Hi guys.
I've got a China-bought Galaxy Tab S (T705C). The current ROM doesn't allow Google Services. Hence, no Gmail, no Google Play store on my Tab.
Can anyone throw me a bone here?
Where do I begin with installing European firmware for the Tab?
1. Do I need to root the device?
2. Do I have to install Cyanogenmod / some other firware loader?
3. Will LTE firmware work on this model? (It's 4G)
Thanks
Click to expand...
Click to collapse
That will not likely happen as China locks everything down, as that product is actually manufactured in China, it will be fully compliant with whatever regulations exist for those products. I got around some of it by extracting the Chinese Odin image and the HongKong image, then I took the Hong Kong Cache.img and placed it in the new Chinese image.
Doing that allowed me to change the csc to whatever country I wanted, in this case Hong Kong, I was then able to get my news and other things in English.
Use 7Zip to create your new tar image, since it is not signed by Samsung you will trip the Knox flag, you will need to root your phone in order to flash GAPPS. The key parts of the firmware are blocked by the Chinese bootloader so rooting is absolutely required.
lorinkundert said:
That will not likely happen as China locks everything down, as that product is actually manufactured in China, it will be fully compliant with whatever regulations exist for those products.
Click to expand...
Click to collapse
Hey Lorin, please let me go back a step with your response:
1) By "That will not likely happen", do you mean it's not possible to root and install a different ROM?
I've found a European-based ROM, based off the stock Samsung 4.4 firmware, which is for the SM-T705. (It's here.)
Are you saying that's not possible / not going to work?
lorinkundert said:
I got around some of it by extracting the Chinese Odin image and the HongKong image, then I took the Hong Kong Cache.img and placed it in the new Chinese image.
Click to expand...
Click to collapse
2. Sounds interesting. Can you clarify slightly about the "Odin image"? Is that an image of the firmware? (Same thing as a stock ROM?) And where did you get a HK Rom?
Thanks!
emfields said:
Hey Lorin, please let me go back a step with your response:
1) By "That will not likely happen", do you mean it's not possible to root and install a different ROM?
I've found a European-based ROM, based off the stock Samsung 4.4 firmware, which is for the SM-T705. (It's here.)
Are you saying that's not possible / not going to work?
2. Sounds interesting. Can you clarify slightly about the "Odin image"? Is that an image of the firmware? (Same thing as a stock ROM?) And where did you get a HK Rom?
Thanks!
Click to expand...
Click to collapse
Sammobile.com has all the ROMs, I just downloaded the Chinese and Hong Kong Versions and replaced cache.img in the Chinese ROM with the HK version, that should work using a cache.img from Europe. Odin will work with a tar image without the md5 extension. If using Window, 7Zip will create a tar file
If you attempt to flash any other ROM on a Chinese ROM ex. T705C, T805C Odin will fail and knox will be tripped, you can flash a custom ROM but you will lose the radio, no LTE, 3G or 2G
105
lorinkundert said:
Sammobile.com has all the ROMs, I just downloaded the Chinese and Hong Kong Versions and replaced cache.img in the Chinese ROM with the HK version, that should work using a cache.img from Europe. Odin will work with a tar image without the md5 extension. If using Window, 7Zip will create a tar file
If you attempt to flash any other ROM on a Chinese ROM ex. T705C, T805C Odin will fail and knox will be tripped, you can flash a custom ROM but you will lose the radio, no LTE, 3G or 2G
Click to expand...
Click to collapse
I see.
Were you able to download a PIT file for the T705C? Linux user here, using Heimdall. On Mac and Linux, we're unable to extract a PIT file from these devices.
2. Regarding "Odin will fail on flashing a non-chinese ROM" - So, supposing I am able to root and install TWRP or CWM Rom Manager, even then, flashing a mostly-stock ROM based on the European stock T705, it's definitively going to lose 3G/LTE ?
Thanks
Status update:
Got device rooted ( used Odin 3.07 in Virtualbox)
Got Busybox installed
Got TWRP Backup *app* installed - not yet been able to install backup Recovery menu.
Where I'm currently at:
Trying to get TWRP recovery working, to make a backup of my current stock ROM.
Problem: Rebooting into recovery menu does NOT yield any menu options for backup/recovery. It seems to be the stock Android 4.4 recovery menu: NO ability to create a backup. (That I can find.)
Anybody got some idea what to do here?
emfields said:
I see.
Were you able to download a PIT file for the T705C? Linux user here, using Heimdall. On Mac and Linux, we're unable to extract a PIT file from these devices.
2. Regarding "Odin will fail on flashing a non-chinese ROM" - So, supposing I am able to root and install TWRP or CWM Rom Manager, even then, flashing a mostly-stock ROM based on the European stock T705, it's definitively going to lose 3G/LTE ?
Thanks
Click to expand...
Click to collapse
Even changing the kernel broke LTE and 3G on mine
Succes!
Thank you very much for the post! I had the same problem.
Before using the ROM you indicated in your post: (pibach's one)
1.I used Odin to root my device.
2.I downloaded the tar file of the TWRP (for this device )
3.Installed the TWRP using Odin
4.Copied the ROM onto device(I didn't use a SD card)
5.I downloaded ROM manager app
and installed it onto the device and used it to reboot in recovery mode(using Reboot into Recovery)
6. In the recovery mode I went to Install and found the zip with the ROM and installed it without any problems
When the system started I was unhappy because there were the same Icons from the Chinese software . But when I opened the menu Play Store was there :good::fingers-crossed:
lorinkundert said:
That will not likely happen as China locks everything down, as that product is actually manufactured in China, it will be fully compliant with whatever regulations exist for those products. I got around some of it by extracting the Chinese Odin image and the HongKong image, then I took the Hong Kong Cache.img and placed it in the new Chinese image.
Doing that allowed me to change the csc to whatever country I wanted, in this case Hong Kong, I was then able to get my news and other things in English.
Use 7Zip to create your new tar image, since it is not signed by Samsung you will trip the Knox flag, you will need to root your phone in order to flash GAPPS. The key parts of the firmware are blocked by the Chinese bootloader so rooting is absolutely required.
Click to expand...
Click to collapse
OK so hopefully nobody had already read my post but none of this was necessary for me as I am still living in China (therefore there's no need to worry about messing up the radio). All that was necessary was to download the "App Search" application that is popular here in China and then search for "Google Play" Store which was still in the mainland China database. In order to set up the account the rest of the way, I used my VPN to connect to the Google network and voila!
The reason it seems tricky at first is because the government blocks a lot of services that are not China-based from reaching China and it also blocks China-based services from going leaving China. So a VPN is an absolute must for using Google...but to find Google apps is a piece of cake.
But if you intend to take the tablet outside of Asia then rooting is most likely still necessary if you want to use LTE/3G.
New to Android
I am in the USA. USA Tablets do not have LTE phones as the carriers want you to buy expensive data packages.
the way around this is to buy the SM-T705C which has the correct transceiver radio in it.
I am savvy when it comes to any windows problem. Recently replaced old X7001 Windows phone with a SM-T705C. S V4.4.2 Kit kat till learning Android
Carrier AT&T 4G LTE
Specs for my own phone
Model: Samsung SM-T705C
Android Version: 4.4.2 (KIit Kat)
Baseband Version: T705CZCU1AOC1
Kernal Version: 3.4.39-4367879
[email protected]#1
Wed March 4 13 40:11 KST 2015
Build Number KOT49H. T705CZCU1AOC1
Se FOR Android Status: Enforcing
SEPF_SM-T705C_4.4.2_0042
WED March 04 13:56:37 2015
Hardware Version MP 0.300
I have read this thread and it seems the best place I have found so far concerning rooting a SM-T705C international version.
I have to date gotten the SM-T705C to mostly speak English. I still get the weather in Chinese and have a few Chinese icons.
I have activated the developers options (Easter Egg)
Downloaded and installed in Win 7
Several android Emulators
Kies3
Downloaded Only: CF Auto root, Odin, Owners manuals in Chinese. Specifications for LTE version
Current Problems:
1. I can not get any Windows 7 or Win 8.1 machine to recognize the SM-T705C at all using the stock USB cable. , Need Help. I need to be able to access & transfer files.
2. Screen shuts off even when connected to USB cable. All I can do is control the delay. Very annoying
My goal is to unlock and then root the phone so that I can dual boot the original OS and any other Android OS.
Some terms I am unfamiliar with:
What is:
TWRP ?
Gapps Manager
Cyanogenmod
What is a Knox Flag ? I understand what it does but Is it hardware or software ?
Please help
MRGCAV @ gmail.com
lol
lorinkundert said:
Sammobile.com has all the ROMs, I just downloaded the Chinese and Hong Kong Versions and replaced cache.img in the Chinese ROM with the HK version, that should work using a cache.img from Europe. Odin will work with a tar image without the md5 extension. If using Window, 7Zip will create a tar file
If you attempt to flash any other ROM on a Chinese ROM ex. T705C, T805C Odin will fail and knox will be tripped, you can flash a custom ROM but you will lose the radio, no LTE, 3G or 2G
Click to expand...
Click to collapse
i need the t805C chinese stock rom to fix my 'baseband unknown' and no 4g/LTe/signal issue.
please??
Doesn't the Hong Kong firmware work on the Chinese version?
Hi
I have the same problem, i want to change to european rom, but can´t, nobody succes?
Thanks
Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?
jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion
I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app
freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.
Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.
Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?
I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't
Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?
Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image
Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!
So this will work for european users who did not break their persist?
Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know
Battery performance is for fully happy and satisfied OVERWHELMING
will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat
will it work for indian version XT1686
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...
I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks
I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough
No risk no Win buddies
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie
LG Joan H930DS OPEN ESA IND 20f 0517 ROM including new OP partition offering airtel VoLTE
Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP. It should be installed only when coming from a previous full original (kdz or flashable fw zip, possibly rooted) firmware for H930DS Plus.
This zip is created from the original KDZ (IND H930DS20F_00_OPEN_ESA_DS_OP_0517.kdz, this time resulting in the correct version number, because OP partition is included, which at the same time gives you VoLTE functionality for airtel. It contains almost the complete 20f firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
New version of OP partition included, pls see above
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already)[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
The TWRP flashable zip file (MD5: visible on AFH, it's correct)
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20f firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20f zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Just give a thanks if you like the zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Am i the first one?:victory:
looks like you want to test? looks like too i send you the link
seadersn said:
looks like you want to test? looks like too i send you the link
Click to expand...
Click to collapse
Sure,but I have a question,can I flash other stock zips like V300l into my ls998?
this info needs to be given by another person, don't know this. i don't even know 100% if you can flash this one on your phone if it's not h930ds plus. am h930 eu open user :good:
better do not flash until you know if this works as this zip doesn't contain only system and boot, but bootloader, modem and other stuff too. not that you end up with a non working phone!
seadersn said:
this info needs to be given by another person, don't know this. i don't even know 100% if you can flash this one on your phone if it's not h930ds plus. am h930 eu open user :good:
better do not flash until you know if this works as this zip doesn't contain only system and boot, but bootloader, modem and other stuff too. not that you end up with a non working phone!
Click to expand...
Click to collapse
Ok,thanks
link.added, testing done
Libart said:
Sure,but I have a question,can I flash other stock zips like V300l into my ls998?
Click to expand...
Click to collapse
No. These "stock" zips are for people who have TWRP and want to update to newer stock firmware very easily. These are not conventional ROMs that any variant can flash. They are merely TWRP flashable versions of full image KDZ. If you live in India/Philippines/Indonesia and have an H930DS this "EAS" region firmware is for you. For instance it would (should) give you India Jio VoLTE with a Jio SIM card and is currently the newest firmware available for that region.
This "ROM" (really TWRP flashable KDZ) is probably compatible with Europe H930 phones as some have flashed other H930DS firmware onto H930 -- but they have slight bugs like showing phantom 2nd SIM card. However someone flashing this "ROM" over H930 should have very good reason for doing so, not just for fun.
But for you specifically, I wouldn't flash LS998 to any other variant other than North America, and even then you can't flash T-mobile H932. Do you have a reason you want V300l firmware?
thanks for these flashable versions, really helps a lot
I'm assuming this is for any V30+?
I've flashed this one for h930 before and it worked.
dave_id said:
thanks for these flashable versions, really helps a lot
I'm assuming this is for any V30+?
I've flashed this one for h930 before and it worked.
Click to expand...
Click to collapse
Theoretically, yes. But if you have specific carrier needs (like India does) having your specific region/country firmware helps. This was for the region (ESA) that includes India.
However, if you flashed H930 then this should also be OK for you...
ChazzMatt said:
No. These "stock" zips are for people who have TWRP and want to update to newer stock firmware very easily. These are not conventional ROMs that any variant can flash. They are merely TWRP flashable versions of full image KDZ. If you live in India/Philippines/Indonesia and have an H930DS this "EAS" region firmware is for you. For instance it would (should) give you India Jio VoLTE with a Jio SIM card and is currently the newest firmware available for that region.
This "ROM" (really TWRP flashable KDZ) is probably compatible with Europe H930 phones as some have flashed other H930DS firmware onto H930 -- but they have slight bugs like showing phantom 2nd SIM card. However someone flashing this "ROM" over H930 should have very good reason for doing so, not just for fun.
But for you specifically, I wouldn't flash LS998 to any other variant other than North America, and even then you can't flash T-mobile H932. Do you have a reason you want V300l firmware?
Click to expand...
Click to collapse
Because I think ls998 is lacks of some LG's applications such as LGmessage and I'm living without computer, but this is a small problem so you just ignore it
Libart said:
Because I think ls998 is lacks of some LG's applications such as LGmessage and I'm living without computer, but this is a small problem so you just ignore it
Click to expand...
Click to collapse
Then convert your Sprint LS98 to US998 via Frankenstein or some other carrier unlocked North American variant. You should NOT be flashing Sprint LS998 to any firmware outside of North America, especially a dual SIM H930DS firmware.
k, updated the op, new links available, and added a firmware only zip (with system and boot excluded, OP included for both zips).
Dirty flashed from v20b (v30+, hd930ds, Philippines) using the latest TWRP from the TWRP thread. Everything is working quite well. Also flashed updated driver from https://forum.xda-developers.com/lg...no-540-gpu-update-boost-gaming-t3844132/page3 and xposed if anyone is interested.
Will report if I encounter any bugs as I just flashed it literally jist about 10 mins ago lol.
Thanks so much OP. Would have been stuck at v20b if it weren't for this! Kind of uncomfortable using KDZs.
Edit:
Wait... It still shows up as v20b (see attachment - is that normal?)? I thought this is v20c? I'm confused... :silly:
Checked the downloaded zip and it's the correct one... On the other hand, checking the update center shows i have the latest software (asked me to update before flashing).
the build.prop thingy already caused me headaches, we don't know why it shows 20a, 10b or even 21c for different persons who installed this rom. security patch is the most recent available, so this rom installed succesfully, but the version numbering is a mysery in build.prop of this software is written 21c for example. it looks like it depends on the firmware version from which it was upgraded to this rom version. and it looks like there's something inside system which keeps the actual version numbering.
guess: maybe the system is configured in a way to use the before used version number because nothing else but security patch changed and the kdz creating ppl thought "hey, nothing beside security changed, no reason for a new version lettering, let's stay at the actual version number, no reason to raise it." i don't know but it works
seadersn said:
the build.prop thingy already caused me headaches, we don't know why it shows 20a, 10b or even 21c for different persons who installed this rom. security patch is the most recent available, so this rom installed succesfully, but the version numbering is a mysery in build.prop of this software is written 21c for example. it looks like it depends on the firmware version from which it was upgraded to this rom version. and it looks like there's something inside system which keeps the actual version numbering.
guess: maybe the system is configured in a way to use the before used version number because nothing else but security patch changed and the kdz creating ppl thought "hey, nothing beside security changed, no reason for a new version lettering, let's stay at the actual version number, no reason to raise it." i don't know but it works
Click to expand...
Click to collapse
Ok. Great.
I was just worried I made a mistake or something. I haven't experienced any issues so I'm happy with it.
(you also mentioned to give feedback about what version appears so I thought there was something I wasn't aware of). Thanks again! You made updating so much easier for me. :good:
FOR INDIA USERS
[email protected] said:
i just tried jio volte on my phone and it works
i flashed 21w eur firmware.... And jio works....to my surprise...i have attached few screenshots as proof.
Screenshot 1- you can see the jan security patch....
Screenshot 2- new aod features..for reference
Click to expand...
Click to collapse
chazzmatt said:
wow!
Lg must have added india jio volte to h930 eu firmware.
This also means you can have the dts 3d stereo, if you have root:
FULLY ENABLE DTS 3D STEREO (root needed)
https://forum.xda-developers.com/lg-v30/how-to/enable-dts-3d-stereo-lg-v30-variants-t3887139
Click to expand...
Click to collapse
chazzmatt said:
JIO VOLTE is supported on ESA region (India) H930DS firmware. The problem is you had to use ESA region, you couldn't use any other H939DS firmware or H930 ER firmware, if you wanted JIO VOLTE -- even though they were compatible in every other way. Jio users can't drop down to HSPA like other carriers -- they only have LTE.
Now apparently H930 firmware does support JIO VOLTE and also has the new DTS 3D framework. plus H930 firmware still gives H930DS dual sim card capability, and keeps the H930DS bands.
This is very big news.
And there's also H930 TWRP flashable zip for those who have TWRP... Thanks to @seadersn.
Click to expand...
Click to collapse
[email protected] said:
yes ....i am using dts surround sound too....
Click to expand...
Click to collapse
This won't show as "21W" for India users but WILL show current security patch, be updated firmware internally, and have DTS libs.
https://androidfilehost.com/?fid=1395089523397929907
20E fw zip with dts-x activated available updating first post soon :good: (edit: updated)
seadersn said:
https://androidfilehost.com/?fid=1395089523397929907
20E fw zip with dts-x activated available updating first post soon :good: (edit: updated)
Click to expand...
Click to collapse
tech_infinity said:
Here's a screenshot.
Click to expand...
Click to collapse
@tech_infinity confirms ESA 20e has February 2019 security patch. I knew with 0213 (February 13) build date, it would at least be January security patch but possibly February. It's February.
ChazzMatt said:
@tech_infinity confirms ESA 20e has February 2019 security patch. I knew with 0213 (February 13) build date, it would at least be January security patch but possibly February. It's February.
Click to expand...
Click to collapse
Dts activated???? So no need of root???????
Good afternoon.
I have moto g5s version xt1799-2 (version for the Chinese market) for stupidity, I installed Oreo from the European version of the device.
As a result, I upgraded the loader version to 12. On the phone from the factory is Android 7.1 ZUI, I wanted to go back to ZUI I did it just did not work mobile communication.
Using the files adspso. bin, NON-HLOS. bin, fsg. mbn from Oreo and the restore folder owners command, I was able to start mobile communication on the phone, But there was a problem the fingerprint stopped working (I can't downgrade the modem version).
Help me solve the problem...
Did you try flashing the phone with the China market based rom?
I can't find any, try searching for one, of one other option is to restore and use the universal stock rom, or use the stock rom in which fingerprint works, and then unlock is bootloader and install TWRP and then flash Lineage OS or the custom rom or your choice...