yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 Questions & Answers] hanneshoch3:
Had the same issue, solved it by :

EDIT: make sure to have a pc with adb/fastboot close to you, for me the clean flash also flashed stock recovery. You could also possibly (haven't tried that) flash twrp itself right after flashing the full zip

Wipe system/cache/dalvik

Flash ONLY full zip - Reboot

Flash ONLY Supersu - reboot

Flash xposed - reboot - should work

No clearing caches after the very first wipe! Installed EX Kernel after xposed, too.

Hope this helps
[OnePlus 3 Questions & Answers] slonn:
I got it sorted by flashing the latest version of FreedomOS. Xposed works fine on that one
[Galaxy A3, A5, A7, A8, A9 General] ashyx:
Closed by ashyx.

Moved to: http://xdaforums.com/samsung-a-series/general/root-cf-autoroot-galaxy-a5-sm-5100-t3438117

MOD please delete.

Mod edit: Thread closed.
[Galaxy A3, A5, A7, A8, A9 General] xiehaibo:
hi bro! Is there a root for SM-A7100 ?
[Huawei P9 Questions & Answers] mihairimia:
Just realised I am not able to use share function in default photo gallery. I click on it but nothing happens. All other photo function are ok. I am unlocked, rooted and using xposed. Is anyone else having the same?
[Huawei P9 Questions & Answers] mihairimia:
So , no one is sharing pictures from default gallery... ! STRANGE
[Huawei P9 Questions & Answers] mihairimia:
well - Flat Style Colored Bar is causing this. Uninstalled.
[Nexus 5 Q&A, Help & Troubleshooting] Bulkatos:
Hi guys,

I currently have an issue with a Nexus 5 which runs smothly the last 2 years but suddenly didn't booted anymore.

I figured out, that something with the partitions is wrong, but didn't found any solutions.

Here is what I've done so far to solve the issue:

At first i tried to reinstall the factorey images via fastboot (unlocked bootloader). The install script run without any error promts, but I wasn't still unable to boot the device (stuck at Google logo).

After some research I found this thread which I think matched my issue the most: [Q] Phone not mounting and unable to flash roms. I followed the instructions and installed Phils recovery

log:

PhilZ Touch 6.57.9
ClockworkMod v6.0.5.1
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Can't open /dev/block/platform/msm_sdcc.1/misc
(No Such file or directory)

Then I got adb shell access and typed the commands in cmd:

C:\Users\mw>adb shell

~ # e2fsck /dev/block/platform/msm_sdcc.1/misc
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/misc
Possibly non-existent device?

~ # e2fsck /dev/block/platform/msm_sdcc.1/system
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/system
Possibly non-existent device?

~ # e2fsck /dev/block/platform/msm_sdcc.1/userdata
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/userdata
Possibly non-existent device?

~ # cat /proc/partitions
major minor #blocks name

~ #

I think that of some reason all partition information (or somethink simliar) got lost, which course the errors.

I would be greatful if somebody could help me.

Greetings Bulkatos
[Nexus 5 Q&A, Help & Troubleshooting] audit13:
I would re-flash the latest stock ROM and flash the userdata.img file last. Immediately after flashing userdata, use the buttons to boot directly to recovery and perform and wipe data, cache, and reboot.
[Nexus 5 Q&A, Help & Troubleshooting] Bulkatos:
I allready did this alot and with different factory images (android versions). All flash processes were successfuly. But I'm still not able to boot into Android.

If I'm booting into recovery (thats the only Image I can flash and boot into) I allways get the same error messages (see first post)

C:\Users\mw>adb shell
~ # cat /proc/partitions
major minor #blocks name

~ # e2fsck -y /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/by-name/persist
Possibly non-existent device?
~ #
~ # make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
open: No such file or directory
~ #
~ # make_ext4fs /dev/block/mmcblk0
Need size of filesystem
~ #
~ # make_ext4fs /dev/block/mmcblk0 32G
Need size of filesystem
~ #
[Nexus 5 Q&A, Help & Troubleshooting] audit13:
Did you perform a factory wipe right after flashing userdata?
[Nexus 5 Q&A, Help & Troubleshooting] diedmaster:
I'd recommend, download the full stom from google, go to fastboot, EXTRACT den ZIP file and flash every image file on your on with:

fastboot flash system system.img

fastboot flash radio radio.img

fastboot flash userdata userdata.img

fastboot flash boot boot.img

fastboot flash cache cache.img ...

then reboot, let the phone FULL boot. If the boot finished, shutdown, reflash recovery and your rom, and try adb shell again
[Android Q&A, Help & Troubleshooting] nijohnson:
I love me my Omniswipe. But I just upgraded to CM13, and the damned overlays bug makes it so annoying that I hate it. Do you all know of anything like Omniswipe that doesn't cause the overlay bug in Android6/CM13?
[G4 Q&A, Help & Troubleshooting] therock11:
If you cannot bring the LG camera app into CM or Resurrection, what is the best camera app for the LG G4?
[G4 Q&A, Help & Troubleshooting] raptorddd:
is not the camera its the stock LG framework that makes camera picture quality better....
[Galaxy S 4 Q&A, Help & Troubleshooting] edbr:
Hello,

So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of

Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.

Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.

So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.

Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.

On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.

To skip any unnecessary questions, I will make a short QA.

Q: Did you tried to boot into recovery/bootloader?

A: yes, nothing happens

Q: Any sign of life on adb while connected to a pc??

A: no

Q: Is battery dead?

A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up :D Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.

Q: Why don't you just buy a new phone?

A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.

Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?

A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.

So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.

In the best scenario, my almost 2 years old phone will revive.

Also, I have a multimeter - I can check the electricity. Just tell me what to check.

Thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] folgore95:
Probabily the rain damaged a part of your hardware. Did you solve?
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
If the battery is dead, the phone won't work.

