yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] ggow:
Use the following commands to flash the recovery

adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery

- I have Cyanogenmod Recovery working except a few minor niggles

- Let you know once it's fully working

- It looks like we can't boot unsigned images that are flashed to the recovery partition

- If I boot the image from fastboot rather than flashing it then it works

- CVE-2014-0973 is patched in the bootloader
[Fire Android Development] Vlasp:
Yeah, I was focused on booting rather than flashing. Now that we have something that can boot, we can make a safestrap for this device.
[Fire Android Development] Awesomeslayerg:
Wait did you already try it on the device? What recovery.img are you using?
[Fire Android Development] ggow:
- I built one from source: Cyanogen 12.1 recovery

- See attached picture
[Fire Android Development] Vlasp:
I am using the one you posted on the first page to build it, but it gives me an error in fastboot.
[Fire Android Development] Vlasp:
Nice. Can you send it to me? I can test making CWM using yours as a base.
[Fire Android Development] ggow:
- I uploaded it here: https://www.androidfilehost.com/?fid=24052804347853392

- This is a work in progress so please be careful
[Fire Android Development] Vlasp:
I should be fine if I just did "fastboot boot recovery.img", right?
[Fire Android Development] Awesomeslayerg:
That's an unedited version.. it wasn't meant for flashing.
[Fire Android Development] Vlasp:
Yeah, I unpackaged it and tried building using the files in it.
[Fire Android Development] ggow:
Yes, that will work.
[Fire Android Development] Vlasp:
OK, Thanks!
[Fire Android Development] Awesomeslayerg:
Gonna try it tiday
[Fire Android Development] ggow:
- With the recovery I previously posted - i have identified several issues

- Signature checking of the update package was mandatory - I have just disabled this

- I have also found that partitions are not been mounted correctly and this accounts for why updates were failing

- I temporarily hack this to work and was able to flash a non amazon update.zip, flashed a modified gapps 5.1 package and SuperSU.zip :)

- I will produce a new version which will enable us to easily root and install a proper GAPPS package

- It is a little crude in operation, but we will also be able to use this to load any ROM we want when fully working

- Then work can begin to port CM-12.1

EDIT: Added screenshot showing fresh FireOS rooted and gapps installed by flashing SuperSU.zip and Modified Gapps 5.1 package
[Fire Android Development] Harry44:
Were you able to fix the partition mounting issue. I was about to disassemble it and do it myself? Can you upload that version please I am trying to make a flash-able prerooted, alternative launcher deamzon'd/debloated rom.
[Fire Android Development] ggow:
- No I was just going to look into the mounting issue

- I just modified the recovery.fstab to be this:

/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/UBOOT /UBOOT emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/TEE1 /TEE1 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 defaults defaults,length=-16385
/dev/block/platform/mtk-msdc.0/by-name/MISC /misc emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/mmcblk0boot0 /boot0 emmc defaults defaults
/dev/block/mmcblk1p1 /sdcard vfat defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 defaults defaults

- then when I booted into recovery the file systems still didn't mount - I issued a 'mount -a' at root prompt and then /system /data etc mounted and became available.

- How did you fix it?

- I'll upload a new version when I have got a couple more bits sorted and tested a little more.

EDIT: Touchscreen element is also not working correctly - suspect that the screen orientation is wrong
[Fire Android Development] Harry44:
Got it thanks. I'm working on mounting now.
[Fire Android Development] ggow:
Why Port Cyanogen Recovery?

In case some of you wondering... "Why Port Cyanogen Recovery?"

- I have never worked with MediaTek devices so this will be easier and quicker to get running.

- I am planning to port TWRP very soon, however...

- This will fulfil the immediate need for a recovery to enable users to at least be able to root and install gapps easily.
[Fire Android Development] Awesomeslayerg:
[MENTION=5749760]ggow[/MENTION] thanks for working a custom recovery for us man. Can't wait to try out custom roms on this device soon and hopefully marshmallow
[Fire Android Development] ggow:
- I have the mounting issue sorted now

- At the moment in fstab the /sdcard is mapped as external sdcard - I think this is ok in case adb access is lost for some reason then we should be able to load files from a microsd reader on a desktop.

