yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 Guides, News, & Discussion] zams85:
cant find google installer v3.. share please
[Android Software/Hacking General [Developers Only]] stephendt0:
Hey guys,

Not sure if this is the correct place to post, but I am at my wits end and think I need a bit of help. I have been cloning devices on Android 7.1 without too much trouble, but something has changed in Android 8.1 which breaks things. Here is my setup:

Device: Xiaomi Redmi Note 4X 16GB, unlocked bootloader

OS: LineageOS 15.1 (Android 8.1)

My setup process is as follows:

Let stock ROM update (for latest firmware), unlock BL, flash TWRP, clean wipe, flash LineageOS + Gapps + Magisk

Skip through setup wizard, apply customisations (apps via APKs, launcher, settings, etc)

Clear Data for following:

com.google.android.gms.setup

Google App

Google Account Manager

Google Backup Transport

Google One Time Init

Google Partner Setup

Google Play Services

Google Play Services for Instant Apps

Google Play Store

Google Services framework

Reboot to TWRP

Connect to PC, run following ADB command: adb pull /data/system/users/0/settings_secure.xml

Open settings_secure.xml and delete "android_id" line

Push settings_secure.xml back to device: adb push settings_secure.xml /data/system/users/0/

Capture system image, flash onto other devices (either via TWRP backup or pushing system images via ADB)

Boot device, log into client Google account, done

Now this process used to work great on LineageOS 14.1 (Android 7.1), but now I get the following issues:

When adding a Google Account, it does not appear in Android device manager, but it appears in the list of devices in the Google Play Store? If I remove the account and then add it again it appears, but the issues below still occur.

Google's messaging / push system is broken. If I send a Hangouts message to my Google account, it won't appear until I open the app.

Any pre-installed apps won't appear in the "installed" list of apps in the play store, and therefore not update automatically until the user manually searches for the app in the Play Store and hits "update" (ugh).

I need to be deploying around 100 units over the next couple of months or so I need something that is scalable. I might be going around this the wrong way completely. I am not a ROM developer or programmer, just found something that has worked well in the past, so if I need to develop a ROM from scratch based on LineageOS I'll probably need to hire someone to do this for me as this is a bit beyond my current capabilities and time constraints. Let me know your thoughts! Thanks.
[Android Software/Hacking General [Developers Only]] Rayman96:
Android ID is same for many devices if you clone. That is really bad and can cause issues.
[Android Software/Hacking General [Developers Only]] stephendt0:
I am deleting the Android ID from settings_secure.xml though. Unless it is somewhere else as well?
[Android Software/Hacking General [Developers Only]] stephendt0:
I'm still struggling with this problem. Is there anything else I can try? I googled this problem and the first result is this thread :/
[Android Software/Hacking General [Developers Only]] rainman74:
adb shell settings delete secure android_id
adb shell settings delete secure advertising_id
adb shell settings delete secure bluetooth_address
adb shell settings put secure bluetooth_name 'YOURNAME'
adb shell settings put global device_name 'YOURNAME'
adb shell settings put global wifi_p2p_device_name 'YOURNAME'

The two IDs are then randomly regenerated. YOURNAME is any name of your choice.
[Android Software/Hacking General [Developers Only]] stephendt0:
Thanks for that. I believe I actually found their respective strings in settings_secure.xml:

<setting id="59" name="config_update_certificate"

<setting id="43" name="bluetooth_address"

And of course the Android ID. Once I deleted these, they auto-generated on the next boot, so I do this using ADB in TWRP.

I tried this and so far I'm not having any problems! Will report back if I experience any issues.
[Android Software/Hacking General [Developers Only]] stephendt0:
Another update - turn out that this is NOT enough. You will also want to clear data for the following apps (ideally just before shutting down the system and clearing android, bluetooth and config_update_certificate) to ensure that push notifications continue to work:

Com.google.android.gms.setup

Google App (not 100% sure if this is required, but I do it anyway)

Google Play Services

Google Play Store

Google Services framework

Reboot, clear your IDs, and then take your image. It should be OK after that, I think. I generally like to setup Hangouts on the device and then reboot, and let it sit for 5 minutes so its fully dozed before I send a test message.