The battery needs to have at least a bit of charge in order for the device to work, even if it is plugged in.

If the battery can't hold the charge, and the device uses more power than it gets, it turns off. I speak from experience.

These devices don't seem to work without a battery. Power goes to the battery, and the phone takes the power from there. Power doesn't go straight to the phone.

Anyway, I don't think a bit of light rain hurts the devices, especially if it was in your pocket. I walked through rain with my device in the pocket many times and no problem.

It looks to me that the hardware is failing. I don't believe that a faulty battery can cause a bootloop. I also don't believe that the power button causes a bootloop.

What I suggest would be:

1) Try going back to stock ROM.

2) Maybe try to get an S4 with a broken screen and switch the motherboards.
[Onetouch Idol 3 General] famewolf:
Pre-requisites: Must be 6045i user in an area that has band 12 lte (t-mobile) willing to flash a test hybrid modem/radio. If it doesn't work you just flash back your old modem. I have a version but am unable to test since band 12 is not in my area. I am attempting to combine the band 12 portion with parts of the 6.0.1 modem. Some issues encountered by users are apparently because they are using the 5.0.2 radio.

If you meet all the requirements and are willing to test please PM me.
[Onetouch Idol 3 General] famewolf:
Who's gonna test this 6.0.1 modem with band 12 support?

Come on...should I assume folks don't WANT to keep band 12? Eventually we will have to move to the newer modems to maintain compatibility with the roms. I've made a 6.0.1 radio that has the t-mobile config from 5.0.2. This radio works FINE on my personal phone for bands 2 and 4 but the closest band 12 is around 80 miles away. I've placed the test radio here under the "testing" folder: https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
[Onetouch Idol 3 General] HeadMajor:
ok, went and done did some tests.

with some interesting results...

--

note my starting point was the marionette's material rom. with 6.0.1 radios zip from famewolf's repository flashed over the top of the factory 5.0.2 radios.

i'm in southern california where Tmo has band 12, on a 6045i

--

questions:

1. are the radios supposed to be flashed right over the top of what was there, or is some partition supposed to be wiped first?

i flashed the radios each time right over the top of whatever was there, so if that was not correct, it would of course effect the results.

2. are we sure that the 6.0.1 radios do not have band 12 already available?

--

semi-related observation:

it appears that the lock screen issue of not being able to change the security method to anything other than none or swipe may be related to a temporary condition with the radio, rather than a permanent condition. as prior to testing this, i couldn't set pattern and so installed the 6.0.1 radios so i could set pattern, and then at the beginning of testing i installed the 5.0.2 radios and i still had the pattern lock screen functional. so the radio appears to only effect the actual act of changing the lockscreen, but doesn't have any other effect after the lockscreen has been set.

----

testing

-> i started with the 6.0.1 radios which i had already installed and LTE Discovery showed i was on band 4 at my office.

i didn't do anything else here because of the premise that i did not have band 12 available with the 6.0.1 radios.

-> i reinstalled the 5.0.2 radios, drove a short loop, and LTE discovery showed i was getting bands 4 and 12

as expected

-> i reinstalled the 6.0.1 radios, drove a short loop, and LTE discovery showed i was getting bands 4 and 12

i had reinstalled the 6.0.1 radios with the intention a little scientific method of documenting the lack of band 12 in the 6.0.1 radios, prior to the next step of testing famewolf's radio.

i do not know why, but i was getting band 12 after installing the original 6.0.1 radios.

this is why in my question above i ask if we were sure the 6.0.1 radios did not support band 12.

-> i installed famewolf's test 6.0.1 with band 12 radios, and drove a short loop, LTE discovery showed i was only getting band 4

so, this was also odd, as it was the opposite of what we were expecting.

-> i installed the original 6.0.1 radios and drove home, LTE discovery showing me going back and forth between bands 4 and 12 the entire drive.
[Onetouch Idol 3 General] famewolf:
It was widely reported that T-mobile was requiring manufacturers to remove band 12 in phones not fully compliant with VOLTE due to the possibility you could be somewhere where you could get ONLY band 12 and you would not have 911 access. Multiple people reported that the 6.0.1 radio stopped access to band 12. I provided a copy of the 5.0.2 radio and several others reported band 12 came back.

Now keep in mind I'm not in a band 12 area so I have 0 chance to test this myself. I took the t-mobile configuration file for the 5.0.2 radio and put it in the 6.0.1 radio...it's possible they also made additional changes I'd have to fix but I had to start with the simplest possible solution. Please take a couple of days to confirm your results. If you can't get band 12 on the hybrid then reconfirm you CAN on the plain 6.0.1. Please note the phone detecting the presence of a band 12 tower does NOT mean it's connecting to it...you need to actually SEE that you are connected to a band 12 tower in the lte discovery app.
[Onetouch Idol 3 General] HeadMajor:
Ok, more tests.

reloaded the 6.0.1 hybrid band 12 radios, and drove to work.

LTE Discovery reported my connecting to bands 4 and 12.

so, on a 30min / 20mile drive the hybrid radios will at least do the same as what the 6.0.1 original radios did last night.

both radios, 6.0.1 original and 6.0.1 hybrid, will connect me to bands 4 and 12 on the same commute route.
[Onetouch Idol 3 General] mendozaram:
Is it posible to have band 3 enable in 6045i?

Sent from my Idol 3
[Onetouch Idol 3 General] kal250:
Fsg partition contains band info see this post

http://xdaforums.com/idol-3/help/warning-eluga-switch-rom-disables-s-lte-t3470543/post68904370

Search google nv 6828 hacks

This may help but you will ultimately have to edit fsg and hope radio supports the fsg mods

https://play.google.com/store/apps/d...dnguyen.nvcalc
[Tilt, TyTN II, MDA Vario III General] bouyaka:
in windows media player the video don't turn to landscape when in full screen. it cut the left and right side... i'v try the "oldSAP Landscape.cab" but it's changing nothing... any idear?:confused:
[Tilt, TyTN II, MDA Vario III General] PerfAlbion:
Mine will go full screen landscape, but only when I have the keyboard slid open. When it's closed, Full Screen=Full Screen portrait, even if I manually shift it to landscape display.
[Tilt, TyTN II, MDA Vario III General] bouyaka:
for me even with the keyboard opened, no landscape! :mad:
[Tilt, TyTN II, MDA Vario III General] bouyaka:
strange, coreplayer plays it in landsape ok...
[Galaxy S3 Neo Q&A, Help & Troubleshooting] Dawson-10:
Hi i am looking for best rom on my GT-I9301l

