yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] stl-soldier:
Ah, makes sense. Not sure why it isn't working for me then. I can try downloading and flashing again. I tried a few copies from different servers, but full disclosure, I never checked the MD5...

CPU Info:

processor : 0

Features : fp asimd evtstrm aes pmull sha1 sha2 crc32

CPU implementer : 0x51

CPU architecture: 8

CPU variant : 0x1

CPU part : 0x211

CPU revision : 2

processor : 1

Features : fp asimd evtstrm aes pmull sha1 sha2 crc32

CPU implementer : 0x51

CPU architecture: 8

CPU variant : 0x1

CPU part : 0x211

CPU revision : 2

processor : 2

Features : fp asimd evtstrm aes pmull sha1 sha2 crc32

CPU implementer : 0x51

CPU architecture: 8

CPU variant : 0x1

CPU part : 0x205

CPU revision : 2

processor : 3

Features : fp asimd evtstrm aes pmull sha1 sha2 crc32

CPU implementer : 0x51

CPU architecture: 8

CPU variant : 0x1

CPU part : 0x205

CPU revision : 2
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'll add them back and see if that resolves your issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Twerkules:
I followed the guide to upgrade with TWRP by flashing the .img through TWRP, and now I don't have a recovery on my phone. I can boot into bootloader but selecting the "Reboot Recovery" option leads to a black screen where neither adb or fastboot commands work. Not sure how this happened, but it did.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] stl-soldier:
I'm not sure if that's necessary or not. I see the latest version has been downloaded several times, but I haven't seen any other report of it working or broken from anyone else. It could just be me or my device. If it helps, I can install the one that doesn't work and try to get a log of it. It basically just boots to a blank screen, but adb might work during that time. I just don't know enough about adb to know what commands to run.

EDIT: Guess I didn't refresh fast enough. The previous post confirms issues with the latest version and that adb doesn't work during failed recovery boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
New build uploaded the image name is the name

Download

Changelog:

Add support for installing fastboot images (Install -> Install image)

Add support for backing up and restoring fastboot images

Add support for double tap to wake (when the screen goes black one tap doesn't work like other devices)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] strifej:
Unjustified, is there a fix for the twrp encrypted data (needs password, but no passwords work) problem? I'm asking because I think tenfar is using your twrp as part of his root without unlocking bootloader. Others and I are hitting this problem using the newest 3.0.2-2 (signed by tenfar for locked bootloader).

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
[MENTION=4911249]Unjustified Dev[/MENTION]

Just to add a note on this. When i used tenfar's TWRP to dump system image, but left the stock boot.img, aftre rebooting into recovery, TWRP log shows that it decrypted the data with default password even though i have FP and patter setup. Data was mounted and available for backup and browsing. Is this by design and patter and FP only work as OS level protection and default_password is still the encryption key?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
It got the password from the crypt key partition. It only asks for password when your encrypted and it can't find the one it stored.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MaxRink:
So that should work with http://xdaforums.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 to avoid typo****ups? based upon it gets signed by [MENTION=540283]tenfar[/MENTION] ofc so you can use it as initial recovery
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
So cryptkey is not re-encrypted when you change security model in OS. I thought that's how it worked, setting one encrypts the default cryptkey and needs password to access it. OTOH your phone would not be able to access data at all after reboot so it actually can mount data without input and use cryptkey to decrypt... This probably work only on same HW for TPE and keystore but still a rather weak encryption model. That firehose tool is actually worse than i though
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] strifej:
Can we get our crypt key while in the ROM?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
I want to say if you are rooted then yes. It's just a partition, so it can be dumped with dd (i did that via TWRP though). It's /dev/block/bootdevice/by-name/cryptkey
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Nan Da Man:
error: cannot load 'twrp-3.0.2-2-a2017u.img'

Hey everyone, thank you so much for this fine development! Anyway I'm trying to install TWRP and don't know what's going wrong.

here's some details:

- I've read the entire thread and hasn't found a fix...

- I'm using a mac

- I've already unlocked the bootloader (B20_Boot showing)

- OEM Unlocking is enabled

- I've placed the downloaded file on the sd card (and internal card, just in case)

first command - adb reboot bootloader - no problems

second command - fastboot flash recovery twrp-3.0.2-2-a2017u.img - I get this: error: cannot load 'twrp-3.0.2-2-a2017u.img'

I'm really looking forward to rooting this, thanks for all your help!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
You mistake is the file Location, You need to have the file in the same location as the fastboot file or :

fastboot flash recovery twrp_file_location_here

So you'll end up with something like this

fastboot flash recovery c:/axon7/twrp-3.0.2-2-a2017u.img

If the twrp image is in the same location of the fastboot just need to type the twrp name after recovery.

Hope that helps
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Nan Da Man:
Draken, thanks for the super quick reply. I got it to work!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Keiler90:
Can we remove the "U" from the thread subject? :P

It works on all models, correct?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Well yeah, but at the time the only version with unlocked bootloader was the U version. I'm still looking for a way to differentiate the devices.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrWilsonxD:
I would like to do this but.. My axon isn't being recognized by my computer. Has anyone had this issue with windows 10? I have used all the connect methods on my phone (charging, install device driver, connect to pc, mtp, ptp) only in ptp does the computer recognize it.. :/

EDIT: https://www.google.com/amp/www.howt...e-to-show-up-in-file-explorer-if-it-isnt/amp/

Helped me figure this out. :laugh: Although my phone was listed under MTP serial, then unknown device.

EDIT: xD Sorry for all the edits, but it seems the link for twrp is down.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JKSurf:
Recovery Gone

I just flashed the twrp-3.0.2-2-a2017u.img in twrp (install, checked image, chose image flashed to recovery) and now I can no longer get into recovery. Fortunately the phone boots up fine. While pressing the volume up and power I get the blue ZTE for a second and then the screen goes black (shuts down). Any idea how I can get twrp back?

Phone is rooted without bootloader unlocked.

Just reflashed with Tenfar's root tool and got TWRP back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrWilsonxD:
Are you able to download twrp from link in OP?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JKSurf:
Yeah I guess I could only use Tenfars twrp. My bootloader is locked. Got it working again with Tenfars tool. Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrWilsonxD:
Darn.. I already unlocked my bootloader and was planning on going with this method.

I'll just wait until the link is updated. :laugh::victory:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JeromeLeung:
Anyone got a mirror for this TWRP? Seems like the link in the OP isn't working :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
https://www.androidfilehost.com/?fid=24723757092307091
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrWilsonxD:
:laugh::laugh::laugh:

Just got off a 11 hour shift of teaching math. You just made me sooo happy!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lian00:
Hi,

[MENTION=4911249]Unjustified Dev[/MENTION]: i have the same error as [MENTION=3973227]stl-soldier[/MENTION], only restore to tenfar's recovery image is working.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Is your bootloader unlocked?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lian00:
yes unlocked. But as far as i remember i had the same problem before i unlocked the bootloader.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ogre6473:
So I try to install TWRP this is what happens. I suspect it's a really easy error to fix and I'm just missing it.

Edit: It WAS a simple error, but now I have another problem.

[IMG="Flash Fail"]http://i66.tinypic.com/t85klu.jpg[/IMG]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
You did not unlock your bootloader
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ogre6473:
That's the weird part. I DID unlock it. It even said I was on B20-Boot. But for some reason it didn't actually unlock or it somehow relocked.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Could you explain the steps you took to unlock it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ogre6473:
Updated my phone. It was an unlock from ZTE so it was pushed as an update. Just went ahead and flashed the unlocked boot loader manually and will try twrp again.

