yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] AcmE85:
Did you flash supersu too? If yes, repeat the above steps and don't do it.
[ONE Q&A, Help & Troubleshooting] w0lfy117:
I don't have supersu installed. I had wiped and unrooted it after it was stuck on bootloop.
[ONE Q&A, Help & Troubleshooting] Renosh:
You never mentioned what gapps you flashed? Flash opengapps (full) and CM13 and do a full wipe (system, data and cache) and you should be fine. Don't flash Supersu if you're flashing CM13
[ONE Q&A, Help & Troubleshooting] w0lfy117:
I plugged it into my laptop and then wiped everything. I installed CM12 and flashed it. Was still on bootloop. I could only go into fastboot mode.
[ONE Q&A, Help & Troubleshooting] w0lfy117:
The GApps for CM13.
[ONE Q&A, Help & Troubleshooting] gs-crash-24-7:
I would strongly recommend going back to stock rom. This way you can ensure the device itself is not broken or damaged.

Since only fastboot can be entered you should download the CyanogenOS fastboot package from https://cyngn.com/support and flash it with the install script. Please note that cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip is the right pack to flash since no root comes with it.
[ONE Q&A, Help & Troubleshooting] Upu:
You should download this file from https://cyngn.com/support cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip

and have Drivers installed, ADB,Fastboot (Android SDK)too.

Or Just let your Windows handle this.

Android SDK - you can download SDK manager(141MB) here and let him download platformtools only or download my attached rar file (2 MB), where is platform tools that u need.

Extract CM fastboot zip to your adb,fastboot folder (mine is: .....\sdk\platform-tools ), run your phone in download (fastboot mode), ofcourse connect it to pc .

Open CMD in that folder (Shift+Right click and open new cmd window here)

Check if its connected by running this command:

fastboot devices

if it show some device connected, then run these commands one by one:

fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img

U can download TWRP or some else recovery and flash it too. :)

After that u wont loose any internal data, so i would recommend you full wipe except internal storage and flash some new rom + gapps.
[ONE Q&A, Help & Troubleshooting] w0lfy117:
My boyfriend has tried every method possible. Even hard bricking it and then soft bricking it and then trying to recover everything. And it's just stuck on bootloop. Also.. I have tried to boot into bootloader and it only goes into fastboot mode and recovery. Nothing else. As if bootloader didn't exist at all. I'm very concerned and I'm freaking out...
[ONE Q&A, Help & Troubleshooting] keks411:
Whatever he did, he did not hard brick it and then soft-bricked it afterwards.

If its hardbricked, you successfully turned it into a brick and there is no easy way to get it back.

I am 98% sure that the solution posted in post #10 works for you.

Instead of posting the same thing over and over, tell us what you tried so far and why it did not work.

Basic IT-Support 101.
[ONE Q&A, Help & Troubleshooting] Renosh:
There is no bootloader mode on the Oneplus One, just fastboot and recovery. You can do everything you need from those two modes. Try the instructions on post 10
[ONE Q&A, Help & Troubleshooting] w0lfy117:
What I did was flash CM13. It didn't come with CM13 GApps. I flashed that after I noticed it. I still had CM12.1 on my SD card. Or so I thought. I wiped it and found out that I didn't have CM12.1 on my SD card anymore.

I downloaded bacon toolkit because my OnePlus One was then stuck on bootloop. I hadn't done a thing to it. Didn't set up adb or anything. I couldn't. Kept getting a pop up (right after I closed it, it would pop up again. Over and over) "set up wizard has stopped working". I couldn't even open the settings without it harassing me. I restarted my phone and the pop up kept coming back up. Once I wiped the CM13, I went to look for CM12.1. When I didn't have it, I realized that I wasn't going to be able to use my phone die to bootloop for an hour.

I used the Bacom Toolkit. Downloaded ADB.exe and worked my way up. I imputed the information. 64 GB, 12.1 CM and then it went on to loading the information for the toolkit.

