yashsingh1/xdaforums huggingface dataset:
[Droid Turbo 2 Q&A, Help & Troubleshooting] lorissuper:
Hi guys I just boght the phone from gearb...I'm going crazy I'm not able to get work correct. I tryed all official ROM

I also think the best is the mexican one (becouse of hardware 64gb dual sim ecc) but wi-fi and phone net doesn't work, I've had the same "intuition" to use the chinese modem file (the only ROM that work with full connection is the officiale chinese one without playstore ecc ecc) I tryed to flash modem files (fsg.mbn and NON-HLOS) maybe I'm wrong? Should I reflash just with chinese version of fsg.mbn and mantain original NON-HLOS file of ROM?

p.s sorry for my english!

thankyou!

---------- Post added at 06:57 PM ---------- Previous post was at 06:41 PM ----------

UPDATE

The russian mexican modified Rom (with china modem) works perfectly to me, thanks [MENTION=769490]over[/MENTION]c you are amazing! so the secret is to flash a ROM just with fsg.mbn from china 5.1.1 ROM?
[Droid Turbo 2 Q&A, Help & Troubleshooting] rionline:
is this mexican rom moddiefied or shall i flash it exept fsg.mbn? by the way, what is this fsb.mbn?
[Droid Turbo 2 Q&A, Help & Troubleshooting] TheNextJames:
Naaa
[Moto G4 Plus Questions & Answers] gamester26:
I have a Moto G4 XT1625 (non amazon), US Retail, with a Beanstalk 7.1.1 custom rom installed. I want to downgrade back to stock firmware, but am afraid that I'll brick my device. Any help? Thanks.
[Moto G4 Plus Questions & Answers] trsix:
here ya go

---------- Post added at 03:43 AM ---------- Previous post was at 03:43 AM ----------

[/COLOR]Follow his video, He even has a link to your stock firmware if you click more.

It won't brick your device.

Pretty simple really :D

https://www.youtube.com/watch?v=_yiKhnFP2O0
[Moto G4 Plus Questions & Answers] gamester26:
I've heard that you need to do something different from downgrading from nougat though?
[Moto G4 Plus Questions & Answers] gamester26:
Never mind it worked. Thanks!
[Tilt, TyTN II, MDA Vario III General] niper1:
I just bought my tytn2 2 weeks ago and every thing is awesome :) except the camera. When i turn on the camera in my house the camera is really slow and if i move it slowly it blurs but if i am in a bright place like outside in the sun it works fine and it doesn't blur even if i move it fast can some one help me fix this problem. Thanks:)
[Tilt, TyTN II, MDA Vario III General] rohanmaini:
That is becasue of a combination of poor drivers & poor light...
[Tilt, TyTN II, MDA Vario III General] grizzley:
Teach a man to fish and he will eat for a life time......

SEARCH the forums. This has been discussed MANY times.

Searching is always the best option when you need an answer to a question. 99% of the time, it has already been discussed on these forums.
[Tilt, TyTN II, MDA Vario III General] niper1:
When i am outside it works fine when i go in the house the camera changes to a different mode and i becomes slow is there any way to keep the mode from changing
[Tilt, TyTN II, MDA Vario III General] fusi:
what did grizzley just tell you to do ffs
[Tilt, TyTN II, MDA Vario III General] g101:
Indoor has no sun, no sun means lesser shutter speed. Lesser shutter means darker photos and darker photos mean that the camera is boosting brightness on everyframe thats why you probably see the lag.

Outdoors isnt a prob coz you've got tons of light. Shutter speed can go up to 1/thousands of a second compared to 1/2 of a sec indoors.
[SuperSU] MalikDrako:
I have a rare phone running Android 6.0 on a MT6750 with an unlocked bootloader (might be MT6750T since it is 1920x1080, but the only things I have found say MT6750)

I have been unable to get TWRP working on this phone after trying several porting guides and TWRP images. Almost all port attempts result in the boot image (logo.bin - android logo), followed by a black screen for a few seconds, then it reboots into Android.

Is it possible to manually patch the boot.img to gain root? If so, can someone point me to a guide for it? I found https://xdaforums.com/android/software-hacking/systemless-root-mediatek-t3309909 but PATH doesnt seem to be set anywhere in my boot image (grep -nrw 'boot.img-ramdisk' -e "PATH"). I tried adding "export PATH $PATH:/data/bin" or "export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin::/data/bin" to init.environ.rc with other exports, but I get a boot loop
[SuperSU] shankar_vl:
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
[SuperSU] rajeshca911:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.

