yashsingh1/xdaforums huggingface dataset:
[Wing, P4350 General] jappo01:
Ease up drclip (doe s ff chill als je wilt dat mensen je helpen)! The point of an forum is to get to better results thru discussion and referrals so each comment has added value, though not always the value your looking for.

The link of duprade is quit usable; if you know what your doing

The answer to your question is remarkably simple; a search thru the different forums would have answered your question. But we're not to lame the help you on your way

You can find all original RUU, including the WWE edition, in these forum and the wikipage. If you flash this WWE edition RUU version to you p3450 you have the english toy. Since your flashing, you might try the Touch-It version. The same OS but enhanced and slimmed down to make it more userfriendly.

One warning before you start flashing; make sure you have read enough to be sure you know what you're doingand you don't brick your phone.

If you have a "vendor-id" error; you will first have to unlock your CID lock. Chech the Mobile 6 subforum and look for a post by canonyang_China on how to flash without CID-unlock

Enjoy!
[Wing, P4350 General] drclip:
Dank u :D

I will try this one canonyang_China

/dC
[Wing, P4350 General] drclip:
nothing work!!!

Just order a 4350 in Eng, it is better...

thanks for all
[Wing, P4350 General] canonyang_China:
It makes me mad when people who misunderstood what they have to do.

or did the things wrong.always like others come out and said:"no,nothing work!"

I just want to say:

is you not work? or is the damn thing not work?

learn more and try more before you give up.
[Wing, P4350 General] dcmtnbkr:
Someone correct me if i'm wrong, but couldnt he have flashed his original rom, used the aserg method and reflashed something like touch it in order to get it into english?
[Wing, P4350 General] drclip:
I do agree with u 100% although i did not have more patient and time to spend on this issue, please accept my appoligies for sure i made something wrong and did not work with my "old" toy, at the moment i have the new one, is working as it is suposted, i'm happy and move on.

thanks

/dC
[G4 Q&A, Help & Troubleshooting] laurct:
Hello guys!

I`m facing a problem on my lg g4.When i try to play some ts files , the sound is very very distorted.I`ve tried many video player ( mx, bs , vlc ) also using mx i`ve tried also the new codecs, but without any good results.The audio stream of that movie i tried to watch was 192kbps, 44.1 khz layer 3.In windows i don`t have any problem on playing that movie, but when i try to play it on my phone/tablet i can hear only distortion.

If anyone had and got it work plz post it here the solution.

10x
[Amazon Fire Phone] Heisenberg:
You already have a thread for this here:

http://xdaforums.com/fire-phone/help/amazon-fire-phone-day-totally-fine-t3447038

From our forum rules:

Thread closed.
[Note 7 Guides, News, & Discussion] apprentice:
.

Here's a random thought, what will we call the Note next year?

We have already had a Note 8 !! :confused:

.
[Note 7 Guides, News, & Discussion] rhadoo_ds:
Note 8 .. 2017 ? :P
[Note 7 Guides, News, & Discussion] HeavenlyFall:
Note 17
[Note 7 Guides, News, & Discussion] mankvl:
Note 8 2017
[Note 7 Guides, News, & Discussion] trickie69r:
Note 8 SE (second edition)
[Note 7 Guides, News, & Discussion] Devhux:
Wasn't the tablet called the Note 8.0?
[Note 7 Guides, News, & Discussion] LeadDawg:
The Notate..
[Note 7 Guides, News, & Discussion] Señor Sjon:
S8 Stylus or S8 plus. No point in having a seperate Note line if almost everything is the same as the previous S series.
[Note 7 Guides, News, & Discussion] kalinskym:
Interesting Point. I think Samsung didn't think they would reach Note 8 in 2013, so they called the Note 8 tablet, tablet. I wonder if they will remember that they sold the Note 8 already.

---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------

It's funny since Samsung did this name change to line up with the Galaxy S series but what do they do for 2017 Galaxy Note phone.

They bumped up the numbers too slow
[Note 7 Guides, News, & Discussion] apprentice:
Well technically yes. But apart from journalists and bloggers who actually called it the "8 point zero" ?
[Note 7 Guides, News, & Discussion] AB__CD:
Samsung Galaxy Note8 (no space as they've been doing since the Note5).

The tablet was the Galaxy Note 8.0
[Note 7 Guides, News, & Discussion] AllGamer:
We already had Note 7, before the Galaxy Note 7 came out just in the last few days ;)

Note 7 (tablet) vs. Galaxy Note 7 (phone)

