yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] chrissyboyhat:
Hi, I'm trying to recover photos from a factory reset moto g. I have CWM installed and the phone is rooted but am having trouble mounting the user data partition in ADB Shell.

Can anyone tell me what the /dev/block/????? address thingy is for a Moto G user data partition is?

None of the usual android recovery apps have found find any files at all so my only hope is to take the data off with the SDK and I'm using this guide: http://xdaforums.com/galaxy-nexus/general/guide-internal-memory-data-recovery-yes-t1994705

Thanks for reading this far :)
[Moto G Q&A, Help & Troubleshooting] lost101:
/dev/block/platform/msm_sdcc.1/by-name/userdata​

or

/dev/block/mmcblk0p36​

Edit: This post / thread might be of interest - http://xdaforums.com/showpost.php?p=64171086&postcount=2
[Moto G Q&A, Help & Troubleshooting] chrissyboyhat:
Thankyou!!!!!!!! :)
[XDA Assist] Nebrass.N.Farfoor:
Hi , thanks for this great forum .

I need an app (or trick) to turn the front flash of my J5 on while making video calls via skype,viber etc....

Thanks
[XDA Assist] Primokorn:
Hi,

Thanks for using XDA Assist.

Did you try apps of automation like Tasker or Trigger?

This thread should be helpful: [TUT] The Ultimate Noob/Beginners Guide to Tasker
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Arthas92:
I just buy a 2nd droid turbo TX1254 64GB, it's running android 5.1

I reboot to bootloader and i see it said my software status is modified.

Before that, I play around with rootking, seeder, set CPU, resolution changer and sunshire (sunshire just run to step for purchase lilicense but i didn't unlock bootloader yet since 25$ not very small in my country).

I recheck moforoot and it say: Sorry, your XT1254 is not supported. Maybe next time.

So how could my software status become modified when bootloader is lock and mofo is not support? :confused::confused::confused:

edit: update image
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Moforoot is not supported because you're on 5.1. Moforoot requires 4.4.4. Also, Moforoot costs $20.

Your system status is most likely modified due to whatever Kingroot did when it tried to obtain root access.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Arthas92:
so Kingroot able to edit my system (i have wipe all and i still say software modified).
[Desire Q&A, Help & Troubleshooting] prima9:
Hiiii my freinds ,i need your helpp ,pleas

I installed twrp recovery on my phone and i wipe data ,devil cach ,.... And every thing ,after reboot my phone cant load android and on recovery showd No os installed ,please help my what can i do ?? Pleas:crying:???
[Desire Q&A, Help & Troubleshooting] uglyjohny:
You shld download rom for your phone, put it on sd card, power up recovery and flash it.
[Desire Q&A, Help & Troubleshooting] prima9:
Thx johny ,but where i can find rom for my phone ,i cant find it
[Desire Q&A, Help & Troubleshooting] uglyjohny:
I was unaware how unsuported this phone is on xda forum :) so question #1 why did you do this and #2 is your phone indian model? If it is hit on facebook user kvkvarun he has nandroid backup but first check that you have same phone. If it doesnt help there is post on forum with RUU rom (will bring your phone to factory state)

Hope this helps
[Desire Q&A, Help & Troubleshooting] prima9:
I don know whay i did it ,my phone is china model ,i dont have facebook id ,where i can find ruu for my phone

Plz help plz ???
[Desire Q&A, Help & Troubleshooting] uglyjohny:
Send me your carrier and android version
[Desire Q&A, Help & Troubleshooting] prima9:
Android ver : 5.0.2

Htc Sense : 6.0

Software number 1.0.0.Desire.826

HTC SDK : 6.55

Kernel ver : 3.10.49-g40c2b6f

Baseband ver : 1.0.u20402

Build number : 1.04.1400.3 CL487750

Htc Desire 826 A52 DTUL

Thx Thx Johny
[Desire Q&A, Help & Troubleshooting] uglyjohny:
My network keeps reseting...

Go to htcdev.com/devcenter/downloads and put your info and download rom and flash it
[Desire Q&A, Help & Troubleshooting] prima9:
i downloaded htc desire 826 kernel from htcdev.com but i dont know how i do flash it ?? can u help me about that ?Plz Johny :crying::crying:
[Desire Q&A, Help & Troubleshooting] uglyjohny:
Ok, send pm to this memmber http://xdaforums.com/member.php?u=6900619 he/she will send you link with rom
[Desire Q&A, Help & Troubleshooting] bhanuprasad1981:
Noob question! is kernel and rom dump same I too own Indian version of 826x I am looking for stock rom please help
[Desire Q&A, Help & Troubleshooting] pokemon_2201:
note