Edit: STILL not working even after all this. Anyone else able to offer an explanation as to why push notifications is such an issue? This is becoming really difficult :(
[Android Software/Hacking General [Developers Only]] rainman74:
ok, if you want to reset everything in a clone, proceed as follows:

adb shell su -c mount -o remount,rw /system

adb shell su -c rm /data/system/users/0/accounts.db
adb shell su -c rm /data/system/users/0/accounts.db-journal
adb shell su -c rm /data/system/users/0/photo.png
adb shell su -c rm /data/system/sync/accounts.xml
adb shell su -c rm /data/system/sync/pending.xml
adb shell su -c rm /data/system/sync/stats.bin
adb shell su -c rm /data/system/sync/status.bin

adb shell su -c pm clear com.android.packageinstaller
adb shell su -c pm clear com.android.providers.downloads
adb shell su -c pm clear com.android.vending
adb shell su -c pm clear com.google.android.backuptransport
adb shell su -c pm clear com.google.android.gms
adb shell su -c pm clear com.google.android.gsf

adb shell su -c mount -o remount,ro /system

Please also follow my instructions above for resetting the IDs before rebooting.

Google then recognizes a new device! Have fun :fingers-crossed:
[Android Software/Hacking General [Developers Only]] stephendt0:
OMG, I think that worked, thank you! I spent 5 hrs and stayed up to 3am trying to work this out with no luck, and this did the trick. To make things easier however, I morphed these commands into a dirty "one-liner" that saves entering each command.

adb shell settings delete secure android_id && adb shell settings delete secure advertising_id && adb shell settings delete secure bluetooth_address && adb shell settings put secure bluetooth_name 'Redmi Note 4' && adb shell settings put global device_name 'Redmi Note 4' && adb shell settings put global wifi_p2p_device_name 'Redmi Note 4' && adb shell su -c mount -o remount,rw /system && adb shell su -c rm /data/system/users/0/accounts.db && adb shell su -c rm /data/system/users/0/accounts.db-journal && adb shell su -c rm /data/system/users/0/photo.png && adb shell su -c rm /data/system/sync/accounts.xml && adb shell su -c rm /data/system/sync/pending.xml && adb shell su -c rm /data/system/sync/stats.bin && adb shell su -c rm /data/system/sync/status.bin && adb shell su -c pm clear com.android.packageinstaller && adb shell su -c pm clear com.android.providers.downloads && adb shell su -c pm clear com.android.vending && adb shell su -c pm clear com.google.android.backuptransport && adb shell su -c pm clear com.google.android.gms && adb shell su -c pm clear com.google.android.gsf && adb shell su -c mount -o remount,ro /system

I'm sure there is a more efficient way of stacking commands, but this worked. Replace "Redmi Note 4" with your actual device and reboot. I cleared data for any messaging apps and removed my Google account before I began, however.
[Android Software/Hacking General [Developers Only]] rainman74:
Perfect! You don't need to remove your Google account as the commands do this anyway ;)
[Android Software/Hacking General [Developers Only]] stephendt0:
Quick update.

After a bit more testing, turns out that there were still a few things that needed clearing, particularly on different versions of Android (7.1). Also, I've noticed that a GSF ID can be generated before you get a chance to capture an image if you leave Wi-Fi enabled, so I've included that in the script. I've ended up with a .BAT file with the following:

echo on
adb shell settings delete secure android_id
adb shell settings delete secure advertising_id
adb shell settings delete secure bluetooth_address
adb shell su -c mount -o remount,rw /system
adb shell su -c svc wifi disable
adb shell su -c rm /data/system/users/0/accounts.db
adb shell su -c rm /data/system/users/0/accounts.db-journal
adb shell su -c rm /data/system/users/0/photo.png
adb shell su -c rm /data/system/users/0/settings_ssaid.xml
adb shell su -c rm /data/system/sync/accounts.xml
adb shell su -c rm /data/system/sync/pending.xml
adb shell su -c rm /data/system/sync/stats.bin
adb shell su -c rm /data/system/sync/status.bin
adb shell su -c pm clear com.google.android.ext.services
adb shell su -c pm clear com.google.android.ext.shared
adb shell su -c pm clear com.google.android.gsf.login
adb shell su -c pm clear com.google.android.onetimeinitializer
adb shell su -c pm clear com.android.packageinstaller
adb shell su -c pm clear com.android.providers.downloads
adb shell su -c pm clear com.android.vending
adb shell su -c pm clear com.google.android.backuptransport
adb shell su -c pm clear com.google.android.gms
adb shell su -c pm clear com.google.android.instantapps.supervisor
adb shell su -c pm clear com.google.android.gsf
adb shell su -c mount -o remount,ro /system

I have found that this works consistently across both LineageOS 14.1 and LineageOS 15.1 devices.
[Android Software/Hacking General [Developers Only]] double-gee:
YES, this did it. I cloned a kindle fire hdx using TWRP backup&restore and had to perform the action mentioned above in order to use both devices independetly.

ATTENTION!

Remember to change the values listed in stephendt0's example that were not part of the original code from rainman74:

- device_name: Equals the device type. E.g. adb shell settings put global device_name 'KFHDX'

- bluetooth_name: Hostname of the device seen in bluetooth.

- wifi_p2p_device_name: Hostname used for a p2p wifi network aka "ad hoc network". Not supported on all devices.
[Upgrading, Modifying and Unlocking] a.jimmy23:
can i change the software samsung galaxy note fe sm-n935l to sm-n935f (xid)? for the state of Indonesia.

if so, where can I download the firmware?

my galaxy is ROOTED by magisk.

thanks
[Android Q&A, Help & Troubleshooting] BooBaa#:
Hi,

i own Huawei Mediapad T2 7.0 BGO-DL09. run with stockrom, unroot, and bootloader already unlock.

i had situation that i can't figure it out (sorry if i'm newbie). i had wrong file when i flashed my boot.img via adb fastboot. and now my tablet bootloop, and also can't enter into fastboot mode.