same with recovery.img also

btw im using oppo f3 mt6750t
[SuperSU] shankar_vl:
Then its a compilation error. Its not being compiled correctly.

Btw, systemless root by supersu and magisk do a lot things like starting sudaemon, injecting supolicy changes, mounting su.img, etc. Its better to port a custom recovery and let supersu or magisk zip do all the required things to root your device.

Or if you want to be ambitious, dirty your hands with hackings, unzip these zip files and try to implement manually what is programmed there.

My suggestion is go for porting recovery from devices matching your device specs ( need not be 100%). There are several threads on this forum helping you out on this. I think chances of porting a workable custom recovery are brighter than manually compiling su compatible boot.img.
[SuperSU] rajeshca911:
There's the problem..

I did port custom recovery.

But when I flash it back to device it's showin error.

I understand that I need to dirt my hands more to get root my device

So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
[SuperSU] shankar_vl:
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.

There are carlive image kitchen tools. get them here https://xdaforums.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.

What is more important now is that you have right tools for compiling imgs. Then you can think of further.
[SuperSU] rajeshca911:
Thanks bro. But im using carliv kitchen tools only.

I didn't tried with other kitchen tools yet.. So i give a try other tools
[SuperSU] shankar_vl:
no need. carliv tools are perfect. stick with them.

are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.

as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t and of OS version similar to yours as well.
[SuperSU] rajeshca911:
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)

Then...

I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)

Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..

seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device

Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
[SuperSU] shankar_vl:
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.

And about the other tools of flashing you mentioned, sorry I will not be helpful.

A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.

Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
[SuperSU] rajeshca911:
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.

However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)

As you said

1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series

2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.

3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..

I know its difficult to u to guide until u have hands on it or personally seen d procedures & results

I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
[SuperSU] shankar_vl:
I empathize with your frustration.

Truth is that with the devices which have not caught the fancy of developers, not having proven root methods, custom recovery, etc only, we take initiatives ourselves and learn the things the hard way which is essentially a true way learning. With popular devices having already so many developments, there is no scope for adventurism and fun as well.

Just see back what are all you gained in doing the things you did with your device for gaining root. Could it have been possible with the so called popular devices?

Now let's come to the issue. In all times of failed booting on compiled imgs, how did you restore them? flashing again stock boot and recovery imgs? and with tools you mentioned?

If you could flash stock boot and recovery with the tools you mentioned, then there is no problem with those flashing tools. Then it comes to the decompiling and recompiling of imgs.

If it could be possible, can you share here stock boot.img, and custom recovery you have selected for porting (also mention the device name, recovery pertained). Let me try.
[SuperSU] rajeshca911:
:DYup.. Bro.

What have you said all true.. during this journey i have learned so manythings like porting custom recovery , read back firmware etc and i cant forget what i have learned..:o so many trail and errors ;)

below link is the stock and custom recovery i tried to port

https://drive.google.com/file/d/0B6wWbhnrRZ_-V2RZQXByYjc4QVU/view?usp=drive_web

and a developer also tried to to port recovery for me .. below is the link which he modified for me

https://www.androidfilehost.com/?fid=745425885120760137

Im also enclosing stock boot.img

https://mega.nz/#!MF1ySQ4D!ku6RWfOP8QTkm75sNq_1_n-_Af0y843J0I0tiCHRa8k

My Device Details are

Manufacture : Oppo

Device name : Oppo f3

Model No : CPH1609

chipset : MT6750T , 4gb Ram , 64 Gb storage

[ I Really praying Inside ....:angel: god may give result for our endless efforts }
[SuperSU] shankar_vl:
[MENTION=5770404]rajeshca911[/MENTION] can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
[SuperSU] rajeshca911:
Aquired custom recovery from

Device : qukitel K6000 plus, chipset MT6750T

android version 6.0 (from below)

https://www.google.co.in/amp/s/xdaf...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
[SuperSU] anandverma458:
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[SuperSU] rajeshca911:
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?

---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------

i generated public and private keys also signed and generated

boot_signed.img

recovery_signed.img

first i flashed both the images... result was soft brick and i had to flash original boot.img

second i flashed only signed recovery.img and same was repeated.
[SuperSU] anandverma458:
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me

As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
[SuperSU] shankar_vl:
Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1ghmy76nfqd/modified_oppo_boot.img

Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)

