yashsingh1/xdaforums huggingface dataset:
[Amazon Fire Phone] Bingo Bronson:
Have you made any significant changes to the OS?

By "hard reset" you mean "factory data reset" from the menu?

There is no custom rom available.

You can try re-installing the OS, if the problems remain, it is most likely a hardware issue.

1. Download the *.bin file (FireOS 4.6.1)

US - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin

UK - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin

GER - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin

I strongly recommend using a download manager to speed up the download. Regular download with a browser is tedious.

2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)

From the list, choose "Apply update from ADB"

3. adb sideload 'name_of_your_bin_file'

I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin

If you have trouble finding your device after entering recovery / ADB mode:

If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.

The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.

That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.

Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.

Try this tool (& driver) http://xdaforums.com/showthread.php?t=2588979

You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.

If everything worked as planned, it should look like this: next to your device name, it will say "sideload"
[Amazon Fire Phone] abuabdallah:
Thank you for your reply.

I tried to install ADB drivers as per your instructions. It get installed successfully but device did not get connected. When I tried to side load got below error:

C:\Users\QUMER\Downloads>adb sideload update.bin

loading: 'update.bin'* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device not found
[Amazon Fire Phone] Bingo Bronson:
Ok, maybe you need to manually check for the "new" device and update the drivers:

Open the device manager while your phone is connected in recovery mode.

Look for its entry in the device list.

Remove it (Deinstall it).

Then "scan for hardware changes":

The device should appear in list the again, it will install the needed driver automatically (best case scenario)

or

you will have to update the device drivers manually:

Assuming, you're using Win 8.1 or Win 7, not Win 10...
[Amazon Fire Phone] abuabdallah:
The phone get up after many restart and three four days with out applying ADB update. But after two days it went back into same old state. Now even ADB option is not coming.

If it is hardware fault, I am not sure locally ( in Pakistan ) someone fix it as FirePhone is not popular here. Returning back to AMAZON is also not attractive option. As they are giving refund not replacing.

As a side note AMAZON told me that for replacement order your payment method some be some financial institution that is registered in US. But at time of purchase there is no such condition.:silly:
[Amazon Fire Phone] abuabdallah:
Installed the latest driver from AMAZON website but still no luck:

C:\Users\QUQQMER\Downloads>adb devices

List of devices attached

C:\Users\QUQQMER\Downloads>adb sideload update.bin

loading: 'update.bin'

error: device not found

:confused:
[Greenify] reeeju:
Greenify doesnt working with xposed module....not all xperimental features....i mean boost mode...running lollipop5.0.2
[Greenify] TNSMANI:
Did it work before? Have you donated? You have root and the correct Xposed framework installed? Is Greenify enabled in Xposed and have you rebooted? etc etc etc
[Greenify] reeeju:
I download cracked apk
[Greenify] TNSMANI:
You have some nerve, reporting it here.
[Greenify] reeeju:
Ok...working now...latest stable apk2.6.2
[Greenify] DB126:
Proud of yourself? Don't expect any help here.
[Greenify] zdravkodubravec:
Oh come on people ... Haven't you ever used a crack??
[Greenify] reeeju:
Its working nicely with all experimental features through xposed.....nd all donation package features...����������������??

?
[Greenify] Smithfolk4:
A Couple Issues

I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.