please:crying:
[Desire Q&A, Help & Troubleshooting] pkb_always4u:
http://xdaforums.com/android/general/mega-thread-htc-desire-826-t3397079

;)
[Desire Q&A, Help & Troubleshooting] pokemon_2201:
Helping me

My device is HTC desire 826 dual sim is no root no recovery no custom rom cm13 please see to helping me to get building my request early thanks you so much:crying:
[Sprint Samsung Galaxy S6 Edge+] SptMogul:
Just woke up and saw the message. The file size is 45.30

Anyone tried it already?
[Sprint Samsung Galaxy S6 Edge+] Omi239:
Just received it but I didn't download, I want to know more about it as I was planning on rooting in the near future...
[Sprint Samsung Galaxy S6 Edge+] Hubblemuffin:
UI is the same, haven't been able to test battery usage yet. "Sprint Features Apps" installed automatically when the phone booted. Just seems like a security update like OJ6.
[Sprint Samsung Galaxy S6 Edge+] infamouzwt:
i installed it nothing major just security updates and bug fixes
[Sprint Samsung Galaxy S6 Edge+] tcas55:
Still rootable???
[Sprint Samsung Galaxy S6 Edge+] Sham-rock:
Yes still rootable.
[Sprint Samsung Galaxy S6 Edge+] lostsoul77:
I just updated as well...no changes and still rootable per method in this thread:

http://xdaforums.com/showthread.php?t=3212573
[General Topics] danielehk:
I, it's possible to delete all call duration list on a wm3 / wm5 device?

There is any software?

Thanks

Daniele
[General Topics] decknologist:
Wouldn't it be easier to back up your device and hard-reset?
[General Topics] mestrini:
Use the batterystatus plugin that has an option to clear the counter and also to schedule it ;)
[General Topics] oldsap:
for WM5:

http://cid-d52d6e7f9016fc0d.skydrive.live.com/self.aspx/Public/CCT.EXE
[General Topics] danielehk:
doen't not work, infact in "system information" I have the call time!
[Xperia Z5 Premium Q&A, Help & Troubleshooting] tzsimtik:
i think the brightness of my phone somehow drops

im in hiest brightness seting and turn of that automatic brightness

and still yesterday when i play games the screen was much much brighter

it is posible it conect to batery status

becouse all the batery save option are off

please help
[Xperia Z5 Premium Q&A, Help & Troubleshooting] fancymans:
If automatic brightness is off then this shouldn't be happening. I can confirm that this doesn't happen to my Z5 Premium. Try turning it on/off again. If that still doesn't work, you can try a factory reset. Last resort is to return/exchange for another.
[Galaxy Tab Q&A, Help & Troubleshooting] blackdolhpin:
My Galaxy Tab 10.1 P7510 died during overnight cycling. Since then I only see the device booting into APX-Mode.

I tried disconnecting the battery but also brought me into APX-Mode.

When I am trying to connect using nvflash I receive the following message:

Nvflash started

rcm version 0X4

Command send failed (usb write failed)

This seems to occur because my bootloader is locked. I also have the CPUID and calculated the SBK with the Asus 500 Tool with no luck.

So I am looking forward to any further ideas you guys may have to recover my data.

Even if I loose the tablet would be very nice to recover the data.

Thank you!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] 1st.qwerty:
Hi,

I have problem with autofocus in my Z3c, if I take picture from 5-20cm it's OK, when i try make photo of longer distance, picture is not focused.

I try stock camera app, google camera app, factory reset, software repair via PC Companion, pictures are still blurry. Any suggestions?

Front camera works OK.

FW: 23.4.A.1.232

custom. 1288-7915_R5c

no simlock

bootloader unlock allowed: yes
[Xperia Z3 Compact Q&A, Help & Troubleshooting] p11tiwari:
I had similar problem with my Z3c! Luckyly, I had my phone replaced under warranty. I hope you still have warranty left coz if it's a hardware issue like it was in my case, then you're out of luck without warranty!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] 1st.qwerty:
Do You know what they repair/change? Replace camera, or mainboard?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] p11tiwari:
I got my phone replaced!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] 1st.qwerty:
Lucky :)