[IMG="it show stucks like this picture"]https://drive.google.com/file/d/1ra28fxnYGLxqfvvh-T_Vz1xAaBOm_OEw/view?usp=sharing[/IMG]

it's useless to try flashing via dload mode, and also i can't enter into erecovery.

how can i fix it?

please help me out of this situation.
[Thunderbolt Q&A, Help & Troubleshooting] dillonorden:
I know this device is severely outdated but im enjoying tinkering with it. That being said why cant i stay signed into my google acct or download any of the roms from xda?
[Android Q&A, Help & Troubleshooting] RidzVarn:
Hi xda Members,

I got a Vivo Y53 here which is belong to my friend and its already bricked. It just bootlooping at bootlogo but I still can enter fasboot & recovery mode by manual pressing buttons.

The bootloader system is lock and Usb debug is also not turned ON.

Downloaded & trying to flash its stock ROMs using QFIL but it always failed because it can't find "system_1.img" in directory, it only have "system.img". Just a single system img.

I Open that raw XML using Notepadd++ to check and found the problem but I dont know how to modify it or maybe I don't have to...:confused:

Here I attach the XML file at bottom of this thread.

I would like to ask if anyone can help me to fix this XML for only flashing

system.img

and not system_1.img until system_30.img. Same for data/cache imges.

Appreciate any help!:rolleyes:

Many thanks!:svetius:

*Sorry for my broken english..
[Android Q&A, Help & Troubleshooting] HippoInWindow:
Choose factory reset from the recovery menu.
[Android Q&A, Help & Troubleshooting] RidzVarn:
Hi,

It doesn't work.

Formatting process done successfully. But when I reboot. I just entering system repair menu.
[Android Q&A, Help & Troubleshooting] HippoInWindow:
Can you send a screenshot?
[Android Q&A, Help & Troubleshooting] RidzVarn:
Hi guys..

Sorry for late updates.

Gladfull I manage to get this problem solved finally.

Attempted to edit that XML file by deleting unnecessary rows, change system_<numbers>.img to only system.img and and same for data.img and cache.img.

Change the start sectors for those imgs to be flashed by refer to its last imgs ending sectors. I know maybe the method I used is sound like crazy. Hahaha.. but it works man! :P

