yashsingh1/xdaforums huggingface dataset:
[Xperia Z4/Z3+ Android Development] MurcielagoNZ:
Thanks but...

Thanks for your reply. But how can I flash magisk zip into my phone? My phone can't start if I enter TWRP even I do nothing but reboot immediately...(or I should ask magisk developer's help?)
[Xperia Z4/Z3+ Android Development] DiscMan55:
If you can't boot, reflash official firmware using Sony flashtool, (except FOTAKernel to maintain recovery). Once /system is modified (even if you mount rw by mistake just once) you will never be able to boot again. So get back to working system by flashing from flashtool, then back in twrp, say yes to mount system readonly then flash magisk normally, then magisk exposed. It should work. I suggest you open a thread in general section asking for more help because anymore replies here about this are polluting this thread.
[Xperia Z4/Z3+ Android Development] subsessa:
anyone knows why i have an error on Mac?

I'm entering command to flash recovery but terminal says "no such file in directory".

but the twrp2.img is in the directory.

same thing for other recovery images.
[Xperia Z4/Z3+ Android Development] teamz111:
The recovery doesn't work in Android 7.1.1 Nougat, i flash the recovery and start my xperia but No led lights
[Xperia Z4/Z3+ Android Development] tensuke6056:
I booted into TWRP but it cannot detect my sd card, please help

---------- Post added at 06:49 AM ---------- Previous post was at 06:34 AM ----------

also it stuck me at the sony logo
[Xperia Z4/Z3+ Android Development] juniofdm:
error when flash lineage15!

because?

dual sim.
[Xperia Z4/Z3+ Android Development] eklavyagupta:
twrp is working but phone is not booting it is stuck at xperia logo....what should I do...

thanks
[Xperia Z4/Z3+ Android Development] DanielMode:
strange thing

i don't get or have an recovery partition on my Z3+ dual sim

when i try to update my TWRP at the recovery menue by install an image its showing me a boot partition only nothing else

struggling since couple days to find out what i did wrong.

phone is working fine

its rooted

xposed is working

but the only think i can't update my TWRP or reinstall any of my backups i made

some peoples saying its because of my old TWRP version 3.0.2

i tried to update by using the TWRP app it says update flash was succesfull but still in TWRP menue i see the old TWRP v3.0.2
[Xperia Z4/Z3+ Android Development] DanielMode:
found this...is that still right ??

cause my Xcompact has an recovery partition
[Xperia Z4/Z3+ Android Development] eklavyagupta:
phone wont boot up after running twrp it got stuck on xperia logo.....

what should I do???

i have reflashed ftf but then twrp has been gone......
[Xperia Z4/Z3+ Android Development] lkjsoiuew:
Can't flash lineage-14.1-nightly

is there a newer TWRP for z4?
[Xperia Z4/Z3+ Android Development] dharanifoxx:
https://xdaforums.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050

check out this ... it has 3.1.1 twrp that's able to flash lineage-14.1-nightly
[Xperia Z4/Z3+ Android Development] seyrarms:
Can for device locked bootloader?
[Samsung Gear S2] mautz001:
Greetings,

I have set my Gear S2 to auto check my pulse every 10 Minutes. But sometimes it doesnt check for my pulse for 2 - 3 hours...

Is it dependent on something like if I move or something? Or is it a bug in the firmware?

Greetings

Robin
[Samsung Gear S2] Ragnarkov:
I know that if the watch doesn't get a good read on your pulse (too much movement, not sitting on wrist right, etc) it won't record the heart rate. At night while sleeping, I'll get pretty consistent readings for an hour or two, and then there will be like a 6hr gap. And on numerous occasions, I'll feel the watch vibrate slightly with no notifications or anything going off. I assume it's just error ed out on the read, and will try again later (or at the next scheduled interval)
[Wing, P4350 Herald Upgrading] CardiffCA21:
I've enabled the panoramic setting on my Wing and have noticed that the camera will occasionally give me a "disk memory full" error. I do get this with regular shots, just not as often.

I have set my settings to have all vids and pics save to my 1gb microsd card.

I have also freed up storage memory on my device and program memory with both ranging at around 21mb each.

any suggestions on different settings or registry edits to enable more shots or not having to do a soft reset?

been reading these forums for a month or so and have learned a great deal.

btw, I have searched and most threads were about button issues for the camera. Any help is appreciated.
[Fire General] ianthomas:
Dude... :fingers-crossed:

I love you. In a non sexual way.
[Fire General] m00head:
Deleted
[Fire General] GRiMP13:
I managed to get it done also. Thanks for posting those steps. It took about 20 trys with kingroot, but it finally went all the way, lol. I had the same problems SuperSU also but following your compilation of forum guides, I got the Fire Nexus ROM and I'm loving the absence of Amazon!
[Fire General] stankyou:
Hello. Just posting to let people know that this also worked for me as well.

Once you get Kingroot to work, it's all smooth sailing. Not sure if this helped the process but keeping the screen on while Kingroot to do its thing might help. I had several failed attempts and on all of those instances, my display expired and I had to unlock my device. The successful attempt, I just held my device and prevented it from locking... went to 30% and rebooted. Then I had root.

I have Fire Nexus installed. :)
[Fire General] feefeeboomboom:
Very nice!

Posting to say thank you! I did not know any of the roms could be flashed with FlashFire! I attached the most recent version of FlashFire.
[Fire General] kgirlx:
Flashfire v.30 appears to be a beta version according to Chainfires site
[Fire General] DB126:
All versions released to date are betas (evidenced by '0.' prefix)
[Fire General] kgirlx:
Ok, boy am I dumb. Thanks
[Fire General] DB126:
Not 'dumb'...learning :)
[Fire General] x13:
Just used your method, am now running 5.1.2 rooted, may have screwed up with KingRoot, but otherwise good, gonna try removing the KingRoot crap now
[Fire General] jhackg0d:
I really appreciate your post. It helped me get SuperSU working great! For some reason FlashFire 0.27 was closing on launch so I had to try the 0.30 version that someone posted using adb install -r

Thanks all!
[Fire General] momonjava:
Thank you a million times!! Fire OS was making me insane :)

Now to block the OTA updates. I haven't seen the definitive word on that as yet (if anyone could guide me, I'd be very appreciative!)
[Fire General] drmattyg:
I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!

(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)
[Fire General] DB126:
Any rollback attempt will yield an unrecoverable brick...as you discovered.

Multiple reports of installing CM 12.1 and Fire Nexus on a device that previously hosted FireOS 5.1.2. FlashFire v0.31. Latest ROM builds.
[Fire General] Robo-rooter:
HOW TO ROOT FIRE 7 THAT HAS FIRMWARE 5.1.2 AND THEN INSTALL NEXUS ROM USING FLASHFIRE.

I have three Fire 7's with 5.1.2 firmware. I rooted them with RootJunky's SuperTool. After they were rooted, I installed FlashFire v.031 and then used that to load the Nexus rom (the latest one from early April). All of those are mentioned in threads here on xda.

Run RootJunky's SuperTool and root the Fire 7.

With the SuperTool, you can also load FlashFire. But it loads v.030. I believe you can get v.031 through a special link here on xda to the Google Play store.

If not, you can find FlashFire v.031 on a european server. Download v.031 apk and install it manually.

The FlashFire program icon will appear with the other installed apps on the Fire 7 apps screen, even on the Amazon Fire OS menu system.

Copy the Nexus rom (a zip file "lp-fire-nexus-rom-ford-20160405.zip" ) to your Fire 7's sd card root folder.

Make sure your Fire 7 is fully charged.

I started FlashFire v.031 and made the following menu selections:

In the FlashFire program do the following:

- Click the Red + and choose 'Wipe'.

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED.

- Click the Red + button and choose 'Flash ZIP/OTA'.

- Navigate to and choose the latest Fire Nexus ROM Zip (I used "lp-fire-nexus-rom-ford-20160405.zip" that I had previously loaded on the root folder of the SD Card.).

- Ensure Auto-mount and Mount /system read/write are UNCHECKED.

- Move (drag) "Wipe" to the Top of the order (just above the ROM flashing).

- Press the big FLASH button.

- Ignore any warnings that appear.

The Fire 7 screen will go black for a few seconds.

-Then it will say, "Loading" and lines of text will go by rapidly for a few seconds.

-A red bar will then appear at the top of the screen titled "FlashFire".

-The rest of the screen is black. Don't touch the tablet. Just let the program run. It takes 5 or 10 minutes. It looks like nothing is happening, but it is.

