Unlocking Bands in MOTO G 2015 (PARTIALLY WORKING) - Moto G 2015 General

SORRY FOR MY ENGLISH !
Guys i just found i way to connect the phone with QPST and modify the RF BC CONFIG (1877). It actually made changes because i see new bands when check it with 4636 code . But the radio turns off and on constantly.
Maybe i'm doing something wrong and with you guys can make this working
Here is a tutorial how i make this parcially working
1- Download Unlock_bands_of_your_qualcomm_device!.zip (i can't post it is illegal) and install QPST
2- Then reboot your phone to Bootloader and select BP Codes
3-The phone will boot normally and you will see in your "Device manager" three new devices with a exclamation mark, there is one that is the correct in my case is ID-HARDWARE USB\VID_22B8&PID_2EC1&REV_????&MI_00, so you need to force a driver install like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4-Once you finish the driver install, you go to QPST Configuration, press "Add New Port", select COM1 and manually rename it with the port that corresponds to your phone. So if you do it correctly you will see in the ACTIVE PHONES tab something like this:
5- From this step you can follow this guides
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031

You probably need a modem.img that will support the frequency you are using. It could be theoretically possible to have the mother of all modems which supports every frequency and then we may be able to actually have fully region-free devices for roms, as well, since an improper match between a region's rom and modem will cause a forced bootloop.

hp420 said:
You probably need a modem.img that will support the frequency you are using. It could be theoretically possible to have the mother of all modems which supports every frequency and then we may be able to actually have fully region-free devices for roms, as well, since an improper match between a region's rom and modem will cause a forced bootloop.
Click to expand...
Click to collapse
so probably the locked frequencies are soft-coded ?. And the only way to unlock bands at least in this phone is with a modded modem.img ? . I hope someone can figure out :fingers-crossed:

Couldn't get mine to work.
@dannygoround

dannygoround said:
Couldn't get mine to work.
@dannygoround
Click to expand...
Click to collapse
What problem do you have ?

lexer98 said:
so probably the locked frequencies are soft-coded ?. And the only way to unlock bands at least in this phone is with a modded modem.img ? . I hope someone can figure out :fingers-crossed:
Click to expand...
Click to collapse
modem.img is just a ZIP file filesystem for the modem partition... On the old Nexus 4 we used to take an old data modem radio (0.33) that supported LTE and use it with a new WiFi radio (1.07) and it worked perfectly. The key was we could get a data radio that supported LTE.
The problem is the radio files themselves inside the image are binary (soft)firmware images, you can't just edit it to enable this or that. To make additional bands work we would need to get a mobile data radio file that has support for all bands, likely the only one in existence, if it exists, are in the hands of Motorola R&D.
Without some kind of an "all bands" region-free engineering radio file, we are probably SOL unless someone can figure out how to stop the forced bootloop if the modem and the ROM image don't match regions.

Would it be possible not to unlock all the bands but only to convert to a different version (say from xt1540 to xt1541 ...)? Flash the region appropriate modem, unlock only the bands that should be supported by that modem and get a stable moto g working on different bands than the ones we used to have?

mandibitola said:
Would it be possible not to unlock all the bands but only to convert to a different version (say from xt1540 to xt1541 ...)? Flash the region appropriate modem, unlock only the bands that should be supported by that modem and get a stable moto g working on different bands than the ones we used to have?
Click to expand...
Click to collapse
TBH, I don't know... perhaps... I am not sure EXACTLY what is being checked for a region match, if it is just the radio image, it will probably work. If it is checking something in the EFS partition, you might be out of luck.
Either way, if I was going to be playing with this, I would be unlocked and have a backup of the EFS partition just in case. Your chances of bricking are low, but better safe than sorry.

Moto G has a EFS partition ? @lost101 there a risk of bricking the device by flashing a modem from another phone with similar specs ? Like a XT1043 modem on a XT1550 (both dual sim)

lexer98 said:
Moto G has a EFS partition ? @lost101 there a risk of bricking the device by flashing a modem from another phone with similar specs ? Like a XT1043 modem on a XT1550 (both dual sim)
Click to expand...
Click to collapse
There should be no risk flashing Modems from different Osprey models.
No Motorola devices have an EFS partition. It would really be worth starting a thread on the subject of Backing up Osprey's IMEI - as there may be partition differences unique to the handset. With the Original Moto G, key partitions appear to be:
/dev/block/platform/msm_sdcc.1/by-name/hob
/dev/block/platform/msm_sdcc.1/by-name/dhob
/dev/block/platform/msm_sdcc.1/by-name/fsc​
Related post: http://forum.xda-developers.com/showpost.php?p=63894196&postcount=311

Hi - I signed up just so I could join this thread. I have the same problem: I have an xt1541 (UK) and live in an xt1542 area (Argentina). I went through dozens, if not hundreds, of posts before making any changes to my G3. As I already have a working LTE Samsung (it really does run like the wind!) I decided to play around with my G3, as I'd rather brick it than have a partially working phone.
Briefly, absolutely nothing I have tried so far has enabled the bands I need. But on the brighter side of things, I have flashed so many images (just about all of them, excluding the Zoom versions), combinations of images (Latam system with UK radio and fsg, the reverse of that, 2GB models on my 1GB phone and on and on), tried dozens QPST and QXDM values etc etc and *nothing* has bricked it. The key is to always make sure that you have access to TWRP and a backup.
I'm not encouraging anybody to go ahead and be reckless but, so far, I've been crazy reckless and I've always eventually wound up with a working phone. These days I've given up for a while, as I'm bored of toying with the phone. I am, however, convinced that the real solution is buried somewhere in the phone's built-in system, as I've run out of ideas when it comes to flashing images. And, let's be honest, though I've learnt a few things, I'm just a noob following instructions Right now I'm using UK NON-HLOS.bin and fsg.mbn, the rest of the image I flashed is Canadian retail which, for some reason, seems to work best in my phone (?) By using the method I describe below, I managed to get a consistent 2G connection (and, let's face it, LTE is incredible, it's frustrating not to have it on such a nice phone, but it's not something I absolutely need - I ditched the LTE Samsung I was using in favour of the G3).
Some random stuff:
CM 12.1 worked great but the phone's radio needed to be in working order before flashing.
It's my understanding that the values that need to be changed in QXDM's NV browser is not limited to 01877, but also include 00946, 02954, 0041 and 06828.
http://forum.xda-developers.com/showpost.php?p=56577252&postcount=455
2G radio can be improved dramatically using QPST's Service Programming application (after doing this, I decided to use the G3 as my main phone because it got my puny EDGE connection to work consistently): connect phone as described above, run QPST config and Service Programming, in the "UMTS System" tab select "read from phone", then tick all the 2Preferred Band" options, write to phone, reboot. Which reminds me of:
Go through the trouble of rebooting every time you tinker with your phone.
Ok, I'll try to keep an eye on this thread. Feel free to ask me about any changes I made to my phone. I hope I didn't break any forum rules.
Hope this kelps

