yashsingh1/xdaforums huggingface dataset:
[General Topics] niits84:
Hi, Thanks for the reply. Well, I used to own a Nokia 7710(3.5" screen)...considered really big when it was out(friends actually made fun of me saying that i was carrying a pencil box or a brick) :) and well, to be honest..i loved it for its big screen ...Internet was a breeze on the big screen...so i would love the big screen on Ameo too...

Well, I guess it might fit(after some struggle)...I wear 32"...how does it perform,..is it fast and snappy. Comparisons to iphone or touch cruise will help immensely...
[X Style (Pure) Q&A, Help & Troubleshooting] silvernirvash:
so i recently got the pixel, had the moto x for about a year and decided to see what was going on with the rooting scene with this device. turns out that someone came along and created a simple solution to rooting and installing twrp for this device. I was happy. TWRP works just fine. But upon flashing SuperSU and rebooting from that i'm now stuck on the M logo permanently it seems. Yes i can reboot back into recovery and fastboot mode. But i can't seem to get past the M logo and all i've done was flash TWRP and SuperSU any idea about what's going on?
[X Style (Pure) Q&A, Help & Troubleshooting] SpasilliumNexus:
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.

The SuperSU zip from my thread does it: https://xdaforums.com/moto-x-style/development/rom-marshmallow-6-0-september-2016-t3536120
[X Style (Pure) Q&A, Help & Troubleshooting] silvernirvash:
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
No offense, but why are you bothering to root if you are just going to flash a ROM?

Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
[X Style (Pure) Q&A, Help & Troubleshooting] SpasilliumNexus:
That's exactly what my zip does. I've only put it together to make the process much simpler, and I love automating stuff when it's possible.

SuperSU inside is unmodified. Updater-script copies a file named "systemless" from the zip which has "SYSTEMLESS=true" in it to /data, renames it to ".supersu", then proceeds flashing SuperSU.
[X Style (Pure) Q&A, Help & Troubleshooting] kaleend101:
Hello all,

I need some help!I have a Moto X Pure Edition XT 1575 I just unlocked bootloader and then intalled TWRP 3.1.1 and then installed SuperSU 2.79 and now no Sim is detected. What did I do wrong?

Thanks!
[X Style (Pure) Q&A, Help & Troubleshooting] dzidexx:
Unroot & clean with supersu app. It should restore boot image.

/You can also restore boot, system, wipe data in twrp/

Reboot & check.

If ok try rooting with supersu 2.82 or

magisk 14.

[MENTION=6923927]kaleend101[/MENTION]
[XDA Assist] tb_durandil:
Hello

I have a problem with this tablet. It was used several people in my company. Someone tried to do a recovery but now, there's a message "this device was reset. To continue, sign in with a google account that was previously synced on this device". Nobody remember the account used.

I asked HP and they want me to pay nearly 400€ for that !!!

I think the USB debugging is OFF.

I can access the recovery mode by pressing POWER + VOLUME UP.

Options :

- reboot system now

- apply update from ADB

- wipe data/factory reset

- wipe cache partition

- apply update from sdcard

I tried wipe data and wipe cache partition, but same problem.

Can anyone help me ?

Thank you
[XDA Assist] xanthrax:
Hi !

Unfortunately it looks like the tablet has been locked by Google via the google account after a factory reset , account which has been set-up previously

I don`t think you have any option considering that the usb debugging has been not enabled so you can`t use any adb commands if there were any workarounds available

The recovery commands you have there doesn`t help on this matter

Basically the manufacturer is the one who can help you out

You can search on Google or youtube , the issue is called FRP bypass

Good luck !
[XDA Assist] tb_durandil:
Thank you
[G4 Q&A, Help & Troubleshooting] cp.engr:
I have an LG G4, on which I had installed a nightly Cyanogenmod build from June or so of 2016, with the Cyanogenmod recovery (not CWM or TWRP recovery). It was working fine...

I was planning on updating to the last CM (from Dec 2016), so I started poking around, wanting to do a backup first. Apparently I did a bad thing by using SuperSU with CM, and trying to have SuperSU update its recovery permissions or whatever. (See reference below.) I first told it to try without rebooting, which didn't work. Then I tapped the other option (for CWM/TWRP), and now my phone can't get past the Cyanogenmod boot logo (teal-colored, alien android-looking thing).

The only recovery-ish thing I can get is to do a factory wipe. (I can do this by holding Pwr+VolDown to turn the phone on. Then when LG logo shows, I briefly release the VolDown button, then press and hold it again, until the "Factory data reset" screen appears. I'm new so I can't post links yet, but if you want to see it, I put a URL in the references below.)

I guess I borked the recovery with SuperSU? Is there a way to fix it, without doing the wipe?

References: (I'm new so I can't post links.)

Factory data reset dialog - i.imgur.com/oB3Hx6u.jpg

How I think I screwed it up - jdrch.wordpress.com/2014/07/01/do-not-use-supersu-with-cyanogenmod-even-if-titanium-backup-suggests-you-do/
[G4 Q&A, Help & Troubleshooting] Levent2101:
that article you listed is from 2014, however I am pretty sure chainfire had supersu removal zip on his website try that.
[G4 Q&A, Help & Troubleshooting] cp.engr:
I can't even find the word "remove" anywhere on chainfire's website (chainfire.eu) in the title of any of his posts back through 2014.

I thought maybe I could flash a new recovery, but I can't connect to my phone with fastboot, either...
[G4 Q&A, Help & Troubleshooting] Levent2101:
https://xdaforums.com/showpost.php?p=63615067&postcount=2459
[G4 Q&A, Help & Troubleshooting] Velcorn:
I had a similar problem a few days ago when I wanted to try out Resurrection Remix and decided to try dirty flashing it which ended up in a bootloop or rather it would boot up to a black screen with nothing to do other than rebooting or shutting down. It took me around 30 attempts to even get to the factory reset. I tried that, resulted in a "regular" boot loop this time. After some more failed attempts to get into TWRP, I tried download mode. ADB wouldn't work and I could reflash TWRP or reboot into recovery. End of story, after getting into the factory reset option again, it glitched and switched to TWRP where I could finally fix stuff.

tl;dr Try getting into recovery "a couple of times" until you might end up in TWRP or whatever recovery you have installed. Maybe try download mode too.
[G4 Q&A, Help & Troubleshooting] cp.engr:
Not sure how this would help me. I can't even boot into a custom recovery to flash things - that's the problem. The only option I have when booted in recovery mode is to wipe the system, which is what I'm trying not to do.

I haven't been so lucky with recovery mode.

I have been able to get into download mode, but can't do much with it so far. I'll make another post about it (on this thread)...
[G4 Q&A, Help & Troubleshooting] cp.engr:
UPDATE: I am able to boot the phone into "download mode". (I do this by holding Vol Up, then inserting a USB cable.) I can talk to it a little. I'm hoping I can maybe flash a custom recovery from here, without wiping the phone... I still need help, though.

When I start the phone in download mode, it shows up in the Windows Device Manger on the PC as a COM port ("LGE AndroidNet USB Serial Port").

[EDIT: The picture on the phone screen in download mode is very faint. I don't know if that's normal.]

Then I can talk to it using Peter Wu's lglaf utility. Unfortunately, the response to most commands is, "Command failed with error code 0x8000010a", which I think is a basic sort of "unknown/unsupported command" error message.

I can at least get some info from the phone, as shown below. Maybe it is helpful?

Is there a way I can flash a custom recovery from download mode, without wiping the phone? I do have a MicroSD card which I could put the files to flash on.

C:\lglaf>python lglaf.py -c "!INFO GPRO \x08\x0b\0\0" > props.bin

C:\lglaf>python scripts/parse-props.py props.bin
download cable = '633A'
battery level = 100
download type = ' '
download speed = 0
usb version = 'UHS'
hardware revision = 'rev_10'
download sw version = ' '
device sw version = 'H81120i'
secure device = 'S'
laf sw version = '1.1'
device factory version = 'LGH811AT-01-V20i-310-260-FEB-01-2016-ARB02+0'
device factory out version = 'LGH811AT-00-V20i-TMO-US-FEB-01-2016-ARB02+0'
pid = 'YE04S160403002785'
imei = [redacted]
model name = 'LG-H811'
device build type = 'U'
chipset platform = 'msm8992'
target_operator = 'TMO'
target_country = 'US'
ap_factory_reset_status = 6
cp_factory_reset_status = 0
isDownloadNotFinish = 0
qem = 0
cupss swfv = '00000000000-00000000000-00000000000-FFFFFFFFFFF-F'
is one binary dual plan = 0
memory size = 61071360
memory_id = '032G74\n'
bootloader_ver = 'MiniOS 3.0'
[G4 Q&A, Help & Troubleshooting] Velcorn:
After getting another bootloop after installing SuperSU for whatever reason, I figured out that in my case hitting "Yes" when getting into the phones standard factory reset option gets the phone into TWRP.

You said you already got to that menu, but I finally figured out the correct way to get there which is holding down vol- and power button until the LG logo appears, letting go of the power button for a splitsecond and holding it again. Other descriptions never worked for me which is why it took me ages to figure that out.
[G4 Q&A, Help & Troubleshooting] cp.engr:
Am I understanding you correctly that if I select "Yes", it won't actually do the factory data reset, but rather will take me to my recovery mode? (CyanogenMod's recovery, in my case.)

More recently, I was starting to suspect that this may be the case, based mostly on this YouTube video: Flash Recovery via Download Mode. At 5:10, he selects "yes" to the wipe, but it takes him right to TWRP. I get the impression it never does the wipe. (Watch starting around 4:25 to get some more context.)

If that works, any ideas how I might fix it so it can boot normally?

Yes, I described this in my first post on this thread:
[G4 Q&A, Help & Troubleshooting] Velcorn:
It did work like that for me the second time. However, the first time this happened, I think it did perform the build-in factory reset, so I cannot guarantee you that it will work on the first try. It did on the second try and since I did a clean install to fix that problem, I cannot tell you whether it actually did the factory reset after all.
[Honor 6X Questions & Answers] thilak devraj:
I wanted to know if there's any user with tarp on honor 6x

I have a debloater script and I want someone to test it (it works for sure , but I wanted to confirm it)
[Samsung Galaxy S7 Edge Questions and Answers] bekasulaberidze:
attery life after 7.0 update is terrible, first beta was great I got 6-7 hour of SOT, now I get only 2 hours, what about you guys ? (4G always on, AOD on, internet browsing, messenger, light gaming)
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
That's suprising. I am getting great battery life since Nougat 7.0

Stock firmware.

Around 110 apps installed

No battery saving apps (such as Greenify).

No apps are optimized for battery saving.

Always on Display enabled.

Auto Brightness Enabled

GPS turned on

Sync turned on
[Samsung Galaxy S7 Edge Questions and Answers] speed s:
Look at mine :D

View attachment 4017723View attachment 4017725

Envoyé de mon SM-G935F en utilisant Tapatalk
[Samsung Galaxy S7 Edge Questions and Answers] icehackk:
i am having the same issue but not from nougat i usually got 5h SOT max

AOD is turned off sync and location always off i guess there is a problem with the battery or the phone i tried factory reset didn't help
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
Awesome! It seems some people are just unlucky. Or maybe they have apps using a lot of battery.
[Samsung Galaxy S7 Edge Questions and Answers] Vivacity:
lol yeah maybe the guy who posted should drop accu battery app to begin with. :/ don't know.
[Samsung Galaxy S7 Edge Questions and Answers] riso123:
My battery life is on par with my original March 2016 MM release, which is pretty decent. I did have huge battery season at first on nougat, but removing the built in news app seemed to resolve this. Not sure if that was coincidence though.
[Samsung Galaxy S7 Edge Questions and Answers] XxReApErxX:
Which rom are you guys using? I have 7.0 BTU. Battery life is average, not better than MM. 4.5 hours.

Enviado desde mi SM-G935F mediante Tapatalk
[Samsung Galaxy S7 Edge Questions and Answers] insaned:
I'm squeezing 8hours only using greenify and doze
[Samsung Galaxy S7 Edge Questions and Answers] Sn0wFl4keZ:
having 10%/Hr standby drain ..
[Samsung Galaxy S7 Edge Questions and Answers] dollar7:
That's obnoxious man. Mine is not even draining 1%/h when it's standby.

Generally I'm so satisfied with s7e battery, whole day with data/WiFi turned on, still remains like 20% when I'm going to bed.
[Samsung Galaxy S7 Edge Questions and Answers] sireniankyle:
Having the same issue. unplugged at 100% and went to sleep for 5 hours. came back and the phone was at 72%. Not normal at all for me.
[Samsung Galaxy S7 Edge Questions and Answers] saurabh808:
standby is great but while using the phone the battery drains a lot more in nougat than marshmallow, even the hd and fhd options seems useless coz they don't help a lot with saving the battery. the moment i unlock my device and start using it the battery starts to drop immediately .may be need to visit service centre.
[Samsung Galaxy S7 Edge Questions and Answers] saurabh808:
Using the device for more than 1 hour and its showing 38 minutes moreover no detail of usage is it a bug? Fee minutes ago it was showing correct
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
I am also using Android 7.0 BTU stock firmware
[Samsung Galaxy S7 Edge Questions and Answers] sireniankyle:
Same. Gonna re-flash, and see if it helps. I did the standard update 1st time around.
[Samsung Galaxy S7 Edge Questions and Answers] bekasulaberidze:
I need to charge it twice a day :( as I mentioned firat beta was perfect, I Don't know what to do......
[Miscellaneous Android Development] fused#1:
Pretty tricky to find anything for this tablet, but I managed to find a way to get an official image.

What you need:

Alcatel Mobile Upgrade Q 5.1.7 (or newer), get it here.

This will overwrite all your data on the device.

1. Install Mobile Upgrade Q

2. Run "C:\Program Files (x86)\Mobile Upgrade Q\tool\usb_driver\installdriver\DriverInstaller.exe" to install the USB Drivers.

3. Enable USB Debugging

4. adb reboot edl

5. Mobile Upgrade Q and select "VF1400" (note it also lists 9030G and 9030Q, the unbranded variants of this tablet (yet unreleased?), but unfortunately you can't flash these, it will just download the Vodafone branded image)

6. It will download the image files into "C:\Program Files (x86)\Mobile Upgrade Q\bin\download" (note while it's downloading the image files, these are just filled with 0s)

7. After it downloaded the image it starts flashing ("initialisation") and you can copy the files to some place safe (from bin\VF1400-2AVDXXX), it deletes some after it's done

B1BEB0B0CD00.mbn is the boot image, R1BEB0B0CD00.mbn the recovery. Some of the files have partition information, probably can use these to flash with QPST.

Going to have a look into compiling a TWRP, now that I have the kernel :)
[Miscellaneous Android Development] fused#1:
Also, Alcatel seems to have released a *very incomplete* kernel source (build scripts and other things missing) over at https://sourceforge.net/projects/alcatel/files/, see OT_VDF_1400_20160520.tar.xz.

A bummer since the kernel in the official image seems to have all kinds of debugging stuff enabled.
[Miscellaneous Android Development] fused#1:
Some more findings. You can coax SUGAR QCT_SP (and maybe Alcatel Mobile Upgrade Q 5.1.7?) into flashing any images.

Before starting SUGAR QCT_SP, copy your backup of the VF1400-2AVDDE1 folder into bin/. It should flash these files.

I flashed a ported recovery, but I couldn't boot it (always boots stock recovery). I guess because of secure boot? Read something about the recovery-from-boot.p file...

Don't worry about bricking, you can get the tab into edl mode with an edl cable. http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
[Miscellaneous Android Development] fused#1:
Some progress, if anyone cares :laugh: (doubt it).

Flashed boot with altered build.pros, selinux is off, but adb root kills the adbd.

Same on recovery, but kind of pointless with zip verification. Now it's either compile a recovery or add a custom key too boot and sign the supersu zip myself.

Also flashed a slimmer system, minus all the google apps I don't use anyway. Stock image carries 1GB of empty space that is being flashed every time :eek:
[Miscellaneous Android Development] fused#1:
One more interesting thing: You can get into fastboot by flashing a recovery with the wrong kernel and then booting to recovery. Fastboot is crippled though and does nothing useful, can't even flash with it.

Btw to turn off the device if you are stuck in a bootloop to recovery: With usb cable unconnected, hold Power and Volume down. It screen goes black after 5 sec, keep holding the buttons. It should come up again and very shortly after, let go of the buttons screen when the screen goes black a second time.
[Miscellaneous Android Development] gella1992:
So, at the moment there is no way to root?

Geeting the device tomrrow
[Miscellaneous Android Development] fused#1:
Yes there is. After getting rid of selinux, you can get temporary root using dirty cow, or bake supersu into the boot or system image.

Also I'm working on porting a recovery. It works, more or less already.
[Miscellaneous Android Development] fused#1:
I just flashed SuperSU via the recovery I ported. Seems to work :)
[Miscellaneous Android Development] gella1992:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
[Miscellaneous Android Development] fused#1:
I can upload it later.

Fastboot is crippled and you can't boot into it directly, at least on mine. Try booting into it (hold power + vol down). Otherwise see my earlier posts on how to do the initial flash. A little inconvenient, but it's only once :)

Will post detailed instructions with the recovery.
[Miscellaneous Android Development] fused#1:
https://xdaforums.com/android/development/recovery-vodafone-prime-tab-7-t3548560
[Miscellaneous Android Development] fused#1:
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel: https://github.com/852Kerfunkle/android_kernel_vodafone_vfd1400

Works for booting into recovery.
[Miscellaneous Android Development] fused#1:
While trying some things with caf android builds, I flashed aboot, thinking I could always get back into download mode with the makeshift EDL cable. Turns out you can't.

Do not mess with aboot unless you are 100% sure (unlike me). The device will only register as HS-USB Diagnostic 900E. Even with an EDL cable.

For anyone who did: your device is not dead, but it's a bit of a mission.

1. Take of the back cover: Remove the screw behind the sim/sd latch and open the device with one of these plastic opener thingies, start at the latch.

2. Bridge the pin marked on the image (take a cable and connect the pin to the ground of the usb connector, i.e. the metal bit).

3. Plug in the usb cable.

4. It should register as HS-USB QDloader 9008 (assuming you have the right drivers).

5. Flash with Sugar.
[Miscellaneous Android Development] gella1992:
Hopefully everything is working great again!

Do you think it would be possible to port a Lineage OS to this Tab?

I know how to compile from source, but actually not developing a Rom :(
[Miscellaneous Android Development] fused#1:
Yeah it's working alright again, thanks :)

I tried, no luck yet. Am stuck on a crash in libsdm. Once I had it boot to the point where it was initialising the apps (dexopt or whatever?), but it crashed right after.

For now I am focusing on codeaurora android. If I get that working, maybe the caf parts can be used to make a working LineageOS build.

I also have little to no idea how to do anything android related, so most of the time is spent reading and googling silly errors. Just give it a go, if you get stuck I can help out with what I found so far.
[Miscellaneous Android Development] gella1992:
At the moment I am busy. Will give it a try when I have more time :fingers-crossed:
[Miscellaneous Android Development] nevexc:
Are you still working on this ?

I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.

Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.

Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.

My ultimate goal is OMNI, im not interested in CM/Lineage.

Problem is at the moment i don't have much time for this.

But we'll see :good:
[Miscellaneous Android Development] fused#1:
Hey,

That's pretty much what I was doing before I got caught up in other stuff :)

Was stuck at trying to figure out how to actually build caf android. Which of the files on the rom belong the the proprietary blobs and how to properly include them in the makefiles so it actually builds...

Hit me up with a PM, maybe we can coordinate our efforts :) :fingers-crossed:
[Miscellaneous Android Development] creatzs:
Thanks for this Guide, but I have a quick question:

I am currently trying to restore my VF-1497 to a stock rom with Mobile Upgrade Q 5.1.7, but the Upgrader always kicks my Tablet out of edl, and throws the error:

'There is no greater version available to upgrade your phone, actual version of your phone is the latest'

Is there any way to restore this device back to stock?

Thank you in advance
[Miscellaneous Android Development] EaglePK:
ASP

Hi is there a custom "clean" firmware for vdf1400 that can go instead of the latest 6.0.1 150fkg1
[Miscellaneous Android Development] slim2100:
vdf 1400 stuck in Android logo

Hi

First i would thank this group for helping me rooting this device a year ago.

Unfortunately , i tried to factory reset it and by accident i did wipe the system partition.

Tablet is stuck in boot logo.

Can not use Sugar software to flash the rom.

I can access adb with pc.

adb devices is showing the tablet connected.

Any advice please how to flash the rom with adb or any other method ?
[Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti] kos25k:
Hello.I want someone's help please cause i face this issue months now with noone giving me an answer.I have this http://www.ebay.com/itm/1080P-MHL-T...277006?hash=item419d33928e:g:NnwAAOSwl8NVXwz7 mhl cable.It mirrors normally the screen to my tv.But the problem starts when i turn on WIFI.Screen remains mirrored on tv but WIFI doesnt work!Why is this happening?Same thing happens on both rooted kitkat and lollipop.I haven't tryied on unrooted room.Is this root or cable problem?Can anyone help me?thanks.
[Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti] _ghiottone:
I ordered month ago this type of MHL cable and last saturday when i tested it i have the same problem, the wifi turn off when i used the MHL cable - my tablet unrooted and in stock Lollipop (SGP621, 23.5.A.1.291)
[Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti] kos25k:
so the problem hasn't to do with root.dude we must find out what causes this..i will use my tablet with wireless mouse keyboard to my tv..i would buy a MINIX media center,but i dont want to waste mh money..so we must find a solution to this..