so next year

Note 8 (tablet) vs. Galaxy Note 8 (phone)
[Note 7 Guides, News, & Discussion] Itchiee:
N8 or Nate
[Note 7 Guides, News, & Discussion] jcadduono:
Winner! I couldn't come up with anything to contribute because he already said it. :P
[Note 7 Guides, News, & Discussion] galaxys:
Note 7+1
[Note 7 Guides, News, & Discussion] wozzels:
Samsung Galaxy Note 8 Edge
[Note 7 Guides, News, & Discussion] AB__CD:
There has never been a Note 7 tablet.
[Note 7 Guides, News, & Discussion] Batfink33:
Galaxy Note 2017.
[Note 7 Guides, News, & Discussion] AllGamer:
I was thinking of this :D

[IMG="http://www.nvidia.ca/docs/IO/143913/TEGRA-promotional-TN7-4-mainimage.jpg"]http://www.nvidia.ca/docs/IO/143913/TEGRA-promotional-TN7-4-mainimage.jpg[/IMG]
[Samsung Galaxy J5 Questions & Answers] Joylopes25:
Model: Samsung J500F

Baseband: J500FXXU1BPF2 (Portugal)

Greetings to everyone.

My samsung j5 has a bug with the lock screen, which seems never ocurred with someone else.

It started when after i updated to Android Marshmallow after OTA updates and then i made a factory reset. After that i tried to put a Pin in lockscreen and after the pin was confirmed i locked the phone. When after a while i hit the button to turn the screen on it didnt asked the pin. In fact when i tried to change the pin in security settings it asked me a pin which wasn't the same that i put before.

To trying to solve this i though of doing a new factory reset, so i had to go to mysamsung.com to unlock the phone via remote controls and then i succefully reseted the phone.

The problem is that in the middle i forgot that and tried to do root but something went bad and i did lost the warranty but root didn't work. So a days after I tried to put a pass code and again the same error, this time asking for a password that didn't match mine.

I did some troubleshot:

-after Putting another pin the phone sends me to the previous page (security page) and instead of "pin" method to unlock screen it says "swip finger"

-it happens with passcode and pattern code too but when pattern code is choosed if i go to change it it firstly shows a pattern change screens but in a sec it dissapear being possible to put a new one and have the same bug

-I downloaded and installed a stock rom to my baseband and model (android 6.0 but my phone came with 5.1) and the error still exist.

-samsung support said to use smart switch initialization service but it says that my device doesn't support.

Notes: I didn't want to install a custom rom cause i like the samsung style.

Like i said: warranty is now voided (knox 0x1 (2)).

Any help would be apreciated.

Ps: I will provide screenshots and more info if needed.
[Samsung Galaxy J5 Questions & Answers] Joylopes25:
Solved

Hey everyone.

Turns out that after almost two months Samsung relased an updated that fixed this error.
[Samsung Galaxy J5 Questions & Answers] saeid.1980:
With installing the new update your phone baseband is still J500FXXU1BPF2 or something else?
[Samsung Galaxy J5 Questions & Answers] Joylopes25:
Actually with this new update the baseband still the same but when I updated the Android 5.1 to 6.0 the baseband changed.
[YotaPhone] krixoff:
Hello,

I would like to buy this smartphone, i like the dual screen concept.

But i live in France and i need 800 (b20), 1800, 2100 and 2600 bands (b7).

I would like to know if you bought this smartphone at banggood shop recently? If yes, please let me know what models did you received?

Because there are 3 models of this smartphone: 201, 205 and 206.

The 201 was the first one built in Russia in 2014.

Now this smartphone is built in China with 2 news models since March 2015 called 205 (for European market with all bands) and 206 for chinese market (without b20).

Thank you very much.
[YotaPhone] captkronos:
Under the BG QA section it states that it is the 206.
[YotaPhone] victro:
I bought from Banggood and it's 206.
[YotaPhone] RobertPS:
Hi, I have a 201 made in China in 2016, shipped from the Netherlands.

I bought it from Coolicool EU stock, it is still available.
[YotaPhone] cyberken:
Poor CS from Banggood

Buyers Beware: Elephone P5000 developed faulty battery whilst still in warranty. CSBanggood informed. Advised us to return phone, which we did. Now being ignored by customer service.