No luck i flashed a xt1043 modem on my XT1550 using this commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
The device just boot up fine but i have the same problem when i modify the bands in NV-MANAGER .... the radio just turn on and off continuously.
I have 3G signal but is a bit poor in some areas because the XT1550 only has the 850mhz band ....
Well I can't complain so much about it. I get the device for half of the price xD

Perhaps using the term EFI partition was a misnomer, my point was to backup the IMEI number and special data before delving too deep into messing with radios, although per the previous poster it probably doesn't matter.
Sent from my MotoG3 using Tapatalk

To flash Radio Firmware, the following commands are required:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​

lost101 said:
To flash Radio Firmware, the following commands are required:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​
Click to expand...
Click to collapse
Oh i forgot the FSG .... well i typed all of them and the device seems to works fine, i have a new code on the 1877 line ...
but how i know what band is using the phone ? In 4636 there isn't any information about that .... maybe QSPT ?

lexer98 said:
Oh i forgot the FSG .... well i typed all of them and the device seems to works fine, i have a new code on the 1877 line ...
but how i know what band is using the phone ? In 4636 there isn't any information about that .... maybe QSPT ?
Click to expand...
Click to collapse
Check this thread for original Moto G: http://forum.xda-developers.com/moto-g/general/unlock-hspa-bands-moto-g-1700mhz-xt1032-t2878441
Included screen-shots display bands supported info via mzTool.

I was wrong with the new code in the 1877 line ... still the same and the radio goes crazy when i do a change on that parameter .
But i just found something curious when i flash the XT1043 Modem restores the original 1877 code from the XT1550 ! .... Maybe is the same modem for all devices ?

Lexer, did you change all the values properly? (01877, 00946, 02954, 0041 and 06828) You need to "read from phone". Then write "0" in each one, "read from phone" again to make sure the 0s stuck. Reboot the phone, then read the values again, then enter the values you want.
I'm not sure QXDM even works with the G3. I think the bands are programmed into the phone's memory or -even worse- into the chipset.

speedy197 said:
Lexer, did you change all the values properly? (01877, 00946, 02954, 0041 and 06828) You need to "read from phone". Then write "0" in each one, "read from phone" again to make sure the 0s stuck. Reboot the phone, then read the values again, then enter the values you want.
I'm not sure QXDM even works with the G3. I think the bands are programmed into the phone's memory or -even worse- into the chipset.
Click to expand...
Click to collapse
I have a XT1550 dual sim Moto G3. What I want is to flash the stock rom of XT1540. I already tried flashing it,the mobile boots fine. The only issue is there is no RIL. Then I tried by flashing the XT1540 stock + radio of XT1550(NON-HLOS & fsg).
Same result-no RIL.
So,is there anyway that the QPST method will work?

theincognito said:
I have a XT1550 dual sim Moto G3. What I want is to flash the stock rom of XT1540. I already tried flashing it,the mobile boots fine. The only issue is there is no RIL. Then I tried by flashing the XT1540 stock + radio of XT1550(NON-HLOS & fsg).
Same result-no RIL.
So,is there anyway that the QPST method will work?
Click to expand...
Click to collapse
Try flashing XT1043 stock rom, that device has the same specs of the XT1550 ... so probably will work

Related

[HOWTO] Enable Band 12 Moto Pure MM (Non OTA ROM included!)