I found used camera on ebay 10 eur, and I'm waiting for delivery.

So, when I change camera i'll write what on.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] 1st.qwerty:
HA!

I don't know why but when I change firmware to 24.4.A.1.264 Baltic Generic via flashtool everything is alright!

Somebody knows why factory reset, or firmware repair via pc companion doesn't work?

Now my camera work OK!
[Kindle Fire 2 Q&A, Help and Troubleshooting] dylantbecker:
I've been trying to figure this out but every method that I have tried doesn't work at all really. Video tutorial or novice friendly guide? Someone help please? Would love to "androidify" this thing.
[Kindle Fire 2 Q&A, Help and Troubleshooting] humanBREW:
Hi! I had the same question but found no answer, until I tried by myself

Download kingroot apk from your tablet, install it and you get root.

Next follow the guide posted in this forum.

But here's the trick: you can't go back after you flash the old bootloader,

So reboot to recovery and push the zip to sdcard

And boom new ROM installed.

Don't worry if you reboot to stock, you get black screen but not a brick, get back yo fastboot, reflash and reboot to recovery
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Michael833:
I just received my SM-T815C this morning. My last tablet at one point "lost" it's /efs folder, creating all manor problems for me. I now understand that it's possible to back that up, but I hadn't done so when I lost it, and it took me forever to recover.

So now, as I begin my journey with my new SM-T815C, I'd like to start by making a FULL system backup of all directories before I eventually root and possibly install a TWRP. Does anyone have a step-by-step tutorial? I've Googled a bit, but most of the pages I found seem to talk more about Jelly Bean than Lollipop. I'm currently running 5.0.2, and I haven't done any rooting or installing of a custom recovery, but plan to do both eventually (if possible).
[Galaxy Tab S2 Q&A, Help & Troubleshooting] micger21:
Of course it is possible to do a full backup of your whole system. For this, you must have a recovery menu customized. The only solution for you is to follow exactly this post to root your machine and to install the customized recovery .... http://xdaforums.com/tab-s2/general/guide-root-tab-s2-t3205019

It's by this menu , you can do a complet backup of the system....You can chose microscard or usb for the backed up
[Xposed General] hellcat50:
So I have a problem with my Samsung Galaxy S3 (GT-I9300) with CM11 newest nightly and xposed.

I only flashed the CM11 zip without gapps and wiped my device completely.

Xposed is not (yet) compatible with Android SDK

version 19 or your processor architecture (armeabi-

v7a)

CANNOT LINK EXECUTABLE: cannot locate symbol

"_ZN7android14AndroidRuntime5startEPKcS2_"

referenced by "/data/data/

de.robv.android.xposed.installer/cache/

app_process"...

SOLVED (thx to orville87): http://xdaforums.com/xposed/xposed-android-4-4-4-t3249895
[Xposed General] Portgas D. Ace:
You could try to re-install Xposed, as flashing the CM nightly seems to have overwritten some files which are required for Xposed.
[Xposed General] hellcat50:
No, I can't install xposed at all. This error is there when I fresh installed CM and the apk.
[Xposed General] thesiki24:
I've got the same problem (posted it here: android.stackexchange.com/questions/130893/xposed-unable-to-install-after-minor-cm-update [sry, cant post links]).