Have been regular customers with Banggood for a few years and told CS about fault whilst in warranty. Then returned the phone following their instructions... And waited and waited and waited... Currently being ignored over a phone that they are in their rights to return to elephone. Consider purchasing from other suppliers...
[YotaPhone] nutsoboy:
Hi, I bought from Banggood (October 9) and received a 206 (November 4 - 4 weeks to Australia).

I was able to flash OS to 202 RU (with the patient help of people on this forum), still only the Chinese bands of course.

I can say that it did come with the full retail box including earphones etc which were not included in the product description...

Good Luck with your decision!
[YotaPhone] victro:
You said that updated to 202RU? Did you mean 201? Is LTE works after update? Can you please explain how did you update or which

guide did you use?
[YotaPhone] nutsoboy:
UOTE=victro;69679044]You said that updated to 202RU? Did you mean 201? [/QUOTE]

Apologies for slow response, have had other priorities...

SORRY that was a typo, you're correct it is 201.

Actually I can't be sure (I live in a rural area) it's only showing 3G at present. My telephone company is supposed to use 1800 but the phone hasn't connected at this yet!

So i followed multiple advice here on the forum:

I had a major problem getting the computer (an old XP) and yotaphone_flasher software to see the phone.

Eventually I found that manually updating the USB drivers in Device Manager worked (by right-clicking on each driver and selecting Update from the drop-down menu) - after hours of frustration...

1/ I downloaded the latest chinese firmware CN/4.4.3-S01-003-CN1.0.3.32a.zip and this russian firmware: RU/5.0.0-RU1.1.124.zip.

2/ I extracted the Radio Folder from the Chinese zip, expanded the Russian one and replaced the Radio folder there with the Chinese version.

3/I placed the expanded/modified Russian firmware Program files/yotaphone/firmware

4/I rebooted the phone in Download mode by holding the down & power buttons down (after choosing restart) until the Downloading text appeared.

5/I ran yotaphone_flasher.exe and followed the prompts, using the cd command to navigate to the firmware folder.

The installer proceeded with the error reported elsewhere: something like "cannot load sytem.img"

Wait for the installer to finish loading the rest of the files then follow VirtuaLeech's instructions:

Good Luck!
[YotaPhone] victro:
Apologies for slow response, have had other priorities...

SORRY that was a typo, you're correct it is 201.

Actually I can't be sure (I live in a rural area) it's only showing 3G at present. My telephone company is supposed to use 1800 but the phone hasn't connected at this yet!

So i followed multiple advice here on the forum:

I had a major problem getting the computer (an old XP) and yotaphone_flasher software to see the phone.

Eventually I found that manually updating the USB drivers in Device Manager worked (by right-clicking on each driver and selecting Update from the drop-down menu) - after hours of frustration...

1/ I downloaded the latest chinese firmware CN/4.4.3-S01-003-CN1.0.3.32a.zip and this russian firmware: RU/5.0.0-RU1.1.124.zip.

2/ I extracted the Radio Folder from the Chinese zip, expanded the Russian one and replaced the Radio folder there with the Chinese version.

3/I placed the expanded/modified Russian firmware Program files/yotaphone/firmware

4/I rebooted the phone in Download mode by holding the down & power buttons down (after choosing restart) until the Downloading text appeared.

5/I ran yotaphone_flasher.exe and followed the prompts, using the cd command to navigate to the firmware folder.

The installer proceeded with the error reported elsewhere: something like "cannot load sytem.img"

Wait for the installer to finish loading the rest of the files then follow VirtuaLeech's instructions:

Good Luck![/QUOTE]

Thank you for explanation. As I understand that system.img flashing issue appears because the YotaPhone rooted before update. Was your phote rooted when you're updated it?
[YotaPhone] nutsoboy:
No not rooted.

My limited understanding was the issue is with available PC memory for the installer (my PC is ancient). Or perhaps the size of replacement system file is larger than what is being overwritten? It is common here on the forum...
[Android Software/Hacking General [Developers Only]] m11kkaa:
EFIDroid is a easy to use, powerful 2ndstage-bootloader based on EDKII(UEFI).

It can be installed one-click with the EFIDroidManager app. You can add/remove/edit multiboot ROM's.

There's no special support needed by ROM's or RecoveryTools(no kexec etc).

Supported devices

fairphone/fp2 (Fairphone 2)

motorola/condor (Motorola Moto E 1rd Gen)

motorola/peregrine (Motorola Moto G 4G)

oneplus/bacon (OnePlus One)

pantech/ef63 (Vega Iron 2)

FAQ

this is a UEFI port, can we port Windows?

no, trust me.