UPDATE: Modem OTA Update Zip for use in TWRP.
@vx2ko and @Spasticdroid put together a fully functional flash-able zip to enable Band 12 on MM. Great work! What a great community of developers!
Here it is
Just load into your SDCARD, reboot into recovery, and install the zip!
Now this is the manual method below...
Band 12 support is only available in the OTA radio package, so basically in order to enable Band 12 you must first sideload the MM OTA. Below is how I did it!
FAIR WARNING!!!! This is what worked for me and I am certain it will not work for everyone else! Use at your own risk!!!
This assumes you have a fully functional SDK/adb environment and you know a little something about the command line. Used the Universal ADB Driver.
Back up your current ROM in TWRP to an external SDCard if you are already running a non-stock ROM. (I am running TruePureXMM)
Make sure you have backed up the internal memory (pics, etc) as it will be wiped clean while restoring the stock image.
Download the "Restore to Stock" project - Restore to Stock
Download the Stock MM image - Blur_Version.23.21.18.clark_retus.retus.en.US.zip
Download the latest TWRP recovery image - twrp-2.8.7.1-clark.img
Execute the "Restore to Stock" batch file. Watch for errors and resolve them as you find them. (Good luck! I had none.)
You have two options: Reboot, restore the developer options in Settings and enable USB debugging. Then from the command line, 'adb reboot recovery'. OR You can boot right into recovery by pressing the power and volume down keys together until the bootloader shows, then select recovery. NOTE: It is NOT important if 5.1.1 works as most likely it will have issues like wifi not functioning. This step is just clear the phone to factory so that the correct modem files are loaded in the next step.
'adb sideload Blur_Version.23.21.18.clark_retus.retus.en.US.zip' (Make sure you are in the directory where the Blur_Version.23.21.18.clark_retus.retus.en.US.zip file is located.)
reboot and you have MM stock.
'adb reboot bootloader'
'adb flash recovery twrp-2.8.7.1-clark.img'
'adb reboot recovery' - reboot to recovery, not doing so the ROM will overwrite the recovery image.
At this point you have a fully functional Stock ROM/OTA. You can choose to restore your previous MM backup without the efs partition, root the OTA using BETA-SuperSU-v2.52.zip, or just leave it alone. You pick.
Good luck!
This is a nice concise write up. This will be great for learners. Thank you.
Thank you for the write-up. I think I saw you poking at this problem in other threads, and appreciate the concise summary of your efforts.
I just installed TruePure yesterday, and kind of don't really want to through the hassle of redoing everything.
This seems like a very roundabout way of getting the EFS partition from the OTA and then updating to a new ROM around that official EFS partition.
Is there no way to stick with one's current ROM and flash just the EFS partition from the OTA update in order to "add" Band 12 support to any stock-based ROM?
Apologies if this is a noob question with a very obvious "not possible" condition attached to it.
I'm having problem used the restore to stock etc.. and problem is in stock recovery I simply can't get past no command (yes I know you have to press vol down and power) but I tried everything,in TWRP it won't flash the zip. I am clueless at this point since i can't get the stock recovery to work so I can sideload the ZIP ota.
EDIT: for those having issues on stock recovery you have to hold power then while holding power after 2-3 seconds press and release volume UP. I didn't get it to work because of this it used to be different.
you can put the OTA ZIP to your phone or you can use adb sideload like OP mentioned. Both will work if you want to do it from sd-card just select install update from SD card.
patt2k said:
I'm having problem used the restore to stock etc.. and problem is in stock recovery I simply can't get past no command (yes I know you have to press vol down and power) but I tried everything,in TWRP it won't flash the zip. I am clueless at this point since i can't get the stock recovery to work so I can sideload the ZIP ota.
EDIT: for those having issues on stock recovery you have to hold power then while holding power after 2-3 seconds press and release volume UP. I didn't get it to work because of this it used to be different.
you can put the OTA ZIP to your phone or you can use adb sideload like OP mentioned. Both will work if you want to do it from sd-card just select install update from SD card.
Click to expand...
Click to collapse
@patt2k did you get band 12 working using this method?
Makalicious said:
@patt2k did you get band 12 working using this method?
Click to expand...
Click to collapse
Hi stock rom just booted and IMEI SV indeed shows SV 02! meaning access to band12 is enabled,I am backing UP STOCK rom and will restore my True-Pure rom without EFS.
Give me another 20 min or so. I will post a screenshot. So far so good! I will test few places today where I had weak signal and if it connects to b12 there! adios Verizon forever and ever lol
So after we sideload the OTA, can we flash a different MM ROM over it and still have B12 access? Or can we only restore a backup without overwriting the EFS?
Stryder5 said:
So after we sideload the OTA, can we flash a different MM ROM over it and still have B12 access? Or can we only restore a backup without overwriting the EFS?
Click to expand...
Click to collapse
Looks like it,when you restore previous backup just don't select EFS b4 you had B12. My backup is still copying. Check back here in 15 min here.
PS. the ota link on dropbox is dead I will re-upload it soon when I am finished with all of this.
patt2k said:
Looks like it,when you restore previous backup just don't select EFS b4 you had B12. My backup is still copying. Check back here in 15 min here.
PS. the ota link on dropbox is dead I will re-upload it soon when I am finished with all of this.
Click to expand...
Click to collapse
Thanks for all your research and persistence on this issue. I hope you are successful, I am in a band 12 area and my wife took the OTA yesterday (confirmed SV 02) but not showing band 12 in LTE discovery.
Makalicious said:
Thanks for all your research and persistence on this issue. I hope you are successful, I am in a band 12 area and my wife took the OTA yesterday (confirmed SV 02) but not showing band 12 in LTE discovery.
Click to expand...
Click to collapse
Just booted True-Pure-X-MM rom SV shows 02 with T-Mobile sim (at my home there is no need for B12) however where my family lives there is barely any signal so I will check and play around with T-Mobile sim today.
Remember that Band4 should be always preferred because it's faster, B12 would be only if you have very weak service like me when I visit my family.
Also now when calling: phone stays on LTE does not drop to HSPA/HSPA+ while calling!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
patt2k said:
Just booted True-Pure-X-MM rom SV shows 02 with T-Mobile sim (at my home there is no need for B12) however where my family lives there is barely any signal so I will check and play around with T-Mobile sim today.
Click to expand...
Click to collapse
Awesome. Did you restore a nandroid? Or did you clean flash the TruPureX MM ROM? I want to see if a clean flash would still retain B12 or not. My guess is no but I won't get a chance to test till the weekend.
Uhhhhhh.....just to help people out this method is not exactly full-proof......
I restored to stock and WiFi is not working and network discovery is kind of slow. It also won't recognize my device in recovery.....so I'm going to troubleshoot this. I'm sure I did something dumb somewhere, but not in following these steps.
Yea, sorry....a little bit of background. My wife works in a hospital, and coming from G3 she would complain she had no signal for hours at a time. I figured if anyone can confirm band 12, it would be her. I have been searching all over boards and am unable to confirm anyone with Moto X actually saw band 12 with OTA
Stryder5 said:
Awesome. Did you restore a nandroid? Or did you clean flash the TruPureX MM ROM? I want to see if a clean flash would still retain B12 or not. My guess is no but I won't get a chance to test till the weekend.
Click to expand...
Click to collapse
I just have confirmation of B12! I live in Brooklyn, in my apartment I get B4 I just went to take my mail lol and in the hall way previously I would lose service now it switched to B12 I can confirm 100%
SS:
1) I did backup of my true-pure before doing anything
2) then I restored true-pure without EFS partition (because I didn't want to setup all my stuff) again
@Makalicious @Stryder5 @vx2ko
here is proof of B12 on True-PURE:
OTA Mirrors: will update more:
http://d-h.st/eSGR
http://www.mediafire.com/download/2...sion.23.21.18.clark_retus.retus.en.US+(1).zip
Im on band 4... how do i get to band 12?
I updated to over the air soak test that was pushed out last week.
Thought I was on band 12 with the crystal clear voice., but when I used LTE Discovery.. says band 4
jaimanny said:
Im on band 4... how do i get to band 12?
I updated to over the air soak test that was pushed out last week.
Thought I was on band 12 with the crystal clear voice., but when I used LTE Discovery.. says band 4
Click to expand...
Click to collapse
what does IMEI SV display for you? 02 or 01? 02 means b12 access however remember it will only switch when B4 has very weak signal.
Things got a little funny for me in the middle (WiFi not turning on, poor network connectivity when I went back to 5.1.1 and having to install the 6.0 .zip without the computer) but I am now on 6.0 and everything magically started working again and IMEI SV updated, so thanks for the post.
gpgorbosjr said:
Things got a little funny for me in the middle (WiFi not turning on, poor network connectivity when I went back to 5.1.1 and having to install the 6.0 .zip without the computer) but I am now on 6.0 and everything magically started working again and IMEI SV updated, so thanks for the post.
Click to expand...
Click to collapse
Wifi didn't work for me on 5.1.1 when I booted it .. however after sideloading OTA everything works as it was.
It might be because of RADIO from MM not working on 5.1.1 nothing to worry about.
patt2k said:
what does IMEI SV display for you? 02 or 01? 02 means b12 access however remember it will only switch when B4 has very weak signal.
Click to expand...
Click to collapse
Yea is shows 02. thanks for that info. Have a good day!
@patt2k did you simply push the OTA via fastboot then restore Trupure backup? I'm currently on that ROM and worried about using restore to stock tool from marshmallow

Yotaphone 2 (YD 206 from China) - can't flash any firmware apart from CN one

I've got a yotaphone YD206 from China. tried to flash the latest firmware RU 1.87 with offical yotaphne flasher , it seems ok on my laptop, but after reboot, it stucked in a boot loop (shows android logo, then black screen). I did a few times restart, still not working. I can get to the "Downloading" screen via power + vol down key.
I've also tried using the Yotaphone flasher to flash the other full android images, such as EU, HK ones, which all downloaded from the flasher menu "option 2" - this also looked like everything was OK on the laptop, but didn't seem to change anything on the phone once the process was complete. it always went to stuck in the bright android logo.
Finally, when I tried to flash the CN version, the phone went live again.
Is there anything I'm did wrong or anything else I can try? really want to have the original EU or RU Lollipop......Any help much appreciated!
also , after flashed the new CN version, the e-link back screen look fine but it doesn't response at all to swip up unlock. I can only use the power off key to unlock it. Any idea ? this is a brand new one , I only had it for a few days. it doesn't look like a hardware problem.
I just got the same problem as you.
Tried HK 5.0 RU 5.0 etc..., no firmware is flashable by my YD206. I found when the YT-flasher load the system.img, it reported error, but other .img files were good. I could select Y to continue flashing, but it just turned out to failure as you described. Whether it has something with this?
Anyone could help, appreciated!
---------- Post added at 07:33 AM ---------- Previous post was at 07:29 AM ----------
Another guess, My YD206 is rooted. It may has something with the failure?
Maybe unlock bootloader can do？ I'm just guessing.
Great! I just solved the problem.
THe root cause is system.img is too big for my PC memory. So I just type THe manual command below to flash The system.img and it turned out ok.
fastboot.exe flash -S 512M system firmware/system.img
Sent from my YD201 using XDA Free mobile app
xingshi356 said:
[...]
Sent from my YD201 using XDA Free mobile app
Click to expand...
Click to collapse
Hi.
One quick question - have you flashed your YD206 with European firmware and now it appears as YD201 (including LTE bands b7/b20) ...or you just have YD201 too?
EDIT: In other words - is it possible to flash YD206 with firmware for YD201?
mc_gee said:
Hi.
One quick question - have you flashed your YD206 with European firmware and now it appears as YD201 (including LTE bands b7/b20) ...or you just have YD201 too?
EDIT: In other words - is it possible to flash YD206 with firmware for YD206?
Click to expand...
Click to collapse
I've received YD 206 version from Tinydeal today and it successfully upgraded from 4.4.3-HK firmware to latest 5.0 EU.
Model is now shown as YD 201 instead of 206.
Edit: LTE bands are the same as were before the upgrade.
Hi
veper said:
I've received YD 206 version from Tinydeal today and it successfully upgraded from 4.4.3-HK firmware to latest 5.0 EU.
Model is now shown as YD 201 instead of 206.
Edit: LTE bands are the same as were before the upgrade.
Click to expand...
Click to collapse
How did you upgrade it? I bought the same device from Tinydeal, I have YD206, then in Device Information it isn't "Check Update" option.
How did you use the yotaflasher for do it?
Which firmware did you download?
did you bought the CN version?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for your attention
There is no Update option under Settings in version 4.4.3 (CN version YD-206).
You have to manually upgrade - download Yota Flasher from their ftp server first: ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Install the Flasher onto your PC.
Then you have to have USB drivers installed and put the phone into Download mode (power it off, then power it on by pressing Power button + Vol Down button simultaneously).
Start the Yota Flasher on your PC, make it download latest FW for the Region you choose and lastly make it flash the new fw to your phone.
Reboot the phone and wait about 5 minutes and there comes your Lollipop setup screen.
Hope that helps.
Edit: I've installed EU version 5.0.0-EU1.1.124b (the latest that was offered by Yota Flasher) and now in Lollipop the phone also has the Update option under Settings.
For me YotaFlasher was failing to do the job and left the phone in a boot loop but then I used fastboot, flashed each partition separately (with a command for chopping system.img into chunks as xingshi356 described a few posts above) and now it smoothly runs the latest RU firmware
Just to mention one thing, make sure you have installed drivers from Yotaflasher folder because otherwise Windows takes something random that doesn't work.
I have this phone since yesterday and it is phenomenal, absolutely worth its current discount price.
Can't flash YD 206
Electropherogram said:
For me YotaFlasher was failing to do the job and left the phone in a boot loop but then I used fastboot, flashed each partition separately (with a command for chopping system.img into chunks as xingshi356 described a few posts above) and now it smoothly runs the latest RU firmware
Just to mention one thing, make sure you have installed drivers from Yotaflasher folder because otherwise Windows takes something random that doesn't work.
I have this phone since yesterday and it is phenomenal, absolutely worth its current discount price.
Click to expand...
Click to collapse
Hello Electropherogram,
Can you help me, I tried to flash my YD206 with Yotaflasher, but it's desn't work. I tried with fastboot but it's doesn't work to, I havewriting 'system'...FAILED ( remote: Unkknow chunk type).
Can you help me, can you tell me the command I must to write.
Thank you very much
New: I tried again to flash and now I didn't connect my phone, I lost boot to "downling..." It boot and stay with "Powered by android". I can't power off.
manu3556 said:
Hello Electropherogram,
Can you help me, I tried to flash my YD206 with Yotaflasher, but it's desn't work. I tried with fastboot but it's doesn't work to, I havewriting 'system'...FAILED ( remote: Unkknow chunk type).
Can you help me, can you tell me the command I must to write.
Thank you very much
New: I tried again to flash and now I didn't connect my phone, I lost boot to "downling..." It boot and stay with "Powered by android". I can't power off.
Click to expand...
Click to collapse
I had similar messages and many attempts. Summarising, I did the following:
-I found a thread on using fastboot (I never heard about it before… I’m definitely not an expert!) http://forum.xda-developers.com/showthread.php?t=2277112
-I unzipped the archive with firmware in the location of the program
-I plugged the phone in downloading mode
-I checked in device manager if it is detected as “Android Composite ADB Interface - fastboot”
-I entered the basic commands for erasing and flashing every partition as described in fastboot thread on XDA with one exception for system.img – I typed something like “fastboot flash -S 512M system system.img” so it was uploaded in parts.
-I restarted the phone and after about 10 minutes it was ready to go.
You may need to charge your phone as the energy goes away very quickly even when connected via USB.
I hope that helps!
i made it!
my yotaphone wasn't rooted.
I downloaded yotaflasher and in the program I downloaded the firmware.
Next I closed the program.
- I pluged mi yotaphone in download mode
- I opened yotaflasher, and i selected the first option(flash firmware).
10 minutes later I already had Llolipop!!!
--Sorry! my English level is so low---
TLE 800 working?
Hello guys,
i think about buying the YD201 because it has the LTE 800 for germany.
Please can you check if your LTE 800 is working after flashing YD201 fw over YD206 hardware.
Than i would buy the YD206, becuase it's cheaper.
Thanks
Marc
vombruch said:
Hello guys,
i think about buying the YD201 because it has the LTE 800 for germany.
Please can you check if your LTE 800 is working after flashing YD201 fw over YD206 hardware.
Than i would buy the YD206, becuase it's cheaper.
Thanks
Marc
Click to expand...
Click to collapse
Your question was already answered on previous page:
veper said:
[...] LTE bands are the same as were before the upgrade.
Click to expand...
Click to collapse
Sorry, but you won't get LTE800 that way.
Wifi connection before flash is horrible, To recive or send a whatsapp i have to wait for 2 min, the google play downloades are eternal.
I will downgrade to kit kat
Electropherogram said:
I had similar messages and many attempts. Summarising, I did the following:
-I found a thread on using fastboot (I never heard about it before… I’m definitely not an expert!) http://forum.xda-developers.com/showthread.php?t=2277112
-I unzipped the archive with firmware in the location of the program
-I plugged the phone in downloading mode
-I checked in device manager if it is detected as “Android Composite ADB Interface - fastboot”
-I entered the basic commands for erasing and flashing every partition as described in fastboot thread on XDA with one exception for system.img – I typed something like “fastboot flash -S 512M system system.img” so it was uploaded in parts.
-I restarted the phone and after about 10 minutes it was ready to go.
You may need to charge your phone as the energy goes away very quickly even when connected via USB.
I hope that helps!
Click to expand...
Click to collapse
Hello,
I did what you do and now it's OK, my phone is on lollipop EU. Thank you vert much.
Other question, I live on France and I have troubles to receive my cell network. At home I received H+ and now nothing, no service...anybody know that ?
just receive but not try to check cell network yet
manu3556 said:
Hello,
I did what you do and now it's OK, my phone is on lollipop EU. Thank you vert much.
Other question, I live on France and I have troubles to receive my cell network. At home I received H+ and now nothing, no service...anybody know that ?
Click to expand...
Click to collapse
Hello,
Same issue for me on french network with my new Yotaphone 2...
But I've found a way to restore the cell network...
1 ) Use Yotaphone_flasher and download this CN version : 4.4.3-S01-003-CN1.0.3.32a.zip
2) Close Yotaphone_Flasher
3) Open the Yotaphone_Flasher folder and copy only the RADIO folder to your desktop.
4) Use Yotaphone_flasher again and download the latest EU stock rom 5.0.0-EU1.1.124b.zip
5) Open the Yotaphone_Flasher folder and replace the RADIO folder with the CN RADIO folder you've place on your desktop
6) Execute Yotaphone_Flasher again and just flash your cellphone
7) Let the phone reboot
Works like a charm for me... (LTE ok / H+ ok / wifi ok )
I hope it will be helpfull for you and perhaps everyone in EU.
++
Bilidjinn
Flashing directly to lollipop didn't work to me. So I was flashing to kit kat and it worked flawlessly. Then I update to lollipop ota. I encountered bad network reception, but thanks to Billidjin, I followed his instruction. I reflashed lollipop with yotaflasher (with CN firmware radio). My yotaphone 2 battery life is great. I don't encounter any issues so far.
Hello Billidjinn,
Great !!!! Everything is ok, thank you a lot Billidjinn.

