yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] Gabry70197:
http://xdaforums.com/oneplus-one/development/toolkit-wugs-bacon-root-toolkit-v1-0-0-t2947627

Read the post, install the driver as its tool and reinstall the COS 12 with this tool, easy and fast ..ricorda never to wipe system. Connect the cell to the PC and the tool does everything that you click, in this case follow the procedure to install the COS 12
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] emailer33:
So I was attempting to get 5.0 dev preview with root.

I flashed 4.5.3, rooted, had TWRP and SuperUser installed.

Stripped 5.0.2 dev preview of the images/ folder, and modified the updater-script to not look for those.

Flashed 5.0.2, rebooted into recovery. I installed root when TWRP asked.

I then used uboot-4.5.3 and replaced the images/ folder with the one from the 5.0.2 dev preview that I stripped out earlier.

I flashed the firmware from the dev preview and rebooted my device.

Now I only have a solid black screen that I can never get anything to happen. No Amazon logo, no recovery when holding Vol+ and Power, nothing. I issue fastboot and adb to wait for device connection and neither ever respond.

I fear that the new boot.img sees I have a non-standard recovery and just halts. I am not sure though as I have no output.

Does anyone have any suggestions? I was going to pop this thing open and connect my Arduino the UART port, to see if any log output would be helpful. Otherwise I"ll see if Amazon will honor a warranty for it.
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] bibikalka:
So, looks you've retraced the bricking steps from here (with a small variation on the theme):

http://xdaforums.com/fire-hd/general/lolipop-ota-capture-t3141810

If you don't see even white Amazon logo, my guess is that your flash for the new 5.0.2 TEE1/UBOOT did not go so well. The sequence for the boot is TEE1 -> UBOOT (white Amazon logo) -> boot.img (yellow Fire logo), alternatively, UBOOT -> recovery. There is also TEE2, but I am not sure how to boot that one. Note that 5.0.2 UBOOT will not boot TWRP recovery, at most one could do here is flash 5.0.2 Amazon recovery in the same go as TEE1/UBOOT. Then you could do factory reset, if this flash goes well.

I've tried to get MTK tools going, but no dice :

http://xdaforums.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784

Tell Amazon that an update made your Fire dark, and don't tell them that you actively participated in the process ;)

At this point I think that Amazon should have provided more recovery options for people here to use, instead they now spend money on shipping bricked Fires back and forth. Sloppy programming, methinks ...
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] emailer33:
Sounds like I should've definitely flashed the stock recovery after flashing the 5.0.2 UBOOT. I will try my warranty options, thank you!

Edit: Amazon support is probably the most helpful and quickest tech support I have ever used. They're sending me a new one and I send the old one back in the shipping box.
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] siegesoldier:
I went through the same screw up. I'm guessing the only way to get TWRP to actually flash a stock recovery would to do an ADB sideload since it protects itself from getting overwritten.
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] bibikalka:
I still wonder why your upgrade did not work. On paper it should have been fine, flash 5.0.2, install su/SuperSu, {clear /data}, flash uboot/tee1, and go boot into 5.0.2. Flashing Fire recovery was not necessary, other than to do a factory reset (clear /data). But, one could have cleared /data in TWRP before. Did TWRP screw up /system partition to an unrecoverable state? Or was it SuperSu flash that did not go well? Anyway, I hope people stop trying this, since so far it's been 2 bricks for 2 attempts ...
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] emailer33:
New Fire just arrived, so I'll probably stick to rooted 4.5.4 for now (5.0.2 was sooo pretty though).

The unit that arrived was version 4.1.1, pretty old, wonder if its easier to root.
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] bibikalka:
Wow, 4.1.1 was never offered for download!!! Try to get root, and copy the UBOOT, and TEE1 partition. Just in case.
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] emailer33:
Already have root on it, which mmcblk blocks should I copy?
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] bibikalka:
The exercise is a bit academic, but what the heck ...

dd if=recovery.img of=/dev/block/mmcblk0p7 (PART 7)

For other partitions, see below.

[PART] 1: 00000100 00000040 'PRO_INFO'

[PART] 2: 00002000 00000800 'PMT'