-Finally the tablet will reboot. The Amazon logo will appear for a little while, then a pulsing color dots animation will appear. This dot animation will run for 5 or 10 minutes more as the tablet boots for the first time. Don't touch the tablet until a Setup screen appears.

You can now set up the tablet, registering it with Google and loading your desired apps.

The Nexus rom gives you a generic Android 5 Lollipop interface. After loading the Nexus rom, I installed the Nova launcher, it gives you a lot of options for menu control.

Nexus is a nice ROM. Much better and faster than the stock Amazon Store ROM.
[Fire General] Robo-rooter:
With the Nexus rom installed, I then added the Link2sd app from the Google Play store to recover 3.5gb of internal storage, linking apps to the sd card.

Link2sd is an app that links and moves most or all of an app to your sd card, but someway links it to the Fire 7 internal storage for the android system to run. Some custom roms allow you to just move and run the apps from the sd card. But with the Nexus rom, the app file is moved to the sd card, but run, maybe virtually from internal storage.

I have 150 apps installed on the Fire 7 with a Nexus rom. Before I loaded Link2sd, the Fire 7 had about 500mb internal storage free. After loading Link2sd and linking apps to my sd card, there is 3.5gb for free internal storage on the Fire 7.

In order for Link2sd to use the sd card you have to partition the sd card into Fat32 and ext4 partitions. The ext4 partition is used by Link2sd for app linking. The Fat32 partition is used in a normal manner for MP3, picture, video, e-book, etc storage.

I am using Linux Mint on my pc, so I used the linux program Gparted to partition a 32gb micro sd card for Link2sd to use. There are also free Windows programs that will allow you to do the same functions on your Windows 7 or 10 pc..

Link2sd uses a linux ext4 partition on the sd card to place and link apps to. The other half of the sd card is partitioned as a Fat32 format, for MP3, video, ebook, pictures storage.

Here is how to partition a 32gb micro sd card using the linux program Gparted. Use some type of micro sd adapter to connect the micro sd card to your linux pc. My Dell laptop has a built in sd slot, so it only needed and sd to micro sd adapter.

First delete the existing partition on the micro sd card. Then create a Fat32,. Primary partition, that takes 1/2 of the space on the micro sd card. Format the Fat32 partition as Fat32.

Next create a linux ext4, Primary partition, using the other 1/2 of the space on the micro sd card. Format the ext4 partition as ext4. The micro sd card is now ready for use by the Link2sd app.

Insert the micro SD card into the Fire 7 with a Nexus rom and Link2sd installed.

Start Link2sd and point it at the ext4 partition on the sd card when it asks and you are set to link apps to the sd card.

You can probably partition 64gb and 128gb sd cards in the same way, although I haven't tried. The Fire 7 is suppose to be able to accept up to a 128gb micro SD card.

Fire 7 boot times with the Nova rom are about 45 seconds to a minute. After installing Link2sd, the first boot after linking about 100 apps took 3 minutes. Later boots took about 90 seconds. So linking apps to the sd card does increase boot time on the tablet. Those times are for a cold start, from pushing the power button to being able to open the lock screen.

ADDENDUM: Well, after a couple of days of use, boot times are back to 60 seconds from a cold boot. Link2sd must have sorted things out. Wow.
[Fire General] vn33:
Thanks for the info, I managed to stumble through most and got root, updated the root.sh as per your instructions above and pushed the MRW folder to SD, installed Superuser, installed FlashFire. However, I am stumped at how to run the root.sh script!

Sorry for the noob question, but I just couldn't find a noob-friendly instructions ...

Do I install a Terminal Emulator on the Fire tablet, and run the script? I tried that (installed "Terminal Emulator") but just couldn't get any prompt to run.

If you don't mind giving me a more detailed instruction of how to run the script ... Mainly how to remove Kingroot ... Most appreciated!

Thanks!

---------- Post added at 09:07 PM ---------- Previous post was at 08:30 PM ----------

Duh! I managed to run the script through Terminal Emulator. It updated the, and rename the Kinguser to com.kingroot.kinguser

Now just trying to figure how to delete that file.

Thanks OP for this thread!
[Fire General] s2pfie:
failed at 33%
[Fire General] sd_shadow:
So you were trying to root with kingroot? android app, PC app, supertool...

5th gen 7in Fire?

was it shipped with 5.1.2?
[Fire General] BriarV:
my kingroot quit at 33% too