- When I get home later or tomorow morning I'll test loading update.zip(s) from /sdcard and that should be good enough for a BETA version
[Fire Android Development] Harry44:
I can confirm after fixing fstab, this installs the supersu.zip easily, gapps was finicky due to the large size of some of the GAPPs packages and the small size of /system SO BE WARNED, the largest Gapps that I was able to get to work was about 79mb, I don't know if it was just me or not. You're also able to install things like Xposed through this. Basically any flash-able zip.

Okay amazon lock down us from flashing a recovery, this is the next best thing!
[Fire Android Development] diegocr:
With this tool can extract fstab from stock recovery.

http://xdaforums.com/showthread.php?t=2798257
[Fire Android Development] Vlasp:
Yeah, that's what I used.
[Fire Android Development] theophile2:
I don't know if it's helpful at all, but a while back there was a project to repartition the Motorola Xoom internal storage to allow for larger ROMs than the stock partitions could accommodate. It ended up being called "BigPart." The thread is here. If the Fire partitions look to be tight quarters for custom ROMs, maybe something like this could be an option?
[Fire Android Development] bullet25:
There was also a similar project done with the 1st Gen Kindle Fire called OtterX.
[Fire Android Development] sd_shadow:
OtterX actually changed the partition sizes, I don't think that will be possible with a locked bootloader.
[Fire Android Development] Vlasp:
Can you post the latest CM Recovery that you have made? I am sure all of us would like to test it and try it out.
[Fire Android Development] ggow:
- Still not working properly

- I tested installing from /sdcard and it was a no go.

- I'll fix that and get a new version out.
[Fire Android Development] ggow:
I have released Cyanogenmod Recovery here
[Fire Android Development] Vlasp:
Updated with the latest on Recoveries for this device.
[Fire Android Development] humanBREW:
I was thinking if it would be possible to do a thing like a temporary custom recovery, one that is booted by stock recovery?
[Fire Android Development] t3chwizard:
We would have to be able to sign it with an Amazon certificate, which I don't think many people can easily get a hold of, or exploit it somehow (I am not sure if the devs have tried that yet, because it could work but who knows).
[Fire Android Development] humanBREW:
Oh! I understand. I saw that kind of recovery in an old samsung recovery but i had no idea what was involved with that. BTW do you know about documents I could read to learn more about recoveries and bootloaders?
[Fire Android Development] hjavaher:
What does this program do? How it works?
[Fire Android Development] sd_shadow:
allows installing custom roms, and other functions

but only works with 5.0.X bootloaders
[Xperia Z3 Q&A, Help & Troubleshooting] ikho47:
Hello there,

have been trying to root my new xperia z3 for 3 weekends now with no luck.

My bootloader has been unlocked through sony website, then relocked and unlocked many times using flashtool.

Looks like all the recoveries (doomlord, twrp) I could find work only on 4.4.4. Then I use flashtool to flash lollipop 5.1.1 23.4.A.1.200 and either wipe and loose the root or don't wipe all and enter a bootloop.

Flashing those recovery kernels straight on lollipop make the phone enter bootloop.

Are you guys able to root those Z3 under 5.1.1 ?

thank you
[Xperia Z3 Q&A, Help & Troubleshooting] jassalmithu:
Sure shot easy way is flash kitkat firmware and use giefroot or flash 5.0 firmware and use kingroot.
[Xperia Z3 Q&A, Help & Troubleshooting] lol1rfs:
Mate, you have to flash a prerooted version of 5.1.1 you can't just flash a stock rom and expect to stay rooted.

Downgrade to Kitkat then root and install a custom recovery. Then you download 5.1.1, Super Su and a custom recovery, create a pre rooted flashable zip with PRFcreator . Then flash it in your custom recovery and you're done. Rooted 5.1.1 with a custom recovery ready to rock.
[Xperia Z3 Q&A, Help & Troubleshooting] Jkay7:
Kingroot isn't recommendable, your IMEI is sent to China. Downgrade to 4.4, root with giefieroot, upgrade with pre-rooted ROM.

Btw: did you make a backup of your TA partition before unlocking bootloader?
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
Thanks a lot for your answer guys. :)

Am unusually struggling with this device.

Have already downgraded to kitkat, installed custom recovery and rooted. But the 5.1.1 stock flash indeed wipe everything.

Haven't found yet a custom recovery for 5.1.1 that doesn't make the phone enter a bootloop. Would you happen to have a link ?