When it didn't recongize it, I had to keep launching the ADB.exe to get the Toolkit to read the phone. Finally about 12 minutes or so into it, I clicked on bootloop/softbrick option and it lead me to some other options. When I read carefully through them, I had clicked on these (in order)

"Wipe"

"Install from zip"

"Installed 12.1Yoga(something numbers ;-; I forgot the exact name, I'll see if I find it tomorrow)"

"Unzipped"

"Pushed"

"Full unroot"

"Lock eom"

I was stuck on CyanogenMod.
[ONE Q&A, Help & Troubleshooting] keks411:
Then now follow the instructions from post #10 and everything will be fine.
[Remix OS for PC] schwabbele:
Hi,

my laptop where I run remix OS requires the firmware iwlwifi-7260-17.ucode (at least this is required when I run debian linux on the same laptop).

I installed remix OS on a partition on hard disk.

With remix os wifi works, bluetooth doesn't.

I booted debian linux, mounted the remix os partition, mounted system.img (which is apparently an ext4 file system) and copied the firmware iwlwifi-7260-17.ucode to the mounted /lib/firmware (of the mounted system.img).

Then I rebooted into remix os.

In remix OS, dmesg shows that the iwlwifi-7260-17.ucode firmware is loaded correctly.

Nevertheless, only wifi works but bluetooth doesn't.

Any ideas?
[Remix OS for PC] Jerri3:
Hi,

Same problem here.. wifi is working fine but bluetooth isn't.

Can't find any fixes.

Tried booting from usb and the Remix OS Player. Both have Wifi and they don't have Bluetooth.

When I use the usb boot I can turn Bluetooth on and after a few seconds it is turned automaticly off.

When I use the player I cant even turn bluetooth on or off cause it's not there. I turned bluetooth on on my laptop and connected to the device, but the player doesn't see that..

Please help me, cause I spend all they day on this issue.

Thanks,

Jeroen
[Samsung Galaxy S7 Edge Questions and Answers] cappuccino500:
There are similar tools for this feature available?

This is a great feature on the Lumia 950.
[Elephone P9000 Questions & Answers] robinvandernoord:
Hi,

I've seen a lot of root tools and guidelines, but they're all for windows... Is there a way for mac os x users to root the Elephone P9000?
[Elephone P9000 Questions & Answers] Jonny:
Yep... use an emulator.
[Elephone P9000 Questions & Answers] robinvandernoord:
Could wine work?
[Elephone P9000 Questions & Answers] Jonny:
I have no idea, I'm not stupid enough to buy a mac... overpriced things that they are, at least for the hardware that they provide.
[Elephone P9000 Questions & Answers] robinvandernoord:
The software works neater than windows though, but let's not talk about preferences... I didn't even buy it myself by the way.
[E 2015 General] BillyMumphry:
ADB Push/Pull Simple Guide​

To Push a single file from PC to Android, in this case a ROM.zip, you must place the ROM.zip inside the same folder as your ADB and Fastboot files. Right click anywhere inside that folder while holding the shift key down to open the cmd prompt and run these commands:

adb devices

adb push ROM.zip /sdcard​

To Push multiple files at once using a single command do this:

In your SDK/Platform-tools folder, or whever you have your ADB files, create a folder called "tmp"

Place all the files you want to push into the tmp folder then run this command:

adb devices

adb push tmp /sdcard​

--Simple eh?

To Pull a file (In this case a TWRP backup located on the sdcard in a Subfolder of TWRP called BACKUPS) from device to PC or HARDDRIVE.:

Create a folder inside SDKplatform tools or where ever you have your ADB located. I call mine TWRP_Pulls. Inside that folder create a subfolder and give it the name of the backup/File you are pulling. In my case I name the folder by the backups date and numbers.

FOLDER Inside the ADB folder-->TWRP_Pulls