Fastboot Mode On LG K10 Qualcomm Variants!

Hi guys!
Never nuke your LAF partition or if you did nuke LAF consider your phone is bricked (repairable but too hard!).
Not the best idea to nuke LAF partition when that's the most important partition of your phone when you brick it!
But a little information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the difference between MTK & Qualcomm "Fastboot" Commands!
fastboot oem unlock works in MTK because it is present in its LK(Little Kernel)
fastboot oem unlock doesnt work in Qualcomm because it isnt present in aboot of Qualcomm
That's why fastboot getvar and download command works in fastboot that's it!
Reserved.
pvineeth97 said:
Reserved.
Click to expand...
Click to collapse
Good work!
Unlock BL.
pvineeth97 said:
Hi guys!
With the help of @Macgeek I bring you the guide to enter "Fastboot Mode" in Qualcomm Variants!
Phones Supported:
K420DS
K420N
Install LG Drivers & Python before trying this.
1. Put your phone in "Download Mode".
2. Connect the phone to your computer using USB.
3. Download these files: https://github.com/Lekensteyn/lglaf/archive/master.zip.
4. Extract those files. Enter the folder. Press "Shift" and Right Click on your mouse. Select "Open Command Window here".
5. Type "python partitions.py --wipe laf" (without quotes)
6. Remove Battery. Place Battery back. Now enter "Download Mode" again.
You entered "Fastboot"!
You loose "Download Mode". If you are rooted you can get it back by using ADB.
Now, I am looking for what possibilities are present since we entered "Fastboot".
If you unlock the bootloader using "Fastboot", Tell us! We are excited!
This is the difference between MTK & Qualcomm "Fastboot" Commands!
fastboot oem unlock works in MTK because it is present in its LK(Little Kernel)
fastboot oem unlock doesnt work in Qualcomm because it isnt present in aboot of Qualcomm
That's why fastboot getvar and download command works in fastboot that's it!
Click to expand...
Click to collapse
So like I understand I will not able to unlock my BootLoader with this guide on my UnRooted LG K420N and also will loose download mode, so will be not able to flash LG Stock KDZ Files to bring my device to life if I will have problems?
I'm very very disappointed with this device, first device that I can't get root access ?
D_Vovan_238 said:
So like I understand I will not able to unlock my BootLoader with this guide on my UnRooted LG K420N and also will loose download mode, so will be not able to flash LG Stock KDZ Files to bring my device to life if I will have problems?
I'm very very disappointed with this device, first device that I can't get root access
Click to expand...
Click to collapse
Well if you are rooted you can get the "Download mode" back by flashing back the partition using adb root shell. All devices except Qualcomm Snapdragon 410 models of LG K10 have unlocked bootloaders.
If we get hold of a "Developer" edition of the bootloader of this device (aboot) we can unlock bootloader.
I have an qualcom 410 snap dragon has locked bootloader lg ls775 stylo2
roadkill42 said:
I have an qualcom 410 snap dragon has locked bootloader lg ls775 stylo2
Click to expand...
Click to collapse
We don't know much about your device.
If i tried it how would i get download mode back im willing to try i know its not same phone but might work
roadkill42 said:
If i tried it how would i get download mode back im willing to try i know its not same phone but might work
Click to expand...
Click to collapse
You need to be rooted first.
Make a backup of "laf" partition.
Then in adb, flash the "laf" partition to flash the download mode.
Lg k10 k430dsF
Haven't any version for Lg k10 k430dsF?
Isn't compatible this fastboot?
I am trying to unlock the bootloader on the LG Tribute HD model LGELS676 which is a k6 varient. We cannot enter fastboot no matter what... Do you think this method and. zip scripts would or could work for us? Would I need to edit the scripts for our device? We can't even get temp root right now and we are going on 3 months of trying to enter fastboot lol any help is seriously appreciated
Sands207 said:
I am trying to unlock the bootloader on the LG Tribute HD model LGELS676 which is a k6 varient. We cannot enter fastboot no matter what... Do you think this method and. zip scripts would or could work for us? Would I need to edit the scripts for our device? We can't even get temp root right now and we are going on 3 months of trying to enter fastboot lol any help is seriously appreciated
Click to expand...
Click to collapse
Give me more details of your device so that I can help you.
Taken from here http://www.lg.com/us/cell-phones/lg-LS676-Virgin-tribute-hd
Technical Specifications
Carrier Virgin Mobile
Display 5.0" (1280 x 720) HD TFT Display
Battery 2,100 mAh Removable
Platform Android 6.0.1 Marshmallow build MXB48T
Processor Qualcomm Snapdragon™ 1.3 GHz Quad-Core MSM8909
Frequency LTE Bands 2/4/5/12/25/26/41; GSM 850/900/1800/1900 MHz; UMTS Bands 2/4/5; CDMA Bands 0/1/10
Technology LTE, CDMA, GSM, UMTS
Data Transmission LTE, UMTS, HSPA+, HSDPA, 1xRTT, EVDO, EVDO Rev A, GSM
Internal Memory 16 GB (up to 9.93 GB usable)
microSD card Support up to 32 GB**
RAM 1.5 GB
My device is unrooted and has a locked bootloader for obvious reasons.
I have a full adb system dump and other files I have built from source also if that is useful to you. I have linux at my disposal so if I can do anything further please let me know. We are basically in the same boat the K10 was in and development and root is at a standstill until we can access fastboot to unlock our bootloader so we can proceed. Mine is a qualcomm I'm guessing that that is why
Code:
fastboot oem unlock
or any fastboot command has zero effect and there is no known button combo to access it, adb works just fine though. I apppreciate your help very much and I know alot of other people do too
Sands207 said:
Taken from here http://www.lg.com/us/cell-phones/lg-LS676-Virgin-tribute-hd
Technical Specifications
Carrier Virgin Mobile
Display 5.0" (1280 x 720) HD TFT Display
Battery 2,100 mAh Removable
Platform Android 6.0.1 Marshmallow build MXB48T
Processor Qualcomm Snapdragon™ 1.3 GHz Quad-Core MSM8909
Frequency LTE Bands 2/4/5/12/25/26/41; GSM 850/900/1800/1900 MHz; UMTS Bands 2/4/5; CDMA Bands 0/1/10
Technology LTE, CDMA, GSM, UMTS
Data Transmission LTE, UMTS, HSPA+, HSDPA, 1xRTT, EVDO, EVDO Rev A, GSM
Internal Memory 16 GB (up to 9.93 GB usable)
microSD card Support up to 32 GB**
RAM 1.5 GB
My device is unrooted and has a locked bootloader for obvious reasons.
I have a full adb system dump and other files I have built from source also if that is useful to you. I have linux at my disposal so if I can do anything further please let me know. We are basically in the same boat the K10 was in and development and root is at a standstill until we can access fastboot to unlock our bootloader so we can proceed. Mine is a qualcomm I'm guessing that that is why
Code:
fastboot oem unlock
or any fastboot command has zero effect and there is no known button combo to access it, adb works just fine though. I apppreciate your help very much and I know alot of other people do too
Click to expand...
Click to collapse
So there are many LG phones which are in the same boat as K10! Wow! I did'nt know that!
Send me the adb system dump, other files you collected and the firmware file if you have it.
I am developing a root method for Android 6.0 with help of other devs. I can port that script to your device if you want.
Its better if you contact me on What'sapp so we can talk about getting into fastboot and root stuff and I can help you easily. I could help you build a TWRP for your device. I sent my number to you as a private message.
pvineeth97 said:
So there are many LG phones which are in the same boat as K10! Wow! I did'nt know that!
Send me the adb system dump, other files you collected and the firmware file if you have it.
I am developing a root method for Android 6.0 with help of other devs. I can port that script to your device if you want.
Its better if you contact me on What'sapp so we can talk about getting into fastboot and root stuff and I can help you easily. I could help you build a TWRP for your device. I sent my number to you as a private message.
Click to expand...
Click to collapse
Thank you so much! I'm getting out of work in a little over an hour and ill try to gather as much as i can that I have for files to help the process. I will add you on whatsapp too. I'm shaking right now hoping this 3 month ordeal to fight for root and unlocking the bootloader will soon be over. Many jumped ship already but ive been trying to tell these guys from the beginning there HAS to be a way, I know this because I worked on the LG Volt which had similar woes but were eventually overcome ? I'll Be in touch shortly. THANK YOU ?
Sent from my LGLS676
pvineeth97 said:
So there are many LG phones which are in the same boat as K10! Wow! I did'nt know that!
Send me the adb system dump, other files you collected and the firmware file if you have it.
I am developing a root method for Android 6.0 with help of other devs. I can port that script to your device if you want.
Its better if you contact me on What'sapp so we can talk about getting into fastboot and root stuff and I can help you easily. I could help you build a TWRP for your device. I sent my number to you as a private message.
Click to expand...
Click to collapse
wait a moment... does this mean there is a chance deleting my download mode and screwed up updates was not completely useless?
MRMACGEEK said:
wait a moment... does this mean there is a chance deleting my download mode and screwed up updates was not completely useless?
Click to expand...
Click to collapse
Yes, sir! That's what I am basically working for...
pvineeth97 said:
Yes, sir! That's what I am basically working for...
Click to expand...
Click to collapse
well, i can only teel you im extremely grateful and happy to havegiven you an entrypoint of some sort
MRMACGEEK said:
well, i can only teel you im extremely grateful and happy to havegiven you an entrypoint of some sort
Click to expand...
Click to collapse
Actually it even motivated me more to get root for Android 6.0!
Two cents
Sands207 said:
Thank you so much! I'm getting out of work in a little over an hour and ill try to gather as much as i can that I have for files to help the process. I will add you on whatsapp too. I'm shaking right now hoping this 3 month ordeal to fight for root and unlocking the bootloader will soon be over. Many jumped ship already but ive been trying to tell these guys from the beginning there HAS to be a way, I know this because I worked on the LG Volt which had similar woes but were eventually overcome I'll Be in touch shortly. THANK YOU
Sent from my LGLS676
Click to expand...
Click to collapse
I'm in the long thread on Androidforums.com about the LGLS775 Stylo 2 (MM 6.0) too.... Caught the entire zd4 upgrade file if that could help, download links somewhere in the thread & few other posts in XDA on this device. If you think it could help, let me know & will toss a download link in.
Got notice on Nougat upgrade... gonna factory reset, logcat it & intercept it as well.....
GREAT JOB IN HERE!!!!
zach
ps. Zd4 is 1.4gb