As you pointed out reinstalling Xposed is not possible :(

I hope someone finds a solution for this annoying problem... I want my modules back
[Xposed General] Portgas D. Ace:
Hmm, my next guess would be that the latest nightly of your ROM includes several security patches for Android, which break functionality of Xposed. And as Xposed for KitKat devices isn't updated any more...

But to eliminate the obvious things: You have granted superuser permission to Xposed, haven't you?
[Xposed General] hellcat50:
Yes, I have.

Ja, habe ich :P
[Xposed General] Portgas D. Ace:
Okay, then check this thread, which is dedicated for Xposed not working anymore after latest security updates. A solution is already provided (check link) in the first post.

German/Deutsch: Schau mal in den oben verlinkten Thread. Da scheint jemand eine Lösung für das Problem gefunden zu haben (siehe Post #1).
[G4 Q&A, Help & Troubleshooting] kapranos:
Hi guys

I just make the process in order to install CM 13, i do everything but in the Google account step cannon contact with Google and return me error.

i check and i have bad time and day, when i go settings and Disable automatic date time and try to change time i can't, doesn't matter which date and hour and date i put, not save me the changes.

can you help me?

(sorry for my english)
[G4 Q&A, Help & Troubleshooting] MickyFoley:
Try following: Install latest busybox (e.g. install it by "BusyBox on Rails: LINK, connect your phone via USB & ADB:

adb shell date -s YYYYMMDD.HHmmss

so it should be like (example):

adb shell date -s 20151207.100000

for 7th of December 2015, 10:00.
[G4 General] nitrous²:
This is not a fix for already persisting issues. If you're currently dealing with ExFAT (or BT) issues, Systemless ROOT will not help you. Bring your device in a state where you don't have these issues by flashing a stock ROM matching exactly your variant and location. Then use Systemless ROOT using a custom recovery.

Unlocked Bootloaders Only

Confirmed working by me on a H815-EUR bought in Germany.

UPDATE: Confirmed to be working on following MM ROMs:

H815 EUR 20A/C/D Germany

H815 EUR 20B Poland

H815 EUR 20A Croatia

Please report if this works for you according to this scheme: H815-EUR-20A-GERMANY

Legend

Blue: Device Model

Black: Device region

Red: Firmware Version

Green: Location

Simple:

After flashing or updating to a stock LG MM ROM, boot into TWRP and flash Chainfire's Systemless ROOT 2.67. It'll automatically backup, patch and flash the Kernel. It'd be great if you could confirm by giving details about your device, e.g. "H815-EUR Germany" or "H815-EUR Poland" etc.

As stated by [MENTION=631273]Chainfire[/MENTION] in his thread:

With the introduction of TWRP 3.X.X., this is no longer an issue. TWRP will no longer ask to install SuperSU if it detects a Marshmallow ROM.

For G4 (H815) users:

You have to reflash the latest stock KDZ or .zip (modem, system, boot - restart recovery - bootloader) if you're currently dealing with exFAT issues. Then you can fire up TWRP and flash Systemless ROOT 2.67.

The reason why you might want to use this method to root instead of simply flashing a pre-patched Kernel is differences in ROM versions. As it happened to me, on my H815-EUR from Germany, I received the MM update. It was called "20A" for some reason, but it has the same fixes and updates as 20B. So it's not to be confused with the early 20A build from Poland! Quick as I am, I flashed the repacked boot.img for 20A by [MENTION=823251]cile381[/MENTION] and lost exFAT support, and somehow corrupted ADB, since cile381's repacked kernel was built from and for the Poland 20A build.

I hope this'll help you =)
[G4 General] Andrea__93:
Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader :)
[G4 General] nitrous²:
No, that's not true. You still need a modified boot.img. With this method, you basically create your very own patched kernel, from the boot.img extracted from your very device.

MM still requires a patched/repacked kernel.

EDIT: Ok, now I see where the confusion came from. Misleading title.
[G4 General] Loulou-13:
thank you ! very useful ...

i have a question :

why ,with a phone (

bootloader unlocked

) with MM 6 ,it's possible to easily have a root .......but the

locked

device no ? ===> but instead of use TWRP , by injecting only the SuperSU with adb fastboot (or kdz pack?) for locked device???
[G4 General] nitrous²:
Basically, Marshmallow has very strict security restrictions. The stock kernel won't allow any modifications. That's why we need a modified (vulnearable) one. You can simply flash a modified kernel onto a bootloader unlocked device. But since you can't flash custom boot.img's on locked devices, people with non-unlockable devices currently have no way to root their MM devices.

More details can be found in this XDA article.
[G4 General] Loulou-13:
very very interesting what you have said ,thank you for sharing and help ;)

i didn't know MM...

that's mean ther

NEVER

have a chance for a root of MM with locked bootloader !!! if i have correctly understood ...

the only way is to unlock this damned bootloader ......or downgrade to LP by LG-UP (kdz) and then root with fastboot method ??? i'm true ???

i just discover this LG G4

in the past i have had a LG optimus series ...with old methods and full possibilities !

i begin to believe that it's the begining of the dead of android development if all manufacturers and google "lock" and add too many securities on these news devices with "hard" methods ... :mad: :rolleyes:
[G4 General] nitrous²:
Haha, sure! You're welcome =)

I wouldn say "never". There's always a chance that a genius will find a way. You also need to factor in the relatively young age of the G4.

To the last part: Yeah, it's getting harder and harder. But nothing unexpected. Remember, power users like us do only make up a very small, almost insignificant amount of all the Android users out there. I'm sure most people don't even know what Android is. Google just went full on Spock and said "Thee needs of the many outweigh the needs of the few or the one" :laugh:
[G4 General] Loulou-13:
ho my god ...sh** ........ :rolleyes:

imagine the future LG G5 (and others manufacturers ) with bootloader locked !!!! and if they

never

want to unlock with these new security politic........and this damned MM for original firmware more and more securised :( ==> we all profoundly have it on ours ass !!! :mad:

otherwise there are big chance to hard brick devices with bests devs attempts ...

Sorry for my bad words ,but this xda article that you previously have given to me ,make me really afraid !!!!!!! ... :(

Another big question :

when we have done MM update on G4 ,i have read that it's possible to easily downgrade to LP with LG-UP ....but full upgrade ??? it change this new MM bootloader with LP one ? for to have the possibility to root with locked bootloader ...
[G4 General] nitrous²:
"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.

Btw. This just happened
[G4 General] dohouch:
Just used this on LG G4 H81520A, ( bootloader officially LG Unlocked ) went sweet as a nut.
[G4 General] autoprime:
I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.

Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now :)
[G4 General] MickyFoley:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me :).
[G4 General] ChriKn:
If it is only for the T-Mobile variant they are probably at the same (if not worse) point that the G4 is. At least we can officially unlock some devices...
[G4 General] Loulou-13:
ok ,sorry for out of topic ... ;)