[PART] 3: 00002800 00002800 'TEE1'

[PART] 4: 00002800 00005000 'TEE2'

[PART] 5: 00000400 00007800 'UBOOT'

[PART] 6: 00004000 00007C00 'boot'

[PART] 7: 00004000 0000BC00 'recovery'

[PART] 8: 00000800 0000FC00 'KB'

[PART] 9: 00000800 00010400 'DKB'

[PART] 10: 00000400 00010C00 'MISC'

[PART] 11: 00008000 00011000 'persisbackup'

[PART] 12: 00258000 00019000 'system'

[PART] 13: 001B8000 00271000 'cache'

[PART] 14: 018F3FDF 00429000 'userdata'
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] emailer33:
Academic or not, that should be posted to a sticky thread or a wiki. But I've backed up everything except cache and userdata, is there anywhere I can put it up? I will say zipped /system/ is 779MB.
[Fire HD 6 and 7 Q&A, Help & Troubleshooting] bibikalka:
Well, the only value would be in UBOOT and TEE1. You should try to boot with "Pwr Vol+" button hold, to see if it lets you into recovery (either Amazon's or TWRP). 4.5.1 and 4.5.2 would not do so, which causes bricks ... If it does not let you into recovery via these buttons, no value then ...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] msaeng:
So, what's it mean when you run GetDeviceData.Exe and all you get in your ../windows/devicedata.txt file is "PH20B" ?

Strange, huh? I've tried it a couple of times. Always the same... Nothing but "PH20B". I'm also having the "No GSM" in the boot screen problem, and can't upgrade (well, load AT ALL!) my radio stack. In my device info screen the OS and Extended info are right, but Protocal and Radio are both blank now. This has all happened after trying to do a ROM upgrade tonight.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] jakubd:
1. What (exactly) device you own? What was DeviceData BEFORE first upgrade?

2. What ROM you had, and which one you tried to load?

3. How did you do that (what procedure)? Have you omitted any steps?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] xplode:
Lets say you really own PH20B (Blueangel) then if the radio is inactive the devicedata.txt will not output the info from it. Reflash radio only

Also this may happen if you have flashed PH20A (Harrier) and you flashed WM5, go back to WM2003 and all will work fine
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] msaeng:
Answers:

1: It is a HTC BlueAngel. It's one of those with just "PocketPC" on the front. No cell provider branding. I bought it off ebay last year. Don't know what the file showed before. Never had a problem, so I never looked.

2: Was running a I-Mate ROM since I bought it. But the radio was really old. The radio version was like .9xx . Don't remember exactly what. SHould have written it down. But it was less than 1.00, I know that for sure. I was upgrading to the Siemens 1.33 ROM with the 1.15 radio added on.

3: Used MaUpgradUt_NoID. Never been able to use BaUpgradeUt. It's always given a country ID error, but Ma..NoID has always worked before.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] msaeng:
Yes. It is a blue angel for sure. See my reply above.

It's always been WM2003, and all I get when I try to flash ANY radio rom version to it now is a country ID error.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] xplode:
flash with noid app

maupgradeut_noid.exe
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] msaeng:
Yep. Already tried that. In fact, that's the ONLY way I've been able to do any upgrades at all since I bought the phone. Never have found a ROM that would work with BAupgradeUt.exe. Strange thing is, I can load the OS and EXT ROM's no problem using Ma..NoID.exe... Just not the Radio ROM. Even using NoID when I try to load a Radio ROM, it dies with a country code error. I believe the error is N-N-50-50-50 if that means anything to anyone. Any more ideas? I've tried all the obvious things I could think of. I wonder if maybe I could use a null data field in editfix.bat? That is, instead of using real data values from devicedata.txt like you normally would, replace the "???" in the .bat file with " ". Anyone know if that's even possible? Or should I just try taking it up to WM5, then back to 2003?

Thanks for all the thought and effort so far folks.
[Chromebooks] Petedev:
Does anyone have a recommendation on which Chromebook to get that is possible to install Arch Linux on without many issues, ideally with a 12+ inch screen?
[Chromebooks] drs413:
HP Chromebook 14