I uninstalled it via TiBU and reinstalled the backup with the same result. I uninstalled via TiBU (could not uninstall via the Android App Mgr. It was grayed out. I reinstalled via the play store - had to do via PC because I can't install from the phone for some reason. I get the same result. Only can see the single screen. Also, Greenify is not asking for root and does not show as having root permission in SuperSU (2.49) . I have rebooted, wiped cache and dalvik, and still have the same issue.

Any help would be appreciated.

Thanks
[Greenify] reeeju:
Which version of greenify r u using now...cos here all working fine in my moto g2
[Greenify] Smithfolk4:
I have version 2.6.2. It had been working in the past. It would sometimes get stuck on the same screen, but I could always get it to go to the main screen for hibernating by reopening.

I installed 2.7 Beta 2 and got the hibernate screen. Then when I rebooted it went back to the same problem.

I figured out that I had to remove administrative rights to uninstall, so I did that, uninstalled, reinstalled 2.7 beta 2 and it asked for admin rights and has them, but still I cannot access the hibernate screen after rebooting. So it seems to work okay until I reboot. I am running the latest Xposed for LP 5.0. I also uninstalled and reinstalled from the play store 2.6.2 (via PC) and I could not access it either through exposed or through the app drawer. I then enabled Greenify in Xposed and rebooted and still it is the same. I may have to remove and reinstall Xposed.
[Greenify] reeeju:
Download and install 2.6.2....tick in module list....reboot.....open greenify..select boost mode...selinux status permissive...do a soft reboot.....
[Greenify] TNSMANI:
Go to SETTINGS>Device Administrators and uncheck Greenify. Then to SETTINGS>Accessibility and switch off Greenify. Then uninstall Greenify the usual way, not through TiBu. Reboot.

Then try to install Greenify from Play Store or download the apk and install. Enable Greenify in Xposed. Enable Greenify in Device Administrators and Accessibility. Reboot, not soft reboot.

Then open Greenify and see whether you are able to access all the features.

You have root and Xposed, I hope.
[Greenify] Smithfolk4:
Thanks

I decided to reflash the ROM. Will see how it goes.

---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------

Reflashed the ROM. Had other strange stuff going on.
[Huawei Ascend P7] andromodgod:
Hello !

Yesterday While Browsing The Huawei Chinese Forum . I Came Across the Thread Which Stated MIUI 5.6.6 . When i opened The Thread It Contained Ported Rom MIUI V6 from Huawei Glory 4C

Rom Was Ported From RY09IU's Build By ycjeson .

Only Bug I Found While Testing Was That There is No Navigation Bar . :(

And The Other was Enabling Root .

How to Enable Floating Navigation Keys --> Go to Settings --> Scroll Down and open Huawei Advance Settings --> Click on MIPop -->And Enable It

If Root is not Functioning Properly Then DO NOT DELETE KINGROOT :eek::eek: .... Instead Flash This and Then Open Kingroot and root will work ...

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Download ROM FROM MEGA

For Screenshots Go Here

THIS WILL ONLY WORK ON P7-L10/05/07

Will NOT WORK ON P7-L09/00
[Huawei Ascend P7] tinyXperia:
have you tried putting in build.prop:

qemu.hw.mainkeys=0

to enable navbar
[Huawei Ascend P7] sympi:
How to install this ROM? Can I install it from B609?
[Huawei Ascend P7] andromodgod:
Yesh You Can . Although I Installed This From B619 .... It Should Theoretically work from any emui 3.0 so Yeah Go AHead and flash it
[Huawei Ascend P7] tinyXperia:
Did this work? Then I might try installing it myself too.
[Huawei Ascend P7] andromodgod:
Download The ROM . Open The ROM With WINrar and Then go to system/build.prop .... double click on build prop and open with notepad ++ or wordpad and find the that qemu line near the end of the file ..... change it to 0 and install :D:D it works
[Huawei Ascend P7] maligno1:
Thanks links , share original post please

Enviado desde mi HUAWEI P7-L10 mediante Tapatalk
[Huawei Ascend P7] andromodgod:
Open This Link in Chrome to Translate
[Huawei Ascend P7] maligno1:
Thakns andromodgod , rom is not work android.phone force closed , please solve problem :'_(

Enviado desde mi HUAWEI P7-L10 mediante Tapatalk
[Huawei Ascend P7] andromodgod:
ROM is work fine ... I tested on p7-L10 and its made for P7-L07-L05

What is Ur Phone Model

Sent from my HUAWEI P7-L10 using MIUI 5.6.6
[Huawei Ascend P7] gregysk:
Same here...
[Huawei Ascend P7] andromodgod:
well do wipe data/cache twice then go to mounts and storage and wipe system and boot and cust then install miui again hopefully no more bugs :):)

i have been using this rom since yesterday haven't faced an FC's also if it helps i was on B619 Before miui
[Huawei Ascend P7] haninatoon:
is it only for P7-L05
[Huawei Ascend P7] l3Nni:
Android.phone force closed is a problem related to the provider (in my case Vodafone Germany) I think. If you enable the flightmode and reboot the rom may work. This was my experience at other Chinese L05/07 roms..
[Huawei Ascend P7] andromodgod:
no .. Its works on L07/L05 and L10 .... I Have L10 And It Works Fine no FC's ...... If u Face FC's Then Wipe cust also
[Huawei Ascend P7] ptlima123:
i installed the rom and i have the same issue, but when i take sim card the fc dissapapear, i had b609
[Huawei Ascend P7] andromodgod:
First of All The Port is from Honor 3C ..... Second i Did full wipe i.e data cache cust boot system everything except for the storages ......

I have not faced any issue .....

:p
[Huawei Ascend P7] maligno1:
forme is not work use version emui2.3, emui3.0 b609？
[Huawei Ascend P7] andromodgod:
Try flashing b619 First use it for few minutes then flash miui Hope It Works and use slimmed version of b619
[Huawei Ascend P7] maligno1:
link 619 slimmed version please