I'll give a look to that PRFcreator, didn't know about it.

This is what I read about kingroot and haven't found any other way to root a 5.1.1 stock.

Where could I find a pre-rooter ROM then ? My wish was to be stock and rooted to be able to use apps like titanium backup and adblockers. Used to try custom roms every other day on my old SGS but today I'd be happy with something that just works.

Did not make any backup before unlocking but looked like flashtool was able to relock the device. Am I right guessing I didn't loose my DRM keys then ?

Thanks again for your answers.

Edit: looks like am missing sthg, what's the point in rooting a kitkat to upgrade with a pre-rooted lollipop right after ?
[Xperia Z3 Q&A, Help & Troubleshooting] Licaon_Kter:
After KitKat root you get a Lollipop pre-rooted image and flash it: http://xdaforums.com/z3/general/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361

Here are the steps: http://xdaforums.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056
[Xperia Z3 Q&A, Help & Troubleshooting] MickieH:
I hope you made a TA backup before unlocking your bootloader, otherwise you have lost your DRM keys forever.

Anyway, if your bootloader is now locked, follow the guide that Licaon_Kter linked in the above post.

The exploit that lets us root our Z3 only works on Kitkat, so downgrade first, run the exploit to obtain root, and install recovery.

You will then have stock, rooted, KitKat.

To get to 5.1.1, you will then need to either create your own pre rooted firmware, or download one that someone has kindly posted on here.

If you want to learn how to do it, read this --> Create your own pre rooted firmware with PRF Creator

PRF Creator will create a zip file that can be flashed from recovery, so once you have recovery installed, it's dead easy.

That will get you where you want to be.

However . . . and there's always a however lol . . .

. . . if you still have an unlocked bootloader, it is much simpler from wherever you are.

Find any custom rom that has recovery built in, and almost all do, then fastboot the kernel only, the boot.img.

Reboot your device and enter recovery.

Install your pre rooted firmware that you have either created with PRF Creator, or downloaded from here.

Job done.

My personal advice is read, read, and then read some more.

It can be very complicated, but you'll get the hang of it.
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
I still have an unlocked bootloader since flashtool can lock and unlock it in a matter of a second.

Went back again in KK rooted with twrp recovery.

Wiped data, cache, dalvik.

Flashed D6603_23.4.A.1.232_Customized_US_SuperSU_XZDR2.8.2 1 from the link above and ... CWM recovery report install from sdcard completed after 1s and nothing more. Am still booting in KK after that.

This didn't work for me. Am losing it now with this phone.

Am I missing sthg ? Any advice ?

Can't use PRFCreator, am under mac os...

Thanks to all for your help
[Xperia Z3 Q&A, Help & Troubleshooting] Licaon_Kter:
Try with TWRP too
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
tried twrp found there http://xdaforums.com/z3/development/recovery-z3-twrp-2-8-4-0-t3028846

phone is not booting anymore.

twrp post says it doesn't work on stock room.

---------- Post added at 02:16 PM ---------- Previous post was at 02:05 PM ----------

Is there really anyone out there with a rooted stock lollipop ?

or you are all using customs ?

am seriously questionning the thing now
[Xperia Z3 Q&A, Help & Troubleshooting] Licaon_Kter:
Why would you NOT follow the steps?