After all process done. Unplug USB and press power button. I dont know why. But it takes almost 1minute to powering up. It entered system repair menu again and I choose to Power Off. And reboot into recovery > wipe data and caches. And reboot....

VIOLAA! It works! PRAISE to God :)

Thanks to members who tried to help. I appreciate your kind efforts. If anyone need more infos or have any questions regarding my revive methods. Please ask. I'm more than happy to help.

Best regards. :)
[Android Q&A, Help & Troubleshooting] miyank:
can you send the file you have edited

can you send the file you have edited ?
[Android Q&A, Help & Troubleshooting] RidzVarn:
OMG.. I missed this thread. I will try to find that edited XML file in my PC. Hope its still there :(

will post it as soon as possible.. my apologize:eek:
[Android Q&A, Help & Troubleshooting] 5261979:
VIVO Y53 Factory Firmware [SD] - PD1628F_EX_A_3.0.18 Only TH[androidhost.ru].zip

http://androidhost.ru/7j9

Dated Uploaded: 05/10/2018 Filesize: 1.81 GB

VIVO Y53 Factory Firmware [9008] - PD1628F_EX_A_3.0.18_vivo_qcom_LA.UM.5.3-02910-89xx.0_msm8937_split Only TH[androidhost.ru].tar.gz

http://androidhost.ru/7j8

Dated Uploaded: 05/10/2018 Filesize: 1.98 GB

VIVO Y53 Factory Firmware [9008] - PD1628F_EX_A_3.0.18_vivo_qcom_LA.UM.5.3-02910-89xx.0_msm8937 Only TH[androidhost.ru].tar.gz

http://androidhost.ru/7j7

Dated Uploaded: 05/10/2018 Filesize: 1.98 GB
[Android Q&A, Help & Troubleshooting] Aantuerpia:
help me i don't quite get what you guys are talking about,

i can't enter recovery mode since it shuts down on its own

i can enter fastboot mode once i let go of the volume- key it resets again

edit: suddenly i was able to enter some mode and was able to reboot it, i dont even lost any files in the process, i think it was because i charged it, can anybody confirm this?

edit 2: it entered bootloop again, is there a way to stop this?
[Android Q&A, Help & Troubleshooting] RidzVarn:
Hi,

Can it boot into System Repair menu by any chance?
[Android Q&A, Help & Troubleshooting] Leosacdalan28:
Sir can i see the xml file? PLEASE:crying:
[Android Q&A, Help & Troubleshooting] BangNapi:
https://drive.google.com/uc?id=12EgsXRQZLrt3k2fQtwhSeTItHmMVO-QF&export=download

try this. its work for me
[Android Q&A, Help & Troubleshooting] -LYNN-:
How did you manage to do that sir? i've been facing that kind of problem now with my vivo y53. i tried to hard reset but still stock on system repair mode everytime i open my unit. can you please tell me how did you fix this problem? thanks a lot
[Android Q&A, Help & Troubleshooting] candy1005:
Good day sir can you please send me the exact format of the XML file,thank you.
[Android Q&A, Help & Troubleshooting] -LYNN-:
GOOD DAY SIR, can you please give me the exact file you edited? thank you
[Android Q&A, Help & Troubleshooting] RidzVarn:
Hi Lynn

My apologize.. I dont have that edited XML file anymore.
[Android Q&A, Help & Troubleshooting] Deep Brar:
Guys, I am trying to fix the same phone, I am stuck in edl mode. All the partitions have been deleted from the phone and it just stays in edl mode. I tried flashing through qfil on windows 11 but got issues like

```download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified```

Please anyone help...
[P8lite Q&A, Help & Troubleshooting] iaio72:
I need a little help, I read many posts, but I still have not found the correct one, my p8 lite 2017 with twrp installed, based on emui 5.0.1 nougat, I would like to install a base rom oreo emui 8, but first I should install a roman stock emui 8 android oreo, but I can not figure out where I can find a working guide, can someone help me?

thank you so much

my p8 lite 2017 PRA-LX1 single sim
[P8lite Q&A, Help & Troubleshooting] green2005:
Hi, i use this very easy, i upgrade from stock emui 5 to emui 8

https://xdaforums.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
[P8lite Q&A, Help & Troubleshooting] iaio72:
thanks for help.... but......

R.I.P.

Amen

this procedure doesnt work for me,

im tryed many time but always error, and dont have the oreo installed, then i change the oem info by elite twrp, and now my p8 completely bricked, not enter in fastboot mode, not enter in recovery mod, not in system only in erecovery but procedure via wifi dont start, "package error", via folder dload/update.app not work.....

any suggestion for unbrick?

thanks so much

all this just because I wanted to put a version of the emui no brand, before I had emui 5.x, brand h3g ....
[P8lite Q&A, Help & Troubleshooting] iaio72:
SOLVED, changed oem info eu
[MDA II, XDA II, 2060 ROM Development] funny keyboard:
I tried to unlock my Himalaya with xdadev_all_unlock-v1.6_138, but when I put in 00000000 for the sim lock answer, it tells me that code is wrong. My telephone is now constantly on this screen, cannot gain access to anything else, so does this mean my Himalaya is now as dead as a dodo?

Have tried to use xda2unlock, but this just tells me the sim is already unlocked.

If it is ruined, it is ruined I will have to live with that, it would just be nice to know their was no avenues to go down.
[MDA II, XDA II, 2060 ROM Development] elmoxdaII:
Have you tried 7 zeroes, or 8 zeroes, or 9 zeroes instead? :)
[MDA II, XDA II, 2060 ROM Development] funny keyboard:
yup! unfortunately no joy.
[MDA II, XDA II, 2060 ROM Development] naren3108:
just let me know it all things have failed. i have a friend in o2 service centre and he can do everything ok. let me know if its ok with u
[MDA II, XDA II, 2060 ROM Development] funny keyboard:
yes everything has failed. if your friend in the o2 service centre can suggest anything I would be glad to know.
[MDA II, XDA II, 2060 ROM Development] naren3108:
see ur set can be revived bu flashing the rom directly into the device by opening it and getting it connected with 3 special cables to the pc and with a appropriate software the rom can be flashed and ur device will be working again. for this u have only 2 options either u send ur phone to me in india or i can send u the instructions,cables and the software and u can try doing it there. just let me know what suits u...ok?
[Android Q&A, Help & Troubleshooting] 870tally:
So I bought a S8+ plus off of craigslist, everything worked good he dhowed me the phone booted up, pressed the butttons to restore it and we mde the transaction then turns out the email was still on the phone, I contacted him for it but never got a reply. Can anybody help me out, I've been searching all over the interenet and tried some different things with Odin but nothing works.