l3Nni

Android.phone force closed is a problem related to the provider (in my case Vodafone Germany) I think. If you enable the flightmode and reboot the rom may work. This was my experience at other Chinese L05/07 roms..

is not work for me
[G4] stabloid:
First off, thanks to all out there for the hard work and brilliant ROMs you throw our way.

I have a problem with my internet settings, and wondered if anyone could help.

i have Farias MB ROM installed, and everything was going fine, until I started to get HUGE battery drains.

I managed to solve this by removing programs I am not using, deleting a load of crap off my 2 Gb SD card, and changing settings regarding items such as IE history. Soft Reset, all good!

Next I decided to try and upgrade my Radio ROM. This failed. I'm stuck with the same Radio ROM, and my device Hard Reset!

I have got the settings from O2(UK), and have put them into my mini s, butu I keep getting the message : "The page cannot be displayed or downloaded because the connection was lost. Check the connection and try again later." The problem is, I have full signal.

Any suggestions would be greatly appreciated.
[G4] human75:
did you patch gprsworkaround.cab?make sure your internet service provider settings are correct.also under the connection settings if proxy is marked make it unmarked...i hope it will help you
[Xperia Z3 Compact Q&A, Help & Troubleshooting] phre5k:
hey guys,

why do you have to downgrade the fw to 4.4.4 if you could easily flash a new firmware with root included already?

guide I used: http://xdaforums.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343

also, where are the DRM keys in the file system? I use Linux and I can't use the mentioned Windows bat file tool to back them up. And I don't want to rewrite the batch files into a shell script...
[Xperia Z3 Compact Q&A, Help & Troubleshooting] pakjebakmeel:
The DRM keys are raw data inside seperate partitions as far as I have understood it correctly. Maybe someone can comment on the details but you should be able to dump them using dd if you identify the correct partitions.. On the first question, I would be interested in this too.

Why would you downgrade and root if you can flash a pre-rooted image?

How come you can flash a pre-rooted image with locked BL? Doesn't the phone check CRC before flashing a firmware with locked BL? Doesn't it refuse to flash if tampered with? How does that work?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] faxd:
Regarding TA-backup

someone worked on a linux port, see

https://github.com/DevShaft/Backup-TA/issues/10

However unfortunately the original developer (Devshaft) is afk and doesn't merge it... :(

https://github.com/DevShaft/Backup-TA/pull/10

and

https://github.com/DevShaft/Backup-TA/issues/6

unlocked Bootloader vs Root

These things doesn't have to do with each other.

Root is "basically" when you have the su binaries in your system partition.

An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] pakjebakmeel:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.

My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] skinniezinho:
I have this question too.

Maybe because pre root images can have something installed that could hazardous?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] phre5k:
I pulled the TA / DRM keys manually like this:

cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img

Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] faxd:
To quote someone else:

And here you are still confusing root with (locked/unlocked/whatever) bootloader:

Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.

HTH
[Xperia Z3 Compact Q&A, Help & Troubleshooting] pakjebakmeel:
No, no, I think I got it now but my wording is a bit off I guess. Here are my understandings:

- Flashtool flashes through Sony firmware flash mode, this mode only flashes official tft files that pass signature check. When you add root to an image it fails signature check because of the mismatching hash and it will refuse to flash.

- To flash a 'tampered' image you need to use a custom recovery as it does not refuse.

- To get a custom recovery you need to get root to be able to flash the recovery partition.

- To get root you need to downgrade and use the exploit to get the su binary on.

Correct right?

Just one more question, how does the signature check work? I would understand it if you could download images from Sony like OTA's, they'd be signed and sealed by Sony. Just like driver signing based on RSA keys and such. If you modify them they fail the signature check obviously.

But I've seen people create FTF files from their own phones and it seems to pass the signature check, how is the file signed then? What is the 'signature' check based upon? Or is the image signature included on the phone and pulled into the FTF file when the image is pulled from the phone?

So basically the question is: "Where does the signature come from if one would create an FTF file from a working phone?"

Sorry, sorry, many questions. I'm just trying to understand all details, can't stand not knowing how stuff works.. :silly: I think I at least understand the root/bootloader/recovery part now. :victory:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] PantsDownJedi:
Restore goes well with this simpler method as well?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] PantsDownJedi:
Windows script does the exact same thing after looking at it, it does some logic for looking at the partitions a bit better is all. Hopefully nothing has changed since newer versions of Andriod.
[Galaxy S6 Q&A, Help & Troubleshooting] tiwas:
Hi,