GO AGAIN from the start: http://xdaforums.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
I just can't, I don't have access to a window machine :(
[Xperia Z3 Q&A, Help & Troubleshooting] Licaon_Kter:
Both giefroot and FlashTool are for Win/Mac/Linux.
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
I appreciate your still trying to help me.

I do use flashtool and am able to root a Kitkat 23.0.A.2.93, so I don't see the point in using giefroot unless it could root a lollipop.

I have read thoroughly and downloaded pre-rooted lollipop stock roms from the link you provided.

Once under KK, rooted, with all settings set properly (debug, security, etc...), and all caches/dalvik/data wiped, the CMW recovery just don't flash those lollipop roms. After just one sec, it says install completed but then the device still boot under KK.

TWRP doesn't even intall, so am wondering if this is even possible to get a TWRP on stock rom.

Have tried all of those with bootloader unlocked and locked, or a mix like unlocked first to be able to root a KK, then relock to flash a stock prerooted 5.1.1 (as stated in the post) but then I get a device that doesn't even boot.

Tried dualrecovery too, flash the zip, and nothing.

I suspect all of you guys have used some sort of .bat windows utility to get through this.

Once again, thanks for your help and patience.
[Xperia Z3 Q&A, Help & Troubleshooting] Licaon_Kter:
The point is to go from the BEGINing _again_: Flash stock KK, giefroot, XZ, pre-rooted LP

I have done it in Linux w/ locked bootloader and stock ROM, hence my pointers.

XZDualrecovery has TWRP 2.8.7.0. But, do take note that you use Volume Down to enter PhilzTouch Recovery and Volume Up to enter TWRP.
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
am sorry, can't find how to use giefroot on a mac.

read quite a few post of people saying that was not working for them.
[Xperia Z3 Q&A, Help & Troubleshooting] Licaon_Kter:
Run the INSTALL.SH file in a console (just like they instruct you for the .BAT file for Windows), it detects OS and runs either adb for Linux or for Mac.

Well, like I said, it worked fine in Linux, I guess it should work on Mac, providing the device is detected ok beforehand and such. ( what does "adb devices" outputs with the phone connected ? )
[Xperia Z3 Q&A, Help & Troubleshooting] ikho:
yaaay, houray it finally worked

big thanks man, you saved me $500 on that one !
[One (M8) Q&A, Help & Troubleshooting] Kyaner:
Hi guys

I got an HTC M8s less than 2 months now and it has so many issues it's driving me insane at this stage....

It's on stock ROM unrooted with all the latest updates.

First issue that came up was not recognising the headphones after i plugged them in, that eventually went away after lots of searching and fiddling with settings etc.

Then it started going into Car mode while it was resting on the table, no input on my end no triggers set for it, hell i don't even own a car to use this function....

I disabled HTC car and that stopped.

The included micro usb cable somehow went bad, tried it on other devices, it will not charge....

Now i'm having some weird charging behaviour, it drops out of charging and resumes or sometimes it just stops charging (that doesn't happen when the phone is charging while being switched off, so i'm guessing it's not a hardware issue)

Another massive problem is that all incoming/outgoing calls go to the speaker which almost burst my ear drum first time that happened.

I have looked in every single forum out there and have tried all possible solutions, ranging from disabling google Chrome to trying every available speaker management/toggle related program on the play store but nothing seems to be working.

Some times if i plug in the headphones, make a call and then unplug them, then it works as it should for a little while. But later on it reverts to the previous mentioned behaviour.

One thing i have noticed, before it routes calls to the speaker, the screen will light up, no notifications come up and then all calls go to the speaker.

I used Wakelock to try and find out which program triggers the screen wake in order to remove it and maybe solve this issue but nothing came up.

Any input would be greatly appreciated as i am at the end of my rope with this device....

I still have my HTC DHD A9191 and i never had any issues with that phone, i'm very dissappointed with HTC :/

Thanks in advance

Yanni
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
Less then 2 months......return it ! Not even sure what you want to achieve here besides messing up warranty ?

:)
[One (M8) Q&A, Help & Troubleshooting] gsozcan97:
I am using Spign slim armor case on m8s and after using it my power button isn't working.

and I have a Motion Launch problem when phone is on my pocket it opens camera, calls someone because of the sensor.Any fix about that?
[One (M8) Q&A, Help & Troubleshooting] Hazem99922:
ok man

look i have htc one m8 + one m7+one max

the one m7 had the same problem of u

i will give to you one solution for try

i try it on the one m7 and its work

but on one max not work

on m8 not test yet

try this:

1. Turn phone OFF

2. Let charge for AT LEAST 10mins even if it doesn't look like it's charging.

3. Press and hold POWER + VOL UP + VOL DOWN for AT LEAST 2mins. Anything less will not reset the charge mode.

4. After 2mins release the buttons and the phone should boot as normal

if it not charge at the first time then try it again andd u will be OK
[One (M8) Q&A, Help & Troubleshooting] Kyaner:
Hi Hazem

Thanks for the input, i'll give this a go when i get back home and let you know if it works out.

Should i try this when the phone is at 4-5% ? And then let it charge all the way ?
[One (M8) Q&A, Help & Troubleshooting] nawarkk:
I'm experiencing these same issues as well after rooting my M8. Hopefully someone here knows what the issue is.
[One (M8) Q&A, Help & Troubleshooting] Kyaner:
Well for me all issues remain unresolved.