I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.

http://www.mediafire.com/file/4als7qmpwdz1iv4/oppo_port_twrpv1.img

http://www.mediafire.com/file/5xz7387at6rr0dy/oppo_port_twrpv2.img

Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.

Best of luck
[SuperSU] rajeshca911:
Bro thanks for your advice.. and i did same what you have said.. i flashed stock boot.img with out rebooting flashed recompiled boot.img the device didnt boot up.. i think culprit is something else .. that prevets booting custom images
[SuperSU] rajeshca911:
Bro first of all Thanks for the efforts & time you allocated for my device.. coz you confirmed that verification was not in boot.img though i flashed your boot.img and the device didnt boot up. it showed an error saying boot was corrupted please take to service centre "so i have googled again and found interesting things about preloader.bin , below link was video tutorial to flash modified preloader.bin for mt6753 device

https://www.youtube.com/watch?v=YS1GFPJB53Q

he used modified preloader.bin to boot into custom recovery.img so i assume that preloader.bin have keys/checksums to verify the boot and recovery images

the same topic was going on xda

https://xdaforums.com/android/help/hacking-preloader-bin-t2909259/page3

but unfortunately i have no enough knowledge about editing preloader.bin so it may take some time google/learn and flash.

i believe your custom images will be prefect after deriving solution. i will update my progress soon. please do share if you know anything about the same.

Thanks in advance
[SuperSU] anandverma458:
Yes, a modified bootloader (preloader) is needed which can boot insecure images. It might be an older version of the bootloader. I too have flashed an older version of the bootloader, and the modified images fail to boot while on stock bootloader.
[SuperSU] rajeshca911:
did you edited your preloader.bin or you have downloaded it ??

if i flashed someone else preloader.bin like other mt6750 preloader.bin will it work ??
[SuperSU] anandverma458:
Flashing preloader is a very dangerous process, as it may readily in a fully bricked device if not flashed properly. The only option then is to get the motherboard replaced.

Also, I don't think flashing preloader of some other device is a good idea. idea.But mediatek is different than qualcomm... It might work, or it might not. I would recommend you to not flash some other device's preloader.
[SuperSU] rajeshca911:
Thanks for the tip.. I DONT flash other preloader.bin

But i do search for other ways.. If u know pls share in this thread
[SuperSU] anandverma458:
Sorry, didn't read your first question:p

I downloaded the emmc_appsboot.mbn (for qualcomm). The developer is a chinese guy on telegram. I will ask him about this and will update you if he tells me how he did it.

But I don't think that even his procedure would help, as mediatek uses preloader, but qualcomm uses emmc_appsboot, which (perhaps) are vastly different from each other.

EDIT: Have you tried fastboot oem unlock(ensure that allow oem unlock is enabled in developer options)?

---------- Post added at 02:38 PM ---------- Previous post was at 02:22 PM ----------

https://xdaforums.com/oppo-f1/how-to/boot-loader-unlock-twrp-related-t3397013/page11

Try following the steps mentioned in the thread. You have to flash the magictricks file through stock recovery. But be warned, it IS risky. If it suceeds (90%chance), then you will be able to boot modified images.

Best of luck!
[SuperSU] rajeshca911:
For my device.. ?

Oppo has removed fastboot/bootloader for its newer devices (mine is newest :) )

---------- Post added at 01:41 PM ---------- Previous post was at 01:38 PM ----------

Bro. I cannot flash that zip bro. Coz

My stock recovery only accept .ozip formats not zip. And I tried with renaming zip but it didn't work
[SuperSU] anandverma458:
I checked the contents of magictricks.zip, and found that it is valid for msm_15309 board, so it is not for your device...
[SuperSU] rajeshca911:
So will it be easy to unlock preloader?

Im still stuck. I didn't find any help online. But trying and keep asking devs.
[SuperSU] anandverma458:
Before vivo, I had an intex aqua power (mt6592). It did have fastboot, but couldn't be accessed with button press. Command from terminal worked to boot in fastboot mode.

If you can enter fastboot by connecting to pc and running adb reboot fastboot, please try to run fastboot oem unlock(will wipe data if it really unlocks the bootloader).
[SuperSU] rajeshca911:
I did tried

adb reboot bootloader

In terminal

Reboot bootloader

