Database Users

Official ZTE Open Fire Fox OS 1.2 and 1.3 builds thread

This thread is all about making it easier for those who cannot build Firefox OS 1.2 and 1.3 to get these updates to their phones.
Please post your build links here with pertinent information about the build. I hope I am right in thinking that builds done on 64 bit linux machines can be flashed by those with 32 bit linux machines. Feel free to add to this thread and I will merge the pertinent information and links to the top of the thread.

Hi donjuankey,
would you like 1.2 1.3 or 1.4 builds?

1.2 and 1.3 are the most needed. 1.4 is probably not worth the trouble at this point for most people but hey if you got it, it is welcome.

The rom has many bugs.

elboo said:
I just compile Firefox 1.3 for inari (from my zte OPEN EU version) follwing this how-to:
http://rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open/
{
"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"
}
In this "rar" are the files: system.img, userdata.img, boot.img and ramdisk.img from the compile.
https://www.dropbox.com/s/2a8h3qavzwutlnc/inari 1.3.rar
The boot.img is the modified version adapted for zte open commercial editions.
http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html
I would like to make a flashable zip for flash with cwm recovery to share the 1.3 rom, but not how to do it.
Sorry for my bad english.
Click to expand...
Click to collapse
Thanks!
Do I just flash these in the bootloader? or what's the best way to apply them. So far, when I attempted to flash these, I got errors.
Anyone know how to put these into a .zip file that can be flashed via CWM recovery?

Thank you.

Thank you!

zteOPEN1.3-signed.zip
not works

not works for me neither

elboo said:
Stock recovery or CWM recovery?
Click to expand...
Click to collapse
CWM, restarting after sitting fox

ZTE Open 1.3signed.zip didn't worked.
Tried from CWM and Stock Recovery as well

LinuxHolic said:
ZTE Open 1.3signed.zip didn't worked.
Tried from CWM and Stock Recovery as well
Click to expand...
Click to collapse
If you want to flash custom builds based on 1.1.0 you need to install ZTE's 1.1.0 firmware first
If you want to flash custom builds based on 1.0.1 you need to install ZTE's 1.0.1 firmware first
If you want to provide custom builds you need to specify which version did you used to build B2G

paziusss said:
If you want to flash custom builds based on 1.1.0 you need to install ZTE's 1.1.0 firmware first
If you want to flash custom builds based on 1.0.1 you need to install ZTE's 1.0.1 firmware first
If you want to provide custom builds you need to specify which version did you used to build B2G
Click to expand...
Click to collapse
I want to flash FF OS 1.3. I have currently installed FF OS 1.2 B2G Prerelease. I tried flashing the ROM provided on this link but it stucks on Fox Logo and keeps restarting
How can i flash THIS ROM?