On the download mode screen it shows as this :

*Pretty sure the model or whatever is 955U or could I be mistaken?*

Carrier: TMB

RPMB Fuse Blown

Rpmb Provisioned

Current binary: Samsung OFFICIAL

System Status : Official

FRP Lock: ON

Warranty void: 0x0

QUALLCOM SECUREBOOT: ENABLE

RP SWREV: B3(1,1,1,1,1) K2 S3

SECURE DOWNLOAD: ENABLE

DID: 205EE96BCD40

SW REV CHECK FAIL: [abl] Fused 3> Binary 2

PLEASE HELPPP
[Android Q&A, Help & Troubleshooting] jryanta:
Hi We can team up. I have a g955u and also have frp lock

Ive tried flashing combo and turning off OEM Lock and then reflashing BL AP and Home CSC but then its still has the google verification making the phone unusable. Im pretty stuck atm any help would be greatly appreciated.
[Android Software/Hacking General [Developers Only]] m.reignier:
Hi all,

I try to enable ov9734 sensor to board msm8953 in 64bits (Open-Q 626 by Intrinsyc)

- Add ov9734.c in kernel/msm-3.xx/drivers/media/i2c/soc_camera/

- Modify Kconfig and add

config SOC_CAMERA_OV9734

tristate "ov9734 camera support"

depends on SOC_CAMERA && I2C

help

This is a ov9734 camera driver

- Modify Makefile and add

obj-$(CONFIG_VIDEO_OV3734) += ov3734.o

- Modify msm8953.dtsi