Not worked. I think. They somehow managed to prevent booting to bootloader at any manner
[SuperSU] anandverma458:
Is there an option to allow oem unlock in developer options?(settings<about phone<tap build number 7 times you will have developer options in settings)
[SuperSU] rajeshca911:
Yes.. There is.

But i dont know its working in favour of mine.

I always enabling oem unlock. But still corrupted image error showing
[SuperSU] anandverma458:
Either you modify the preloader file yourself to allow unsecure images to boot, or wait for a developer to post one on the internet.

Keep looking!
[SuperSU] rajeshca911:
Ok.

I wait. I dont have any option either

?
[SuperSU] 77777777777777:
hi,

Root the boot.img with magisk app and flash the rooted boot.img back with fastboot to phone.

I hope it helps.

Patch boot.img:

# 3. Download en installeer MagiskManager officiële site)

# 4. open de app en selecteer download / install en Patched Boot.img . Een terminal zal openen en patchen procces starts = wachten tot voltooid.

# 5. Ga naar sd0 (interne opslag) naar de map magiskmanager en open en kopieer vervolgens de Patched_Boot.img naar pc.

# 6. Installeer adb installer is eenvoudig te installeren op je pc (download hieronder)

Pre-voorbereiding voor fastboot:

# 7. Kopieer de Patched_boot.img naar je pc-harde schijf C: \ adb Map en hernoem naar " boot.img "

# 8. start je telefoon opnieuw op om snel te starten en connect-pc

# 9. Open command promp ( As Administrator )

# 10. En typ '' adb devices '' en Enter

je ziet in promp op pc of je telefoon succesvol verbonden is

Flash the Patched Boot.img terug naar je telefoon:

# 11. Typ vervolgens nogmaals Promp op pc

'' fastboot flash boot C: \ adb \ boot.img '' en Enter .

wacht tot je ziet dat Promp op pc

OKAY [0.281s]

klaar is. totale tijd: 0.767s

Herstart

Uw telefoon is geroot en u hebt geen root-app nodig
[Galaxy Note5 Q&A, Help & Troubleshooting] Clode:
Hi, i have a problem record video in UHD.

The most of times, the video are flickering or like losing frames.

The audio goes right, but the video fails.

Anyone has this issue? Any idea to solve?

The preview while record appears ok.

Thanks and Regards
[Asus Zenfone Selfie Questions & Answers] 01000010:
Hi, I bought a new zenfone selfie and it does not detect the headphones. (the radio asks for headphones and the music player plays only through speakers)

I have tried 4 different headphones which work fine on other phones.

I got the phone replaced by the seller and the new one presents the same problem.

Is this a known software problem? I am on the stock rom ww...1887...20160903

EDIT: Solved, once I installed CM 14.1 it worked ... it's a software problem
[Asus Zenfone Selfie Questions & Answers] arputhatonyking:
No it will work.
[Asus Zenfone Selfie Questions & Answers] Member 12345678910:
I have this problem too with my zenfone selfie, any solutions?

I have this problem too, any help?
[Asus Zenfone Selfie Questions & Answers] 01000010:
Solved.

It's a software problem.

I have flashed Cyanogenmod 14.1 and now headphones are recognized and radio works fine
[LG V20 Questions & Answers] Tilde88:
Hello, I am uploading my MOD ROM and kernel for Sprint. A previous attempt failed, and I just learned that the boot.img I had received was not the actual stock Sprint ROM, so the RAMdisk did not work.

Need someone, or some people to test, so I can make an official post in the ROM section.
[LG V20 Questions & Answers] Tilde88:
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.

Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).

Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.

Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.

(reuploading, old zip would not flash due to a typo)

Updated, fixed link : https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
[LG V20 Questions & Answers] ruthlessnature:
what is the decryption key? it will not allow me to download it without it.
[LG V20 Questions & Answers] Tilde88:
whoops
[LG V20 Questions & Answers] ruthlessnature:
thanks gonna download now and give it a go I will report back as soon as I can.
[LG V20 Questions & Answers] Tilde88:
hold on. i gotta reupload... there was a typo in the script >.> my bad
[LG V20 Questions & Answers] ruthlessnature:
Ok let me know when it's good to go.
[LG V20 Questions & Answers] Tilde88:
Here is the updated link

Sorry about that!

https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
[LG V20 Questions & Answers] ruthlessnature:
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
[LG V20 Questions & Answers] Tilde88:
How long are you waiting? First boot takes about 15 mins.

You still have to do whatever the static boot fix is.