FOLDER Inside TWRP_Pulls-->2016-05-03--17-54-24​

The full command would look like this:

adb pull /sdcard/TWRP/BACKUPS/ANDROIDSERIAL/2016-05-03--17-54-24_cm_surnia-userdebug_6.0.1_MHC19Q_bdf9ce04cf C:\Users\Name\Desktop\SDK\platform-tools\TWRP_Pulls\2016-05-03--17-54-24​

(Where ANDROIDSERIAL is your devices serial number and can be found by entering "adb devices")

Make sure you place a space between the first pull and the /sdcard and another one after the ROM.zip and before the <path to location>

adb pull[Space]/sdcard/TWRP/BACKUPS/ANDROIDSERIAL/

2016-05-03--17-54-24_cm_surnia-userdebug_6.0.1_MHC19Q_bdf9ce04cf[SPACE]C:\Users\Name\Desktop\SDK\platform-tools\TWRP_Pulls\2016-05-03--17-54-24​

============================================================

CREATED BY: BillyMumphry for educational purposes only. I hope it will help some people as I know I sure fumbled with these Push Pull commands when I was learning.

------------------------------------------------------------------------------------------------------------

* If anyone has any questions or additions fell free to comment or PM or email me:​

bmumpy@gmail.com​
[Sony Xperia T, TL, TX, V] fantasmag0ria:
Hi,

also camera app won't save photos directly to internal storage. Looks like apps have no permission to write to internal storage.

XPERIA V: unlocked,rooted and CWM installed.

I flashed XPERiA_V_LiTE_V2_by_doenen and Toxizen. The same problem on both. On CM 12 everything was fine.

I had some problems getting rid of CM backup and installing CWM.

Any ideas?
[Sony Xperia T, TL, TX, V] MESA:
Write this in terminal emulator:

su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
[Sony Xperia T, TL, TX, V] fantasmag0ria:
Already tried that, didn't work.

But, I formatted internal memory from CWM, did full recovery and it started working!
[Xperia Z5 Android Development] zacharias.maladroit:
Hi guys,

just finished building TWRP 3.0.2-0 for the Z5

Download

TWRP-for-CM (folder)

recovery_3.0.2.img (fastboot flashable file)

Source:

https://github.com/omnirom/android_bootable_recovery (TWRP, recovery - place in bootable/recovery-twrp)

https://github.com/CyanogenMod (CyanogenMod source)

https://github.com/Sony-Kitakami (place in .repo/local_manifests )

Build:

source build/envsetup.sh

lunch cm_sumire-userdebug

mka clobber && mka recoveryimage RECOVERY_VARIANT=twrp

Thanks to [MENTION=5864662]moonbutt74[/MENTION] for bearing with me and all my questions :silly:
[Xperia Z5 Android Development] Sony guy:
Not Working on E6633 , When I power on the device , Sony logo show and the device power off immediately

Edit :

It works Successfully , I had flashed It as a kernel hahaha

Thank You ^_^
[Xperia Z5 Android Development] Sh4douw:
Hello,

I've had the same issue than Sony guy (the device which power off after few seconds on the Sony logo), but I've had correctly flashed this recovery... I don't understand

Any idea ? I have also an E6633.

Thx
[Xperia Z5 Android Development] Sony guy:
How did you flashed ? As kernel or as recovery ?

If as kernel you will have this problem . But as recovery it will work successfully
[Xperia Z5 Android Development] Sh4douw:
Sorry, I misspoke xD

I flashed it as a recovery btw.

But, by "it works Successfully", what did you mean ? You can access on the recovery or you can boot on CM13 ?

Indeed, my device power off not after the flash of the kernel and the recovery, but AFTER the flash of the CM13 + GApps.

So, if by "success" you meant that you can boot totally on CM13, which ROM and which kernel did you flashed ?

But if it concerned the recovery only, this is good, I have the same result than you x)
[Xperia Z5 Android Development] Sony guy:
Yeah I can boot into cm13

