yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] ale5000:
[MENTION=6668929]franky14[/MENTION]: Can you please test the latest alpha version of my installer and post the log?

[MENTION=2022267]ShapeShifter499[/MENTION]: Done.
[Miscellaneous Android Development] ShapeShifter499:
Thank you.
[Miscellaneous Android Development] joelh:
Yeah, I've determined that the ROM must be the issue. In CM13, I pass SN without moving any parts of microG into /system, but on crDroid 2.x, microG's status page tells me the ROM version is not supported and that UnifiedNlp didn't bind to the system, so I need to move it into /system, at which point I get a CTS profile mismatch.
[Miscellaneous Android Development] thesecondsfade:
Installation Failure

I'm having a problem getting the zip to flash. It's giving me the following error:

Phone motorola Moto G4 Plus (athene)
Manufacturer: motorola
Board: MSM8952
file_getprop: malformed line "import /oem/oem.prop ro.product.brand1": /tmp/microG/build.prop not a prop file?
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/microG-unofficial-installer-ale5000-v1.0.13-alpha-signed.zip'
Updating partition details...
...done

I am on Stock Marshmallow 6.0.1 with all GAPPS removed.

Any insight?
[Miscellaneous Android Development] ale5000:
Probably your ROM have a particular build.prop that confuse file_getprop.

In the latest version I no longer use file_getprop.

Please try it and report back.
[Miscellaneous Android Development] ale5000:
The message that say that the Android version isn't supported can be ignored, I also get it and still pass SafetyNet.

I think the ROM isn't the issue, as all Android 7 ROMs have the same problem (beside the ones with relaxed SELinux rules).

But usually it works when microG DroidGuard Helper is moved to /system/priv-app
[Miscellaneous Android Development] ShapeShifter499:
I should clarify I pass SafetyNet now just fine on LineageOS 14.1 with microG and Magisk Hide. DroidGuard needed to be installed to /system due to sepolicy from what I understand.
[Miscellaneous Android Development] sfoot13:
Hi guys, I installed the flashable zip, and I'm getting this error "server error", someone knows how to fix it?

My phone is a moto g4, ruining android 7.1.1
[Miscellaneous Android Development] Meloferz:
Same here, working like a charm as you on my Z2 with LineageOS 14.1

Enviado desde mi Xperia Z2 mediante Tapatalk
[Miscellaneous Android Development] ale5000:
Hi,

where do you get it?
[Miscellaneous Android Development] sfoot13:
Is from the first post, the error is from the play store.

No matter how I installed it, from the zip or direct from the apk, I'm getting this error, I tried with old versions of microg and playstore, but no luck.
[Miscellaneous Android Development] adikri:
Did you dirty flash your rom and then flash microG or updated your play store??
[Miscellaneous Android Development] sfoot13:
I flashed the rom first, then I downloaded this zip and I flashed it, (I never flashed gapps, so playstore was not installed)

I'll wipe data and system partitions, then I'll flash the rom with microg.
[Miscellaneous Android Development] ale5000:
Does your Wireless work? (it show a question mark).

Try to terminate the Play Store, verify by opening a browser that internet is working and then opening Play Store again.
[Miscellaneous Android Development] sfoot13:
I did a clean installation, Rom+Microg, and I'm still getting the same error, the wifi has no problems, maybe is my phone, or the android version (7.1.1), is a weird issue because it was working before, so maybe is my rom, I'll try flashing the stock firmware and see what happens.

Thanks for the help guys :):fingers-crossed:
[Miscellaneous Android Development] thesecondsfade:
Worked like a charm!
[Miscellaneous Android Development] kmem:
Is it normal for my seLinux mode to get switched to permissive when flashing your package? SeLinux was enforcing but after the installation of microG it reverts to permissive. microG seems to work with maps, giving proper location using the Mozilla backend but under a lineage ROM I get a CTS mismatch when testing safetynet from within MagiskManager.

I installed the magisk systemizer module but I am unsure how to direct it to install droidguard to the proper location.

Any help would be appreciated.
[Miscellaneous Android Development] ale5000:
No, it isn't normal.