i keep you thread preciously whe i will decide to unlock my bootloader ;) thank again and again ! ;)

i like your optimism ! i want to believe ... ;)
[G4 General] i-m:
I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?
[G4 General] MickyFoley:
[MENTION=3099420]i-m[/MENTION]: exFAT-issues of CM13 should be solved at 7th of December :):

g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)
[G4 General] nitrous²:
I did that too. I mean, flashing repacked 20B on German 20A. I then no longer had issues with exFAT formatted cards, but ADB was still "corrupted", meaning it wouldn't let me authorize my PC and the option to de-authorize was no longer available in the developer settings menu. Of course, might as well be an isolated case.

Sure you hadn't. But if you read OP closely, you'll see why some people, me included, had issues. No, it will not solve exFAT issues for CM13.

It was still broken when I tried the nighlty from December 7th.
[G4 General] Jens1969:
Followed OP, root is working. :)

Still can't use my SD Card as on rooted 5.1:

- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,

- Lightroom says SD Card not available.

But this is a Marshmallow specific problem, isn't it?
[G4 General] X0rzist:
Apps have to be updated for proper support for SD cards. I switched to Solid Explorer because FX hasn't been updated for months.
[G4 General] nitrous²:
This is not a fix for devices that ran into SdCard issues. This is supposed to help you prevent exFAT issues from happening. The pre-requisite is an alread working device without exFAT issues.

This is specifically for Marshmallow devices. I'm surprised your device booted up after this :confused: Systemless ROOT patches your Marshmallow FW's kernel.
[G4 General] Jens1969:
I know. But you'll never know... There were no such problems on my N5, since there is no sd card.

You can add BT issues to the op. Besides an non operating sd card, I couldn't use BT at all.
[G4 General] Rockst4r007:
Amazing, thank you very much!
[G4 General] feds64:
Thanks...
[G4 General] autoprime:
decided to try this out today... I get an error...

*edit*

ignore...

all is working now. made post here.
[G4 General] nitrous²:
Yeah, that's why I was asking for feedback. Until now, only two people confirmed this to be working. That'd be [MENTION=3032379]dohouch[/MENTION] and me on 20A only, while I was on German 20A. Can't say anything about [MENTION=3032379]dohouch[/MENTION] though. I need to update OP about this. Anyway. Which version did you use [MENTION=2684188]autoprime[/MENTION]? I tried it two times using Beta-2.60. successfully. As you'll see there's an updated beta if you follow the link to the forum post.

EDIT: Have you actually had a look into the updated 20A builds? How likely is it that LG actually went on uzing gzip for the ramdisk? (Advisory: I know nothing about kernel building and stuff).
[G4 General] autoprime:
I suppose it's possible the boot.img was repacked differently... maybe a tad odd... as I am pretty sure LG has been using LZMA compression for a few generations now.

can you dump your boot.img? I could take a look at it and maybe even flash it and see what's what.

*update*

so I just unpacked the 20B boot.img and it's using gzip....

so now I'm rather confused. :confused:

*edit*

ignore...

all is working now. made post here.