Edit: Oh hell. Didn't know about the Fastboot OEM Unlock step. -_-
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
i've a question. if i slide for system modified and don't flash anything i get bootloop. right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
Best to just not slide it. You can still root without sliding.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
thanks again. which supersu version we should use to root?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
I used 2.65, which installs in systemless mode by default. If you want to make changes to /system (needed for things like AdAway, freezing in TitaniumBackup, etc), make sure to disable system write protection: http://xdaforums.com/axon-7/help/co...to-persist-t3440276/post68206618#post68206618
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
I'll flash latest version of supersu. Not systemless one. Because I use Adaway and titanium backup.

First of all, I'll unlock bootloader via stock recovery, then I'll root it and backup all images to return unmodified stock rom. To do this systemless root is enough or not?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
No, don't. Install it as systemless (2.65). Installing the latest will try to install it as a system install unless instructed not to, and TWRP modifying system is what seems to be breaking things.

Unlock bootloader, flash TWRP, do

not

slide to allow system modification, backup your stuff, flash SuperSU 2.65 (which does not break things because it only installs in systemless mode), boot back into OS, and then run that command I linked above, and then you can AdAway/TiBu fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
how will i use adaway or tibu when i flash systemless root?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
They work fine with systemless root. You just need to make sure to disable system write protection.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] corpdecker:
So, I've been going in circles on this for a couple days now. I can get my phone locked or unlocked, rooted or not, B20, B27, stock boot or recovery or not, etc. The only problem I'm having appears to be related to TWRP and it's handling of the /system partition, as in I get file corruption fairly often on it when I mount it as read/write in TWRP and do something as simple as replacing a bootanimation.zip . When I say corruption, I mean I have to e2fsck it from TWRP using 'adb shell'. So far, if i reboot the phone with 'adb reboot disemmcwp' and let it boot back to the system, I can 'adb shell' to it, remount system r/w with 'mount -o remount,rw /system' and replace the bootanimation.zip, remount it r/o again and it's fine. Otherwise, I end up with either very corrupted /system (to the point where it will force remount read-only, or even fail to mount in TWRP at all) or show the Data password decrypt prompt when starting TWRP, refusing any password even if set explicitly with something like 'vdc cryptfs changepw $NewPassWord' . It seems like this must be a bug in the fs driver for TWRP or something wonky with the Axon 7 ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] manu7irl:
I'm trying to change the password with this command but it is asking me the current password...

Is there anyway to bypass that?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MrWilsonxD:
I thought xposed broke systemless root. Is there a way to have both? D:

Supplemental Edit: Got TWRP up and running :D tyvm! Had to move the img to where I installed adb..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lian00:
[MENTION=4911249]Unjustified Dev[/MENTION], i had still no luck flashing the newest TWRP, it just goes black after rebooting recovery. I tried even to flash it with tenfars root tool, but its the same.

Do you need some more information?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] corpdecker:
I think you need to use the current pass, but by default it should be your screen lock password if I understand the system correctly. This link http://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ has some info on using it. Note that whenever I was in TWRP and swiped right to mount system read/write and actually wrote to it, I got severe filesystem issues that caused it to not be able to decrypt the data partition from TWRP (it asked for pass, but wouldn't accept anything as correct), the system partition got quite messed up and just general chaos ensued.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
Sorry to bring back this after a while, but it took me while to get around reading on the FDE. If i get this right the /cryptkey is the crypto footer that holds the encrypted DEK plus salt and the keymaster blob. The DEK is encrypted initially with the "default_password", but once a lockscreen security method is setup, the DEK should be re-encrypted with new KEK based on pin/patter/password of lockscreen. So TWRP should not be able to decrypt using default password as indicated by the logs. So if that's the case, something is broken in the stock rom and the lockscreen password is detached from the FDE so the DEK is still encrypted with the "default_password". Because of the TEE, decryption of DEK is still somewhat device dependent for generating the intermediate keys but knowing what the password is makes brute forcing decryption of DEK much easier.

Does this sound about right?

Reference reading material for anyone who is interested, since it has nice work flows