My guess so far for the culprit seems to be the magnetic sensor, either badly programmed or a factory defect.
[One (M8) Q&A, Help & Troubleshooting] Hazem99922:
u must charge ur phone

turn off the phone

let him charge to full about 3 hours

and try the method

it will work

i test it on 2 one m7 phones

let me know if that work

thx
[One (M8) Q&A, Help & Troubleshooting] Kyaner:
Sorry Hazeem I understand that English isn't your first language, and you are trying to help but you are not making much sence....

You are basically telling me to charge my phone, then switch it off and charge it again even though it's already charged for another 3 hours....

Ok an update !

HTC Released a service pack along with an update for the car application, after installing these and a couple of reboots the charging problems stopped and the phone doesn't seem to be waking up without any reason, as it did before.

The calls getting routed to the speaker still remain but thanks to an app called Auto Speaker, I've managed to work around this issue. Before the updates this application had no effect, but now it works as it should by turning off the speaker when the proximity sensor is blocked.

I hope I am not celebrating too soon on this and I'll keep this post updated if anything else, related to these issues, happens.

Update 2

So far so good and with another unexpected benefit, I removed my phone from the charger Saturday morning around 11 and as of now Monday 7:30 it's at 27% !
[Nexus 6P General] AndyCr15:
I have to admit, I was surprised...

[youtube]c6Pl_LHFaPw[/youtube]

Nexus 6P really needs OIS...

[youtube]kTp51-uKa1I[/youtube]

[youtube]qYHsEtlEjTw[/youtube]
[Nexus 6P General] prophet42:
Definitely.

There's no cheating or getting around it.

But then I didn't think this camera would be as good as my S6 for video or lower light conditions. I have to say, I prefer the pictures of my S6 to this in almost every mode and condition.

12.2 Megapixels, but only in 4:3? Are you kidding me?

No, this camera is definitely not a win for me.

But then again I knew that going in, and decided I'd rather have the 6P Google pureness than put up with TouchWiz anymore.
[Nexus 6P General] shook187:
Why even bother with a comparison or a VS thread with the Note 5? Note 5 will probably win in every category which it does but the Nexus crowd will probably just make it into a TouchWiz sucks thread. Just look at the post above me, it really didn't take long.

Pretty hilarious if you ask me.
[Nexus 6P General] AndyCr15:
I wouldn't say so.

You have an odd sense of humour...
[Nexus 6P General] walrusmonarch:
I am surprised that the 6P looks so good compared to the Note 5, the still pictures...

The videos, I think Google's EIS implementation is too strong. The videos look smooth, but the "jello" effect is very apparent.
[Nexus 6P General] easyc:
How's the battery life comparison? I'm considering making the switch from the 6p to the Note 5 because of the band 12 fiasco. Just want to make sure I wouldn't be sacrificing battery life.
[Nexus 6P General] ChongoDroid:
I'll be reviewing it with a comparison to the s6

I found the 6p can handle it's own in certain situations. However the focal length for macros surprised me. The s6 definitely wins there.
[Nexus 6P General] digweed4me:
I just sold my note 5, these two are number 1 and 2 but I would nexus 6p on top because of low light, low light is unreal on 6p

---------- Post added at 12:22 AM ---------- Previous post was at 12:15 AM ----------

First charge I am on 89% almost an hour sot this is the perfect phone

---------- Post added at 12:30 AM ---------- Previous post was at 12:22 AM ----------

Update on battery
[Nexus 6P General] easyc:
I know the 6p battery life, I'm talking about the Note 5 with similar usage by comparison.
[Nexus 6P General] digweed4me:
6p is far better on battery I just sold my note 5 to my brother it had a okay battery not like 6p

My first charge I got it this morning
[Nexus 6P General] AndyCr15:
Having had the 6P for only 5 or 6 days, I find the Note 5 to have a better battery. Also, my unscientific test -

[youtube]DV580XB5j0E[/youtube]
[Nexus 6P General] itch808:
OP, thanks for the comparison. I have a S6 Edge with the same camera as the Note 5 and in my eyes the 6P does a better job in low light. But video quality definitely goes to the Note 5