Related
Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?
xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Anyone else?
[email protected]
xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.
this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...
Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.
Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.
I followed some tutorial in this site https://goo.gl/fz0bIx and now i can't fix the wi-fi mac address (appears as 02:00:00:00:00) and it can't find the wifi networks
Can anyone help me?
Please tell what you have flashed
garva1 said:
Please tell what you have flashed
Click to expand...
Click to collapse
I followed the tutorial and flashed this: https://dl.twrp.me/athene
followed the next steps on the tutorial and flashed this: https://drive.google.com/file/d/0B3TKzy1UugHNT1RvNURsWmRoMVk/view
and then installed the supersu as described there: https://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
The wifi does not work (gives me the strange address) and i don't know if this is related to a corrupted /persist partition. The wifi folder inside it has no files.
----
I think the issue may be related to this (not sure tho): the ROOT files are for "athena 1641/1643" model. I have "athene 1626" model.
If it is related to the files i pointed above, how do i fix it? Is Returning to stock rom the right way?
----
DTV module is faulty too. Probably the thing i flashed corrupted it too.
I have the same problem!
May I make the claim that there's no working root available for Moto G4? I had this problem as well.
I jumped from Moto G1 to Moto G4 a couple of weeks ago. I tried to root it immediately after I received my device. I came across with several posts talking about the rooting process. By following those instructions, I got a clean backup after installing TWRP and before doing anything else. Then I tried to install SuperSU for a couple of times with different versions from 2.36 to the latest one 2.74 - NONE of them worked. It left you a non-bootable Moto G4. it stopped at the Moto logo - no animation of changing to Lenovo logo. I have to restore my phone over and over again.
Suddenly, I found the one posted above and flashed the modified boot.img. It can boot the device. However, before I tried to check if the root was successful or not, I noticed the wifi problem. Then I realised that the modified boot.img might be ONLY suitable for Moto G4 Plus (I don't know if it really works, I have not G4 Plus to test - it's just a guess!). So I make a full restore and get the wifi working now.
That's my attempts on rooting Moto G4 till now. If anyone has a working root, please tell us the process.
libralibra said:
May I make the claim that there's no working root available for Moto G4? I had this problem as well.
I jumped from Moto G1 to Moto G4 a couple of weeks ago. I tried to root it immediately after I received my device. I came across with several posts talking about the rooting process. By following those instructions, I got a clean backup after installing TWRP and before doing anything else. Then I tried to install SuperSU for a couple of times with different versions from 2.36 to the latest one 2.74 - NONE of them worked. It left you a non-bootable Moto G4. it stopped at the Moto logo - no animation of changing to Lenovo logo. I have to restore my phone over and over again.
Suddenly, I found the one posted above and flashed the modified boot.img. It can boot the device. However, before I tried to check if the root was successful or not, I noticed the wifi problem. Then I realised that the modified boot.img might be ONLY suitable for Moto G4 Plus (I don't know if it really works, I have not G4 Plus to test - it's just a guess!). So I make a full restore and get the wifi working now.
That's my attempts on rooting Moto G4 till now. If anyone has a working root, please tell us the process.
Click to expand...
Click to collapse
I did not make a backup (stupid, i know). I'm trying to find a rom that works but had no success. The one i've found is giving me an error in twrp. I just want to get it back to original :/
lokinmodar said:
I did not make a backup (stupid, i know). I'm trying to find a rom that works but had no success. The one i've found is giving me an error in twrp. I just want to get it back to original :/
Click to expand...
Click to collapse
Try to search in this page: wwwDOTfilefactoryDOTcom/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Remember that our Moto g4 is XT1622. there're some on that page. I did download them in case something went wrong while rooting. but i never flash them - thanks to the backup. There's one said XT1622 specifically in the file name but it also said TESCO. I'm not sure if it's for TESCO network only or not - better to try. Someone mentioned that the file 'XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip' contains the XT1622 image and thought to be correct as it appears in the file name. I also tried 'mfastboot.exe getvar all' before the modification. The saved txt file from that command has the same version information: Athene 6.0.1, MPJ24.139-23.4.
Anyway, try to get the stock rom and flash it. Reboot to see if the wifi worked. If so, fastboot and flash TWRP and that's it - do not proceed any further. For the time being, we have to be patient for a working root method on Moto G4. I just cannot understand why people are writing some 'INSTRUCTION' they don't know if it worked or not.
libralibra said:
Try to search in this page: wwwDOTfilefactoryDOTcom/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Remember that our Moto g4 is XT1622. there're some on that page. I did download them in case something went wrong while rooting. but i never flash them - thanks to the backup. There's one said XT1622 specifically in the file name but it also said TESCO. I'm not sure if it's for TESCO network only or not - better to try. Someone mentioned that the file 'XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip' contains the XT1622 image and thought to be correct as it appears in the file name. I also tried 'mfastboot.exe getvar all' before the modification. The saved txt file from that command has the same version information: Athene 6.0.1, MPJ24.139-23.4.
Anyway, try to get the stock rom and flash it. Reboot to see if the wifi worked. If so, fastboot and flash TWRP and that's it - do not proceed any further. For the time being, we have to be patient for a working root method on Moto G4. I just cannot understand why people are writing some 'INSTRUCTION' they don't know if it worked or not.
Click to expand...
Click to collapse
I'll search this site. My phone box says XT1626 (Brasil version with DTV)
Update:
Flashed the 1626 version from the site using mfastboot and this sequence: This Post
Now it seems to be working fine (gotta test DTV. It found the channels but my signal is bad so...)
WIFI is alive and well ^^
lokinmodar said:
I'll search this site. My phone box says XT1626 (Brasil version with DTV)
Update:
Flashed the 1626 version from the site using mfastboot and this sequence: This Post
Now it seems to be working fine (gotta test DTV. It found the channels but my signal is bad so...)
WIFI is alive and well ^^
Click to expand...
Click to collapse
How you solved the WiFi issue.
garva1 said:
How you solved the WiFi issue.
Click to expand...
Click to collapse
Just flashed the entire XT1626 firmware using the sequence i posted above. No issues at all. Phone working completely fine
Help!
I have the same Issue, my MAC-Adress shows some bull***t and my WiFi wont show anything. I already tried to flash two different XT-1622 ROM's but it did NOT help me at all. I now will also try to flash the XT-1626 ROM, hoping that it will somehow fix my device. If anyone who sees this has an idea how to fix this or encountered the same problem and already fixed it, please notify me.
Thank you.
EDIT:
Turns out, that I am the biggest retard and not worth living on this world anymore.
I always executed the different ROM-Flashes by using the default batch-file given by the "how to reset" post creater... But instead of putting it in the core directory of the extracted zip i just put it in the mfastboot folder. Ofcourse, it executed very fast, i couldnt read the error codes, but my device always just resetted itself, and restarted. I thought it already was a new rom flashed, but it actually was the same over and over again. Now i found out, flashed one xt-1622 rom and its back up, working
God I feel stupid now.
TomasWilson said:
I have the same Issue, my MAC-Adress shows some bull***t and my WiFi wont show anything. I already tried to flash two different XT-1622 ROM's but it did NOT help me at all. I now will also try to flash the XT-1626 ROM, hoping that it will somehow fix my device. If anyone who sees this has an idea how to fix this or encountered the same problem and already fixed it, please notify me.
Thank you.
Click to expand...
Click to collapse
Which model is in the phone box barcode? I followed that and managed to make my phone come back to life following the steps i posted above
Sent from my Moto G (4) using Tapatalk
lokinmodar said:
Which model is in the phone box barcode? I followed that and managed to make my phone come back to life following the steps i posted above
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
I cant actually look at the box, because I dont know where it is right now. I am actually pretty sure it was an XT-1622.
There is a tag on the phone's battery. Model is in there too. What country are you?
or you can use the command I posted above: mfastboot.exe getvar all
there's a line said something like: (bootloader) sku: XT1622
that's the model. it's better to make backup and record as many information as possible before doing any modifications.
Hi, i have same problem. Please, can you tell me any way around not installing stock rom again or another custom rom to see if it has wifi fixed or if all fails, install stock rom
Please any way to fix the wifi problem?
Yudi313 said:
Hi, i have same problem. Please, can you tell me any way around not installing stock rom again or another custom rom to see if it has wifi fixed or if all fails, install stock rom
Please any way to fix the wifi problem?
Click to expand...
Click to collapse
Where do you see this bogus address?
I;ve unlocked and rooted 2 Moto G4 XT1625 phones that show this bogus address in a wifi widget I use on my home screen. I don;t seem to have a problem connecting to wifi. When I go to Settings about phone status I see the correct address
I used to see it on the advance settings in wifi.. however, I like Android so I play alot with it if you ever get any problem make sure you have a stock mpj or npj Rom with fastboot flash compatibility. And flash all the. Image sparse chunk :good:
After updating to Nougat, the bogus 02:00:00:00:00:00 address still displays on my wifi widget but displayed correctly in settings. No problem getting connected to wifi networks.
Sent from my Moto G (4) using Tapatalk
Hello, Ya all... hope you're doing fine.
I searched for days to find a serious guide to root moto c, xt1754, and wasnt successful. Now, am an older guy and I sure cant dive as deep as you do into that area Had me a fine Moto G and rooted it with XDA know how pretty good. Unfortunately this device got stolen a few weeks ago. Since am not a rich man and that I needed a new device, I got the Moto C. I can see for myself thats a pretty simple piece... but till am able to get a better Moto - I'd like to root XT1754 either. So, is anyone willing to help me? Could I use the files I once successful used for Moto E and G, logically updated?
Is Moto C another kind Moto E?
Hope I'd describe my case well enough for you. I also truly hope someone might have mercy with me and can let me know what I've to do.
Wish you all a Good Time at All.
Tyd27
In short, no, you cannot use the same files as on previous gen Moto's. The reason behind it... quite simple: they have absolutely nothing in common. This Moto C sports an MTK processor, to begin the long list of differences.
What you can try is this:
1. Unlock your bootloader. Either via Motorola Developer Website, or via fastboot oem unlock.
adb reboot bootloader
fastboot oem unlock
OR
fastboot oem unlock UNLOCK_CODE_FROM MOTOROLA
Once you're done with that, re-enable USB Debugging and OEM UNLOCK ( if you need to turn it back on ).
Then install the latest Magisk app from www.tiny.cc/latestmanager
At this stage, you will need your original boot image ( from here: https://www.needrom.com/download/moto-c-4g-xt1754-nrd90m-054-row-official-rom/). You will need to register there, and wait basically until forever for that firmware file to finish downloading. Open that up with 7zip and extract it. Find the file called boot-signed.img.
Patch it using Magisk.
move that patched_boot.img in your ADB directory.
adb reboot bootloader.
fastboot flash boot patched_boot.img
At this point, 2 options:
a. It will flash, in which case you will do fastboot reboot
b. it will not flash, in which case you will get an error ( boot image not signed etc)
If the first option occurs, you might get a "corrupt" error screen upon reboot. Follow the steps and let the phone do a factory reset. If it reboots properly, re-install Magisk and enjoy root.
if it does not want to reboot properly... you'll congratulate yourself on having the firmware handy
So, thanx alot for this answer. Am happy that someone took care now coz i really dont like unrooted devices. Well, the other side is am 58 now and not a professional at phones. Rooted a few motos with xda help and all went good. Unfortunately my last moto g got stolen and fir what reason ever else i chose to get moto c. Probably it was realky damn ****n stupid. Until i can afford another moto i going to try everything to root moto c. I'll read your reply now before i start doing it. Too bad that there is no way rooting it like moto g. Does it mean i wont have twrp neither?
Have a Good Day.
Tyd27
Definitely no TWRP on it, until someone with the knowledge will port it. That's just how it goes with MTK Devices and their closed source, I'm afraid.
Hi can u make a custom recovery for moto c xt1754
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-1-0-moto-c-t3703184
If your moto e4 XT1768 won't go into fastboot, try following the XT1767 instructions from here.
https://forum.kingfirmware.com/thread-Moto-E4-XT1766-XT1767-Dead-Boot-Repair
The instructions are for the XT1767 but I can confirm that I used those instructions to boot my XT1768 into fastboot. I hope this helps some people. : )
AceTheDolphinGuy said:
Hello
My moto e4 XT1768 is bricked and after talking to KevMetal, he informed me that a blank flash.mbn file in order to recover it using QFIL. He said he didn't have that file but suggested that I'd ask around if anyone had that file for the moto e4 XT1768 qalcom version. I'm also under the impression that it might be possible to use a working moto e4 to get that file. If that is the case would anyone know how to do that.
Thanks for your help, Ace : )
Click to expand...
Click to collapse
What you need is for someone to pull the mmcblk0.img from their xt1768 after doing a factory reset and then follow the instructions in this thread for the E4 Plus:
https://androidforums.com/threads/b...-to-stock-for-motorola-e4-plus-owens.1264881/
If you do everything right, it should work.
sorry, axadently posted twice
Jason M. said:
What you need is for someone to pull the mmcblk0.img from their xt1768 after doing a factory reset and then follow the instructions in this thread for the E4 Plus:
https://androidforums.com/threads/b...-to-stock-for-motorola-e4-plus-owens.1264881/
If you do everything right, it should work.
Click to expand...
Click to collapse
The instructions say that I have to boot into fastboot. But my phone won't boot into fast boot. But thanks for the help anyways.
AceTheDolphinGuy said:
The instructions say that I have to boot into fastboot. But my phone won't boot into fast boot. But thanks for the help anyways.
Click to expand...
Click to collapse
It won't without the necessary files properly written to an sdcard. If you read all the instructions, it says exactly what you need to do and if you did it all properly and numerous attempts don't work I'm not sure what to tell you. You do need to make sure to plug in your phone for a few hours prior to trying this because it won't boot at all if the battery is dead.
AceTheDolphinGuy said:
Hello
My moto e4 XT1768 is bricked and after talking to KevMetal, he informed me that a blank flash.mbn file in order to recover it using QFIL. He said he didn't have that file but suggested that I'd ask around if anyone had that file for the moto e4 XT1768 qalcom version. I'm also under the impression that it might be possible to use a working moto e4 to get that file. If that is the case would anyone know how to do that.
Thanks for your help, Ace : )
Click to expand...
Click to collapse
You can use xt1767 blankflash in order to restore xt1768..
Salik Iqbal said:
You can use xt1767 blankflash in order to restore xt1768..
Click to expand...
Click to collapse
Thank you so much. I found a xt1767 blankflash file here https://forum.kingfirmware.com/thread-Moto-E4-XT1766-XT1767-Dead-Boot-Repair and it worked.
What is the point of installing twrp and custom ROMs and magisk etc when we can't even remove this annoying Bootloader unlocked warning telling any would be thief to steal it. Im starting this here forum too see what we can do to change this. I have previously owned at ZTE Axon 7 4gb ram 64gb gold has a Snapdragon 820 in it. Your asking wtf does this have to with the op5t relax I'm getting to that. ZTE phone was amazing for awhile. Custom ROMs, kernels, recoveries etc. When you install custom ROM on unlocked bootloader you get the warning every time you boot up. A couple of devs or more I believe through XDA came up with a bootloader warning remover zip and custom splash images for the Axon 7 and it worked perfectly no more boot warning God I loved that. Now what I would like to do is to find away to modify that very script to work with the op5 and op5t. Basically the warnings are jpegs and the remover zip removes them from the bootloader and replaces it with the splash IMG or modified no splash IMG eliminating the warning completely. Wouldn't it be nice op5 and op5t users to flash custom ROMs and not have to worry about that annoying warning like forever. I will upload the ZTE post about the bootloader remover zip and splash images and see if some devs can't figure out how to modify that script. I know codeworx is one of the op5t maintainers who might be interested in this. I'll post again soon. Let me know who else is interested first thanks.
Interested... :good:
kirknado18 said:
What is the point of installing twrp and custom ROMs and magisk etc when we can't even remove this annoying Bootloader unlocked warning telling any would be thief to steal it. Im starting this here forum too see what we can do to change this. I have previously owned at ZTE Axon 7 4gb ram 64gb gold has a Snapdragon 820 in it. Your asking wtf does this have to with the op5t relax I'm getting to that. ZTE phone was amazing for awhile. Custom ROMs, kernels, recoveries etc. When you install custom ROM on unlocked bootloader you get the warning every time you boot up. A couple of devs or more I believe through XDA came up with a bootloader warning remover zip and custom splash images for the Axon 7 and it worked perfectly no more boot warning God I loved that. Now what I would like to do is to find away to modify that very script to work with the op5 and op5t. Basically the warnings are jpegs and the remover zip removes them from the bootloader and replaces it with the splash IMG or modified no splash IMG eliminating the warning completely. Wouldn't it be nice op5 and op5t users to flash custom ROMs and not have to worry about that annoying warning like forever. I will upload the ZTE post about the bootloader remover zip and splash images and see if some devs can't figure out how to modify that script. I know codeworx is one of the op5t maintainers who might be interested in this. I'll post again soon. Let me know who else is interested first thanks.
Click to expand...
Click to collapse
The more people with one plus 5t phones we can get interested in this project the better. It will force the developers to do something about it. So everyone interested please chime in with your thoughts on this. I loved it on the Axon 7 and the one plus 5t blows the axon away in ram and storage. Axon 7 still love the front firing speakers though lol. So please share your thoughts I'm trying to get as many oneplus 5and 5t users as I can. So show your love modders what do you think. You love custom ROMs like I do. You like to mess with your device to see what it can do. So do I but the bootloader warning has gots to go. If you'd like to check this out look up remove bootloader warning axon 2017g in chrome read up. I'll get the URL for this soon and it give you an idea of what I'm taking about thank
interested
I'm pretty sure a number of users would want this.. and I get it. It doesn't bother me that much though.
Personally, whenever that splash warning pops up, I just press the power button twice to pause then continue. This cuts the wait time for that warning and phone initiate the actual boot process right away and I'll be on my way.
Sent from my OnePlus 5T using XDA Labs
I'm also interested
This has been discussed before. The warning on the 5/5T isn't an image like it was on older devices. Since it's not an image, it's not a simple replace 'warning image' with another picture. You would need to modify the bootloader to ignore the verity check so the actual warning goes away.
I have seen one person get rid of the warning and that required him to build and sign all of his own packages. Essentially, he re-locked the bootloader and since all of his items were signed (properly) the device would continue to boot.
Edit: Found the post.
superatmel said:
You have to sign boot.img and recovery.img to remove the warning.
I have managed to eliminate it by signing those two images.
In my oneplus 5 and 5t I have twrp installed and with rom lineageos without warning.
Who wants to try to send me your boot and recovery and return it for you to try.
Remember that you have to close the bootloader whereby the phone will be wipe
Process:
fastboot oem unlock
unlock bootloader
You have to go back to fastboot mode
fastboot flash boot boot.img
fastboot recovery recovery_name.img
fastboot oem lock
Wuala
It can be done in any rom from firmware 5.1.5
Click to expand...
Click to collapse
kirknado18 said:
...
Click to expand...
Click to collapse
@kirknado18 THREAD CLOSED as a subject matter related thread already exists, to which the relevant posts from above have been copied: https://forum.xda-developers.com/oneplus-5t/help/remove-unlocked-bootloader-warning-t3841712
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse