HideMyAndroid Headless API

Requirements

Headless API aapko HideMyAndroid ko poori tarah ADB ya kisi bhi automation tool se control karne deta hai — app UI ki zaroorat ke bina. Ye ek Premium feature hai.

• Premium account — Headless API sirf Premium users ke liye hai.
• App version 1.2.8 ya usse naya. Uske baad jo bhi juda hai woh extra field ya method hai, isliye 1.2.8 abhi bhi chalta hai — lekin naye hisson ke liye naya build chahiye: hook_spoof_uptime ke liye 1.3.4+, geo aur profile.duplicate ke liye 1.4.5+, aur poore backup / restore group ke liye 1.5.3+. Purana build anjaan field ko ignore kar deta hai aur phir bhi ok=true hi bhejta hai — lekin anjaan method zyada shor karta hai: 1.5.3 se purane build par backup / restore group call karne se BAD_REQUEST milta hai, jiske error_message mein hota hai “Unknown method: …”. Agar koi setting bekaar lage to status se chal rahi version check karein — packaged release usse imaandaari se report karta hai, lekin version bump se pehle khud compile kiya gaya build feature rakhte hue bhi purana number dikha sakta hai.
• Root + LSPosed — wahi setup jo HideMyAndroid ko pehle se chahiye hota hai. Installation guide dekhein.
• ADB aapke device se connected ho (adb devices usse list karta hai).
• Device par internet — sirf tab zaroori hai jab aap proxy enable karein (usse live test kiya jaata hai).

⚠️ VPN permission sirf un profiles ke liye chahiye jo proxy use karte hain. Headless system ka VPN consent dialog nahi khol sakta, isliye ise ek baar app ki Headless API screen se de dein. Bina iske, proxy waale profile ko activate karne par profile to activate ho jaata hai, lekin proxy connect nahi hota aur call INTERNAL lautati hai jisme yahi likha hota hai.

Authentication

App mein Settings → Developer → Headless API kholein aur Enable on karein. Ek key apne aap generate ho jaati hai — Copy par tap karein. Har request is key ko token parameter ke roop mein bhejti hai.

Isse private rakhein — jiske paas key aur ADB access ho, woh aapke profiles control kar sakta hai. Regenerate ek nayi key banata hai (purani band ho jaati hai); log out karne par ye mit jaati hai.

Is poore reference mein, <your_access_token> ki jagah apni key aur <profile_id> ki jagah woh id daalein jo profile.create return karta hai.

Requests banana

Do transports, ye is hisaab se chunne jaate hain ki kisi value mein colon : hai ya nahi

content call har --extra ko colon par split karta hai, isliye woh JSON nahi le ja sakta — isi wajah se JSON values broadcast ke through bheji jaati hain.

Sirf teen methods ka broadcast roop hai: HEADLESS_UPDATE (profile.update), HEADLESS_SET_ACTIVE aur HEADLESS_DEACTIVATE. Baaki pandrah — status, saare read operations, profile.create, profile.duplicate, profile.delete, target-app calls aur poora backup / restore group — sirf content call se chalte hain. HEADLESS_CREATE — ya HEADLESS_BACKUP — naam ki koi cheez hai hi nahi, dhoondhne ki zaroorat nahi.

Broadcast sirf JSON ke liye nahi hai. HEADLESS_UPDATE theek saat extras aage bhejta hai — name, hookFlags, proxy, geo, deviceMock, sim, gmails — isliye name aur gmails dono transport se ja sakte hain. Upar ki table ye batati hai ki kaunsa aasaan hai, na ki kaunsa mumkin hai. In saat ke alawa jis bhi extra ka naam ho, use bina error diye hata diya jaata hai.

Responses. Success ka matlab hai ok=true (content call) ya result=0 (broadcast); failure par error_code aur error_message add ho jaate hain. Error codes dekhein. Har method token bhi leta hai. Niche kisi bhi operation par click karke uske parameters, request, aur response expand karein.

Status

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method status --extra token:s:<your_access_token>

Bundle[{data={"premium":true,"featureEnabled":true,"freshnessOk":true,"activeProfileId":"a1b2c3d4-...","version":"1.5.3"}, ok=true}]

💡 status hi ek aisa method hai jo license expire ya stale hone par bhi jawaab deta hai — baaki har call sirf LICENSE_EXPIRED ya LICENSE_STALE lautati hai. Jab koi request reject ho, in dono ko alag pehchaanne ka tareeka yahi hai: premium dekhein ki Premium sach mein khatam hua hai kya, aur freshnessOk dekhein ki bas app ek baar kholna hai kya. status par bhi FEATURE_DISABLED aur UNAUTHORIZED lagte hain, isliye band API ya galat token yahan bhi waise hi dikhte hain jaise kahin aur.

Profiles

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.list --extra token:s:<your_access_token>

Bundle[{data=[{"id":"a1b2...","name":"Demo","isActive":true,"createdAt":1717000000000,"updatedAt":1717000500000}], ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.get --extra token:s:<your_access_token> --extra id:s:<profile_id>

Bundle[{data={"id":"a1b2...","name":"Demo","isActive":false,"hookFlags":{"hook_wifi":true,...},"proxy":{"enabled":false,...},"geo":{"source":"PROXY",...},"deviceMock":{"enabled":false,...},"sim":{"enabled":false,"simCards":[]},"gmails":[],"targetApps":["com.whatsapp"]}, ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.create --extra token:s:<your_access_token> --extra name:s:Demo

Bundle[{data={"id":"a1b2c3d4-..."}, ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.duplicate --extra token:s:<your_access_token> --extra id:s:<profile_id>

Bundle[{data={"id":"e5f6a7b8-...","name":"Brave Falcon 42"}, ok=true}]

Copy mein kya-kya jaata hai

Profile ko bilkul waise hi clone karta hai jaise app ka Duplicate menu — app 1.4.5+ chahiye. Settings saath chali jaati hain, lekin har pehchaan wali value dobara generate hoti hai, taaki copy ka apna fingerprint ho, na ki original ka hamshakl. Iska broadcast roop nahi hai: fire-and-forget broadcast aapko nayi id laut kar de hi nahi sakta, aur yahi to is call ka poora maqsad hai.

Apna naam chahiye to pehle duplicate karein, phir doosri call mein rename karein:

# 1. duplicate — the new id and its generated name come back together
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.duplicate --extra token:s:<your_access_token> --extra id:s:<source_profile_id>

# 2. rename the copy — profile.duplicate never takes a name of your own
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.update --extra token:s:<your_access_token> --extra id:s:<new_profile_id> --extra name:s:"My Profile"

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.update --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra name:s:"My Profile"

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e hookFlags '{"hook_wifi":false,"hook_nearby_bluetooth":false}'

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.delete --extra token:s:<your_access_token> --extra id:s:<profile_id>

Bundle[{data={}, ok=true}]

Activation

Profile tabhi spoof karta hai jab woh active ho, aur ek samay par sirf ek hi profile active rehta hai. profile.setActive active profile ko badal deta hai — pehle jo active tha use apne aap deactivate kar diya jaata hai, isliye pehle profile.deactivate bulaane ki zaroorat nahi.

⚠️ Activate karne se target apps ka data mit jaata hai. profile.setActive unhe sirf restart nahi karta: woh har target app ko force-stop karta hai aur uska data wipe kar deta hai, taaki woh saaf-suthra chalu ho aur nayi identity sach mein le sake. Ye jaan-boojh kar aisa hai — lekin iska matlab hai ki un apps ke andar ka sab kuch chala jaata hai, logged-in sessions samet, App ke andar yahi kaam pehle confirmation maangta hai aur Backup feature ki taraf ishaara karta hai; headless call koi dialog nahi dikhata aur seedha chal jaata hai, isliye yahi ek chetavani aapko milti hai. Headless mein safety net hai switch karne se pehle backup.start (1.5.3+) chalana. Aur 1.5.3 se, jab tak koi backup / restore job slot pakde hue hai, profile.setActive aur profile.deactivate BUSY lautate hain — us job ke liye bhi jo cancel ho chuki hai; tab tak retry karein jab tak BUSY aana band na ho jaaye.

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.setActive --extra token:s:<your_access_token> --extra id:s:<profile_id>

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_SET_ACTIVE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id>

Bundle[{data={"id":"a1b2...","isActive":true}, ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.deactivate --extra token:s:<your_access_token>

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_DEACTIVATE -p com.wowsoftware.hidemyandroid -e token <your_access_token>

Bundle[{data={}, ok=true}]

content call hi behtar tareeka hai: ye synchronous hai aur laut kar aaya Bundle print karta hai. HEADLESS_SET_ACTIVE aur HEADLESS_DEACTIVATE broadcasts wahi kaam Tasker jaise automation tools ke liye karte hain. Ye ordered broadcast ki tarah jawaab dete hain, jo hamesha data wapas laata hai: safal hone par am broadcast result=0 ke saath result JSON data="…" mein print karta hai, aur fail hone par result=1 ke saath data="{"error_code":…,"error_message":…}". Yaani ye poori tarah fire-and-forget nahi hain — data= parse kar lein to wahi jawaab milta hai jo content call deta. HEADLESS_SET_ACTIVE profile id ko -e id ya -e profile_id dono roop mein leta hai; HEADLESS_DEACTIVATE ko id ki zaroorat hi nahi. Hamesha ki tarah -p com.wowsoftware.hidemyandroid zaroor lagayein.

Target apps

Target apps woh apps hain jinhe ek profile spoof karta hai.

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.getApps --extra token:s:<your_access_token> --extra id:s:<profile_id>

Bundle[{data=[{"packageName":"com.whatsapp"}], ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.addApp --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra packageName:s:com.whatsapp

Bundle[{data=[{"packageName":"com.whatsapp"}], ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.removeApp --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra packageName:s:com.whatsapp

Bundle[{data=[], ok=true}]

Backup & restore

1.5.3 mein naya, ye group profile ke app data ko device par archives mein copy karta hai aur baad mein wapas daal deta hai — wahi kaam jo app mein Manage Backups karta hai, bas UI ke bina. Sabhi chhe methods sirf content call se chalte hain (broadcast roop nahi hai), aur dono *.start calls asynchronous hain: ye aapko turant ek jobId thama deti hain aur background mein kaam karti rehti hain — saath-saath dekhne ke liye backup.job poll karein. Ek hi app ka backup lene mein bhi minutes lag sakte hain.

⚠️ Ek waqt par sirf ek job. Jab ek job chal rahi ho, tab doosra *.start BUSY lautata hai, jisme chal rahi jobId error_message mein hoti hai. Dono *.start calls ke liye target profile ka active hona bhi zaroori hai — warna REQUIRES_ACTIVE_PROFILE, aur koi override flag nahi hai. Baaki chaar methods kisi bhi profile par kaam karte hain. Aur jaise headless API mein har jagah hota hai, koi confirmation nahi maanga jaata — har call seedha chal jaati hai.

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.start --extra token:s:<your_access_token> --extra id:s:<profile_id>

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.start --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra packages:s:com.twitter.android,com.facebook.katana

Bundle[{data={"jobId":"f0e1d2c3-...","type":"backup","total":2,"packages":["com.twitter.android","com.facebook.katana"],"foregroundHeld":true}, ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method restore.start --extra token:s:<your_access_token> --extra id:s:<profile_id>

Bundle[{data={"jobId":"09a8b7c6-...","type":"restore","total":1,"packages":["com.twitter.android"],"foregroundHeld":true}, ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.job --extra token:s:<your_access_token> --extra jobId:s:<job_id>

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.job --extra token:s:<your_access_token>

# while it runs
Bundle[{data={"jobId":"f0e1d2c3-...","type":"backup","profileId":"a1b2...","state":"RUNNING","total":2,"done":0,"ok":0,"failed":0,"currentPackage":"com.twitter.android","currentComponent":"Internal Data","progress":0.31,"results":[],"error":null,"foregroundHeld":true,"startedAt":1712345678901,"finishedAt":null}, ok=true}]

# when it finishes — note: DONE even though one app failed
Bundle[{data={"jobId":"f0e1d2c3-...","type":"backup","profileId":"a1b2...","state":"DONE","total":2,"done":2,"ok":1,"failed":1,"currentPackage":null,"currentComponent":null,"progress":1.0,"results":[{"packageName":"com.twitter.android","ok":true,"error":null},{"packageName":"com.facebook.katana","ok":false,"error":"tar exited 2"}],"error":null,"foregroundHeld":true,"startedAt":1712345678901,"finishedAt":1712345699999}, ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.cancel --extra token:s:<your_access_token> --extra jobId:s:<job_id>

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.list --extra token:s:<your_access_token> --extra id:s:<profile_id>

Bundle[{data=[{"packageName":"com.twitter.android","appName":"X","timestamp":1712345678901,"totalSize":12345678,"components":["INTERNAL_DATA","EXTERNAL_DATA","OBB"]}], ok=true}]

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method backup.delete --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra packageName:s:com.twitter.android

Bundle[{data={}, ok=true}]

Jobs kaise behave karti hain

• DONE ka matlab ye nahi ki har app safal hui. Iska matlab sirf itna hai ki job aakhir tak chali. App fail ho sakti hai aur job phir bhi DONE par khatam hoti hai — failed aur results[] hamesha padhein.
• Activation ab jobs ka intezaar karta hai. Jab tak koi job slot pakde hue hai, profile.setActive, profile.deactivate aur profile.delete BUSY lautate hain — us job ke liye bhi jise aap cancel kar chuke hain, kyunki neeche chal raha root tar file ke beech mein roka nahi ja sakta, aur snapshot ka koi bhi field slot report nahi karta. Jo job apne aap DONE ya FAILED par khatam hoti hai woh slot lagbhag turant chhod deti hai; cancel ke baad CANCELLED ko “slot khaali” na samjhein — bas call ko tab tak retry karein jab tak BUSY aana band na ho jaaye.
• foregroundHeld ek observation hai, promise nahi. Ye batata hai ki koi foreground service job ko OS ke haathon kill hone se bacha rahi hai ya nahi. API 36 par ye true maapa gaya hai, lekin true ka bhi matlab sirf itna hai ki service start accept hua — baad waala promotion step kuch devices par ab bhi chupchaap fail ho sakta hai. Lambi jobs ke liye ispar bharosa karne ke bajaye device ko jagaye rakhein.
• Backups kahan rehte hain. /sdcard/HideMyAndroid_Backups/<packageName>-<profileId>/ — har app ke liye har profile mein ek folder, jisme .tar.gz archives (data.tar.gz, data_ext.tar.gz, media.tar.gz, …) aur metadata.json hote hain, root tar se likhe gaye. {package}-{profileId} key hi woh wajah hai jisse restore sirf same-profile hota hai. Headless se banaye gaye backups app ki Manage Backups screen mein bhi dikhte hain.

Configuration

Ye woh values hain jo aap profile.update ke saath bhejte hain. Profile bante waqt ki defaults:

⚠️ enabled:false waala config store to hota hai par inert rehta hai — values save ho jaati hain taaki aap baad mein isse on kar sakein, lekin enabled:true hone tak kuch spoof nahi hota. geo iska apvaad hai: usme enabled switch hai hi nahi. hook_geo_* flags tab bhi lagte hain jab geo se koi kaam ki location nikal aaye — chahe source: CUSTOM se, ya aise proxy se jo enabled:true ho aur apna live test paas kar chuka ho.

hookFlags

Default: har flag ON hai sivaay hook_spoof_uptime ke, jo OFF hai. Ye "flag": true|false ka ek map hai. Update poore map ko replace kar deta hai, lekin sirf us map ko jo aapne sach mein bheja hai: jis update mein hookFlags extra hai hi nahi, woh kisi bhi flag ko nahi chhedta. Aur jo map aap bhejte hain, usme aap jo bhi flag chhod denge woh apni-apni default value par laut jaata hai, isliye baaki 20 wapas ON ho jaate hain jabki hook_spoof_uptime wapas OFF ho jaata hai, chahe aapne use on kiya ho. Kuch flags badalne aur baaki rakhne ke liye, pehle profile.get chalayein, poora map edit karein, phir sab wapas bhej dein.

proxy

Default: OFF. enabled:true ke saath, app sach mein iske through connect karta hai, iski location padhta hai, aur countryCode/lat/lon/timezone bhar deta hai. Live test mein ~8s tak lagte hain; jo proxy fail hota hai woh PROXY_INVALID return karta hai aur save nahi hota. Ye chaar fields output hain — inhe app khud likhta hai, isliye aap inme jo bhi bhejenge woh overwrite ho jaayega. Location khud set karni ho to geo ke source: CUSTOM ka istemaal karein; usme proxy ki zaroorat hi nahi. profile.get proxy ko in chaar fields samet wapas deta hai, lekin username ya password kabhi wapas nahi bhejta.

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e proxy '{"enabled":true,"host":"10.0.0.1","port":1080,"protocol":"SOCKS5"}'

geo

Default: {"source":"PROXY"}. App 1.4.5+ chahiye. Profile ki location yahin se aati hai, aur iske do source hain — source se ek chunein. PROXY woh location leta hai jo proxy ke live test ke dauran padhi gayi thi. CUSTOM aapko coordinates, timezone aur region khud set karne deta hai, bina kisi proxy ke — yaani profile ko Tokyo mein rakh sakte hain jabki traffic kahin bhi jaaye, ya kahin bhi na jaaye. Uske baad teen hook_geo_* flags har hisse ko alag-alag on karte hain: GPS, region + language, aur timezone.

⚠️ Field ke naam dhyaan se dekhein: geo mein ye latitude/longitude hain, jabki upar proxy mein chhote naam lat/lon hain. Ye do alag objects hain, alias nahi — geo payload mein chhote naam bas ignore ho jaate hain.

⚠️ source: CUSTOM poora hona chahiye: coordinates jo 0/0 na hon aur range mein hon, 2-letter countryCode, aur timezone. Inme se ek bhi chhoot gaya to call BAD_REQUEST deta hai — ye proxy par wapas nahi girta. App kabhi geocoding nahi karta aur inhe bharne ke liye kabhi online nahi jaata. Agar dono mein se koi bhi source kaam ka na nikle, to koi geo hook load hi nahi hota aur asli location dikh jaati hai.

🛑 timezone hi ek aisa field hai jiski asli jaanch nahi hoti. Sirf itna dekha jaata hai ki khaali na ho — IANA database se kabhi milaaya nahi jaata. Asia/Tokyoo jaisi typo accept ho jaati hai, ok=true deti hai, profile.get use jyon ka tyon wapas kar deta hai, aur phir device par chupchaap GMT ban jaati hai. Kahin bhi koi error report nahi hoti, isliye naam bilkul theek copy karein. Coordinates iska ulta hain — unki range sach mein check hoti hai aur galat value turant BAD_REQUEST ke saath fail hoti hai.

CUSTOM — location khud set karein, proxy ki zaroorat nahi

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e geo '{"source":"CUSTOM","latitude":35.6812,"longitude":139.7671,"countryCode":"JP","timezone":"Asia/Tokyo","language":"ja"}'

PROXY — location proxy se lein (default)

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e geo '{"source":"PROXY"}'

deviceMock

Default: OFF. Device ko ek alag model dikhaata hai. "enabled":true ke saath in fields mein se koi bhi set karein — sab optional strings hain (default khaali), har ek Android ke Build property se map hoti hai:

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e deviceMock '{"enabled":true,"manufacturer":"Samsung","brand":"samsung","model":"SM-S918B","device":"dm3q","product":"dm3qxxx","board":"kalama","hardware":"qcom","buildId":"UP1A.231005.007","buildIncremental":"S918BXXU3CWK9","buildType":"user","buildTags":"release-keys","buildFingerprint":"samsung/dm3qxxx/dm3q:14/UP1A.231005.007/S918BXXU3CWK9:user/release-keys","deviceName":"Galaxy S23 Ultra"}'

sim

Default: OFF. SIM/carrier spoof karta hai. "enabled":true set karein aur simCards mein do tak cards dein. List hamesha theek do par normalise hoti hai: teesra card chupchaap hata diya jaata hai — call phir bhi ok=true deta hai — aur ek hi card dene par doosra khaali card jod diya jaata hai, isiliye profile.get hamesha do cards wapas deta hai. Har card:

networkType ke aage-peeche ki space hata kar, bina case ka dhyaan rakhe match kiya jaata hai, aur har network generation ke ek se zyada roop chalte hain:

⚠️ Is table ke bahar ki koi bhi value us card ka network-type spoof chupchaap band kar deti hai — na error, na BAD_REQUEST: value bas save ho jaati hai aur kabhi istemaal nahi hoti. Dhyaan dein ki NR 5G mein space hai: NR5G pehchaana nahi jaata aur seedha isi khaamosh gadde mein gir jaata hai.

adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e sim '{"enabled":true,"simCards":[{"slotIndex":0,"carrierName":"AT&T","countryIso":"us","mcc":"310","mnc":"410","operatorCode":"310410","networkType":"LTE"},{"slotIndex":1,"carrierName":"T-Mobile","countryIso":"us","mcc":"310","mnc":"260","operatorCode":"310260","networkType":"NR 5G"}]}'

gmails

Default: khaali. Virtual Google accounts ki ek list — sirf @gmail.com addresses accept hote hain. Nayi list purani ko replace kar deti hai; [] usse clear kar deta hai. Andar koi : nahi hota, isliye content call chal jaata hai:

adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.update --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra 'gmails:s:["[email protected]","[email protected]"]'

Poora example

Shuru se ek poora setup:

# 1. create a profile — copy the returned id into <profile_id> below
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.create --extra token:s:<your_access_token> --extra name:s:Demo

# 2. add a target app
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.addApp --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra packageName:s:com.whatsapp
# 3. add the virtual Gmail accounts
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.update --extra token:s:<your_access_token> --extra id:s:<profile_id> --extra 'gmails:s:["[email protected]","[email protected]"]'

# 4. enable + set the device mock
adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e deviceMock '{"enabled":true,"manufacturer":"Samsung","brand":"samsung","model":"SM-S918B","device":"dm3q","product":"dm3qxxx","board":"kalama","hardware":"qcom","buildId":"UP1A.231005.007","buildIncremental":"S918BXXU3CWK9","buildType":"user","buildTags":"release-keys","buildFingerprint":"samsung/dm3qxxx/dm3q:14/UP1A.231005.007/S918BXXU3CWK9:user/release-keys","deviceName":"Galaxy S23 Ultra"}'

# 5. enable + set the SIM mock (two cards, full fields)
adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e sim '{"enabled":true,"simCards":[{"slotIndex":0,"carrierName":"AT&T","countryIso":"us","mcc":"310","mnc":"410","operatorCode":"310410","networkType":"LTE","phoneNumber":"+12025550123","iccid":"8901410123456789012","imsi":"310410123456789"},{"slotIndex":1,"carrierName":"T-Mobile","countryIso":"us","mcc":"310","mnc":"260","operatorCode":"310260","networkType":"NR 5G","phoneNumber":"+12025550456","iccid":"8901260987654321098","imsi":"310260987654321"}]}'

# 6. enable + set the proxy (tested live, ~8s)
adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e proxy '{"enabled":true,"host":"10.0.0.1","port":1080,"protocol":"SOCKS5"}'

# 7. pick where the location comes from — geo has two sources, choose ONE
#    A) from the proxy you just set. This is the default, so the line is optional:
adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e geo '{"source":"PROXY"}'
#    B) or set it yourself — this needs no proxy at all. Use B *instead of* A, not after it:
# adb shell am broadcast -a com.wowsoftware.hidemyandroid.HEADLESS_UPDATE -p com.wowsoftware.hidemyandroid -e token <your_access_token> -e id <profile_id> -e geo '{"source":"CUSTOM","latitude":35.6812,"longitude":139.7671,"countryCode":"JP","timezone":"Asia/Tokyo","language":"ja"}'
#    geo and proxy are independent: setting one never rewrites the other, and only
#    geo.source decides which one feeds the hooks. So CUSTOM together with a proxy in
#    a different country means your IP says one place while your GPS says another.

# 8. activate (restarts the target app and clears its data)
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.setActive --extra token:s:<your_access_token> --extra id:s:<profile_id>

# 9. verify
adb shell content call --uri content://com.wowsoftware.hidemyandroid.headless --method profile.get --extra token:s:<your_access_token> --extra id:s:<profile_id>

Error codes

Fail hone par aapko ok=false ke saath in error_code values mein se ek milta hai (broadcasts result=1 return karte hain):

Tips & troubleshooting

• Broadcast kuch nahi kar raha? Pakka karein ki aapne -p com.wowsoftware.hidemyandroid shaamil kiya hai — iske bina Android broadcasts block kar deta hai.
• Koi value : ke baad kat gayi? Us value mein colon hai, isliye content call ne usse truncate kar diya. Isse HEADLESS_UPDATE broadcast ke through bhejein.
• JSON broadcast apply nahi ho raha (aksar Windows par)? Desktop shell aur device shell, dono mein am broadcast JSON (hookFlags, proxy, deviceMock, sim) ke quotes aasaani se hat jaate hain, jisse am value ko galat padh leta hai (ho sakta hai woh dat=… data URI ban jaaye) aur kuch nahi badalta. Pakka tareeka ye hai ki JSON ko command line se bahar rakhein — poore workflow ko ek .sh file mein daalein (single quotes har JSON ko intact rakhte hain), phir usse device par push karke chalayein. Script device par chalti hai, isliye woh nayi profile id bhi capture karke dobara use kar sakti hai:
  bash Copy

  # setup.sh — the full example as one runnable script (runs on the device)
  URI=content://com.wowsoftware.hidemyandroid.headless
  PKG=com.wowsoftware.hidemyandroid
  K=<your_access_token>
  
  # 1. create a profile and capture its id
  ID=$(content call --uri $URI --method profile.create --extra token:s:$K --extra name:s:Demo | grep -o '"id":"[^"]*"' | head -n1 | sed 's/.*"id":"//;s/"//')
  echo "profile id: $ID"
  
  # 2. add a target app
  content call --uri $URI --method profile.addApp --extra token:s:$K --extra id:s:$ID --extra packageName:s:com.facebook.katana
  
  # 3. add the virtual Gmail accounts
  content call --uri $URI --method profile.update --extra token:s:$K --extra id:s:$ID --extra 'gmails:s:["[email protected]","[email protected]"]'
  
  # 4. enable + set the device mock
  am broadcast -a $PKG.HEADLESS_UPDATE -p $PKG -e token $K -e id $ID -e deviceMock '{"enabled":true,"manufacturer":"Samsung","brand":"samsung","model":"SM-S918B","device":"dm3q","product":"dm3qxxx","board":"kalama","hardware":"qcom","buildId":"UP1A.231005.007","buildIncremental":"S918BXXU3CWK9","buildType":"user","buildTags":"release-keys","buildFingerprint":"samsung/dm3qxxx/dm3q:14/UP1A.231005.007/S918BXXU3CWK9:user/release-keys","deviceName":"Galaxy S23 Ultra"}'
  
  # 5. enable + set the SIM mock (two cards)
  am broadcast -a $PKG.HEADLESS_UPDATE -p $PKG -e token $K -e id $ID -e sim '{"enabled":true,"simCards":[{"slotIndex":0,"carrierName":"AT&T","countryIso":"us","mcc":"310","mnc":"410","operatorCode":"310410","networkType":"LTE","phoneNumber":"+12025550123","iccid":"8901410123456789012","imsi":"310410123456789"},{"slotIndex":1,"carrierName":"T-Mobile","countryIso":"us","mcc":"310","mnc":"260","operatorCode":"310260","networkType":"NR 5G","phoneNumber":"+12025550456","iccid":"8901260987654321098","imsi":"310260987654321"}]}'
  
  # 6. enable + set the proxy (tested live, ~8s)
  am broadcast -a $PKG.HEADLESS_UPDATE -p $PKG -e token $K -e id $ID -e proxy '{"enabled":true,"host":"10.0.0.1","port":1080,"protocol":"SOCKS5"}'
  
  # 7. pick where the location comes from — geo has two sources, choose ONE
  #    A) from the proxy you just set. This is the default, so the line is optional:
  am broadcast -a $PKG.HEADLESS_UPDATE -p $PKG -e token $K -e id $ID -e geo '{"source":"PROXY"}'
  #    B) or set it yourself — this needs no proxy at all. Use B *instead of* A, not after it:
  # am broadcast -a $PKG.HEADLESS_UPDATE -p $PKG -e token $K -e id $ID -e geo '{"source":"CUSTOM","latitude":35.6812,"longitude":139.7671,"countryCode":"JP","timezone":"Asia/Tokyo","language":"ja"}'
  #    geo and proxy are independent: setting one never rewrites the other, and only
  #    geo.source decides which one feeds the hooks. So CUSTOM together with a proxy in
  #    a different country means your IP says one place while your GPS says another.
  
  # 8. activate (restarts the target app and clears its data)
  content call --uri $URI --method profile.setActive --extra token:s:$K --extra id:s:$ID
  
  # 9. verify
  content call --uri $URI --method profile.get --extra token:s:$K --extra id:s:$ID

  phir usse device par push karke chalayein:
  bash Copy

  adb push setup.sh /data/local/tmp/setup.sh
  adb shell sh /data/local/tmp/setup.sh

  Plain content call commands (bina JSON ke) bina script ke seedha type kiye ja sakte hain. Git Bash mein, adb lines ke aage MSYS_NO_PATHCONV=1 lagayein taaki device ka path re-write na ho.
• Changes dikhe nahi? Target app ko restart hona zaroori hai — profile activate karne par ye apne aap ho jaata hai, aur usi step mein us app ka data bhi wipe ho jaata hai, isliye woh nayi identity ke saath bilkul saaf chalu hota hai.
• Jis proxy par aapko bharosa hai uske liye PROXY_INVALID? Test ke liye device ko internet chahiye, jo ~8s tak limited hai, isliye slow proxy timeout ho sakta hai.
• Jis job ko aap cancel kar chuke hain usse BUSY? backup.cancel job ko turant CANCELLED kar deta hai (aur finishedAt bhi set kar deta hai), lekin usne jo tar shuru kiya tha woh roka nahi ja sakta aur chalta rehta hai, isliye slot pakda hi rehta hai. Slot busy hote hue bhi backup.job CANCELLED dikhata hai, aur koi field slot report nahi karta — CANCELLED ko “slot khaali” na samjhein; bas profile.setActive / deactivate / delete ko tab tak retry karein jab tak woh BUSY lautana band na kar dein. (Jo job apne aap DONE ya FAILED par khatam hoti hai woh slot lagbhag turant chhod deti hai.)