I have read on the Stack Exchange Forums that the HP Chromebook 14 runs this smoothly. I Run Ubuntu on mine and it has only given me the expected little issues you deal with on these types of installs... Totally worth it. I only had one issue with my Chromebook and it was my battery dying. Not sure of other brands but you have to ship back to HP for this particular model. CS was great to deal with and they returned it back quickly...... All in all I would make sure you get a book running Intel. I hear the most issues on other ARM processors, with the exception of the 13.04 on the Samsung ARM chromebook.

ask Ubuntu dot com - best I have found for answers. Kind of like this one.. Not a lot of people just arguing trying to prove they are smarter than the other.. Just good help!

Hope this helps, please feel free to check out the Ubuntu section on Stack Exchange and I find the people on the Google+ very nice as well. :):)
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
NOSP is a open source project based on Slim,AOSP and Cyanogen-Mod founded by jenkins-84, my aim is to bring a fast and smooth lightweight base with optimized performance, This Rom started out on the HTC One (m7) but now starting to make its way to other devices. Maintainers and Support is always welcome as this Rom is pretty much a one man show atm. I'm not responsible for anything that happens to your device so do recommend you do make a backup before flashing!​

Feature's

* Advanced reboot set to default
* Development options unlocked
* Status bar Battery/Clock customization
* Configurable 0, 90, 180 and 270 degree rotation
* Quick tile customization
* Recent clear all
* Ambient display (only certain devices)
* Expandable desktop
* Partition size info
* Brightness control on status bar
* Double tap status bar to sleep
* Network traffic in status bar
* Disable/enable search bar in recent menu
* LCD density control
* SuperSU in settings
* Optimization boot-up message with random colours
* Eleven Music app
* AudioFX
* Viper4Android
* Kernel Adiutor
* Cyanogen STK
* Layers
* Slim Pie
* Slim Heads Up Customizations
* Hide Network Arrows
* Navbar Customizations
* Hardware Key Rebinding
* Slim Actions
* Slim Recents
* Live Display
* Advanced Volume Controls
* Chamber of Secrets
* Slim Global Menu
* Expanding Volume Panel
* Silent mode now available
* Blacklist
* Double tap lockscreen shortcuts
* Slim recents
* CMHW features
* App2sd
* More quick setting tiles
* Extra dashboard switches
* Expanding volume panel
* Silent mode now available

How To Install :

* Make sure your on FOTAWRP RECOVERY https://www.androidfilehost.com/?fid=95916177934529111

* Download ROM & GAPPS to ext sdcard

* Enter Recovery and do a FULL wipe

* Flash ROM, Flash Gapps

* Reboot device after finishing installation

* Enjoy

Downloads :

ROM:https://www.androidfilehost.com/?fid=24052804347771745

GAPPS:http://xdaforums.com/slim...imkat-t2792842

**For V4A To Work Please change SELINUX To PERMISSIVE in Dev options**

XDA:DevDB Information

[ROM] Official NOSP , ROM for the Sony Xperia Z3 Compact

Contributors

AnGrY sCoTsMaN, jenkins-84

Source Code: https://github.com/NOSP-LP

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.4.x

ROM Firmware Required: UNLOCKED BOOTLOADER

Based On: AOSP,SLIM, CM12.1

Version Information

Status: Alpha

Created 2015-06-28

Last Updated 2015-07-12
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
Changelog:-

JULY 10TH

* Android release 6

* Ad blocker

* Unknown sources enabled by default

* Appops accessible from security

* Selinux switcher in dev settings

* Restart System UI in dev settings

* Live volume steps in advanced volume settings