i2c_5: i2c@7af5000 {

compatible = "qcom,i2c-msm-v2";

#address-cells = <1>;

#size-cells = <0>;

reg-names = "qup_phys_addr";

reg = <0x7af5000 0x600>;

interrupt-names = "qup_irq";

interrupts = <0 299 0>;

qcom,clk-freq-out = <400000>;

qcom,clk-freq-in = <19200000>;

clock-names = "iface_clk", "core_clk";

clocks = <&clock_gcc clk_gcc_blsp2_ahb_clk>,

<&clock_gcc clk_gcc_blsp2_qup1_i2c_apps_clk>;

pinctrl-names = "i2c_active", "i2c_sleep";

pinctrl-0 = <&i2c_5_active>;

pinctrl-1 = <&i2c_5_sleep>;

qcom,noise-rjct-scl = <0>;

qcom,noise-rjct-sda = <0>;

qcom,master-id = <84>;

dmas = <&dma_blsp2 4 64 0x20000020 0x20>,

<&dma_blsp2 5 32 0x20000020 0x20>;

dma-names = "tx", "rx";

ov9734@36 {

compatible = "ov9734";

reg = <0x36>;

mclk_khz = "24000";

num_lanes = "1";

/* V4L2 device node location */

devnode = "video0";

/* Physical dimensions of sensor */

physical_w = "3.674";

physical_h = "2.738";

/* Define any required hw resources needed by driver */

/* ie. clocks, io pins, power sources */

avdd-reg = "vana";

dvdd-reg = "vdig";

iovdd-reg = "vif";

/* Sensor output flip settings */

vertical-flip = "true";

mode0 { // OV9734_MODE_1280X720

mclk_khz = "24000";

num_lanes = "1";

tegra_sinterface = "serial_c";

discontinuous_clk = "no";

dpcm_enable = "false";

cil_settletime = "0";

active_w = "1280";

active_h = "720";

pixel_t = "bayer_bggr10";

readout_orientation = "0";

line_length = "1478";

inherent_gain = "1";

mclk_multiplier = "6.67";

pix_clk_hz = "160000000";

min_gain_val = "1.0";

max_gain_val = "16";

min_hdr_ratio = "1";

max_hdr_ratio = "64";

min_framerate = "1.816577";

max_framerate = "30";

min_exp_time = "34";

max_exp_time = "550385";

};

};

};

- Modify msmcortex_defconfig and add

CONFIG_I2C_DEBUG_CORE=y

CONFIG_I2C_DEBUG_ALGO=y

CONFIG_I2C_DEBUG_BUS=y

CONFIG_VIDEO_ADV_DEBUG=y

CONFIG_SOC_CAMERA_OV9734=y

Driver are call, but I have error message during probe function:

[ 6.453473] ov9734 5-0036: Missing platform_data for driver

[ 6.453488] ov9734: probe of 5-0036 failed with error -22

Somebody can help me ?

Michaël
[Android Software/Hacking General [Developers Only]] blystad:
Heya,

That's not an officially supported Intrinsyc camera, right? I have the OpenQ 820 and that comes with a Sony IMX214 camera. Have you created your own adapter board, or what?

Even if you can get it connected/attached you'll still need to make modifications to proprietary Qualcomm files (in vendor/qcom/proprietary) to add support for this camera. These files Intrinsycs BSP doesn't give you access to. You also need the Qualcomm Chromatix tools to generate the driver, and calibrate the sensor.
[Android Software/Hacking General [Developers Only]] m.reignier:
Yes is not an officially supported Intrinsyc camera. You have all good.

How add my camera ? Impossible ?
[Android Software/Hacking General [Developers Only]] blystad:
Unless you have contacts in Qualcomm then yeah, it's pretty much impossible. See: https://faq.intrinsyc.com/t/can-i-develop-a-camera-sensor-driver-with-your-dev-kits/29

You need Qualcomm tools, internal documentation, access to proprietary source code, etc. Plus, a ton of equipment to verify the camera behaviour.
[Android Software/Hacking General [Developers Only]] parth.darji:
Hey, did you ever solve this? We are in the exact same situation and don't have the resources to go through Intrinsyc to build new drivers.