https://nelenkov.blogspot.com/2014/10/revisiting-android-disk-encryption.html

http://bits-please.blogspot.com/2016/06/extracting-qualcomms-keymaster-keys.html

http://source.android.com/devices/tech/encryption/index.html
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rikin93:
[MENTION=4911249]Unjustified Dev[/MENTION] So ive got the official root and bootloader unlock installed on the A2017G version (i will create a topic later with proof that it is official and is coming). Am just wondering whether following this guide in theory should work, and also whether it will wipe my data?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Although not mentioned in his guide tenfar uses my twrp recovery. So expect the same results it only changes your recovery partition and a data wipe isn't necessary.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rikin93:
Cool will do it tonight and keep the EU users updated :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rikin93:
No luck couldnt get it installed!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Only way to install latest TWRP is for [MENTION=540283]tenfar[/MENTION] to sign the new TWRP , if not when you flash [MENTION=4911249]Unjustified Dev[/MENTION] latest TWRP will not boot at all, till you reflash [MENTION=540283]tenfar[/MENTION] sign Recovery (which is actually [MENTION=4911249]Unjustified Dev[/MENTION] TWRP ).

This is just assuming you are Lock Bootloader, otherwise should boot to system without a problem
[Sprint Samsung Galaxy S III] mbellot:
Greetings,

I'm hoping someone can help out. My daughter's GS3 is acting strange and the only answers I've found via Google aren't right.

It's running CM11 (20150831 SNAPSHOT) and TWRP 2.8.7.0.

The problem is that the phone will not charge when powered off. If I connect a charger (tried several) the phone will vibrate every 2-3 seconds, and it never shows the charging animation.

If I boot the phone into CM11 it charges just fine, so I'm inclined to think it's a software problem and not a hardware failure of some kind.

A broken/stuck power button seems to be the most popular answer for the "continuous vibrating" problem, but the power button works just fine and the phone does NOT power on if I just insert the battery.

I've tried re-flashing (dirty) the ROM to see if something simple got corrupted, but no luck.

Next step (unless I get advice for something less drastic) is to flash back to stock to see if the problem persists.
[Sprint Samsung Galaxy S III] rootinchase:
Change the kernel. You can run cm11 with different kernels. Try dkp
[Xperia Z3 General] roy022794:
has anyone have create or have a FTF file of new firmware update the D6633 23.5.A.1.291 Customized RU 1288-7362 R3D?? we really appreciate if anyone could upload a link??

thanks
[Xperia Z3 General] Bajotaz:
http://xdaforums.com/crossdevice-dev/sony/pc-xperifirm-xperia-firmware-downloader-t2834142
[Eee Pad Transformer Q&A, Help & Troubleshooting] goattee:
:confused:This is odd. I have not changed my TWRP version (2.8.1.1) in a very long time so the problem below is not triggered by flashing a new recovery image-- or anything else for that matter. Today I went into recovery mode and:

The tablet turned on the touchpad interface (a mouse cursor appeared)

The touch screen interface is off.

The keyboard interface is off.

I tried to click on everything but although I could see a visual indication, there was no change to the chosen onscreen menu "button."

Removing tablet from keyboard dock does not help.

In desperation I held down the power button hoping to force a hardware restart. But TWRP went into lock mode.

I can't access the swipe motion to unlock.

I can't force a reboot.

I tried ADB to see if I could do a command line reboot.

Windows 10 Device Manager shows the ASUS device in the list.

Windows 10 PC can display the filesystem on the tablet.

But command "ADB devices" never shows the tablet. (Empty list.)

Weird!

Is my only choice to run the battery down?
[Eee Pad Transformer Q&A, Help & Troubleshooting] goattee:
The problem condition suddenly cleared. It's as if the tablet knew I was complaining to the XDA community.

One hour after the problem first appeared, I tried plugging the USB into the PC again. The touch screen spontaneously turned on. I was able to swipe the unlock and perform the cache clear. And performed the reboot.

