Related
HI THERE!
I HAVE A HUAWEI GX8 UNLOCKED US VERSION RIO-L03 (RIO-L23)
I HAD BEFORE C567B141 ANDROID 5.1.1: download-c1.huawei.com/download/downloadCenter?downloadId=75372&siteCode=us
I'M FROM ARGENTINA , AND I NOTICED THAT THERE WAS A MM UPDATE, consumer.huawei.com/gt/support/downloads/detail/index.htm?id=86543 FOR RIO-L03, LATIN AMERICA AND DUAL SIM.
I INSTALLED THAT CORRECTLY , USING LOCAL UPDATE METHOD. (MY VERY WORST MISTAKE)
AFTER THE INSTALATION SUCCESS, I HAD NO SIGNAL, IVE TRIED EVERYTHING BUT EVERYTHING WAS THE SAME. I NOTICED AFTER THAT I HAVE ONLY 1 IMEI. SO I THINK THE HUAWEI STAFF UPLOADED THIS FIRMWARE WRONG AND WAS FOR SINGLE SIM , LIKE RIO-L01 I DONT KNOW.
AFTER THAT I HAD NO CHOICE BUT DOING A DOWNGRADE, UNFORTUNALLY THERES NO ROLLBACK PACKAGE FOR MY PHONE. SO I UNLOCKED THE BOOTLOADER FINE AND DOWNGRADE USING ADB (FASTBOOT FLASH CUST CUST.IMG (WITH ERROR) , FASTBOOT FLASH BOOT BOOT.IMG , FASTBOOT FLASH RECOVERY RECOVERY.IMG, AND SYSTEM) NOW IT WORKS FINE BUT I HAVE NO FINGERPRINT, EVEN IT ISNT ON THE SETTINGS MENU. I VE TRIED EVERYTHING, ROOTED IT AND TRIED TO ERASE CUST FOLDER AND FLASH THE 5.1.1 CUST, WITH ERROR, FLASH USING ADB AGAIN, NO RESULT , MODIFING THE CUST FOLDER, NO SUCCESS . TRIED TO FLASH AGAIN USING 3 BUTTONS, NO SUCCESS, EVEN LOCAL UPDATE OR ENGINEERING MENU . (SO NOW I HAVE THE RIO-L03C567B141 BUT WITH CUST / OEMINFO ERROR, AND NO FINGERPRINT)
I READ IN FORUM SOMETHING ABOUT OEMINFO, BUT I DONT KNOW WHAT SHALL I DO.
IN PROJECT MENU , VENEER INFORMATIONS, VERSION INFO IT SAYS: CUST VERSION : CVERSION: CUST, DVERSION: CUST (THIS IS SURE MY PROBLEM)
IN NETWORK INFORMATION QUERY , VENDOR COUNTRY INFO IT SAYS: VENDOR : HW, COUNTRY : USA (THIS IS OK, I THINK)
IN CUST FOLDER, HW, IS A FOLDER NAMED LA (THIS WERE SURE INSTALLED WITH THE LATIN AMERICA MM ROM), BUT THERE MUST SAY USA, NOT LA.
PLEASE I NEED YOUR HELP PEOPLE, I JUST WANNA HAVE 5.1.1 WITH THE FULL ROM INSTALLED CORRECTLY , USING ANY METHOD, BUT I CANT BECAUSE OF THE CUST OR OEM INFO, I DONT KNOW.
ANY HELP WILL BE APRECIATED . I JUST DONT KNOW WHAT ELSE TO DO
THANKS AND HAVE A NICE DAY.
First, use lowercase...
I think you should install android 6 stock, and install TWRP for nougat and use a custom rom in nougat. There is a lot of rom available for Huawei Gx8
Thx for replying, but which mm stock ROM shall i use? I need a gx8 real dual sim MM rom
Hi, check the thread fromf surdu_petru, there is something about no fingerprint and, i think, its solved flashing the modem from your 5.1 rom.
I dont know, maybe it can help you
Ive also tried that
So I was on Oreo and accidentally flashed back to 7.1.
Didn't brick it but now it doesn't recognize my sim even after flashing back to Oreo.
I tried to fastboot the tmo baseband but no luck there.
Anyone run across this or have any suggestions?
That was one of the 1st thing I ran across in the Oreo update thread. With development just really getting fired up I'll be surprised if you find a fix. If. I was you I would flash the mod that hides the unlocked bootloader warning and take it to TMobile. It's only a 5 dollor charge for defective devices. I've returned a total brick before.
So I am on the same board. The problem is I'm in UK and I cant claim warranty repair. Also my warranty was void in December soon when I generated bootloader unlock key.
SO what have I tried so far?
Hard brick bootloader to state when it is Qualcomm loader- only blank flash and Oreo Flash All is able to bring it back to live.
Ive also tried boot from B slot in twrp but it looks like my B partition is messed up. Fastboot will show red warning about no flashable A/B slot and only oreo flash can get it back to boot because it will oem lock itself.
When I get back fully on unlocked bootloader to 7.1.1 I cant update via adb sideload or update menu in settings. Both will fail.
Sim looks like it is detected on start but when taken out and slided back in it wont show up.
I have QCN area backed up with nv data but it wont help me.
Please note when boot is bricked oreo flash all will flash it on locked bootloader and will not show warning screen at all about botloader. However I was unable to boot to recovery from that point so I had to unlock it and flash 7.1.1 then oreo again.
So if someone could do nandroid backup of clear not set up rom it would be great. I can try restore it. I dont even know if twrp is able to do backup on A/B device.
Also if someone could read NV data from phone and share it ( from phone with working radio of course) would be really appreciated.
Can someone PM me NV backup? I need urgently qcn file. I think my hw partition is messed up. Please don't share it in this post as it can contain IMEI.
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
byt3b0mb said:
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
Click to expand...
Click to collapse
Sorry but warning isn't clear. I did not enjoy Oreo and was looking for unlock method.
Also bootloader match to my current Oreo rom and radio but still no sim detected so I think it is hw partition messed up. When I flash retail Oreo on it bootloader just change itself to retail Oreo version. Still no sim.
Device is useable as paperweight with WiFi
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Everything about the phone works 100% except the Sim slot. It's like it can't read the Sim. It knows there is a sim in, but it can't access it.
On Oreo oem retail version.
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
robdevil said:
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
Click to expand...
Click to collapse
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Kaesberg said:
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Click to expand...
Click to collapse
pm sent. i could use this
Please let us know if it works
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
breakerfall said:
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
Click to expand...
Click to collapse
Where did you get this modem?
mattlowry said:
Where did you get this modem?
Click to expand...
Click to collapse
from the tmo oreo zip here (bottom of the OP):
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
it's the NON-HLOS file
this is the retail oreo:
https://forum.xda-developers.com/showpost.php?p=75250794&postcount=82
I swapped the NONHLOS file from the tmo oreo into the retail oreo and I currently have working tmo service/SIM on the retail (tmo-less) oreo
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
My Moto Z Play is bricked, after downgrade of oreo to nougat, my imei not work. so i decided go to oreo again, when i reboot my phone bricked. help me please!!!
Try this. Updated my Sprint only thread to be a little more universal.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
bricked moto z2 force tmobile
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
--- QUALCOMM ONLY ---
Motorola Moto E (4th Gen) SPerry xt1766
Stock Android 7.1.1 Factory Firmware
Build No. NCQS26.69-64-10
Blur_Version.26.231.8.sperry_sprint.sprint.en.US
Restoration & Firmware Flashing Guide
WARNING: by proceeding further, you are assuming full responsibility for the integrity and operability of your device. Although this firmware package has been fully tested on my own device, I am not responsible in the event something goes wrong. Follow the comprehensive instructions and things should go smoothly and without incident.
Thanks & Credit:
Once again, I owe credit and give an abundance of thanks to XDA member @ALI12 for so graciously providing this needed firmware package. His RSD Lite firmware thread for this build is here https://forum.xda-developers.com/mo...tock-rom-moto-e4-sprint-ncqs26-69-64-t3852464
I would respectfully ask any members who use this firmware to thank @ALI12 on the above thread.
CHANGELOG:
This firmware update brings standard bug fixes and stability improvements, as well as security patches up to September 1, 2018. Please note that the radio firmware (baseband version) was not updated from the previous firmware build, and remains at version M8920_15000.280.06.58.05R. However, the radio firmware did receive some minor patches to improve cellular data handover whenever a WiFi connection loses internet access or becomes unstable. Patches were also added to update the PRL databases.
SPECIFICATIONS:
Device Name: Motorola Moto E (4th Gen)
Compatibility: xt1766 SPerry (Qualcomm)
Provider(s): Sprint, Boost Mobile, Virgin Mobile
Android Version: 7.1.1 Nougat
Build No. NCQS26.69-64-10
System Version: 26.231.8.sperry_sprint.en.US
Bootloader Version: moto-msm8920-BB.32
Radio Version: M8920_15000.280.06.58.05R
Kernel Version: 3.18.31-perf
FSG Version: FSG-8953-11.22
Build Date: August 28, 2018
Security Patch Level: September 1, 2018
Package Size: 1.55 GB
APPLICABILITY:
Flashing this firmware package via the instructions below will restore your device to the default stock factory configuration. Also, your device will be up to date with the latest firmware version. All files, media, etc., stored on your device will be erased, so please make a suitable backup of anything important prior to proceeding. Flashing this package will enable dm-verity (device mapping), force encryption of the /userdata partition, and will remove any modifications such as root binaries, BusyBox, Xposed Framework, etc. Also, if you have a custom recovery installed, such as TWRP, it will be replaced with the stock recovery. Upon reboot, your device will be fully capable of installing any future OTA update packages as well.
INSTRUCTIONS:
This guide assumes that you already have the most current version of Minimal ADB and Fastboot utilities installed on your PC or laptop, as well as the most current version of Motorola Device Manager (to ensure current USB device drivers are installed on your PC/laptop). It is also assumed that you have at least a rudimentary understanding of AP Fastboot Mode and executing fastboot commands. While this package may be installed using alternative methods such as mFastboot or RSD-Lite, this guide focuses on a standard fastboot command set. Also, it should be noted that I have only tested this package on a device with the bootloader in an unlocked state. While, in theory, a factory firmware package should flash to a device with a locked bootloader, I have not confirmed on this package.
NOTE: Flashing this firmware package to an OEM unlocked device does not re-lock the bootloader. Also, contrary to popular belief, your bootloader does not need to be in a locked state in order to install an OTA update package. The state of the bootloader has no significance with respect to OTAs. As long as your device has been flashed/restored with a factory firmware package -- such as this one -- OTA updates will install properly.
1. Download the firmware package from the below link and extract the contents of the archive to your ADB/Fastboot directory on your PC;
2. Power off your device, then hold the Power + Volume Down buttons simultaneously for 7 - 8 seconds until AP Fastboot Mode appears on your device display;
3. Connect your device and PC using the OEM supplied, or quality equivalent, micro USB to USB charge/sync cable;
4. Open a command prompt window in the path of your ADB/Fastboot directory. Execute the following command:
fastboot devices
If properly connected, your command prompt window will return an alphanumeric string synonomous with your device serial number;
5. Once a proper connection has been confirmed, execute the following commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Reboot your device by executing:
fastboot reboot
Upon reboot, your xt1766 should now be restored to stock factory condition and running on the latest firmware build version.
DOWNLOAD LINKS:
Android 7.1.1 -- NCQS26.69-64-10: https://drive.google.com/file/d/1H5V6ZUHWhSrBn1_8pHq8_qrwiXYga2YC/view?usp=drivesdk
PREVIOUS FIRMWARE BUILDS:
Android 7.1.1 -- NCQS26.69-64-8:
https://drive.google.com/file/d/1CG9Bb2csn2dWLy1jfP0yimhVpMq-NDub/view?usp=drivesdk
Android 7.1.1 -- NCQS26.69-64-5:
https://drive.google.com/file/d/1ZoACEF5-lruTu4yhGknKjUqdXxGTf7kQ/view?usp=drivesdk
The people with this phone unlocked gsm using it in other country or not using Sprint just don't upgrade the phone never ever stay with the original firmware that comes by default with the phone because the new versions of the stock firmware don't let you add or edit the Apn's or even use Hotspot , the version of stock that let you edit apn is ncq26.69-48 people should know this already that's why there are so many people bricking their phones trying to downgrade i already owned 2 Moto e4 and never had problems with default stock rom I just disable Motorola Update Service App and never get bother again with system updates for other people this post is useful don't know who but it is I don't recommend upgrading. Thanks.
ozmage said:
The people with this phone unlocked gsm using it in other country or not using Sprint just don't upgrade the phone never ever stay with the original firmware that comes by default with the phone because the new versions of the stock firmware don't let you add or edit the Apn's or even use Hotspot , the version of stock that let you edit apn is ncq26.69-48 people should know this already that's why there are so many people bricking their phones trying to downgrade i already owned 2 Moto e4 and never had problems with default stock rom I just disable Motorola Update Service App and never get bother again with system updates for other people this post is useful don't know who but it is I don't recommend upgrading. Thanks.
Click to expand...
Click to collapse
Downgrading is typically never an issue unless sensitive bootloader partitions are downgraded or attempted to be downgraded. But this is nothing new. Motorola Mobility has included downgrading safeguards on most of their smartphones since at least 2013. Unfortunately, however, Motorola does not routinely release QPST blankflash files so that users can repair hard bricked devices.
As far as upgrading, I am running the most current version of firmware (NCQS26.69-64-5) and have no problem switching to a custom ROM for use with any GSM network. I'm actually using AT&T on my xt1766 Moto E4 right now.
MotoJunkie01 said:
Downgrading is typically never an issue unless sensitive bootloader partitions are downgraded or attempted to be downgraded. But this is nothing new. Motorola Mobility has included downgrading safeguards on most of their smartphones since at least 2013. Unfortunately, however, Motorola does not routinely release QPST blankflash files so that users can repair hard bricked devices.
As far as upgrading, I am running the most current version of firmware (NCQS26.69-64-5) and have no problem switching to a custom ROM for use with any GSM network. I'm actually using AT&T on my xt1766 Moto E4 right now.
Click to expand...
Click to collapse
And Can The Apn Area Can be edited and Add or Delete new apn settings >? and Use The hotspot ? a lot of people has this problem including me with my other E4 and i had to downgrade
---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------
i can use my moto with stock firmware on any gsm network here in my country without use custom roms.
ozmage said:
And Can The Apn Area Can be edited and Add or Delete new apn settings >? and Use The hotspot ? a lot of people has this problem including me with my other E4 and i had to downgrade
---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------
i can use my moto with stock firmware on any gsm network here in my country without use custom roms.
Click to expand...
Click to collapse
The APN settings can be edited on any Android 7.1.1 stock build for the xt1766. With root access and a root file editor, the apns-config.xml file can be modified/edited.
With the original Stock that comes with the phone by factory NCQS26.69-48 there is no need of root for any APN edit on Settings.
ozmage said:
With the original Stock that comes with the phone by factory NCQS26.69-48 there is no need of root for any APN edit on Settings.
Click to expand...
Click to collapse
Correct. As you have pointed out, NCQS26.69-48 appears to be the only build that permits an APN to be added/edited directly from Settings>Mobile Networks. On subsequent builds it is necessary to edit the apns-config.xml file from the root filesystem.
Well I was Preparing To Upgrade Because I was Intrigued What Can Do My Phone With New Software And Edit /etc/apns-config.xml like you said to add apns and i was making a backup of my Actual apns-config.xml File but then i started Searching And Finding The Custom APN'''s entries I made With Custom Names and Everything on Settings>Mobile Networks and guess what there is NONE of them on apns-config.xml So this means is not going to work like that , i dont think that custom apns are inserted in the file in question so No Upgrade for me also im using a custom kernel with the f2fs patch to pass SafetyNet with Magisk which is based on the NCQS26.69-48 kernel source but i was going to leave all that behind just to upgrade , No GO for me . Can The Bootloader be Locked With this signed OEM Firmware just asking :> , I hope Oreo 8.1 Roms Come To Moto E4 ................. soon.
ozmage said:
Well I was Preparing To Upgrade Because I was Intrigued What Can Do My Phone With New Software And Edit /etc/apns-config.xml like you said to add apns and i was making a backup of my Actual apns-config.xml File but then i started Searching And Finding The Custom APN'''s entries I made With Custom Names and Everything on Settings>Mobile Networks and guess what there is NONE of them on apns-config.xml So this means is not going to work like that , i dont think that custom apns are inserted in the file in question so No Upgrade for me also im using a custom kernel with the f2fs patch to pass SafetyNet with Magisk which is based on the NCQS26.69-48 kernel source but i was going to leave all that behind just to upgrade , No GO for me . Can The Bootloader be Locked With this signed OEM Firmware just asking :> , I hope Oreo 8.1 Roms Come To Moto E4 ................. soon.
Click to expand...
Click to collapse
You're completely right. I recall now that apns-config.xml is not the only file needing editing. One of the db.telephony.common.jar files plays a role as well as a system//framework/lib file. Let me research this a bit and I'll get back to you on exactly what to edit. I've been developing on the Moto E LTE Surnia and the Moto E5 Play James a lot lately, so I tend to sometimes cross up device configs. There is a thread dedicated to this exact subject and it seems the simplest was to achieve GSM support on the more recent OS builds is to downgrade the radio firmware to a previous version. But again, I'll double check this.
Flashing the firmware package does not re-lock the bootloader. You must manually relock it should you want your device back in OEM locked state.
MotoJunkie01 said:
You're completely right. I recall now that apns-config.xml is not the only file needing editing. One of the db.telephony.common.jar files plays a role as well as a system//framework/lib file. Let me research this a bit and I'll get back to you on exactly what to edit. I've been developing on the Moto E LTE Surnia and the Moto E5 Play James a lot lately, so I tend to sometimes cross up device configs. There is a thread dedicated to this exact subject and it seems the simplest was to achieve GSM support on the more recent OS builds is to downgrade the radio firmware to a previous version. But again, I'll double check this.
Flashing the firmware package does not re-lock the bootloader. You must manually relock it should you want your device back in OEM locked state.
Click to expand...
Click to collapse
Ok Thanks For your Good Job Man , i just wanted to know if it was possible to re-lock the bootoader but not for my phone . Well Im Going To Leave The Phone as it is now but if there is some way to edit apn on new stock firmware maybe some magisk module or xposed app , would be nice , i just need oreo lineageos 15.1 in some certain future.
Ok Man I Upgraded M Device No Problems But No Way To Introduce My Custom Apn Settings I Really Need a Way I Been Looking around on Google and Nothing GravityBox Cant edit Apn Dont Know What To Do Just ...
#1 = I Flashed This Upgrade and i had to rollback downgrading to the original Stock , Why well No way to Add Custom Apn , Magisk Modules Wont work with the new kernel and if i flash older kernel with f2fs loopback bug patched WIFI wont work , So No Apn , No Magisk Modules , No Xposed . And Neither the F2fs Loopback bug Workaround works i used the last version . this new Stocks Are Not For Me but thanks anyway because now i have newer Bootloader.
ozmage said:
Ok Thanks For your Good Job Man , i just wanted to know if it was possible to re-lock the bootoader but not for my phone . Well Im Going To Leave The Phone as it is now but if there is some way to edit apn on new stock firmware maybe some magisk module or xposed app , would be nice , i just need oreo lineageos 15.1 in some certain future.
Click to expand...
Click to collapse
To relock your bootloader, you can use either the WinDroid Toolkit or you can use the exact opposite command that you used to unlock it.
fastboot oem lock
ozmage said:
#1 = I Flashed This Upgrade and i had to rollback downgrading to the original Stock , Why well No way to Add Custom Apn , Magisk Modules Wont work with the new kernel and if i flash older kernel with f2fs loopback bug patched WIFI wont work , So No Apn , No Magisk Modules , No Xposed . And Neither the F2fs Loopback bug Workaround works i used the last version . this new Stocks Are Not For Me but thanks anyway because now i have newer Bootloader.
Click to expand...
Click to collapse
The f2fs loopback bug workaround module works fine on the latest update. Flash it in twrp. Sometimes you have to flash it twice.
Thanks @madbat99 for the tip , now I need Someone Who Tells Me How To Add Customs Apn Settings Using This New Version Of Stock Android , I Really Like to Have Android Security Patches And Kernel With All The New Improvements
But Cant Find Any Way To Edit Apns On This Rom Anybody Knows ? this is sad..
ozmage said:
Thanks @madbat99 for the tip , now I need Someone Who Tells Me How To Add Customs Apn Settings Using This New Version Of Stock Android , I Really Like to Have Android Security Patches And Kernel With All The New Improvements
But Cant Find Any Way To Edit Apns On This Rom Anybody Knows ? this is sad..
Click to expand...
Click to collapse
On my xt1766, I initially told you wrong. Sorry about that. I was referring to the apns-config.xml on another Moto device of mine. I used the MSL code on my xt1766 to manually set the APN to a GSM carrier. (in my case, AT&T). Network preferences and such can also be edited with your MSL, including LTE band priority and carrier aggregation settings. You can get your MSL by contacting your mobile provider and giving them your device info, MEID, etc. To enter into MSL programming mode (Data Settings Menu), just go to your dialer and enter ##3282#. You will be prompted for your six digit MSL by selecting the "Edit" option in any of the listed fields.
MotoJunkie01 said:
On my xt1766, I initially told you wrong. Sorry about that. I was referring to the apns-config.xml on another Moto device of mine. I used the MSL code on my xt1766 to manually set the APN to a GSM carrier. (in my case, AT&T). Network preferences and such can also be edited with your MSL, including LTE band priority and carrier aggregation settings. You can get your MSL by contacting your mobile provider and giving them your device info, MEID, etc. To enter into MSL programming mode (Data Settings Menu), just go to your dialer and enter ##3282#. You will be prompted for your six digit MSL by selecting the "Edit" option in any of the listed fields.
Click to expand...
Click to collapse
Ok There Is No Other Way To Get The Msl Code , Because i Don Really Know if "Viva" here in domican republic know this i dont think so , they dont now how to give me a msl code , is a new company
MotoJunkie01 said:
On my xt1766, I initially told you wrong. Sorry about that. I was referring to the apns-config.xml on another Moto device of mine. I used the MSL code on my xt1766 to manually set the APN to a GSM carrier. (in my case, AT&T). Network preferences and such can also be edited with your MSL, including LTE band priority and carrier aggregation settings. You can get your MSL by contacting your mobile provider and giving them your device info, MEID, etc. To enter into MSL programming mode (Data Settings Menu), just go to your dialer and enter ##3282#. You will be prompted for your six digit MSL by selecting the "Edit" option in any of the listed fields.
Click to expand...
Click to collapse
##3282# Dont work for me
ozmage said:
##3282# Dont work for me
Click to expand...
Click to collapse
1. Phone information
*#*#4636#*#*
2. IMEI Info
*#06#
3. Calendar
*#*#225#*#*
4. Debug info for Google Play Service
*#*#426#*#*
5. Access Google Partner Setup
*#*#759#*#*
6. Engineering Mode
*#*#2486#*#*
All THAT ^^^^^^^^ works
ozmage said:
##3282# Dont work for me
Click to expand...
Click to collapse
Works fine here.
Hello,
I have a problem with my Z2 Force TMO US version. I live in Poland. I bought the phone on the internet and it was TMO simlocked. I did the temporary unlock to check if it is working. Then I wanted to flash custom rom (DU in this case) and my problems has begun.
1. After first attempt of unlocking boot I got it unlocked but couldn't flash any custom rom. I figured out it is TWRP problem (flashed 3.2.2-2 not 3.2.1.1).
2. Flashed TWRP 3.2.1-1 and I was able to flash custom rom.
3. After flashing custom rom I lost phone signal: I'm getting no service and zero signal bar. I checked *#*#4636#*#* and noticed that I have radio off. I had IMEI and BASEBAND then.
4. I tried many other roms to get my signal back but no success.
5. I flashed stock TMO and was able to unlock simlock temporary again but it has no service and signal again. Radio is off.
6. Today I tried flashing stock OREO OCX27.109-36 with locking bootloader now I'm stuck.
I have locked bootloader and no baseband which means I don't have any signal or WIFI (mac is 0). I can't connect to google account so I can't get oem unlocking option - it's greyed out.
Can somebody help me with enabling OEM unlock? Or even better can somebody help me with getting signal back?
Thanks in advance for reply.
Try flashing the newest TMO firmware, which is the only thing you can flash with a locked bootloader. Check post #2 of the return to stock thread for the flashall utilities and the TMO flashall. The latest firmware provided for TMO is ocx27.109-51-7
You can do it
, I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you.
Use pdanet app, you need two Android devices. Connect using Bluetooth...
Thank you guys. BT tethering helped. Thread can be closed.
How did you connect to Bluetooth to get through first start up? I can't get to Bluetooth settings to pair. I have this issue currently...
Remember you're doing this at your own risk. I won't be hold responsible for any damage.
Read and follow steps carefully.
First follow the tutorial to unlock your bootloader, install twrp and root.( https://forum.xda-developers.com/lg-v30/how-to/korean-variant-bootloader-unlock-root-t3804505), after unlooking the bootloader,
flash twrp flashable v300l android 8 rom( 2019 prefered) and boot android first.
Go to developer options and enable usb debugging and OEM unlocking if is unticked.
Now download v300l pie rom and flash with LGUP( Use the dualmode version to get all options), but this time choose refurbish.
After it successfully boot, go back to enable developer options and enable usb debugging.
Now Download H930 pie rom you like and flash with lgup but this time choose partition dl then click start.
Now this is the important part, when the partition selection menu pops up, select all partitions except xbl, xbl 2 and modem, these three partitions must be unselected or unmarked then hit ok to flash.( if you dont unselect them, it will flash H930 Modem and you wont get network since the korea variants and Global variants dont have the same modem. unselect those 3 options to retain the korea modem)
After it finishes, hold the volume down and power button to got to recovery and do factory reset.
Wait for it to finish booting and configure to get your lg v30 korea variant as a global version.
Notes:
Any time there is an update, please use the LGUP to flash kdz and select partition dl, and leave xbl xbl2 and modem unselected or else you will not get network or service signal.
Never use a flashable zip or else you will get softbrick( you can use a back up global rom to restore as update but make sure you dont select modem anytime youre doing update)
sometime registering network seems to take longer time, be patient.
You can also root by using the recovery installion method and root using twrp.
I dont know if this will work on the other korea versions but you can try.
You can now flash any aosp rom made for H930 you want without any problem because your device is now global version.
Please Fm radio will never work because the Korea Variants don't have Fm hardware. LG replaced the Fm hardware with DMB hardware for Korea market.
Saying thank you will be appreciated
@Amosika
Please just to verify, you mean all custom roms available to H930 can now be installed on V300L?
fi5z.x9 said:
@Amosika
Please just to verify, you mean all custom roms available to H930 can now be installed on V300L?
Click to expand...
Click to collapse
yes. every rom for H930 works on v300l with a single problem unless that rom is buggy.
fi5z.x9 said:
@Amosika
Please just to verify, you mean all custom roms available to H930 can now be installed on V300L?
Click to expand...
Click to collapse
But just covert from v300l to H930 first or else you wont get network signal. follow the tutorials and you will see the magic
just finish converting mine. V300S
from v21e
1.i flashed v300s 30h
2.next flashed H93030q_00_OPEN_EU_OP_0902.kdz (unchecked xbl,xbl2,modem)
3.flash TWRP-3.2.3-7-DataIMG.img
4.from twrp: flash magisk v19.4, dm_verity, ak3_rctd remover.
reboot successfully with signal and data. buy one thing i notice, there is no 3g/lte indicator under signal icon. but then again, i have data connection.
Now, my concern is:
1. if I backup my current stock rom (h93030q) via twrp, then i restore it via twrp. will I get softbrick?
2. what twrp version must prefer to install custom rom?
3. what are the working custom rom do i use?
4. whats the proper step in twrp to have a clean install for custom rom?
5. lastly, when im in custom rom, can i go back to stock h93030q via RESTORE on TWRP?
Earlier i flashed v300l rom step by step but i got no signal so i revert back to us998 20h oreo. But still i lost signal. (When i search it shows "error while searching networks) and (i check ims status in *#*#4636#*#* the n phone info and tap three dots and ims status. Ims status : not registered) my original device is h931 converted to us998.
I done everything flash rom in DL/Refurbished but no success till date. So if you guys have any fix please help me. And yes i don't loose imei number , i have it but no network. And wifi not able to search Wi-Fi's every time i need to restart to connect wifi. Sometimes it connect. Till restarting for wifi connection.
hi guys. this method works well, but network searching is too long, because firmware is searching for a second sim. At Oreo roms it was possible to fix it by changing (removing) persist.radio.multisim.config property in build.prop or OP folder. is there any way to fix it at Pie?
---
ok guys, i found a solution if you have root
edit file /vendor/bin/init.class_main.sh
about string ~120-130 find
multisim=`getprop persist.radio.multisim.config`
Click to expand...
Click to collapse
and change it with
multisim=tsts
Click to expand...
Click to collapse
looks like workaround, but works well
viktor.s said:
hi guys. this method works well, but network searching is too long, because firmware is searching for a second sim. At Oreo roms it was possible to fix it by changing (removing) persist.radio.multisim.config property in build.prop or OP folder. is there any way to fix it at Pie?
---
ok guys, i found a solution if you have root
edit file /vendor/bin/init.class_main.sh
about string ~120-130 find
and change it with
looks like workaround, but works well
Click to expand...
Click to collapse
i tried that, after reboot i have no signal anymore even i backed the default.
fortunately i have backup from twrp.
---------- Post added at 01:13 PM ---------- Previous post was at 12:44 PM ----------
coming from v300s pie and flashed h930 30q. my only problem is lte/4g icon on statusbar, how can I fix it?
no Vietnamese language
Hi bro. Can it be used with volte?
The guide look promising and I would like to try it on my V300L that I bought to replace my H930 with a smashed screen (unfortunately a screen assembly would have cost more).
But I got two questions before trying it out:
1. The Bootloader unlock and root guide is based on Oreo, but I got my V300L on Pie, unfortunately (V300L30h). According to the hidden menu, ARB is 0 for APPSBL, SBL1, TZ and RPM, so it should work, right?
2. My goal is to convert the firmware to the EU variant, but I don't necessarily need a bootloader unlock or root myself. In the bootloader unlock guide you are supposed to flash the H930 firmware as a whole, including XBL, XBL2 and modem. So it seems like the V300L and H930 firmware is signed using the same key. As bootloader unlocking requires to reflash the firmware multiple times, which is not optimal for the EMMC chip, and bootloader unlocking could introduce some hassle with some apps, I wondered if it was possible to flash the firmware directly without peforming the bootloader unlock first, of course without flashing XBL, XBL2 and modem. Unfortunately, I don't really know how Qualcomm's chain of trust works, but I can imagine that having bootloader stages from different device firmwares might trip up the validation and I really don't want to mess up the bootloader chain.
Thanks in advance
what h930 rom that have not dual sim. i need a single sim version of h930 firmware
dchinacay said:
what h930 rom that have not dual sim. i need a single sim version of h930 firmware
Click to expand...
Click to collapse
Android Oreo or pie?
dchinacay said:
what h930 rom that have not dual sim. i need a single sim version of h930 firmware
Click to expand...
Click to collapse
??? I think you are confused about something.
All actual H930 firmware is single SIM. LG H930 and (even LG H930G) are single SIM phones.
There are only two "V30" dual SIM variants -- H930DS and H930D. So don't flash H930DS or H930D KDZ.
But actual H930 is single SIM. So, any LG stock KDZ for H930 is single SIM. The hard part is finding dual SIM KDZ not avoiding them.
________
I'm a little confused by "ROM". Are you talking about LOS custom ROMs? Or stock firmware TWRP flashable zips built like ROMs? Or are you merely using the word ROM to describe LG stock KDZ? In the OP, they use the word "ROM" to mean LG stock KDZ, so I will assume that's what you mean.
sorry that's for stock kdz. as i have v300s and converting to h930. this is the file i fl(H93030q_00_OPEN_EU_OP_0902.kdz) but it has a dual simcard option in settings.
i
dchinacay said:
sorry that's for stock kdz. as i have v300s and converting to h930. this is the file i fl(H93030q_00_OPEN_EU_OP_0902.kdz) but it has a dual simcard option in settings.
Click to expand...
Click to collapse
That's a single SIM phone. It is compatible with dual SIM H930 variants (DS and D), but H930 is a single SIM phone.
If it has dual SIM card option, just ignore it.
Early Oreo H930 KDZ didn't have that option and H930DS people who flashed that couldn't use their dual SIMs.
ChazzMatt said:
That's a single SIM phone. It is compatible with dual SIM H930 variants (DS and D), but H930 is a single SIM phone.
If it has dual SIM card option, just ignore it.
Early Oreo H930 KDZ didn't have that option and H930DS people who flashed that couldn't use their dual SIMs.
Click to expand...
Click to collapse
i can confirm what @dchinacay has said above with regard to stock H930 30q firmware having Dual SIM option in Korean V300 Frankenstein; is that option visible by default in non DS version of H930 too?
i have just converted a V300S to H930 Pie using method by @darkidz555 and @Amosika and flashed the stock H930 30q KDZ firmware from your mega upload last to achieve that.
many thanks to everybody that has contributed to this marvel!
while signal searching was instantaneous when the phone was still in its V300 state, it has slowed down noticeably as a H930 now.
is the slow down due to the Dual SIM option or because the phone is now searching for networks in bands not supported by the V300?
hope some gurus can shed some light and maybe we can solve the problem with a simple config file edit.
(i did not try the suggestion (https://forum.xda-developers.com/showpost.php?p=80558959&postcount=7) by @viktor.s as @dchinacay has encountered problem with it.)
@dchinacay, I do have 4G on top of the signal bars when mobile data is in use (wifi off or when not connected to wifi).
Dual SIM and slow signal search issue resolved!
I accidentally stumbled upon the solution for slow signal search after conversion to H930.
As I did not uncheck the box beside recovery and recoverybak for Partition DL when flashing H930 30q KDZ firmware, I had to reflash TWRP after 30q.
As known, Format Data is required during the first boot in TWRP recovery for TWRP to work.
After formatting data and rebooting back into TWRP recovery, I went ahead to flash Magisk 20.1, Disable DM Verity and RCTD Remover.
To my surprise, after the phone has booted into android PIE, there is no more Dual SIM option and the 4G cellular signal caught on almost instantaneously, like how it was when the phone is still a V300!
@dchinacay, the 4G signal icon display went back to that of V300's too!
Hope the above works a treat for all those facing the same issues!
potatohead said:
I accidentally stumbled upon the solution for slow signal search after conversion to H930.
As I did not uncheck the box beside recovery and recoverybak for Partition DL when flashing H930 30q KDZ firmware, I had to reflash TWRP after 30q.
As known, Format Data is required during the first boot in TWRP recovery for TWRP to work.
After formatting data and rebooting back into TWRP recovery, I went ahead to flash Magisk 20.1, Disable DM Verity and RCTD Remover.
To my surprise, after the phone has booted into android PIE, there is no more Dual SIM option and the 4G cellular signal caught on almost instantaneously, like how it was when the phone is still a V300!
@dchinacay, the 4G signal icon display went back to that of V300's too!
Hope the above works a treat for all those facing the same issues!
Click to expand...
Click to collapse
finally someone explained properly about this situation, as I'm not good in english.
so what step i will do? go back to v300s kdz - flash h930 30q - uncheck xbl, xbl2, modem, recovery, recoverybak - start?
potatohead said:
I accidentally stumbled upon the solution for slow signal search after conversion to H930.
As I did not uncheck the box beside recovery and recoverybak for Partition DL when flashing H930 30q KDZ firmware, I had to reflash TWRP after 30q.
As known, Format Data is required during the first boot in TWRP recovery for TWRP to work.
After formatting data and rebooting back into TWRP recovery, I went ahead to flash Magisk 20.1, Disable DM Verity and RCTD Remover.
To my surprise, after the phone has booted into android PIE, there is no more Dual SIM option and the 4G cellular signal caught on almost instantaneously, like how it was when the phone is still a V300!
@dchinacay, the 4G signal icon display went back to that of V300's too!
Hope the above works a treat for all those facing the same issues!
Click to expand...
Click to collapse
Glad you got it worked out.
dchinacay said:
finally someone explained properly about this situation, as I'm not good in english.
so what step i will do? go back to v300s kdz - flash h930 30q - uncheck xbl, xbl2, modem, recovery, recoverybak - start?
Click to expand...
Click to collapse
He did NOT uncheck the recovery and recovery_bak, so he wiped out TWRP... Which actually solved his problem. He then re-installed TWRP, reformatted his data (necessary), flashed Magisk 20.1, Disable DM Verity and RCTD Remover.
He basically followed these steps:
INSTALL or REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285