* Battery bug in settings fixed﻿
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
Screenshots (I have a custom layers theme applied, but you get the idea of what's include)
[Xperia Z3 Compact Original Android Development] jenkins-84:
Nice to see your thread up bud [emoji106] thanks testing the ROM out and maintaining it too [emoji12] hope z3c users will enjoy NOSP too....
[Xperia Z3 Compact Original Android Development] Cr1ms0n:
Thanks for the new ROM for our brilliant little Z3c's. Is the Ambient Display working on Z3c under this ROM?

Thanks.
[Xperia Z3 Compact Original Android Development] jenkins-84:
Not at the moment but this is the first build for your device hopefully fixes like that will come in up coming updates too
[Xperia Z3 Compact Original Android Development] mtsfilms:
Sounds awesome, just curious about the camera (hate to be that guy), is it still distorted? And can it be launched/lock focus+exposure using the camera button?
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
[MENTION=6638321]mtsfilms[/MENTION] yeah, still have camera issues but only noticeable on square/rectangular objects from a distance. Fine fore portrait and selfies imo. Camera can be launched with dedicated camera button but cannot be used to capture pic.

Cheers
[Xperia Z3 Compact Original Android Development] mtsfilms:
Okay thanks mate :)
[Xperia Z3 Compact Original Android Development] mtsfilms:
I flashed it anyway....and it's awesome. Nice work :) I'm a photographer and shoot films for a living though, so that distortion is noticeable in every instance, no matter what hehe...is it a thing that Sony need to address? Or something that just needs time and dedication to fix...or a bit of both? Sorry if my question seems nooby, it's because beyond flashing, I have no idea what I'm talking about here on XDA. Great forum though :)
[Xperia Z3 Compact Original Android Development] FcukBloat:
tried this rom very nice ;) one question, it seems long press volume buttons when screen is off to switch tracks feature is not present.. possible??
[Xperia Z3 Compact Original Android Development] jenkins-84:
Cheers, I will look into it on a update thank you
[Xperia Z3 Compact Original Android Development] House3272:
What is this and how is it different from regular twrp?

I noticed there wasn't an official twrp listing for the Z3c anywhere, yet I have 2.8.7.0 installed through dual recovery.

But trying to flash this and another rom gave me the aries error

Flashes fine after getting the fota version, albeit the recovery messes up after the first boot into the rom where everything's diagonally distorted (unusable, but still responses to touch in the correct locations).

(why isn't there just a working and official twrp for the Z3c :()

Sorry if this is commonish problems/questions, just got the Z3c yesterday, been outta this world for a few years haha.
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
Sory for late reply, been really busy. i feel [MENTION=3816568]Myself5[/MENTION] explains the answer to your question better than i could here http://xdaforums.com/z3-compact/orig-development/cm12-kernel12-22-2-2015-t3037663/page8

Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer [MENTION=912474]Dees_Troy[/MENTION] (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery!

twrp included in dual recovery wont work with cm based roms thats why its suggested to flash the fotatwrp, which works fine so i dont understand how you can say its unusable?
[Xperia Z3 Compact Original Android Development] House3272:
Thanks for the info! Looks like I got a bit of catching up to do~

In regards to Fota-TWRP not working, I most likely did something wrong.

Using the file linked through the 1st post, I was able to flash cm roms just fine, including this one. But after the initial flash, going back to the recovery looks like the attached pic.

No idea there.

Also, using this one: http://xdaforums.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573 just bricks it, and then I have to use flashtool to reflash the one you included in fastboot mode, otherwise, I just get vibration, no sony logo or anything.

Is there a sensitive order/flash methodology that is essential to get things to work?

I can get back to a rooted and unlocked/locked stock 5.0 state with dual recovery.

From then on, I'm probably working off of more assumptions than I should.
[Xperia Z3 Compact Original Android Development] FcukBloat:
thanks. that's a real pity because in such conditions camera can't be used at all, and I need it daily so I can't stay with custom, have to keep stock because of this problem :( :crying:

so the only hope is a fix from sony?

pardon my ignorance, but it is not possible maybe to use cam drivers from other phones with wideangle sensors running cm? all wideangle phones have this problem in custom rom? can't believe that?! :crying::silly:
[Xperia Z3 Compact Original Android Development] sm4tik:
Thank's for a nice rom! Here's my feedback after using it for a few days.

Bugs:

Navbar in homescreen randomly turns opaque. It happens seldom and I can't find a pettern to reproduce it either. Going to launcher settings and back will make it transparent again

ADB over network isn't working

If there's a notification, swiping it in lockscreen (to enlarge) will allow Quick Settings to be pulled down in a secure lockscreen

Usb connection options: charging only doesn't work (and there's no option to mount sdcard as a mass storage device)

Cellular networks > Carrier settings causes com.android.phone to stop and connection is lost. Hado to reboot to get connection back

APM can't be disabled from power menu and the indicator falsely stays active after disabling it in settings

Feature requests:

Additional dictionaries (Using Finnish)

Option to disable alarm icon in statusbar

Option to edit default lockscreen shortcuts

Quick pulldown width

Unlock pattern options (hiding dots, error..)

Editing power menu items

Other:

When using expanded desktop mode, swiping to activate nav-/statusbar swipes the active app also. In CM only the bar is shown while the active app stays untouched

It would be better to have Kernel Adiutor as a separate app. Now I can't have it running in the background if I want to edit other settings and also there's currently no way to have a shortcut for the app itself

A minor thing, but when a sim pin is required, it would be nice to boot directly to the numberpad. Currently I first have to swipe to unlock, enter sim pin, swipe again to unlock and then enter lock pattern

If you need a logcat or other more detailed info, pelase ask and I'll try to provide them! Cheers.

Edit: Couldn't get M5 kernel to work with this rom. Any plain reason for it (as this one uses cm kernel?). Hope I can get the info forwarded to Myself5 if it's something trivial as I would like to have a bit more control over the things going on ;)
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
OK mate, I'm trying to reproduce some of your issues but am currently at work so limited to what I can try.