Best for : GAMING,PERFORMANCE,BATTERY LIFE, INTERNET

thank you so much :

PS: Sorry for my bad English Iam Czech :)
[Galaxy S3 Neo Q&A, Help & Troubleshooting] GRoland08:
i think it's motion. Its's stable, fast, battery is good sry my english

:D
[Galaxy S3 Neo Q&A, Help & Troubleshooting] kimiaarian:
Cm 12.1 and ciro os
[Galaxy Grand 2 Q&A, Help & Troubleshooting] AiWaNczewski:
Hello guys! :), I have Grand 2 LTE, rooted, TWRP 2.8 , had installed xposed, can i install Evo-A5 (4.4.2) by the TWRP? or i need flash CWM? :) really need speed help :D
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Dankie001:
Dude,i don't think it matters.I am on philz and i've almost tried all roms for grand 2 and philz never let met down.

Philz is the best.Hope i helped :)

Note:-I ain't on LTE.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] AiWaNczewski:
Thanks for help. But in CWM and in TWRP i get the same stuck on logo samsung... :/ i try download 2 roms and both roms wont run more than samsung logo.. idk what i doing wrong
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Dankie001:
Make sure you're rooted and supersu installed,Philz recovery installed,follow exact installation procedure of the rom.

There's usually a recommeded recovery so i'd advice use that but i've used philz for almost all roms on my grand 2 [ms013g] and works like a charm.

Hope you get your desired rom installed?
[BlackBerry Priv] gcbxda:
Starting this thread to document my adventures on rooting via QUADROOTER

https://www.checkpoint.com/downloads/resources/quadRooter-vulnerability-research-report.pdf

(is there a main android->hacking thread? i can only find empty threads mentioning this as news, not as any effort)

Vulnerabilities:

* CVE-2016-2059

* CVE-2016-2504

* CVE-2016-2503

* CVE-2016-5340

feel free to join and point to other developments on the same lines.
[BlackBerry Priv] gcbxda:
I am on a ATT model but not on att network, so I am denied updates... this is what I got:

please share yours if on other models, or after receiving updates.

Sent from my STV100-1
[BlackBerry Priv] .K':
I am on the latest MM Beta.

Model: STV100-4

Android Version 6.0.1

Build Number: AAF960

My device seems to be only vulnerable to :