I'm trying to root the recently patched 5.1.2 that undid some people's root (including mine)
[Fire General] sd_shadow:
if the Kingroot 4.x app repeatedly fails around the 30% mark

try Restoring 5.1.2 firmware in Stock recovery (adb sideload)

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire General] DB126:
You have to sideload a clean version of FireOS 5.1.2. Updates from 5.1.1 can not be rooted w/Kingroot.
[Fire General] BriarV:
Just finished restoring to 5.1.2 and KingRoot worked!

Thank you so much.
[Fire General] Dunard:
Make sure that you disabled the updates after that. Updates will delete it out.
[Fire General] BriarV:
I think I blocked them. I found another thread to showed me how to block things via adb.
[Fire General] Dunard:
I use the Apps2SD to disabled those.

Another way to do this is to rename the apk. For example below.

base.apk~

Reboot afterward. Android can't read it.
[Fire General] DB126:
Rename me, yes. Disable, no. Trivial to re-enable a disabled app. Akin to a rubber seat belt.
[Fire General] Dunard:
Well those are still disabled. Apps2SD does it better job than the adb tool. When you do a reset. It go back to enabled.

Rename those won't reset it back to enabled though. Might get erased after reset. Be careful.

I never could get the adb to do a disable the apk. Even the message saying it did. Don't be fool by the message. Doesn't work on some of the Android builds. Same way tried to make a backup.
[Fire General] regidark:
Hello everyone.

I´m trying to root with kingroot. My kindle is 5.1.2 and i´m using the latest version without any luck, appears an error at 30%, i tried more than 10 times already and always the same behaviour, any ideas about this?
[Fire General] DB126:
Known problem. Your device likely updated from an earlier version of FireOS or arrived with 5.1.2.1. You need to manually sideload (reload) a 'clean' version of 5.1.2. Then it will root fine.
[Fire General] regidark:
Thanks for your fast reply, do you know where can i find instructions to make that manual sideload?

Thanks a lot in advance
[Fire General] Robo-rooter:
I used xda's RootJunky's video instructions a couple of times to restore my Fire 7 by sideloading the firmware before I finally loaded the Nexus rom:

If your Fire 7 has 5.1.2 firmware, don't attempt to go to an earlier version or you will brick the Fire 7 permanently.

5.1.3 or 5.1.2.1 to 5.1.2 is okay. However, 5.1.2 to 5.1.1 or 5.0.1 will permanently brick the Fire 7.

How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet

https://youtu.be/RQLoH-ahjy4?list=PLaPvcEA8BA-JMmKqiaJvZM93iTyiOAWuK
[Fire General] bmurphr1:
I can confirm that the new Kindle Fire tablets running 5.1.3 (the latest) firmware can be downgraded to 5.1.2 by flashing the image via stock recovery and using the "adb push xxx.bin" method of downgrading the tablet without bricking it, and then rooting the tablet via Kingoroot. I read dozens of pages trying to figure out if people were using the desktop app to root the tablet or the APK, and I started with the desktop version. I tried 3 different times and each time it made it to 100% and then said "root failed" so I allowed the tablet to get on the internet to download and install the Kingoroot APK and once I opened up the program within 30-45 seconds I was rooted. I rebooted the tablet and now have Kingoroot's version of SuperSU installed and root privileges.

Right now I'm trying to figure out what these issues are that I keep hearing about FlashFire not wanting to get along with Kingoroot and having to install SuperSU and simultaneously removing Kingoroot to keep root access before I can hot-flash over to another firmware. This is something I haven't done before and haven't seen any clear instructions on how to perform - only a few ways of installing the SuperSU APK and then copying a folder over to the tablet, getting shell access via adb and changing some permissions, and then removing Kingoroot and rebooting. Once I get Kingoroot swapped out for SuperSU I'll be able to install the latest FlashFire and use either Nexus or CM12.1 to perform the wipe and hot-flash. If somebody could help me out by letting me know how to swap the two root apps out I'll be good from that point. I've already bricked two Fire tablets since they've been released and really do not want to brick a third tablet (especially since Flashfire is so risky to use) so I'll have Kingoroot swapped out before I flash to a different firmware by using the latest version of Flashfire available here on XDA and the most recent firmware that's been released.
[Fire General] DB126:
- FlashFire freezes with Kingroot installed

- Use SuperTool to remove Kingroot and install SuperSU (automates process)

- Recent versions of FlashFire (post 0.30) are not especially risky