no 3g connection lost after a while
Hello, thanks for your work first of all.
I have flashed 1.3 signed .zip via CWM. Everything works great, internet connection via wireless/3G.... etc (i'm writing from SPAIN, if it matters).
But after a while, the 3g connection does not works, only wireless. The H symbol is on in notifications bar and seams it is trying to connect but is not possible. The only way to turn 3G connection back working again is to put plane mode on for a while and try again. Or rebooting the phone.
Some similar experience? I' flashed it twice with complete wipe of my zte open.
Update: Surprisingly it's working 3g connection. To get it working fine:
If you are use wireless connection, to use 3g you have: (1) stop wireless connection, (2) enable plane mode, (3) disable plane mode, (4) enable 3g connection. In this way, there is not loose of connection.
But there is another problem. I'm using this smartphone as daily use and the alarm to get up at the morning. Two consecutive days I'm arriving late to my job ;-p . When I get up at the morning I see there is not any signal, no internet, no signal to call. And the alarm do not work at time. When I reboot the smartphone, the alarm sounds (2hr later). The alarm works fine later, but while i was sleeping, no signal, no connection...and no alarm. I will continue telling more things here

How?!
archymedes said:
Hello, thanks for your work first of all.
I have flashed 1.3 signed .zip via CWM. Everything works great, internet connection via wireless/3G.... etc (i'm writing from SPAIN, if it matters).
But after a while, the 3g connection does not works, only wireless. The H symbol is on in notifications bar and seams it is trying to connect but is not possible. The only way to turn 3G connection back working again is to put plane mode on for a while and try again. Or rebooting the phone.
Some similar experience? I' flashed it twice with complete wipe of my zte open.
Update: Surprisingly it's working 3g connection. To get it working fine:
If you are use wireless connection, to use 3g you have: (1) stop wireless connection, (2) enable plane mode, (3) disable plane mode, (4) enable 3g connection. In this way, there is not loose of connection.
But there is another problem. I'm using this smartphone as daily use and the alarm to get up at the morning. Two consecutive days I'm arriving late to my job ;-p . When I get up at the morning I see there is not any signal, no internet, no signal to call. And the alarm do not work at time. When I reboot the smartphone, the alarm sounds (2hr later). The alarm works fine later, but while i was sleeping, no signal, no connection...and no alarm. I will continue telling more things here
Click to expand...
Click to collapse
How did you flashed 1.3 using CWM?!
I can't!

LinuxHolic said:
How did you flashed 1.3 using CWM?!
I can't!
Click to expand...
Click to collapse
Yes, I used CWM
I can't insert urls for the tutorials, sorry , I'm new user and I have not that permission ;-p
So, I can tell you my problem was as very commented in internet:
"The bootloader on the ZTE Open does not allow to flash or boot unsigned code through fastboot protocol. The stock recovery image will verify the signature of update packages and not allow you to flash self-signed updates"
So write this in google, or this:
"ZTE Open FirefoxOS Phone, root and first impressions"
and you will find how to solve it (if it was your problem too). After that, you shoud install any ROM.

archymedes said:
Yes, I used CWM
I can't insert urls for the tutorials, sorry , I'm new user and I have not that permission ;-p
So, I can tell you my problem was as very commented in internet:
"The bootloader on the ZTE Open does not allow to flash or boot unsigned code through fastboot protocol. The stock recovery image will verify the signature of update packages and not allow you to flash self-signed updates"
So write this in google, or this:
"ZTE Open FirefoxOS Phone, root and first impressions"
and you will find how to solve it (if it was your problem too). After that, you shoud install any ROM.
Click to expand...
Click to collapse
My Phone is rooted and also have cwm installed but still can't install any custom ROM(1.3)
Stuck on bootloop
I currently have 1.2 prerelease

LinuxHolic said:
My Phone is rooted and also have cwm installed but still can't install any custom ROM(1.3)
Stuck on bootloop
I currently have 1.2 prerelease
Click to expand...
Click to collapse
First of all, I have to say that I'm only a simple user, I'm only reading around Internet and playing with the zte-open, so be careful ;-p
If you are root, great. I had problems to do that but I could ;-p
To install any custom rom (I installed v1.3), I installed CWM but you say you have it yet, so I don't know.
In my case I found the answer in gnulinux.vagos.es :
"Compilando/instalando la última versión de Firefox OS para el ZTE Open"
And precisely, the sub-section I followed was this:
"Desbloquear el ZTE para instalar "custom rooms" "
Have fun

Working build of today for ZTE Open (master, 1.4-prerelease, VARIANT=user). Maybe this one works for you. For me this boot.img works, but the other bootimages in this thread are not
This is in the zip: boot.img, system.img, ramdisk.img, userdata.img
https://cloud.kistlerfamily.info/public.php?service=files&t=991de577184209081f1c9860761edfd7

psywolf said:
Working build of today for ZTE Open (master, 1.4-prerelease, VARIANT=user). Maybe this one works for you. For me this boot.img works, but the other bootimages in this thread are not
This is in the zip: boot.img, system.img, ramdisk.img, userdata.img
https://cloud.kistlerfamily.info/public.php?service=files&t=991de577184209081f1c9860761edfd7
Click to expand...
Click to collapse
Thanks a lot!
is it necessary to flash ramdisk.img file?

Mobile Radio Not Working

Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!

Tgab100 said:
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Click to expand...
Click to collapse
You'll need to elaborate on how exactly you flashed back to stock.

Heisenberg said:
You'll need to elaborate on how exactly you flashed back to stock.
Click to expand...
Click to collapse
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.

Tgab100 said:
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Click to expand...
Click to collapse
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.

Tgab100 said:
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Click to expand...
Click to collapse
If you flash the factory images they overwrite what's already there.

Heisenberg said:
This is why I recommend people not use the damn things.
Click to expand...
Click to collapse
{
"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"
}

Heisenberg said:
If you flash the factory images they overwrite what's already there.
Click to expand...
Click to collapse
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.

Same here with SkipSoft Toolkit, after unlock, root, busybox, wifi noproblem, but no LTE/3G on my phone, i try to relock bootloader and back to Factory image now.
Sigh!?!

Tgab100 said:
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Click to expand...
Click to collapse
I honestly don't know what's going on there, it might be worth trying the L build instead of M.

Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.

badboy47 said:
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
Click to expand...
Click to collapse
I seem to have touched that issue I was on the L build and went to M build using toolkit but noticed my apns got screwy so I corrected them and I'm on pure nexus and a-ok now!

I'm having a similar but different issue, I bought a used 6p... Good ESN.... A 64 GB to upgrade from my current 32 GB 6p. Everything works (including mobile data and texts) except for phone calls, it won't call out and goes strait to voicemail when calling in.
I had unlocked the bootloader and installed chroma, but still no phone calls, so I flashed back to stock and relocked the bootloader. Still nothing. I read this thread suggesting that I shouldn't use the automated tool kits, so I backed up and manually flashed it back to the latest stock image via fastboot. But same issue.... Back to no phone calls in or out, everything else working though.
Any suggestions?
Justin

For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?

kboya said:
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
Click to expand...
Click to collapse
For me, yes. I can see my imei from the normal "about phone" settings menu.
Justin

Delete and readd your APN for your carrier.

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"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"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

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.

No possible way of getting into download mode. Please help. LG V20 H918 T-Mobile

I was able to root my phone and use it for a while but then it started reboot for no reason. It is currently running Oreo, H91820h.
I tried to restore to different earlier back up but same issue and a whole bunch of apps complain and terminate itself. Tried to flash Lineage OS and same problem.
So I tried to use LGUP to restore it to stock image but cannot get the phone into download mode.
When I hold the volume down button and plug in the USB cable, I get the fastboot screen.
{
"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"
}
When I hold the volume up button and plug in the USB cable, I get the "Download Mode" icon for about 2 second and then it switches to TWRP screen.
I remember when I first tried to install TWRP, it was version 3.2.1-3. Then I tried to flash twrp version 3.3.1-0 but for some reason, sometime it boots up with version 3.3.1-0 and sometime it boots up with version 3.2.1-3.
I cannot flash anything in fastboot or adb since it always come back with "FAILED (remote: 'unknown command')".
I have tried for over a week, read everything I could on the internet and tried everything but without success in getting into download mode to reload the stock image with LGUP.
Could anybody provide any suggestion or an alternate way of restoring the stock image without requiring going to download mode? May be re-flash with a different twrp version or remove twrp completely so it doesn't show up when I press volume up and plug in the USB cable.
Please, I am desperate. I can even send you the phone if you think you can fix it.
Thanks.

bqbase said:
I was able to root my phone and use it for a while but then it started reboot for no reason. It is currently running Oreo, H91820h.
I tried to restore to different earlier back up but same issue and a whole bunch of apps complain and terminate itself. Tried to flash Lineage OS and same problem.
So I tried to use LGUP to restore it to stock image but cannot get the phone into download mode.
When I hold the volume down button and plug in the USB cable, I get the fastboot screen.
When I hold the volume up button and plug in the USB cable, I get the "Download Mode" icon for about 2 second and then it switches to TWRP screen.
I remember when I first tried to install TWRP, it was version 3.2.1-3. Then I tried to flash twrp version 3.3.1-0 but for some reason, sometime it boots up with version 3.3.1-0 and sometime it boots up with version 3.2.1-3.
I cannot flash anything in fastboot or adb since it always come back with "FAILED (remote: 'unknown command')".
I have tried for over a week, read everything I could on the internet and tried everything but without success in getting into download mode to reload the stock image with LGUP.
Could anybody provide any suggestion or an alternate way of restoring the stock image without requiring going to download mode? May be re-flash with a different twrp version or remove twrp completely so it doesn't show up when I press volume up and plug in the USB cable.
Please, I am desperate. I can even send you the phone if you think you can fix it.
Thanks.
Click to expand...
Click to collapse
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?

bqbase said:
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?
Click to expand...
Click to collapse
Yes you need a motherboard
Or another phone
Sent from my Mi MIX 2S using Tapatalk

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
bqbase said:
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?
Click to expand...
Click to collapse
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
OMG, OMG, OMG, I got my download mode back. I am so appreciate your help. I wish I can send you a beer.
I must have gone through this lafsploit thread a hundred times but never paid attention to this "OPTIONAL" note and I wasted sooo much time refusing to post a question on this forum thinking I can find the answer just buy combing through the internet.
I believe you are dead on with reboot issue too. I got more than a few times with the phone complaining that wrong battery was inserted and need to shutdown. But I thought my un-experienced flashing of all the junks I did on the phone are causing it.
"OPTIONAL
If you would like to restore download mode onto your laf partition AFTER you have installed TWRP onto recovery:
Boot to TWRP that is on recovery
Flash this zip: laf_restore.zip
This can be done at any time after you are rooted. About the only reason you would want to flash laf back is if you use LG Backup.
TWRP has the ability to backup your phone, so I am not sure why someone would want this (maybe you are more comfortable with it?).
Also, flashing back to 100% unrooted stock can be accomplished by flashing a zip in TWRP, you don't NEED to flash a KDZ, but again, maybe you are more comfortable doing it that way.
The bottom line is TWRP on both laf and recovery is FAR FAR more useful than flashing laf back. You can test new versions of TWRP while keeping your old known working version (for example)."

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
I just want to say thank you to clsA and Phoenix591 for the help. I found the answer and was able to successfully restore my phone to 100% stock. I know it's hard to pinpoint the issue while trying to understand all the craps that people post on their question. Hit or miss, right or wrong, work or not, I really appreciate all the effort that you did to help me figure out the solution.

bqbase said:
I just want to say thank you to clsA and Phoenix591 for the help. I found the answer and was able to successfully restore my phone to 100% stock. I know it's hard to pinpoint the issue while trying to understand all the craps that people post on their question. Hit or miss, right or wrong, work or not, I really appreciate all the effort that you did to help me figure out the solution.
Click to expand...
Click to collapse
Guess I missed it on this one
V20 does have a lot of motherboard issue over the years. Apps crashing and phone rebooting randomly are 2 of them.
Glad you got it sorted and back to stock
Sent from my Mi MIX 2S using Tapatalk

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
Thank you very much, i can Relock and unroot my device with this, thank you so much

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
Hi I've happened to run into the same mistake however the link is broken. If you still have the file I would really appreciate the help.
I'm usually very careful when it comes to flashing but I made the mistake of trusting someone to unlock my V20 for global use, vendor told me they didn't know if they could do it since it was rooted and their unlocking software detected the root. He needed to remove the root and charge me extra. I trusted him into removing the root and pushed back the agreed upon date like three times. He kept saying he could not remove twrp. Long story short he told me he wasn't able to do it and gave me a discount, he said he was able to unlock it but was not able to power it on as it was bootlooping. I assume it was because he locked the bootloader and once I unlocked it again when I try to go into download mode to restore into LGUP it boots me into twrp instantly. Thanks in advance