I used cm13 rom , cm kernel and this recovery

I flash GAPPS after the rom and I get setup wizard FC

so I did factory reset and then it works fine without problem
[Xperia Z5 Android Development] Sh4douw:
Oh, I see :o

Do you can link me which kernel and which ROM did you use ?

Also, what pack of GApps did you use ?

Sorry, it's the first time I try to flash a custom ROM, I'm little lost as you could see xD
[Xperia Z5 Android Development] Sony guy:
Click here to download the rom

http://xdaforums.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163/page11

And Gapps you can find it in the first page of the above thread
[Xperia Z5 Android Development] Sh4douw:
Okay, I don't understand why, but for booting on CM, I had to reflash the kernel !

Without it, my device power off one second after the Sony logo

It finally works, thanks you :D
[Xperia Z5 Android Development] frostmore:
Hi,

Are you able to make one for the Z5P??

some of us are still stuck at ver 2.8.

also, i have used your root kernel program with the lastest twrp and it can boot into recovery,since i am using a custom kernel, i think it will be nice if there is a flashable img file for the latest twrp.

Many thanks in advance.
[Xperia Z5 Android Development] Nayibmc:
Will this work with my new Z5, Android 6.0.1, totally stock?
[Xperia Z5 Android Development] albertobom:
No. Just Cm/Aosp
[Xperia Z5 Android Development] Sergeyra29:
How can amplify the sound in Bluetooth?
[Xperia Z5 Android Development] mpro420:
Faux sound setting in Kernel Adiutor is not working(im on Z5 RR latest build plus Zach's kernel), but it working on Romaur 4.2.0 plus Aur-kernel 4.0.

try "FauxSound app v1.5" from play store, its worked with wired headset, maybe worked with Bluetooth too.
[Xperia Z5 Android Development] Sergeyra29:
How can amplify the sound in Bluetooth mixer_paths?
[Xperia Z5 Android Development] CyNoob:
Sorry wrong reply. XD
[Xperia Z5 Android Development] adize:
I have questions:

1. How to install/flash as recovery? via adb fastboot?

2. Will this work on stock rom? if yes, what firmware?

Thank you
[Xperia Z5 Android Development] Sony guy:
1 - fastboot flash recovery x.img

2 - I think this recovery is for CM ROM

You can search in the android development section for stock ROM , it works on all firmwares
[Xperia Z5 Android Development] GeramanX:
Hi guys, noob question here: I have twrp old version, can I flash this in recovery?

And also I want to try the xz rom but tried flashing and didn't work, it is my understanding that it was caused by the old twrp and using this I'll be able to use that rom.

Thank you for your help.

[emoji41]
[Xperia Z5 Android Development] Rjaka:
oh, sorry, wrong thread
[Xperia Z5 Android Development] _cab13_:
Hey [MENTION=3037651]zacharias.maladroit[/MENTION]

Flashed your recovery but got a problem with decryption...

I'm using a PIN, tried disabling it at startup and using default_password but it didn't worked

Any idea ? Thanks
[Xperia Z5 Android Development] ataraxist:
Is this recovery also usable for Xperia M5? Does anyone know?
[Xperia Z5 Android Development] Bautinho88:
I can't backup boot partition with TWRP 3.0.2.0. There is no point to check when I want to backup my whole system
[Xperia Z5 Android Development] HaoZeke:
Hey, using the omnirom sources I can build twrp but it can't do anything. No recognition of the partitions or system data or anything... Ideas?
[Xperia Z5 Android Development] CHROME19969:
no it's not ,anywhere on xda if you don't see your device's number in the title or on the main thread it means that it's NOT compatible.

unless explicitly stated by OP. this TWRP is only for Z5 series sorry.
[Xperia Z5 Android Development] TonskuDaigle:
Any idea why I might be getting these sort of errors in TWRP?

Failed to mount '/system' (invalid argument)

Others besides system are: data, cache, firmware, appslog, oem, persists, lta-label, diag

At the beginning of the log it says:

E:Unable to find partition size for '/boot'

E:Unable to find partition size for '/FOTAkernel'

E:Unable to find partition size for '/ta'

E:Primary block device '/dev/block/bootdevice/by-name/userdata' for mount point '/data' is not present

E:Unable to find partition size for '/modemst1'

E:Unable to find partition size for '/modemst2'

Failed to mount '/data' (invalid argument)

Unable to recreate /data/media folder.

Updating partition details.

Then a bunch of those failed to mount variations. Then "...done" and "Full SELinux support is present."

So when I tried to take a backup, it doesn't find anything so there's nothing to back up.

And when exiting TWRP, it tells me there's no OS installed. I've PixN ROM installed via fastboot and it's working fine.
[Xperia Z5 Android Development] _cab13_:
Hey,

Flashed a backup with this twrp. I got hard bricked, no way to get into fastboot / flashmode. Any idea ?

Full thread here
[Xperia Z5 Android Development] zacharias.maladroit:
encryption and/or decryption is uncharted territory,

afaik TWRP isn't even supposed to work with it

sorry, no idea, I don't get that - this kind of doesn't make sense :/

something wrong in fstab ?

Did you meanwhile solve it ?

yep, you booted the TWRP image by chance ?

reboot to TWRP from the partition and the detection should work

If it doesn't get into fastboot or flashmode, the chances are pretty moot :(

from SonyAOSP Hangouts:

did you flash your TA partition back (and potentially something went wrong) ?
[Xperia Z5 Android Development] frabe8378910:
It works flawlessly after some fixes/rebuild from [MENTION=6979267]nailyk[/MENTION] on the Z3. Maybe he could give a hint what he did which could help on the Z5.
[Xperia Z5 Android Development] nailyk:
I wasn't able to handle stock encryption because they use a modded version of dm-crypt and never can find the sources.

However if a custom rom had encryption you can get it into twrp.

Are we talking about FBE or FDE?
[Xperia Z5 Android Development] frabe8378910:
Just as simple as in the former Android Versions since 5.x.

FDE, all or nothing. You know the pass at boot or the phone will wait (for ever).

Gesendet von meinem Xperia Z3 mit Tapatalk
[Xperia Z5 Android Development] nailyk:
In most case, when stock rom is booted and loop forever at the padlock logo, this is not an decryption problem but a filesystem one.

Probably device are f2fs encrypted and the stock rom doesn't handle f2fs.

So I'm confused, are we talking about TWRP? (sorry didn't read the full backlog)
[Xperia Z5 Android Development] frabe8378910:
Sorry, if I confused you. I'm looking for TWRP support for "Full Disk Encryption" (FDE). When booting TWRP it will ask for the PW, but always complain about entering the wrong PW. The exact same behavior we had on TWRP for the Z3 and was fixed by you.
[Xperia Z5 Android Development] nailyk:
TWRP decryption