- Suggest going with Nexus as only one file needs to be flashed

- FlashFire defaults are fine; no need to twiddle mount options

- Be sure to include a wipe action (system, data, dalvik, cache) before rom flash
[Fire General] DoLooper:
Maybe someone knows of a Kingroot/SuperSU swapper posted here. If not, my FireHD tool works on the 2015 Fires and has a "Replace Kingroot w/SuperSU" option. I've used it successfully a couple times on OS 5.1.2 on the Fire.

EDIT: Sorry, was composing this complex reply and didn't see [MENTION=5488402]Davey126[/MENTION] message. There ya go . . . SuperTool has it too!
[Fire General] sd_shadow:
Kingroot and Kingoroot are to different root tools

not sure if Kingoroot will root the 7in 5th gen with 5.1.2, but it may have been updated

the supertool probably will not work with removing Kingoroot if that is what you have.

you might be able to manually install supersu with a terminal emulator

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

just replace the kingroot apk names for the Kingoroot apk(s)
[Fire General] DoLooper:
Ha! Of course you would catch that Kingo! Great suggested solution.
[Fire General] bmurphr1:
That script unfortunately does not work with Kingoroot (which the latest seems to have rooted my device after the first attempt) and I'm having to look up alternate methods of removing Kingoroot and swapping with SuperSU. There's a tool called SuperSU-Me that is supposed to automate the process and remove Kingo and install SuperSU as well as automatically update the SuperSU binaries but I haven't been able to get it to work yet. There are a lot of entries in the root.sh that point to folders and files that don't exist on this device since I used a different rooting tool, and I wish that I would have rooted with KingRoot instead of Kingo...of course I haven't given up hope though. I'm going to continue to look for an application that can remove Kingo completely and install SuperSU in it's place in the mean time.
[Fire General] bmurphr1:
Well, SuperSU-Me Pro does not work with the latest version of KingoRoot and had to request a refund from the Play store. The app would only reach the second step of "processing" and would then freeze each and every time, even after rebooting and such. It's a shame because in my testing KingoRoot actually worked 100% of the time for me on the first try, which is crazy considering how inconsistent KingRoot is. I ended up having to boot into recovery, pushing the 5.1.2 bin file via adb to the tablet and then using KingRoot instead to root the tablet. KingRoot finally completed the root after 5 reboots using the most recent SuperTool zip but when the second step of swapping KingRoot for SuperSU executed it only removed Kingroot and did not install SuperSU successfully and the root was effectively lost. I tried installing SuperSU manually hoping that I still had temporary root access but it failed. Lastly for the 4th time I pushed 5.1.2 bin via recovery/adb to the tablet once again and used the SuperTool and it finally worked - I now have an Amazon Fire running 5.1.2 rooted with SuperSU and have FlashFire 0.32 installed on the tablet.

I'm planning on using FlashFire to hot-flash the latest Nexus firmware on to the tablet (I know that gapps aren't required since they are already integrated into the Nexus zip) but I've seen different instructions on which boxes to check in FlashFire regarding the mounting /system read/write and automount. I read one forum post that just said to leave all of the default boxes checked in FlashFire 0.32 when flashing Nexus to the tablet, which on my tablet only has "mount /system read/write" checked and automount unchecked. I haven't performed the FlashFire yet because mainly I want to move the files over to an actual micro-SD card instead of /sdcard on the tablet itself. Whenever somebody mentions "SD card" involving the Kindle Fire I assume it refers to /sdcard but RootJunky's video of flashing Nexus to the tablet actually involves a physical micro-SD card where he has his files located. I wish some of these instructions were a little more updated since newer firmware has been released, newer tools, and such but that's the nature of these forums and why flashing the Fire is so experimental.

Anyways, I will be moving my files over to a physical micro-SD card, using FlashFire 0.32, and then setting FlashFire up where I make sure the tablet gets wiped first by putting it in the first position and then letting it flash the Nexus firmware by leaving the default boxes checked and then letting FlashFire work its magic. I sincerely hope that the default checkboxes are selected properly in the latest version of FlashFire 0.32 otherwise I will have bricked a third Amazon Fire tablet and I won't be bothering with buying another one (I'm more of an iOS user than Android) - even though my tablet was only $10 after a $20 refund from Amazon for not including a power adapter. I'll do a little more reading before I proceed with FlashFire for the last time and hope that I don't brick my Fire tablet.