What launcher you using, do you have xposed installed and have you applied a layers theme?
[Xperia Z3 Compact Original Android Development] sm4tik:
I'm using the default launcher and actually now that I think about it, after installing a theme I've not seen it happen again. So, default launcher, default theme, navbar resized. That's all I did I guess..

Edit: it could also be that something i did required a reboot, I haven't had the navbar problem today?
[Xperia Z3 Compact Original Android Development] AnGrY sCoTsMaN:
OK, I've reflashed rom and been running it for last 5hrs trying to replicate your issues . messed about with navbar height, APM, network services, settings etc etc...... I'm not getting any issues, it's all fine my end Bro. Adb over network, I never tested as I don't use it. The USB charging only issue I confirm is there but it still charges. With regards to your extended desktop issue, I can only assume that you've reduced the height of your softkeys/statusbar (navbar) too small and that's what's causing the issue (too small for touch interface to determine what your trying to do) anyways as for request: I'll pass it on to the creator of NOSP and see if he wants to add them to his rom.

Cheers
[Xperia Z3 Compact Original Android Development] sm4tik:
Hmm.. from the sound of it, there's something wrong in my end.. Anyways, I'm currently "romhopping", will get back after a fresh flash of NOSP. The expanded desktop thing is not happening with crDroid either, but with nosp it was obvious; the navbar does get exposed, but the page under it will scroll. Nothing to do with nb height, 42dp isn't that small.. Last time I had that was with an xposed module.

Thanks for testing it, will get back in a while !
[Xperia Z3 Compact Original Android Development] sm4tik:
OK, decided to test things right away..

I can confirm

the expanded desktop mode swipe thing (enable exp.dt, goto browser, swipe up to reveal navbar, the page scrolls though it's not supposed to)

ADB over network not working

settings > cellular networks > carrier settings results in "unfortunately com.android.phone has stopped" (not something I need, was just browsing through settings and bumped into it)

Expanding a notification in a secure lockscreen will allow quick settings to be pulled down

Things working after all..

APM from power menu

Navbar has been ok in home screen

(USB connection options behave the same in CM)

I also noticed the default DPI being 280 instead of 320, is this on purpose? I like it this way though, but I don't think it's right for z3c?

Cheers
[Xperia Z3 Compact Original Android Development] jenkins-84:
To me it seems has you state your ROM (hopping) also makes to believe your dirty flashing that's probably where your issues are. No issues on my end on the m7. Before jumping on here saying things don't work even they do. Learn how to do a clean install of a ROM.. All I notice so far is your trying to find every fault possible even every ROM isn't perfect. If you don't like my ROM go use another I put hours into this ROM so doesn't bother me..