Galaxy S4 Play Edition (GT-I9505G) and Lineage OS 15.1

Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.
Did you check the updater script to ensure the phone's model # is included?
audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.
audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.
I guess the only other thing would be to try different versions of TWRP.
audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.

Modem not turning on issue

Hey guys, would really need he help of the very well knowledgeable this this particular phone and the way it works as far as the modem software and hardware wise......
Issue: my modem will not come on, so I will get no service in ANY way, shape, or form no matter what I do.
Things I have tried: go into *#*#4636#*#* menu and attempted to turn on radio, the slider does move to turn it in, but nothing happens. If I leave this menu, and come back, that slider is ticked off. If I go to settings and go to mobile data area, it tells me to "turn off airplane mode" ITS NOT EVEN ON!!!
Brief history of device.....
Was working perfectly fine, had bootloader unlocked, had a custom ROM on it for like 5 or 6 months, no issues. Until one day, the bottom mic just stopped working. No one could hear me talk. Only top mic worked for recording video. Ordered the bottom daughter board that has the mic on eBay, it was the one for my phone, A2017u, no issues at all installing it. Pretty straight forward, I've repaired many phones in my day, this worked for like 1 month. Then I suddenly had software issues, random restarts, kept getting process error so frequently I could do anything on the phone....everything Google ND Android related processes kept crashing making phone inoperable. Decided to reflash the SAME ROM I had without formatting data, I've done before, just had to update system apps of course...bad move. Less crashing, but still crashed and stopped getting service. Only wifi worked. In light of all this....I decided to just EDL back to B21, or whatever the latest one is for my phone, did it through emergency download mode, because phone was inoperable. Everything flashed fine as far as the screen prompts. Phone booted, first took way longer then usual 5-10min, like 15-20. But it booted. I set up everything....STILL NO MODEM!!! I even though the daughter board was defective, emailed the eBay store, they sent me another one, kudos to this guy, he took care of me. Changed the board again, still no MODEM........the only difference I'm noticing is Everytime I boot up the phone, I get a black warning screen saying phone is not protected or something, with the word "START>" on the top right to press volume up or down, not sure which to enter a menu or do nothing and it will start normal. I've never had this before I flashed the EDL.
Any advice or help towards the right direction would be greatly appreciated. Thank you guys in advance.
Sent from my Moto Z (2) using Tapatalk
did you flashed your correct modem for your axon model?
Predatorhaze said:
did you flashed your correct modem for your axon model?
Click to expand...
Click to collapse
I believe it did, as i mentioned, i flashed the full edl package.....doesn't it include the modem??
kevace1 said:
I believe it did, as i mentioned, i flashed the full edl package.....doesn't it include the modem??
Click to expand...
Click to collapse
What model you have and what edl package you flashed? If you flashed China edl firmware you get China modem,USA edl firmware USA modem etc...you need to flash modem seperate
I got the same problem since yesterday. My device was away for a battery replacement some days ago. After I get it back everything was fine. Yesterday the modem stopped working. In my option I changed nothing. I just get no signal anymore. I'm still on 14.1 Nougat. I have tryed to flash the modem again, made a system, EFS, bootloader and twrp recovery but nothing worked so far. I also tryped to reset network settings and tryed another sim card..
Predatorhaze said:
What model you have and what edl package you flashed? If you flashed China edl firmware you get China modem,USA edl firmware USA modem etc...you need to flash modem seperate
Click to expand...
Click to collapse
I'm pretty sure I flashed the USA edl as I have the USA model. I know I need the USA one, not new to flashing things. But your saying I would have to flash the modem as well even after the full EDL flash?
Sent from my Moto Z (2) using Tapatalk
Here is the screenshot of the phone itself. I'm on it now that I'm home. So I guess I use the edl tool from DJ and flash the modem again is the consensus?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, I can tic the mobile radio on, which I did, but if I leave it and let come back it's ticked off ...
And in the second picture you see after I insert my sim car...it'll give a prompt of a voicemail I have, but I get no service.....
Sent from my ZTE A2017U using Tapatalk
Sorry, it didn't let me attach the screenshot from the phone in my previous edited post, told I didn't have permission to post attachments....lol
Sent from my ZTE A2017U using Tapatalk
kevace1 said:
Sorry, it didn't let me attach the screenshot from the phone in my previous edited post, told I didn't have permission to post attachments....lol
Click to expand...
Click to collapse
Using two neurons was enough for me to figure out that you flashed two different U packages, i.e. did nothing wrong. These packages WILL flash a modem, which is fine.
I don't think flashing a modem will automagically fix your issue, but it's worth trying. If you have TWRP, simply get a modem file from somewhere (for example the LOS threads, 14.1 has an old one but it works, also try 16.1's modem) which of course has to be for your model, and flash it. You can also extract the non-hlos.bin from an official zte update, change its extension to .img, then either flash via Fastboot (fastboot flash modem non-hlos.img) or via TWRP (install - install image - to Modem - select the file)
If nothing works.try wiping all partitions including vendor and reflash.Your modem is included in the USA edl firmware,
Predatorhaze said:
If nothing works.try wiping all partitions including vendor and reflash.Your modem is included in the USA edl firmware,
Click to expand...
Click to collapse
Doesn't doing a EDL flash formats all partitions? I do have twrp, that is the only other think I did after flashing the EDL. In any case, I agree to try the re-format everything and try the flash again...what would be the steps to do that correctly, so I don't brick the phone, though I know it seems it's pretty hard to permanently brick this phone, I prefer not to be the first loser to do it.....
Sent from my Moto Z (2) using Tapatalk
By the way, this is the black warning I get Everytime I boot my phone..........this started to occur after I flashed the EDL package..also wanted to add I never re-locked the bootloader to do the flash....could that have to do with my issue
Sent from my Moto Z (2) using Tapatalk
kevace1 said:
By the way, this is the black warning I get Everytime I boot my phone..........this started to occur after I flashed the EDL package..also wanted to add I never re-locked the bootloader to do the flash....could that have to do with my issue
Click to expand...
Click to collapse
That warning is completely normal. It appears if you have an unlocked bootloader. I have it myself. Not gonna remove it tho as its easier to get into recovery (by pressing volume buttons a menu appears on which recovery, fastboot etc can be selected)
kevace1 said:
By the way, this is the black warning I get Everytime I boot my phone..........this started to occur after I flashed the EDL package..also wanted to add I never re-locked the bootloader to do the flash....could that have to do with my issue
Click to expand...
Click to collapse
Never relock the bootloader... Makes zero sense, and you'll brick the phone if it is not fully stock.
and yeah, the 5 second screen is just normal
Choose an username... said:
Never relock the bootloader... Makes zero sense, and you'll brick the phone if it is not fully stock.
and yeah, the 5 second screen is just normal
Click to expand...
Click to collapse
I hear what your saying. But the weird thing is I never ever has this screen until I flashed the EDL. Obviously, I've unlocked the bootloader way before I started having issues with phone. And I never got this screen.... ever. What triggered it to start popping up now??
Sent from my Moto Z (2) using Tapatalk
kevace1 said:
I hear what your saying. But the weird thing is I never ever has this screen until I flashed the EDL. Obviously, I've unlocked the bootloader way before I started having issues with phone. And I never got this screen.... ever. What triggered it to start popping up now??
Click to expand...
Click to collapse
What rom did you use before?
Edit: nvm. I just read op again.
It was because of the custom rom you had flashed before that there was no warning screen (the rom probably contained a patch to remove it).
All stock roms have have this warning. So don't worry about that
GodOfPsychos said:
That warning is completely normal. It appears if you have an unlocked bootloader. I have it myself. Not gonna remove it tho as its easier to get into recovery (by pressing volume buttons a menu appears on which recovery, fastboot etc can be selected)
Click to expand...
Click to collapse
It appears he got a modified bootstack,,this screen does not proof the bootloader is unlocked.When you flash a edl stock firmware with these new bootstacks and your bootloader is locked,you still get this screen
Predatorhaze said:
It appears he got a modified bootstack,,this screen does not proof the bootloader is unlocked.When you flash a edl stock firmware with these new bootstacks and your bootloader is locked,you still get this screen
Click to expand...
Click to collapse
The lack of it doesn't prove that it is locked, which is not the same. While I have never heard about what you said of locked BL and stock firmware (shouldn't happen at all - are you sure you had the bl locked?) he said that he had unlocked the bootloader, and usually the unlocking packages for the G and U flash the modified aboot and fbop files that give you fastboot and get rid of the 5 sec screen. That's what happened. After flashing something else, those files were replaced and the screen appeared, nothing catastrophic
Can you link to whoever said that he got the screen with a locked bootloader? or was it you who had that happen?
Choose an username... said:
The lack of it doesn't prove that it is locked, which is not the same. While I have never heard about what you said of locked BL and stock firmware (shouldn't happen at all - are you sure you had the bl locked?) he said that he had unlocked the bootloader, and usually the unlocking packages for the G and U flash the modified aboot and fbop files that give you fastboot and get rid of the 5 sec screen. That's what happened. After flashing something else, those files were replaced and the screen appeared, nothing catastrophic
Can you link to whoever said that he got the screen with a locked bootloader? or was it you who had that happen?
Click to expand...
Click to collapse
i also flashed the edl package with locked bootloader,but now i remember it was the china edl.And that screen showed up(with locked bootloader).It should not happen with the corresponding model.My mistake,lol
Predatorhaze said:
If nothing works.try wiping all partitions including vendor and reflash.Your modem is included in the USA edl firmware,
Click to expand...
Click to collapse
what would be the best way to completely wipe all partitions? i thought going through EDL does all of this already??

Categories

Resources