Can I still use fastboot after installing this?

If you flash to the boot/recovery partitions, UEFI will be overwritten.(dd in android/recovery instead). all other partitions work as usual.

I FOUND A BUG

Report it on Github. If there already is an issue for your bug and you don't have anything useful to add, just hit the thumbs-up button. This way I know how many people are affected and can adjust my priority list. I will not keep track of all bugs reported in posts of this thread. If you want a bug to get fixed, report it on github

Installation

Just download the EFIDroidManager App from the playstore and hit install.

XDA:DevDB Information

EFIDroid, Tool/Utility for all devices (see above for details)

Contributors

m11kkaa

Source Code: http://github.com/efidroid

Version Information

Status: Alpha

Created 2016-08-25

Last Updated 2016-11-11
[Android Software/Hacking General [Developers Only]] HelpMeruth:
can explain a little more what the benefit is?
[Android Software/Hacking General [Developers Only]] m11kkaa:
benefit over what? if you mean multitom: efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.

in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.

This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
[Android Software/Hacking General [Developers Only]] xdvs23:
Nice to see this, really interested in it... :D
[Android Software/Hacking General [Developers Only]] crazydude10:
Looks great ! Can this co-exist with existing multi-roms?
[Android Software/Hacking General [Developers Only]] m11kkaa:
EFIDroid uses a completely different concept and is not compatible with multitom.
[Android Software/Hacking General [Developers Only]] xenreon:
Love what you're doing here!
[Android Software/Hacking General [Developers Only]] core7x:
Worth to try.
[Android Software/Hacking General [Developers Only]] Manu99:
Probably this project has a lot of potential, why don't you publicise it a little more? Make some request to other devs so that they can note your work, and help you to support more functions and devices
[Android Software/Hacking General [Developers Only]] m11kkaa:
Thank you.

My publication skills are very bad :D but I guess I could scroll through device forums and PM a few talented devs.

Btw I spent the last 2 years working on this project(I had to build up an entirely new technical infrastructure) and before that I worked on Xiaomi Mi2 for 3 years(before Xiaomi was allowed on XDA) so I don't know who the big devs are on XDA :D
[Android Software/Hacking General [Developers Only]] xdvs23:
Work is actually going on behind the scenes for various devices, they should pop up here soon too.
[Android Software/Hacking General [Developers Only]] MSF Jarvis:
Sultanxda, arter97, Grarak will cover most of OnePlus for ya
[Android Software/Hacking General [Developers Only]] MishaalRahman:
[MENTION=3530648]m11kkaa[/MENTION] would you like to chat? I'm one of the XDA News Writers. We're interested in featuring your work.

Thanks to [MENTION=6552280]MSF Jarvis[/MENTION] for pointing us towards this amazing project!
[Android Software/Hacking General [Developers Only]] Trafalgar Square:
I will follow this :)
[Android Software/Hacking General [Developers Only]] m11kkaa:
1+1 is now supported too :)
[Android Software/Hacking General [Developers Only]] CBpbxEcmecmBeH:
i think 小米2 forums are missing you ;)

Great work, by the way!!!
[Android Software/Hacking General [Developers Only]] m11kkaa:
Fairphone 2 is now supported too :)
[Android Software/Hacking General [Developers Only]] avinashjirapure:
[MENTION=3530648]m11kkaa[/MENTION]

As per understanding, the project will make our device dual boot but unlike Multirom it doesn't requires any patched kernel. This is interesting... & surely exciting :)

I am using a nexus 4 (mako) with Android 7.1 r7 (Nitrogen-OS). Can you please enable support for Nexus 4?

Please let me know...
[Android Software/Hacking General [Developers Only]] m11kkaa:
yes that's right.

I can't just enable support for devices. Somebody who owns the device has to port it(it's pretty easy though).

You should ask one of your device's big developers.
[Android Software/Hacking General [Developers Only]] avinashjirapure:
That's super prompt reply :)

I won N4 but unfortunately I am not dev.

But has some understanding so If you could share porting procedures I may give a try... & if that didn't work... Surely will ask some N4 dev to help to port.
[Android Software/Hacking General [Developers Only]] m11kkaa:
well u'll need to boot stuff at some point. you can boot/flash to lk.img in whatever way works best on your device. finalize does only care about the device being in fastboot already.

If you can't boot lk.img because of a locked bootloaer u won't be able to boot uefi either.
[Android Software/Hacking General [Developers Only]] 5ud0:
This is awesome.Everything works great on my OPO even oxygen alongside nougat roms which is not possible with Multirom. One issue I am facing now is I am unable to set selinux permissive in my roms.