Oh ok. Please post a full /tmp/recovery.log after trying to decrypt only once with the good password. (please read the log to change the password if it appears, or change your device password to foobar before)

When hardware encrypted (on D6603 with TZ) your password unlock the TZ which contain the dm-crypt random password for your partition(s).

My job was pretty easy, all the TWRP team has done the unencrypt code before, only need to add the hardware part: getting qseecomd to start.

First rebuild with TW_INCLUDE_CRYPTO & TARGET_HW_DISK_ENCRYPTION (expect some build troubles :p) then add blobs to get qseecomd starting.

Can't do for you as I don't own the device but should be really similar.

First, when twrp will be built with hardware crypto support you *should* be able to decrypt with:

1. Cancel the prompt of password,

2. mount the system partition,

3. start the qseecomd service,

4. try to uncrypt (twrp uncrypt foobar should work, also, just in case, please try twrp uncrypt $(echo FOOBAR|xxd -c 256 -ps) : uppercase hex).

It should work because you have all your blob set. Now you can play with blobs to find which one are needed.

Obviously this will work *only* with opensource dm-crypt implementation as TWRP rebuild it.

Hope this will help you and the dev to make encryption available into twrp.

Good luck :highfive:

P.S.:

readelf help a lot:

nailyk@ :) % readelf -d vendor/qcom/prebuilt/proprietary/msm8994/vendor/bin/qseecomd ~/lineageos/14.1