- CVE-2016-5340
[BlackBerry Priv] drtechy:
Verizon lollipop
[BlackBerry Priv] Dvdxploitr:
Isn't QuadRooter the program that has been on tech sites regarding viruses/malware?
[BlackBerry Priv] Veritas06:
It can be used maliciously because the exploits allow root access. We would just need someone to create an app (& manually disable Android's Verify Apps feature), that would inject SuperUser instead of a malicious app. I guess the next problem to overcome would be the Locked Bootloader, & if the PRIV's extra security settings would even allow the rooted phone to boot.
[BlackBerry Priv] Sethcreed:
It wouldn't work because of the BIDE and trusted boot chain.
[BlackBerry Priv] Veritas06:
Thanks, I was wondering about that. Oh well, I didn't really think it would be possible with the extra security measures, I was just hoping we could have gotten lucky.
[BlackBerry Priv] gcbxda:
can you point me to more info on that please? I'm for now just trying to bootstrap su in the active session.

after i have that i can start to worry about those other pieces to have proper roms/permanent root
[BlackBerry Priv] Sethcreed:
When u turn the power on them the boot chain of trust gets power:

1. Primary Bootloader in the SoC, which loads

2. secondary Bootloader. This loads the OS and after that the apps.

All steps are signed by secret key.

Every SoC has an own UID and secret key, which is protected by Fuse technology. These keys using ECC key-2-key Encryption to produce new keys.

Because of the signing process none of the bootloaders can be compromised.

The secondary Bootloader and the OS have non-editable eMMC starting addresses secured by Fuse.

And the SoCs don't have JTAG anymore.
[BlackBerry Priv] mitp0sh:
difficult but not impossible...

Hey,

so far that is pretty much the default design for a chain of trust. Nothing special here. But even these system cannot protect against every attack. The problem we are talking about here is always persistence, right. We might be able to takeover the phone, by utilizing an browser exploit or any other type of exploit, but once the device is rebooting all will be gone.

The challenge now is find a way to reinvoke the exploit after boot without doing it by direct manipulation of the system or one of the binaries.

This is certainly possible, but it has to be researched. IPhone jailbreaks are not different, btw.

My idea would be to have a look at all of the system application so see if they use a mechanism like for example Java Reflection or Serialization. Sometimes applications do dirty things like delay load code with a mechanism different from a default invokation. The interesting part here is that once such a mechanism is found you will be likely have to possibility to create a "modified" payload that resides in the "data" part of an application and luckily that cannot be protected by a boot chain of trust.

I have a Blackberry Priv here, and it will be vulnerable ( haven't used it for quite some time... ). When I have some free time, I will give it a try.

Regards,

mitp0sh of [pdx]
[BlackBerry Priv] Shani Ace:
It would be so awesome if this would eventually work! I'm getting sick and tired of this annoying BB Bloatware on the Priv (not to mention, not having root access in the first place). I'd love to install CM or any other AOSP ROM for that matter...
[BlackBerry Priv] PaintballerAlex07:
I'm happy as long as we can get rid of some of the downloadable bloatware. That way we can have more storage space and ram to use. I'm sure temporary root can help with this.
[BlackBerry Priv] Shani Ace:
Well actually, storage and RAM are not a problem on the Priv, it's got both in spades - unlike all those outdated QWERTY-smartphones I had before (Droid 4, mytouch 4G slide). ;)
[BlackBerry Priv] leblah:
Any chance of generating a useful SHA collision in a BB OS reload image? Also wondering if there could be any exploits via BlueTooth or the radio, (did they isolate radio CPU resources from the rest of the system?)
[BlackBerry Priv] 1linuxfreak:
Is there a way to do a root execute after boot, it would seem that the quadrooter exploit would need a booted phone to work either as a malicious exploit or as a way to gain user root. This would bypass the check at boot too. To bad the AutoMagisk will not work but on bootloader unlocked phones.
[BlackBerry Priv] maxpayne4:
Its gonna be an achievement, seeing root on a priv
[BlackBerry Priv] wokawoka:
that's the last qwerty android phone (with ok specs for nowaday's standards) on the market and having even a temporary root access to the phone (until the following boot) would be just great!!!
[BlackBerry Priv] todarkness:
Thinking of getting the Priv. Bootloader will be locked forever and Root seems unlikely. that is bad :( especially if BlackBerry decides to stop the Android Updates.
[BlackBerry Priv] chris8189:
Do people here not understand that BlackBerry has always been about security? The whole point of the Priv, and all other BlackBerry handsets is that they can't be 'rooted', exploited or jeopardised in any way, thanks to the years of experience that they have in making secure software platforms.

Pick a non-BlackBerry phone to root, and have some respect.
[BlackBerry Priv] santimaster2000:
No, the whole point of the Priv is having a good keyboard and Android.
[BlackBerry Priv] chris8189:
As well as a fantastic layer of security that is extremely tough to hack. Which I'll say again, is what BlackBerry have always put first and foremost.
[BlackBerry Priv] ZeDestructor:
You can have both. That's how Secure Boot on Windows x86 works: you can disable the secure boot chain in the UEFI or, even better, enter your own keys that you sign your own binaries with. Of course, Android vendors are still refusing to accept their fate in becoming basic, boring hardware vendors (mind you, Google isn't exactly helping there), so they're locking down bootloaders and removing user control.. so we have to hack our way in instead.
[BlackBerry Priv] Maiselff:
Wut?

Bb is nom rootable, like j sm exynos bug series.

Resuming, is not rootable, because nobody gain money, and small number sell, and now Bb so non rootable, because the people rejects arbitrary things.

You cannot deny, today Bb is failed.

Enviado de meu MB886 usando Tapatalk