Revive e-Motorike Android App

@nutankumarftp

With a decade-long track record developing flawless web and mobile applications including Android APK reverse engineering, I strongly believe I am the right pick for your e-Motorike project. Boasting 10+ years of extensive experience in Kotlin, Java and Smali, I’ve successfully worked across diverse industries including automotive. Having delivered 2000+ projects with 100% client satisfaction, your app's renewed build functionality is a commitment I take seriously. I've also got a deep understanding of modern Android build pipelines which could prove crucial in avoiding any crash or dangerous-permission warnings on the initial run - other essential deliverables we have mutually agreed upon.

@roxyhasan76

Hello, My name is Rakibul Hasan. I’m an Android and cross-platform developer with experience in APK analysis, Android build systems, and Bluetooth-based device communication. I reviewed your project description regarding the **e-Motorike utility app** and the OTP issue after the app was removed from Google Play. Before starting, I would just like to confirm that you have the **legal rights or authorization to modify and rebuild this application**, since it involves APK reverse analysis. ### Proposed approach 1. **APK Analysis** * Decompile the APK using standard Android reverse-analysis tools. * Inspect the authentication flow responsible for generating the OTP. 2. **Identify the OTP failure** The OTP issue usually occurs because: * the app calls a **deprecated API endpoint** * a **server key or certificate expired** * OTP logic depends on **time-based validation (TOTP)** that is no longer synced * the Play-services dependency was removed or changed. 3. **Patch or rebuild** * Restore the OTP generation logic or bypass the broken call. * Rebuild the APK and ensure compatibility with modern Android versions. 4. **Functional testing** We will verify that the following work exactly like the original version: * Bluetooth pairing with the e-Motorike * live telemetry data * settings and device controls * stable installation with no crashes or permission warnings.

@nicolasalexandro

Hey — saw your post about reviving your e-Motorike Android app from the APK after it was removed from Google Play. The tricky part here is usually untangling why it was taken down (policy, SDK, or security issues) and getting it compliant again without breaking existing functionality. Quick question before I suggest an approach: Do you still have access to the original source code, or are we strictly working from the APK and reverse-engineering it? I’ve helped bring older Android apps back to Play by updating SDKs, cleaning up policy violations, and rebuilding from APKs when source wasn’t fully available. If you can share the APK and any Play Console emails or warnings you received, I can review them and tell you what’s realistically needed to get this live again.

@adilmalikdev

I have strong experience working with Android APK analysis and reverse engineering, and I will handle the project using Kotlin along with Smali/Java adjustments where required. I can analyze the APK, identify why the OTP generation stopped working, and modify the logic so the app functions properly again. I will ensure the updated APK installs correctly, has no crashes, and maintains Bluetooth pairing, live data readouts, and settings exactly like the original app. Please share the APK so I can review the issue and start working on the fix immediately.

@vasylklymiu

Hi, I just applied after read your job posting carefully and I believe that I am good fit to your project. I have thoroughly reviewed your requirements and I am confident in my ability to deliver excellent results. I'm a serious bidder. I will satisfy you with my high skills! I am an expert which have 8+ years of experience on C Programming, Java, Mobile App Development, Android, Kotlin, Mobile Development, Android App Development, Android SDK I will work on your project hard with full time. I am looking forward to meet you to discuss the further detail about this project. Looking forward to hearing from you. Thank You

@dejanm44

Hi, I've carefully read your project description regarding the e-Motorike Android app and I am confident in my ability to help you revive it. My experience includes extensive work with APK reversing and I've successfully resolved similar issues with OTP generation in previous projects. I will utilize my expertise in Smali, Java, and Kotlin to ensure a smooth APK reverse-engineering process, making sure that the app reinstates its core functionalities such as Bluetooth pairing and live data readouts without any crashes or permission warnings. My goal is to provide you an updated build that you can test right away. I can start immediately upon receiving the APK and would appreciate any additional information on the expected behavior of the app. What specific features or behaviors would you like me to prioritize during the APK reversal process?

@Retrytechteam

From your description, the most likely issue is that the OTP generation is tied to an outdated API endpoint, certificate validation, or a disabled server-side check. By reverse-engineering the APK, I can analyze the Smali/Java code, identify where the OTP logic fails, and patch or redirect the functionality so the app can generate or handle OTP correctly again. Here is how I would approach it: • Decompile the APK using tools like JADX / APKTool • Analyze the OTP generation or verification flow in Smali/Java • Patch or rebuild the logic so the OTP process works again • Recompile and sign the APK with a clean build pipeline • Test installation and runtime behavior to ensure no crashes or permission warnings • Verify that Bluetooth pairing, live data readouts, and settings behave exactly like the original version I have experience working with APK reverse-engineering, Smali modifications, and rebuilding Android apps so they install cleanly on modern Android devices. If you can send the APK, I’ll first inspect the OTP implementation and confirm the exact fix required. Once identified, I’ll provide a working rebuilt APK for testing on your device. Looking forward to taking a look at it.

@fizaa170

Hello, I have experience with Android APK reverse engineering and debugging, including working with Smali, Java/Kotlin decompilation, and rebuilding APKs to restore broken functionality. How I can help: • Decompile the APK using tools such as Apktool/JADX to inspect the authentication and OTP generation flow. • Identify why the OTP generation no longer works (API endpoint changes, expired keys, server validation, or local algorithm issues). • Patch or rebuild the affected logic in Smali/Java so the OTP process functions again. • Recompile and sign the APK to produce a stable updated build. Testing & verification: • Ensure the updated APK installs without warnings or crashes. • Verify Bluetooth pairing with the e-motorike, live data readouts, and settings functionality. • Work with you during testing to confirm the behavior matches the original version. Skills relevant to your project: • APK reversing and modification • Smali / Java / Kotlin debugging • Android build & signing pipelines • Bluetooth and API communication troubleshooting If you can share the APK and any details about how the OTP previously worked, I can analyze it and outline the fix quickly. Estimated turnaround: 2–4 days depending on the OTP implementation.

@benw358

Hi there, When an APK stops generating OTPs, it’s usually due to expired API endpoints, broken auth logic, or disabled verification services. The challenge is restoring the authentication flow while keeping the original Bluetooth and device communication intact. I’ve worked on APK reverse‑engineering projects where legacy Android apps were restored after services changed or apps were removed from the Play Store. One project involved patching Smali code to restore authentication and API calls, and another required rebuilding an APK with fixed libraries while preserving hardware connectivity. My approach: • Decompile the APK using APKTool/JADX and analyze the OTP generation logic • Identify whether the issue is server endpoint failure, local OTP logic, or time-based token validation • Patch the Smali/Java code to restore or emulate the OTP flow • Rebuild and sign the APK with a stable Android build pipeline • Test Bluetooth pairing, live data readouts, and settings to ensure original functionality remains intact You’ll receive a working rebuilt APK and notes on the fixes. Best Regards