Even KAMod, Selinux Mode changer not working. They are showing that it is changed but the about rom is still showing enforcing. Anything I can do about that?

[MENTION=3530648]m11kkaa[/MENTION] Thank you for this! :)
[Android Software/Hacking General [Developers Only]] Anghirrim:
Which recovery version are you using?
[Android Software/Hacking General [Developers Only]] 5ud0:
TWRP 3.0.3-2-TugaPower
[Android Software/Hacking General [Developers Only]] Anghirrim:
Ok thanks. That's weird then. I can't flash anything with the very same recovery....

What's your primary internal rom?
[Android Software/Hacking General [Developers Only]] 5ud0:
Oh... I donno then. I might be lucky.

1) Primary is COS 13. That too I flashed it via fastboot to STOCK.

2) Installed TWRP

3) Installed Magisk from here https://github.com/stangri/MagiskFiles

4) Installed EFIDroid via App

5) Enabled all in the boot settings (Permissive,Terminal & all those)

6) And then I am able to install all the roms from there, the usual procedure. I took a proper TB backup, so I just restore my ID and restore my app data in all those.
[Android Software/Hacking General [Developers Only]] Anghirrim:
Ok thanks for all those details. I'll give COS 13 a try, I am currently back to Slimsaber 5.1.
[Android Software/Hacking General [Developers Only]] MMWolverine:
I have the same config with COS13 as primary, but experiencing all sorts of issues on Nougat secondaries (RR & LineageOS). For example Spotify won't work, same with Boeffla-config app (although Boeffla kernel flashed ok), problematic TB restoring etc.
[Android Software/Hacking General [Developers Only]] 5ud0:
Did you enable selinux to permissive and other options in the EfDroid menu?

I haven't done anything special, I stuck to the guide and followed the same steps.

Only issue I am facing is the permissive one and Play Services FC (Although I have that problem with multirom as well). Spotify is working fine for me. Even I installed Arise on all of them and that is working perfectly!

Edit : I installed RR-N with Lightning OOS and OOS blobs but on Lineage, I haven't installed any kernel.
[Android Software/Hacking General [Developers Only]] MMWolverine:
Yes, I enabled all the options in EFIDroid.
[Android Software/Hacking General [Developers Only]] dedraks:
All tools are downloaded by the build scripts.

I deleted everything and downloaded again.

Now I'm having anther errior:

make uefi
...
compiling /home/carlos/android/uefidroid/bootloader/lk/common/shared/uefiapi/main.c
compiling /home/carlos/android/uefidroid/bootloader/lk/common/shared/uefiapi/event.c
compiling /home/carlos/android/uefidroid/bootloader/lk/common/shared/uefiapi/mutex.c
make[3]: *** No rule to make target '/home/carlos/android/uefidroid/out/device/motorola/addison/lkuefi_kernel/build-msm8953//home/carlos/android/uefidroid/bootloader/lk/common/shared/uefiapi/target/msm8953.o', needed by '/home/carlos/android/uefidroid/out/device/motorola/addison/lkuefi_kernel/build-msm8953/lk'. Pare.
make[3]: Leaving directory '/home/carlos/android/uefidroid/bootloader/lk/qcom/LA.BR'
makefile:20: recipe for target 'make-make' failed
make[2]: *** [make-make] Error 2
make[2]: Leaving directory '/home/carlos/android/uefidroid/bootloader/lk/qcom/LA.BR'
out/build.mk:1057: recipe for target 'lkuefi_kernel' failed
make[1]: *** [lkuefi_kernel] Error 2
make[1]: Leaving directory '/home/carlos/android/uefidroid'

#### make failed to build some targets (14:17 (mm:ss)) ####

build/core/main.mk:38: recipe for target 'uefi' failed
make: *** [uefi] Error 2
[Android Software/Hacking General [Developers Only]] m11kkaa:
bootloader/lk/common/shared/uefiapi/target

you can copy the file msm8952.c to msm8953.c.
[Android Software/Hacking General [Developers Only]] dedraks:
Thanks.

Now it compiles. without errors.

When I try to boot uefi_boot.img from fastboot, the device shows it's splashscreen for one second or two and then reboot.
[Android Software/Hacking General [Developers Only]] m11kkaa:
sounds like hypervisor security. can you boot lk.img and run fastboot oem findbootimages and post the output?