There isn't any change regarding SELinux in the flashable script.

If SELinux is permissive you will always get CTS mismatch.

Have you tried a clean flash of the ROM you use?
[Fire Original Android Development] globula_neagra:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/

Hello people.

Due to the fact that I have a tablet built around the MTK8127 SOC I decided to adapt some stuff for the Amazon Fire 2015

I need to mention that I don`t own the tablet so I don`t have the means to test the recovery.

The recovery is built from source using CM 12.1 and is based on the classic CWM with further additions designed for MTK devices like backup of important partitions (uboot. tee1, tee2 and so on)

What could be wrong:

-mounting points, as I used the default ones that are being used for twrp

-resolution (the recovery might not fit properly on the screen.

-other random stuff

Features

-full touch recovery

- all cwm functionalities (adb, sideload, backup, restore, install, mass storage...).

-in Carliv menu there is now a new section for flashing boot and recovery images.

-a special menu from where you can restore specific partitions

-multizip flashing function

The main sources used are here:

https://bitbucket.org/amazonfire2015/cm_device_amazon_ford/src

I have not uploaded yet the device tree that I am using as I don`t know if the build is actually working (it should), Will do when I have some days off from work :).

If someone is willing to flash and tell me what are the flaws, I will address the issues.

Credits to [MENTION=777546]carliv[/MENTION] aka [MENTION=5186178]bluefirebird[/MENTION] for his efforts in continuing the CWM project in his new form as CTR.
[Fire Original Android Development] DB126:
For awareness:

- this (any) custom recovery can only be started from fastboot on devices with 5.0.x bootloaders (rather rare)

- no custom recovery can be flashed (installed) on this device as bootloader remains locked.
[Fire Original Android Development] fmc000:
Thanks for your work but... no one will flash this because it's impossible on Fire due to the locked bootloader. People with the 5.0.1-based fastboot implementation will be able to boot it but not to flash it. I will try it and report back as I use this recovery on my MTK-base Asus and I love it.
[Fire Original Android Development] globula_neagra:
A bootloader downgrade should be achievable with SP flash tools.

Are there any bootloaders uploaded somewhere ?
[Fire Original Android Development] fmc000:
Have a look at the various threads in the different sections of the "Amazon Fire" forum. There are some downgrade protections from Amazon on these devices and hard bricks are unfortunately not so difficult.
[Fire Original Android Development] globula_neagra:
I will get one on BF just to see if I can sort something out regarding the bootloader.

The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.

But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
[Fire Original Android Development] DB126:
Partial responses:

- no one has successfully flashed twrp or any other custom recovery

- a custom recovery could be booted from fastboot on early devices; the 'vulnerability' was closed with bootloader 5.1.x and above

- bootloaders 5.1.x+ can not be rolled back to 5.0.x; hard brick

- Amazon rollback efuse has proven to be fairly robust; was never cracked on 3rd/4th gen devices that enjoyed a 2+ year run (albeit on a different chipset)
[Fire Original Android Development] Kramar111:
We don't have .auth file for authentication. SP Flash tool useless without it (we can't even readback). We have secured chip.
[Fire Original Android Development] beautiful3cellar:
*delete thread*

Please...?

?
[Fire Original Android Development] sd_shadow:
quick review:

recovery boot fine

resolution seems to be off

buttons don't work

touch screen is off
[Fire Original Android Development] ldeveraux:
Sounds like a home run ;)
[LG G5 Questions & Answers] tomb007:
I have a LG G5 H850, with 6.0.1 and stock V10c-EUR-xx.

I disabled disk encryption using the no-verity-opt-encrypt.zip utility by jcadduono.

Now I wiped again using TWRP, but encryption is still disabled as the boot.img/partition still has his modifications to the fstab files (where he does

the change s/\bforceencrypt=/encryptable=/g etc.)

How to I set that back to as it was?

I got into this sitation as I kept finding TWRP could not access the partition - asked for password and there was none.

I do want to use encryption but in my first hour of setting up the phone I had a problem where when I booted into TWRP it would ask for a password and it was not "default_password", and I had not set anything and never used lock screen/pin etc. I tried setting a lock screen/boot screen password - the phone worked but TWRP could not access the filesystem. I tried the cryptfs application and still TWRP was not able to decrypt/access the partition.

Then I tried a terminal with vdc cryptfs changepw command and that just locked me out of the phone completely, as the new or old boot password would not work.

So I went for the no-verity-opt-encrypt.zip solution - but I dont want an unencrypted phone either. Now I want to try encryption and TWRP again - this time setting a pin at the first setup screen opportunity to see if that gets set as the password that TWRP could use. However I can't remove the disable encryption patch!

Ideally I am trying to get to a setup where:

encryption is enabled

I want to be able to boot TWRP and access the encrypted filesystem and install more zip files such as xposed/supersu updates etc anytime in the future.

I dont want to use the "no-verity-opt-encrypt.zip" patch.

I do not want TWRP to be locked out from modifying the encrypted system partition.

Additionally, I havbe not been able to install xposed using TWRP and the zip file (http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip) .

In TWRP it installs, I dont see any errors, but on boot up I have no xposed icon. I have been able to install it by downloading the apk and installing as an untrusted source, not sure if there is something wrong in having to do it this way?

Thanks.
[LG G5 Questions & Answers] gwolfu:
current TWRP build for G5 doesn't support encryption

you can use encryption but in TWRP you won't be able to access some partitions (if I remember right is data partition but I might be wrong here)

in order to do so, you need to restore base firmware with LGUP that will turn encryption back on
[LG G5 Questions & Answers] tomb007:
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
[LG G5 Questions & Answers] khaledtaleb:
may i ask how did you root it after that? because everytime i try to rooted while encrypted,i flash the zip in twrp (with no errors) but system still has no root! the only way i could root was to format /data in twrp, hence have a decrypted phone!

I am looking for the same thing as you are : encrypted phone with twrp and root access.
[LG G5 Questions & Answers] tomb007:
I rooted using TWRP adding supersu at the time of installing the OS before the OS encrypts the partition. Once the partition is encrypted TWRP can no longer access it, and I can no longer install supersu or anything else.

I may have installed root before encrypting, then reflashed the boot partition so that encryption is re-enabled, then ran twrp to reapply supersu - which would fail to put files on the encrypted partition - but this is fine as they were already there, and let the twrsp supersu installation modify the boot partition.

The result is an encrypted phone with root and TWRP. However, TWRP can not access the encrypted partition so I don't think I can update supersu using TWRP, and I dont think I can patch the OS easily without wiping the encrypted data and reinstalling everything due to this. As I am not sure if updating the OS works without wiping data, I have yet to try that.
[LG G5 Questions & Answers] autoprime:
you shouldnt have to mess with data at all to use supersu while encrypted.

my g5 is encrypted and always has been (besides in various testing) and there's never been an issue of flashing supersu.

though there may be some issues if trying to restore encryption and flashing supersu in the same reboot cycle.

and yes, data partition in twrp cant be accessed in twrp if encrypted.. but you can just push a file to the /tmp directory while in twrp and then flash anything... or enable adb sideload and flash something that way... or use an external sd card and put the file on there. the only thing you really miss out of if using twrp while encrypted is being able to manipulate the data partition... it does not stop you from flashing files or running scripts that modify /system or other partitions (besides /data).

supersu uses the unencrypted /cache/ partition to work in when you flash it while encrypted so an encrypted /data partition should not be relevant.
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
Hi, I have a new E6683 from Hong Kong. In Xperifirm, I see a list of CDAs for the E6683 and I'm guessing it's the only Hong Kong one (because there is only one HK one fortunately). But is it possible to be absolutely sure which one it is? I tried adb shell getprop but couldn't see it in there. I'm guessing I'm just not looking hard enough. :)

TIA

m
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
Gave up in the end and just picked one at random! (Singapore.)
[XDA Assist] ninclemdo:
I am able to connect my phone (BLU STUDIO 6.0 HD) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. :crying: I would appreciate any help.
[XDA Assist] GuestK0087:
OP reposted:

http://xdaforums.com/general/help/volume-button-trying-to-unlock-t3432439

Thread closed.
[Xperia Z5 Premium Q&A, Help & Troubleshooting] david1985:
forgot my password haven't used this phone in while anyway to boot into recovery? thanks
[LeEco Le Max 2 Questions & Answers] valy_cta:
So by a stupid mistake I have selected in *#*#4636#*#* the Radio Band to USA. The signal suddenly dropped and it stopped working at all, the nework does not connect except in 4G and only for data. Calls and text are not working, only 4G data works fine. This is on the sim1 though. On sim2 all is ok (except that with the X829 ROM, on sim2 I have no data, and on sim1 I have no calls :))) ). I was on sim1 when I've changed the Radio Band, so I guess that only this one got affected since sim2 is working properly.

Is there any Radio Band files that I can restore? Or some app that can restore the settings of the modem?

Any help is highly appreciated.

PS: Reinstalling the ROM (clean or dirty) doesn't help. Factory resetting also doesn't help. I would downgrade to 014s but I'm afraid not to end up with a brick.
[LeEco Le Max 2 Questions & Answers] Ootp:
Change the rom

If i were you. I would change the rom from china to indian rom. It would help you. The radio band of chinese rom and the indian rom is different. It would replace the radio band of chinese rom and if it doesn't work. Then return to the chinese rom

I'm 100% sure it would help you.
[LeEco Le Max 2 Questions & Answers] chatmonchy:
I did the same thing by my mistake.And my le max 2 also became not able to connect internet. In my case, it can't connect both 4G and 3G .

But I fixed it. But I don't know that it get back to the original completely.

I'm japanese.And I'm sorry for that my English skil is very poor.

My current rom is Le2_X820-MAX_ROW-5.8.015S_V29_CUOCO92.

I used DFS CDMA TOOL and checked the items on the "Band Preferred" same as "RF BC Config".

1. download HTC Diag Driver. You have to customize .inf file later.

2. conect device to your windows pc and choose MTP and USB Debugging.

3. enter the follows command.

"adb shell"

"su"

"setprop sys.usb.config diag,adb"

When you enter this command, your device change over diag mode.

4. diag driver install.

You have to find hardwawer ID from device manager.

And replace the hardware ID in .inf file.

5. If you install diag driver correctly, you will be able to use DFS CDMA TOOL.

sorry, I can't explain any more..English is difficult...
[LeEco Le Max 2 Questions & Answers] xterminater07:
I bought my phone from china and I'm in US, and it works perfect on stock with LTE enabled for AT&T by default. Might I ask why did you change it to US band and it stopped working? It would still work right?
[LeEco Le Max 2 Questions & Answers] valy_cta:
Many thanks for the advice but it didn't help. I had installed the indian rom and then to the chinese without any change in the behavior of the modem. I'll try the chatmonchy's advice to see if there will be any improvement.

Actually I'm in Europe and looks like we use slightly different bands (??). I get 4G data but without calls. To other networks like 2G and 3G it connects sometimes but it's for few seconds only. I even don't remember what made me change the bands to USA, I guess I was curios what settings those were. The options are "USA band" and "Band 6", neither one is working well for my device. And strangely though, there is no other option to go back like "Auto" or something. It seems that I'm not the only one that did it. After a google search, it turned out that a lot of people had the same issue. For some, the factory reset helped, for others was flashing via TWRP the radio bands again.
[LeEco Le Max 2 Questions & Answers] valy_cta:
I had solved the issue and I will post a guide later on for those who want to unlock additional bands or did the same mistake as I did.

Thanks for the help guys.
[LeEco Le Max 2 Questions & Answers] chatmonchy:
That's good!!

I'm looking forward to your guide about unlock additional bands.
[LeEco Le Max 2 Questions & Answers] readion:
thread: [SOLVED] Accidentally changed the Radio Band to USA

Hi, gyus

I had the same problem, i select USA band and everything went wrong,

The simplest way for me was:

installing "X820 LeMax2 RevolutioN_Team Resurrection Remix", no other from TeamSpain, only Resurrection Remix

http://revolutionlemax2.blogspot.al/

https://mega.nz/#!T9o0wAhJ!iLa9mrPAr...VkCg3_L-q2RgnA

then after installation, go in dialer and call *#*#4636#*#*.

There are three band: Automaic, USA, and EURO.

I select the EURO and everything i'ts OK.

BEFORE DO ACTIONS DON'T FORGET TO BACKUP ALL THE ROM WHERE YOU ARE WITH TWRP
[LeEco Le Max 2 Questions & Answers] karellang:
Hi, how to install this ROM? Which TRWP I need? I install with official TWRP, but bootlop after instalation. :(
[LeEco Le Max 2 Questions & Answers] readion:
Try this link for recovery by GrossoShop Couco92

https://www.androidfilehost.com/?w=files&flid=57913

---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------

Try this link for recovery by GrossoShop Couco92

https://www.androidfilehost.com/?w=files&flid=57913
[LeEco Le Max 2 Questions & Answers] karellang:
Does not help. If I go to servise menu (dial *#*#4636#*#*) , I see Radio turned OFF and I can´t change it. How to solve this ?
[LeEco Le Max 2 Questions & Answers] IFightCode:
Did you post any guide how you solved the issue?
[LeEco Le Max 2 Questions & Answers] jayrajkudale:
Unfortunately USA band selected

Hi,

I live in India. I bought Oppo F3 Plus (CPH1613) 4Gb Ram, 64GB Storage, Qualcomm MSM8976 Pro Snapdragon 653 a year ago and was working too much fine. I was wondering about Qualcomm mobile secret codes and found this *#*#4636#*#* . I dialed this and accidentally changed radio band to USA band and suddnly on instant my mobile didn't get any network signal. From then, I went for Oppo care, and mobile repairing shops and self tried and tested for lots of time; but everyone unable to bring phone to normal. I reset my mobile, flashed stock rom for countless times, wiped all data but nothing helped me out. Finally i rooted my oppo f3 plus and tried to boot in fastboot mode; but Oppo removed bootloader and fastboot mode from 2016 (as posted in XDA). I got a little link about resetting USA band to automate and is erasing modemst1 and modemst2. But again it have to be performed from fastboot.

Help me out for my mobile.
[LeEco Le Max 2 Questions & Answers] valy_cta:
You can flash a modem file, it will reset it as well. Changing the ROM won't update the modem configuration. Try to search modem files and flash them via TWRP.
[Android Head-Units] feikuk:
Hi, ive bought one of these units, i previously had one which i had no trouble with. Until the usb and wifi died so became useless to me.

i have a new one no with the rkpx3 chip and a soldered board, i can get root access with no issue, but if i soft boot to recovery, i get "no command" . I have tried the usual buttom combinations to get a response but nothing. the only way i can seem to exit the recovery mode is via the reset button which deletes everything and returns to stock.

i cannot gain recovery via the hard buttons either!

the dev password is 3386, could i be right in thinking this is a seller locked software? i have asked the seller and they told me it couldnt be rooted (have su access so i know its rooted)

my serial number is listed as 00000000 also.

any help would be greatly appreciated

regards
[Dell Venue] moxiot:
As the titles says, my tablet stopped charging. I already had this problem while it was under manufacturer's warranty and they fixed it for me. Now, with the warranty expired and all, I have no idea what to do.

I have looked everywhere and I can't find anyone who even knows how to fix this, let alone finding the spare part needed. I guess I'm just venting and asking for advice at the same time. Any pointers would be greatly appreciated.

Many thanks!
[Dell Venue] thebreezer:
Bummer. Probably possible to resolder a micro usb power jack. Had it done on my HP Chromebook 11. Go to your local computer wizard shop.
[Galaxy S6 Q&A, Help & Troubleshooting] mzlmdgn:
Hello guys.

I want to use pelya's USB Keyboard Gadget.

But there is no patched kernel for Galaxy S6.

I tried to patch it myself but I couldn't do it.

Can you patch the kernel and send it to me?