SOLVED: https://forums.oneplus.net/threads/solved-cant-flash-twrp.268957/page-3#post-10876574
Okay, so all i needed to do was skip the "fastboot reboot" stage, and everything worked wonderfully. Once again XDA freaking ROCKS!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hey all! I've got my OnePlus 2 for a while now, and its one of the 'chinese' models i think..
Now! I'm having some serious issues with this phone, The phone itsself is AMAZING, more than i could ask for, But for some reason, the device came pre-loaded with some BS apps, some chinese apps, etc, etc..
The issues i'm having is that SOMETHING that they pre-loaded into the systems apps is causing me FULL-SCREEN pop up ads, and my ADB REFUSES to work!! Fastboot has been working without problem, and i followed the steps HERE to no avail, my device is detected in all states through "fastboot devices" command, but any attempt at meddling with my phone using ADB seems to fail.. Also my OTA Updates always fail, It will NOT let me update my phone by any of the normal means.. Which is also incredibly strange!
When i try to use "adb devices" command, my device refuses to show up (Yes, USB Debugging is enabled, yes, i've tried google) although for some reason when i use ADB to flash the recovery, it seems to go through the motions, tell me that the custom recovery (Newest twrp for OP2) has been succsessfully installed, When i attempt to reboot into recovery, i get the default OP2 recovery screen!!
It has been driving me completely mental, And i really need your help XDA, some of the names of the system apps that were pre-installed are sending information in bulk to servers in china, and i cant stop it.. I need to make this phone compeltely fresh!
**NOTES**
Fastboot works
Adb (kinda?) works
OTA Updates DO NOT WORK (Download okay, but any attempt to change the device in any way seems to fail!)
Weird /system apps that are doing weird things, and shouldnt be there
Screenshot of Fullscreen-pop up ads
DEVICE:
OnePlus Two
Oxygen OS 2.0(?)
Chinese Model
Carrier: Amaysim (Optus?) [ Australia, Melbourne ]
System Pic
Please XDA! Im getting quite desprate to make this device 'mine' and it just isnt working out.. Let me know if i missed any info!
After rooting with the KingRoot apk apps would start crashing randomly (no message, just every running app would exit and throw me to my home screen), so I decided to factory reset. I grabbed Titanium Backup, grabbed the app backups I needed, then did the reset. Phone booted up, but now the setup wizard just crashes every run through and restarts itself, leaving my phone useless.
It may be important to know that after KingRoot, my boot screen had an unlocked lock with the text "custom" under it- I figure this means my bootloader is unlocked, but I could be wrong.
I've enabled USB Debugging through the recovery screen.
Setup Wizard (Without SIM):
Connect to Wifi network -> Next -> Crash
Skip connect to wifi -> Skip anyway -> Crash
Setup Wizard (With SIM):
Properly IDs my number and connects to 4G -> Next -> Sometimes crash
Skip Verizon Cloud -> Not Now -> Crash
Setup Verizon Cloud -> Finished Setting up -> Crash
Installing TWRP via h00ps://twrp.me/devices/samsunggalaxycoreprimequalcomm.html
Option 1 (TWRP) nogo, no previous TWRP installed
Option 2 (Odin) nogo, tried both through the website on Linux/FF and through Windows (VirtualBox). The website asks me for the PIT, then when it tries to retrieve it from the device it fails. The app on Windows doesn't ask me for it, but when trying to install it it pops up "secure check fail: recovery" on the phone's screen (the app does nothing).
Option 3 (dd) nogo, can't get an adb root shell
Rerooting through the KingRoot desktop app:
It looks like it succeeds (it's all in Chinese).
adb root gives "adbd cannot run as root in production builds"
adb shell su gives "[-] Connection to ui timed out"
Trying to remove or disable the Setup Wizard app:
ps | grep setup returns the following package names:
com.android.setupwizard (pm disable -> Unknown package)
com.google.android.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=11940, uid=2000, package uid=10014)
com.google.android.partnersetup (pm disable -> Permission Denial: attempt to change component state from pid=11958, uid=2000, package uid=10030)
com.sec.android.app.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=12180, uid=2000, package uid=1000)
kill <package> -> Operation not permitted)
pm uninstall <package> -> "Failure [DELETE_FAILED_INTERNAL_ERROR]"
pm path com.android.setupwizard -> nothing
pm path com.google.android.setupwizard -> /system/priv-app/SetupWizard/SetupWizard.apk
pm path com.google.android.partnersetup -> /system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
pm path com.sec.android.app.setupwizard -> /system/app/SamsungSetupWizard/SamsungSetupWizard.apk
I had also sideloaded gapps-lp-20150314 (for 5.1.X) in hopes that it would fix it up.
Anything else I should try? Any stock images so I can do a complete, fresh, reinstall? I know someone here was working on getting stock everything uploaded- will that be my best bet?
Thanks!
EDIT: Additional information
Download mode returns the following strings:
ODIN MODE
PRODUCT NAME: SM-G360V
CURRENT BINARY: Samsung Offical
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, H1, R1, A3, P1
SECURE DOWNLOAD: ENABLE
When trying to flash TWRP with ODIN add line
SECURE CHECK FAIL: recovery
I think the twrp was not for your phone. All the cores have Qualcomm snapdragon processors and I do believe most of them are LTE. I know for a fact tmobiles is an lte. The problem is Verizon paid for the kernel so they could control our access. That's why we're the last one to get anything done. Basically, by flashing the recovery, you may have soft bricked your phone since it compiles with a different kernel. Yes, Verizon has a different kernel. If you check opensource.samsung.com, you'll notice our phone is not listed. Thats thanks to Verizon. I'm pretty sure that's illegal too but I'm not a lawyer. Until we get a stock rom or someone has an idea, I do believe your phone is KIA.
Ugh, thanks verizon. However, the soft brick immediately happened after the factory reset, not the install of twrp (it kicks out of that pretty quick). I know you're working on a stock rom in another thread, anything you need to speed up the process? I'm honestly about to just get a Nexus 5 from Amazon Prime, they're pretty cheap and it's getting rough not having mobile data.
With the new OTA having just rolled out, I'm going to pull it. You'll be able to use it to recover
https://mega.nz/#!0Q1nFQ7a!pHublKgmjElaZmePKUWxTB5rlgLytu921bFIJJbII_E
Link to the new OTA.
Flash using either recovery, if you still have access or fastboot.
And TWRP is official. I found the actual name from verizon, and it matches. Careful with the OTA, I'm now soft bricked.
jaywillsoul said:
Link to the new OTA.
Flash using either recovery, if you still have access or fastboot.
And TWRP is official. I found the actual name from verizon, and it matches. Careful with the OTA, I'm now soft bricked.
Click to expand...
Click to collapse
Awesome, you're a lifesaver. I'll do this once I get back from work- can't say I really want to deal with VirtualBox USB passthrough today or that sketchy looking java/web one.
I've still got access to everything (download, recovery, adb, no fastboot though). So the linked version of TWRP (coreprimelte or whatever) is specifically for this phone? Any reason I wasn't able to successfully flash it?
Last thing- and thanks so much- what does that zip actually contain, and if it is just the OTA files, then will I still avoid the soft brick you ran into?
Unfortunately, the OTA update changed nothing. Dunno if it was supposed to (I didn't see Setup Wizard files in there) but I'll trade a soft brick for a soft brick. There was some red debug info on screen when applying, but the phone quickly rebooted afterwards. If you need me to, I could probably adb in and check the version numbers to see if it applied and/or rerun the update and capture that debug info.
Maybe all I need is a stock copy of the Setup Wizards- I should be able to sideload them over the existing versions, right?
Maybe. I'll dig through the system and see if I can find the original.
It might be a part of gapps
That's what I was thinking too, and I've tried reapplying gapps-lp-20150314.zip. I think the Setup Wizard it's crashing on isn't the stock android one, but one of the samsung/verizon ones I listed in the first post.
Found it. Once my son goes down for his nap, I'll upload it for you.
https://mega.nz/#F!BE1TVbTL!d2G2P9S1jVyV-mr8UsfAGw
That's the entire folder in /system/app
It was worth a shot, but sideloading that apk failed. The stock you are working on should be the ultimate fix though.
I uploaded the official md5 from Samsung kies 3. It's in a new thread.
AWaterFountain said:
It was worth a shot, but sideloading that apk failed. The stock you are working on should be the ultimate fix though.
Click to expand...
Click to collapse
Did the ROM work for you?
Yep, I guess I only confirmed that with jay in PM. The stock ROM he uploaded worked fantastically, just threw it in Odin and I was good to go.
AWaterFountain said:
Yep, I guess I only confirmed that with jay in PM. The stock ROM he uploaded worked fantastically, just threw it in Odin and I was good to go.
Click to expand...
Click to collapse
Good to hear! What version of odin did you use and what settings in odin do you select to get the ROM to flash?
All stock, latest version. All I had to do was throw phone into DL, put the stock rom into ap/pda, and let odin do its thing.
Thanks!
jaywillsoul said:
I uploaded the official md5 from Samsung kies 3. It's in a new thread.
Click to expand...
Click to collapse
were do i find te tread you posyed it on?
Hello, so I downloaded my phones stock firmware (G9006v) and it had a lot of chinese bloatware and after some time it started saying "unfortunately google play services has stopped working" and after some time nothing from google works, even google play doesn't open up. I rooted my phone using CF auto root and then I wanted to install TWRP to install custom ROM, but then I learned that I need to enable OEM or bootloader, but when I go to developer settings there's no OEM unlocker or something like that, I watched a lot of videos, but couldn't figure it out. I saw that I can use ADB, but that's very complicated (for me). Isn't there a bit easier way to unlock bootloader? And by the way, when I go to recovery mode there's a line that says: reboot to bootloader, when I press on it, it just takes my to download mode (maybe it should do that, I don't know). I really need Your help, cause I want my phone back. Thank You
1. if not OEM-unlock, bootloader is unlocked (which is, for ALL S5 models except North American Verizon, T-Mobile AT&T, etc.)
2. flash a recovery in download-mode with Odin.
Just wanted to share that I have working Android Pay with my rooted Nexus 6 XT1003.
Phone Info:
Nexus 6 XT1003
Bought it from ebay for $180 (from China)
Android version: Nougat 7.1.2
LineageOS version: 14.1-20180202-Nightly-shamu
Process:
Unlocked bootloader
Fastboot boot'd latest twrp (no install)
Wiped the phone and installed latest LineageOS from their site + gapps package with twrp
Upon first boot, skipped all account setup and first boot setup
Accessed developer settings and enabled "OEM unlocking"
Back to fastboot boot twrp
Flashed SU package provided by LineageOS
Ran Fastboot OEM lock command
Waited what seemed like 20 minutes for the first boot to complete
Setup phone as normal
Opened Android Pay and added my card
Now a few more details.
Before using this at the store, I enabled root for apps in settings for an app "System app remover (ROOT)" Excellent app, get it here: ( https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp )
After this with root still enabled, went to the store and attempted to pay with Android Pay.... "THIS PHONE CAN NO LONGER BE USED FOR PAYMENTS" - That was a huge let down and I was sad.
I thought right off the bat, DUH! Disable root in developer settings..... no dice, same error.... but my bootloader is locked and root is disabled....
I followed the google message and sent feedback in the app and said "My bootloader is locked and root is disabled"
Now I didn't really expect this to work with Google's security with this service.
I went to the store a few days later with root still disabled, after a reboot or two and tested it... IT WORKED!
I wonder why it didn't work the first time? Maybe because I had not restarted my phone after disabling root? Maybe because I cried to Google? (doubt it)
I'm going to re-enable root at some point and test it out again to see if a simple restart after disabling is what fixes this.
Does Android Pay work for you?
My Android Pay works on current Lineage OS, but I never flashed root. I did install TWRP as normal. Otherwise I did the same as you. (Doesn't help you answer your question, though, sorry.)
I have magisk installed and android pay works fine with it.
OEM unlocked too.
los+magisk 15.3+universal-safetynet-fix-v2-beta-5= work fine
Disabling root access in the developer settings and rebooting worked for me.
I have had my Essential Phone for almost two years now and one day last week when I turned the phone on I saw the following error message.
You device is corrupt. It can't be trusted and may not work property.
Visit this link on another device:
gc.o/ABH
Press Power Key to Continue
There is a red exclamation point at the top that looks like this <!>. I contacted Essential Support and they told me the only way that message gets displayed is when someone has unlocked the bootloader at some point. I have never connected my phone to a USB cable for anything other then charging it with a power outlet and I have certainly never heard of ADB before this error occurred.
I would like to know how this error has happened if all I do is install a few apps from the Play Store and install OS updates when the are officially available OTA. Essential Support has said its my fault and will not help.
I tried to reset the phone back to factory settings several times. I have used the reset from within the Settings, I have used ADB to side-load the latest OTA OS from Essentials website and I have also tried some kind of flashing reset but no matter what I did I could not get this error to go away. These methods are described on the Essential site linked below.
Here is the link to Essentials website that I used. Since this is my first XDA post it will not let me post the whole URL. (essential.com/developer/current-builds)
I eventually ran the following command which did remove the error.
Code:
adb reboot "dm-verity enforcing"
From what I can tell this just prevents the error message from being displayed, correct? If the reason for the error is still there then what are my options? Should I worry about this error? Is it possible for me to reset the phone in someway to get this error message to go away and put the phone back into a secure and safe state? I don't care about any user data on the phone. The whole thing can be erased, which I think I have done sever times already trying to fix this.
Any suggestions would be greatly appreciated because beyond trying to fix this error I have no experience with ADB or modifying a phone in anyway.
Thanks,
-eric
Is there anyone who can offer help?
EricAndroid said:
Is there anyone who can offer help?
Click to expand...
Click to collapse
You can unlock your bootloader and unlock critical partitions than flash the latest bts (back to stock) from the link below. Make sure to read the directions and use a quality type c USB 3.0 or 3.1. you basically download the zip and unzip it, then run the flash-all-wipe.bat from fastboot mode. This will fix the actual problem. Good luck and make sure to ask in that thread if you get stuck.
Almost forgot, make sure to download the Essential Window's drivers(from thread below as well). You don't need to worry about setting up adb and fastboot because it's Automatic when you run the commands from the zip you download. Also make sure you first uninstall any instance of adb or fastboot that may already be on your computer.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484