Dynamic section at offset 0x1cb8 contains 35 entries:
Étiquettes Type Nom/Valeur
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="RoyalBlue"]libc.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="royalblue"]libcutils.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="royalblue"]libutils.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="royalblue"]liblog.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="royalblue"]libdl.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="red"]libQSEEComAPI.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="Red"]libdrmfs.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="royalblue"]libc++.so[/COLOR]]
0x0000000000000001 ([B]NEEDED[/B]) Bibliothèque partagée: [[COLOR="royalblue"]libm.so[/COLOR]]
0x0000000000000020 (PREINIT_ARRAY) 0x11c88
0x0000000000000021 (PREINIT_ARRAYSZ) 0x10
0x0000000000000019 (INIT_ARRAY) 0x11c98
0x000000000000001b (INIT_ARRAYSZ) 16 (octets)
0x000000000000001a (FINI_ARRAY) 0x11ca8
0x000000000000001c (FINI_ARRAYSZ) 16 (octets)
0x000000006ffffef5 (GNU_HASH) 0x288
0x0000000000000005 (STRTAB) 0x5d8
0x0000000000000006 (SYMTAB) 0x2c0
0x000000000000000a (STRSZ) 397 (octets)

Blue ones are built, red ones are proprietary. IIRC I wrote a script to do this recursively (too lazy to do it manually) but I can't find it anymore.

P.S.: so good to remember that, it was my first step into the android world (:
[Xperia Z5 Android Development] HaoZeke:
Well.. I gave up on twrp compilation... I mean the good thing is this recovery works perfectly and twrp gets very scarce updates (not surprising, it's more or less perfect)
[Xperia Z5 Android Development] frabe8378910:
Thanks a lot for you help, nailyk!! I'll post at least the logs on the weekend.

But after browsing through some docs on the last weekend what's all required to compile that TWRP beast I'm not sure whether I find the time to get that done in the next weeks. Before really digging into that Lineage14.1 for Z5 needs to support FDE, otherwise I'd had to work an that too first ... :laugh::laugh::laugh:
[Xperia Z5 Android Development] nailyk:
Yes, to build twrp you need to setup a full build environment (Lineage ok but omnirom preferred)
[Xperia Z5 Android Development] TonskuDaigle:
Pardon, but how do I boot an image? And how do I define where I boot from really?
[Xperia Z5 Android Development] Aiman Hossain:
Bro, will it work in anfroid 7.0?

Did anyone try?

Please help, i have upgraded my sony xperia z5 to nougat, but I'm afraid to try since this recovery was made for previous android version
[Xperia Z5 Android Development] klemen241:
yes i just tested, it works
[Xperia Z5 Android Development] Hamidreza2010:
[MENTION=3037651]zacharias.maladroit[/MENTION] can i use this on android N ?

I want to copy this rocovery.img to poc folder and make advanced kernel for android N ( ON 6633 android N )

Can i do this?
[Xperia Z5 Android Development] HaoZeke:
Works perfectly well on N...

About the advanced kernel, I guess you could but... is there much point in hardbaking the recovery?
[Xperia Z5 Android Development] Hamidreza2010:
i want to do this:

https://xdaforums.com/showpost.php?p=71270012&postcount=815

i need correct recovery.img for android N.for this i ask this recovery work on N or not and get my answer :D

thanks