I know I asked a little while ago about going back to stock, I was informed that I could still use Android Pay with Leedroid, which I have for the last few weeks. A few days ago Pay stopped working so I decided to go back to total stock. i followed this to the letter and after a reboot I did a OTA update to 195. In my mind I was totally stock to be able to get the OTA update and have it install.
The problem I have is that Android Pay still does not work and checking with safetynet app, it fails.
Why would this be on a totally stock setup that was able to receive and instal the latest OTA?
I saw this today: http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Could this be the reason?
Thanks for that, it makes interesting reading.
Looks like I'll have to relock my bootloader.
Sent from my HTC 10 using Tapatalk
Related
I just did the root, nand, and radio
However I didn't know that I was going back to 2.1
What are the cons of 2.1 vs 2.2 and how long usually before there is an updated rooted 2.2?
Thanks
2.2 is out officially??? Where/how can I/we get it?
It just automatically downloaded when I got my phone yesterday. Now I'm wondering if I should go back and update and wait then re root later or just wait.
Are you sure you had 2.2? Where did you get your phone? What is your hardware version?
Positive I had it. I got it at walmart yesterday. As soon as I activated it downloaded like three updates.
I was using flash etc.
kikwear002 said:
Positive I had it. I got it at walmart yesterday. As soon as I activated it downloaded like three updates.
I was using flash etc.
Click to expand...
Click to collapse
Flash lite?
Flash works with 2.1 also (at least on the evo)
I'm not really sure. I just know it said 2.2 and not 2.1.
also my hardware is 2.2
I wish I would've known I would've backed up before rooting. I didn't see any reason since the phone was new with nothing on it.
I just checked and it said no updates available.
So in order to go back to stock all I have to do is reflash with the stock rom. Just throw it on sd and flash as normal?
kikwear002 said:
I'm not really sure. I just know it said 2.2 and not 2.1.
also my hardware is 2.2
I wish I would've known I would've backed up before rooting. I didn't see any reason since the phone was new with nothing on it.
I just checked and it said no updates available.
So in order to go back to stock all I have to do is reflash with the stock rom. Just throw it on sd and flash as normal?
Click to expand...
Click to collapse
Just flash RUU from your computer.
Settings > About > Hardware, your Hardware Version is 2.2, NOT 002 or 003?
no its 002 sorry running on two hours of sleep here.
Ok i'm going to try to go back to stock then upgrade.
at least I know I can root it again. maybe faster next time too.
well I unrooted and got some prl updates but no firmware
here goes
Take the battery out of the for about 5 sec then put the battery back in and go in to recovery and try reflashing the rom that work for me
One of three things happened..
You are either have a nexus one and are in the wrong forum..
Are mistaken that you had 2.2 prior to root..
Or you're just trying to mess with everyone..
2.2 is not out in any way officially on any HTC phone, so you couldn't have had it. And no, you couldn't have been the only person in the country to have accidentally gotten it somehow.
Once you root a phone, is possible to go back to a fully stock rom?
backstory:
not long after the s3 was released, i rooted it.
a month or so later, i went back to a stock rom.
what i noticed, my phone never seemed to update to the latest releases.
doing it wrong?
You can Odin back to 100% stock unrooted if you really want. The download link is in the Android Development thread. It has the latest update available both rooted and not. Fact is, there's not much reason to give up root for an OTA as a stock release will be available here within a day or two - sometimes hours. And if you're worried about your carrier if you had to turn the phone in, they really don't care. Just get rid of the custom ROM if you can.
ODIN: http://http://forum.xda-developers.com/showthread.php?t=1722686
STOCK FIRMWARE: http://http://forum.xda-developers.com/showthread.php?t=1968625
Why would you want to is a better question?
Aside from returning for warranty, I see no reason to ever unroot!
crixley said:
Why would you want to is a better question?
Aside from returning for warranty, I see no reason to ever unroot!
Click to expand...
Click to collapse
Tried one of the custom ROMs on here, no real issues.
Tried CM10 and it was a total cluster-fok.
Only reason I liked being rooted was tethering and adblocker.
So, my wife (and I) own the E4GT. I've got mine rooted; no issue; done a long time ago. My wife's currently running 100% stock, has never been rooted, and has received all the official OTA updates, to date.
I'd like to root her phone, and install the Wild-for-the-Night ROM on it. Are there any new caveats to rooting her phone since it has received all the official OTA updates? If so, would someone please point me to the correct guide? I've searched, but all the rooting documents I've found appear to be 1+ year old and seemingly out of date.
Thanks!
Silentknyght said:
So, my wife (and I) own the E4GT. I've got mine rooted; no issue; done a long time ago. My wife's currently running 100% stock, has never been rooted, and has received all the official OTA updates, to date.
I'd like to root her phone, and install the Wild-for-the-Night ROM on it. Are there any new caveats to rooting her phone since it has received all the official OTA updates? If so, would someone please point me to the correct guide? I've searched, but all the rooting documents I've found appear to be 1+ year old and seemingly out of date.
Thanks!
Click to expand...
Click to collapse
You can check this out http://forum.xda-developers.com/showthread.php?t=1953783. If you are still having trouble you can go on YouTube and check out QBKing 77 can't go wrong. :thumbup:
Sent from my SPH-D710 using xda premium
I have searched countless threads for assistance. I have been able to root every phone I've had. I am finally having an issue with my GS4 from AT&T. I bought it back in May, but had to go out of the country for work before I could root it and I just got back this last week. It had received the updates from the server so it is now running the I337UCUAMF3 build. I ran Motochopper, but it said failed and no SU. I have tried utilizing Odin to revert back to the original firmware so that I can try running Motochopper, but when I try it shows fail when in the middle of running the program. I tried factory reset from within android and the stock recovery, but it just reverts back to the latest firmware. I tried going through Kies, but it won't do a recovery and says that it is only through the phone server. I have downloaded 10's of gigs of firmwares, motochoppers, loki flashes, etc.... I am officially lost and would love any assistance someone could offer, cause I would really like to get a better ROM installed like on my other phones.
Thank you
Read the gs4 forum. The info is there. You cant revert back to a later firmware. You can't use Loki or motochopper. All you can do now is root mf3 firmware and that process just became available a few days ago. Stop what your doing and read read and read.
Sent from my SAMSUNG-SGH-I337 using xda premium
venomoussniper said:
I have searched countless threads for assistance. I have been able to root every phone I've had. I am finally having an issue with my GS4 from AT&T. I bought it back in May, but had to go out of the country for work before I could root it and I just got back this last week. It had received the updates from the server so it is now running the I337UCUAMF3 build. I ran Motochopper, but it said failed and no SU. I have tried utilizing Odin to revert back to the original firmware so that I can try running Motochopper, but when I try it shows fail when in the middle of running the program. I tried factory reset from within android and the stock recovery, but it just reverts back to the latest firmware. I tried going through Kies, but it won't do a recovery and says that it is only through the phone server. I have downloaded 10's of gigs of firmwares, motochoppers, loki flashes, etc.... I am officially lost and would love any assistance someone could offer, cause I would really like to get a better ROM installed like on my other phones.
Thank you
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=44165374#post44165374
You are on MF3 build which means this is only root method that will work, but be careful what you do after rooting, currently there is no custom recovery available for the MF3 build due to locked bootloader and loki being patched and there is not any Odin images to restore stock firmware if need be yet. Once you upgrade to MF3 from MDL, there is no way to go back either.
Hope this helps!
Thank you so much for your help!! Much appreciation to all the techs out there for making all these sweet ROMs and roots!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hi, hoping I could get some help.
I just got a huawei watch and cannot get it to update. It is on version 1.3xxxx. When I try to update it, it says it's already the latest version. Hopefully I'm just overlooking something very obvious as right now I feel stuck in the mud. Thanks for your help in advance!
Same issue here! Own the watch from 4 days now.
Same for me
An idea ?
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
jainanshal said:
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
Click to expand...
Click to collapse
The issue with flashing the stock image is that you have to unlock the bootloader, and after that it seems that you loose the warranty.
Better flashing OTA if you want to stay stock. I bought my refurb from newegg.ca too.
ndompierre said:
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Click to expand...
Click to collapse
Same problem.
Then I took your advice and it worked out great, and without changing the bootloader, thank you so much ndompierre :good::victory:
I got my newegg refurb yesterday and could not force the OTA despite resetting and checking multiple times. This afternoon it updated to marshmallow.
Each time time it reboots, I check for updates. I am currently receiving my fourth update of the day.
I guess each security patch has to be downloaded separately. I'm up to August so far..