I'm looking for an app I can use for my workouts. I have some exercises with set intervals and pause lengths and I like surfing during these pauses. However, I need to keep track of how long my break has been. So...Anyone know of a floating app that will help me keep the time between sets?

Cheers!
[XDA Assist] ShkUmar1:
Hi Guyz

I am totally new in this . I have an AT&T Note3 900A. i want to install i9005 firmware in it. can anybody tell me it's throughout procedure?

It has kikat version 4.4.2 & baseband 900A*******NC2
[XDA Assist] Razvan:
Hi,

All about your device you will find in this index thread: http://xdaforums.com/showthread.php?t=2710972

For more/other questions please ask directly here: http://xdaforums.com/showthread.php?t=2471074

Good luck
[LG G Flex 2] zerow:
My Flex2 is acting very weird lately.

On Saturday i turned it off. I was going to flash the 5.0.1 software because i saw the colors on 5.1.1 get warmer than on the previous version.

Nevertheless, the phone never actually booted again.

I contacted the service and had the phone to be collected today.

Today, i accidentally pressed the ON button while i was trying to get off the cover to retrieve my SIM card.

The phone booted, signaling 0% battery. Immediately i put in on charge and it opened without a hassle.

Then, when the charging was around 85%, the phone shut off without a warning. The phone was super hot when this happened.

I contacted the service again and the phone was collected.

What is interested though, is that both times the phone refused to open, it stayed a little warm like it's in an infinite loop with the display off and it;s not really shutdown.

Today, that booted successfully, it was completely cold. Battery must have died, and it exited the loop.

I am very concerned that whenever reaches the service station, battery will be again depleted and the phone will turn on, so nothing will be to blame on my phone.

Any thoughts? :confused:
[LG G Flex 2] kutulu32:
Before you sended it to service i would have downgraded to 5.0.1 and try stability checks first. Lets hope service will investigate if there are temperature issues
[LG G Flex 2] zerow:
I never had the chance really. That was my intention. But the phone worked for one hour or so and i was at work so...

I'll try to do it, when it comes back.
[LG G Flex 2] yyy999deba:
But we meet that issue. One day we take off the SIM Card from the phone . When we put back the SIM Card . But the phone never recognize it. Finally. We figure it out after several days.
[LG G Flex 2] bonebeatz1234:
That phone have to many issues. Take it back and hope you get a good device. If you still can get a g4 when you take it back. My wife has it and it runs way better than the flex 2 . Took my flex 2 back after 3 devices of overheating to the point it felt unsafe. Screen going out showing rainbow colors on the system notification bar and screen not turning on
[LG G Flex 2] zerow:
Mine had a faulty main pcb. I had it replaced and now everything is as it should be
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MacVader89:
Hi XDA,

My Z3 Compact has been running fine since i bought it in October 2014.

I rooted it in April, still running 23.0.A.2.93.

I've had it in a case all of the time, and i've only recently tested it underwater (<10cm). The flaps still work properly, and they were covered by the case as well.

A few days after the underwater test, I wanted to do a backup (before flashing a FTF). However,

my PC didn't register the phone

(no Windows USB connected notification sound, nothing in Device Manager).

What I've tried:

It

does

charges with the DK48 dock

It does not charge with the original charger in the microUSB port

I've rebooted and tried the power off button

It does not charge while powered off

It does not charge through USB with another original charger and cable that I borrowed

Now:

My next step is to reset the phone, but I'd like to be able to flash a stock FTF. Or just remove the root I'm running now. But since I'm unable to connect it to a PC, how can i flash a stock FTF?

TL;DR

How do i flash a stock FTF (or remove root) when i cannot use the USB on the phone?

Thanks in advance

​
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MacVader89:
Possible solution

I found this post regarding unroot:

http://xdaforums.com/xperia-z-ultra/help/removing-root-to-ota-lolipop-t2971449/page2

There's a function for completely removing root in the SuperSU app. I'm going to try that tonight and hopefully an OTA update will remove all traces of the root afterwards.

Btw, i haven't unlocked the bootloader.

I'm still curious about my phone being able to charge via the dock, but not via USB.

Regards.
[Galaxy S 5 Q&A, Help & Troubleshooting] Glazun:
This issue is rather infuriating as I never notice it until my batteries suddenly dropped to 5%, which does not take very long.

I'm just wondering if there's steps around the issue that don't involve uninstalling every app that uses the camera, because my main communication apps are Whatsapp/Viber.

The issue is stranger in that not all S5s seem to have it, but myself and my co-worker are both on the same network (Three Ireland) and both experience the issue.

So far my only way to resolve is to periodically check my phone and pull out the battery to reset it.

I only started getting this issue since updating to 5.0