You don't have to waste energy guessing what happened. But if any of you are convinced you know why this ocurred, I'd love to know so I can prevent a recurrence.

Is there a later compatible TWRP for the TF101? I couldn't find one.
[General Questions and Answers] myutube09:
I have a pattern password set on my Nexus 5, but it doesn't ask for any password when I connect it to my PC, it just shows all the files. This is ridiculous. How can I protect my data?
[General Questions and Answers] Planterz:
With all my Androids, with which I use a pattern password, the files won't show on my PC until I unlock the phone.
[G3 Q&A, Help & Troubleshooting] edgarong:
how to recover the internal storage. i already have my phone rooted and tried to upgrade again my phone in marshmallow via lgup. sad to say i pressed the refurbish rather than the upgrade and now im experiencing my system is only appearing in twrp but when i tried to put my backup again from pc to my lg g3 there is no internal storage and cant even see the twrp where i will put my backup.
[G3 Q&A, Help & Troubleshooting] Chrisjjj:
Same thing just happened to me. Won't even detect my external storage.
[G3 Q&A, Help & Troubleshooting] bmatney:
If you can still access TWRP I'd recommend wiping everything and then sideloading your rom of choice.
[G3 Q&A, Help & Troubleshooting] Chrisjjj:
I was getting into TWRP but when I went to select a storage device they all had 0 capacity. I decided it was most likely a hardware issue. With nothing to lose I cooked the motherboard and it started working again. Guess I've got about 2 to 3 weeks before it dies again. I ordered a LG G5 from china.

My wife's LG G3 also would not boot and I cook that 3 times before it fully died. That also lasted 2-3 weeks before playing up again. From my experience they only seem to have a life span of 2 - 3 years. I loved my G3 and it will be sad to see it go. :(

Might buy another motherboard for it and it can be my backup/experimenting phone.
[G3 Q&A, Help & Troubleshooting] Chrisjjj:
It lasted about 2 weeks and now I have the same issue again. Tried to cook it again a few time but nothing. Goodbye G3. :(

LG seems to have some serious quality issues with their phones. My wife G3 also died after a 2 years with similar issue. Her screen was flickering then eventually it would just come up with a blue screen. After cooking a few times and resurrecting it, it too eventually died. I think their solder joint seem to be a huge problem.
[XDA Assist] :
I have a samsung galaxy tab 4 7.0 3G SM-T231 and it hasnt got lollipop yet

Whereas the sprint and lte version of the tab have got it

Sprint and lte version are exactly same in specs just the difference comes into carrier

Sm t235 has got lollipop i need a guide so that i can port t235 to t231

Both devices are same ,7 inch display,1.5 gb ram etc

I need help or if someone can help me make this rom

I have both roms downloaded with me already im just a beginner in android development im rooted

And can follow instructions well enough
[XDA Assist] :
Greetings,

Thank you for using XDA Assist.

Please have a look at the Tab 4 homepage:

http://xdaforums.com/tab-4

Please create an XDA account so you can ask the experts here:

http://xdaforums.com/tab-4/help

Good luck and welcome to XDA!
[P3300, MDA Compact III  upgrading etc.] bigleo187:
hello everyone!

i am still abit new so please help!!!

how do i upgrade from my WM5 to WM6 on my xda orbit?

please can i get the dummies guide reply :D
[P3300, MDA Compact III  upgrading etc.] Technoboots:
Just read this page for the official WM6 upgrade.

http://member.htc.com/ruudownload/O...r=http://www.my-xda.com/xdaOrbitSoftware.html
[P3300, MDA Compact III  upgrading etc.] wbambrook:
Windows Mobile 6 on Orbit

Hello all,

This is my first post and hopefully useful.

http://www.my-xda.com/xdaOrbitSoftware.html

I have loaded it and it is brilliant.

remember to back-up you data first!!!!

regards

Warwick