Related
Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner. I am running the latest TWRP recovery.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
IlyaKol said:
Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Click to expand...
Click to collapse
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
arfon said:
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
Click to expand...
Click to collapse
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
msw141 said:
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
Click to expand...
Click to collapse
Update was OTA last night, so I guess its as natural as it comes.
arfon said:
Update was OTA last night, so I guess its as natural as it comes.
Click to expand...
Click to collapse
Yeah...my process was as natural as possible.
I was on 4.3 at first...so when I was going to 4.4 KitKat I first flashed back to some basic stock Sense ROM to run RumRunner and attain S-OFF. Then I COMPLETELY NUKED my phone and went to 4.4 KitKat. Had no problems, got the OTA, and now this.
It's aggravating, that's for sure.
I really don't want to completely wipe my phone again and have to re-setup all of my home screens, etc.
I received the OTA which installed despite me having TWRP, not stock recovery (as per http://forum.xda-developers.com/showpost.php?p=48586329). Now I have the same issue installing paid apps (the ones I had already installed before the OTA disappeared off the device).
Short of starting from scratch, I'm at a bit of a loss for a solution...
Nick
Sounds like this is wide-spread...or at least amongst the people who are running newer GPE ROMs on their Ones.
im having the exact same issues here
artmunkie said:
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
Click to expand...
Click to collapse
Can you point me to where you got the stock recovery from please?
Fixed
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
arfon said:
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
Click to expand...
Click to collapse
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
franciscols said:
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
Click to expand...
Click to collapse
This.
Also, you left 4.4.2 on the device and just 're-applied' the OTA update? Or did you go back to a NANDROID backup of you on 4.4 or 4.3?
arfon said:
Can you point me to where you got the stock recovery from please?
Click to expand...
Click to collapse
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
artmunkie said:
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
Click to expand...
Click to collapse
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
IlyaKol said:
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
Click to expand...
Click to collapse
Yeah, that's about it. I used adb to flash the stock recovery to replace TWRP, then used the stock recovery to flash the same update you linked to. After it was done updating I reflashed TWRP. And don't forget to make a nandroid.
Thank you! Will report back when I'm done!
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
IlyaKol said:
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
Click to expand...
Click to collapse
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
artmunkie said:
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
Click to expand...
Click to collapse
What if you don't have an "apply from adb" option?
I have:
- reboot system now
- apply from sd card
- apply from phone storage
- apply from cache
- wipe data/factory reset
- wipe cache partition
Can't I just open a ADB shell while on the fastboot USB option?
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.
Same thing here, always installation failed
Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables
Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???
@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
veroby said:
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
Click to expand...
Click to collapse
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
k.s.deviate said:
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
Click to expand...
Click to collapse
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
veroby said:
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
Click to expand...
Click to collapse
I did do this last night as I was greeted with the same Verity error after flashing the beta.
k.s.deviate said:
I did do this last night as I was greeted with the same Verity error after flashing the beta.
Click to expand...
Click to collapse
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Seems a little weird as the fastboot oem disable_dm_verity commands have only just come onto xda this morning. Seems weird because its working for most which would assume most are on 4.0.2 firmware. Meaning they havent update for a long time.
Updated - I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither. Thankyou..:good:
veroby said:
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Click to expand...
Click to collapse
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
k.s.deviate said:
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
Click to expand...
Click to collapse
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
veroby said:
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
Click to expand...
Click to collapse
Glad my explanation helped.
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
xtacb4 said:
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
Click to expand...
Click to collapse
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
veroby said:
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
Click to expand...
Click to collapse
Hi, last message mine in this thread talking about this here, don't want to be offtopic, I purchased it yesterday, came home installed the usual (twrp[i love how fast the backups are made], CM14.1) and delivered the Nexus 6 to a friend (he bought it from me).
Thanks!
Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.
I wanted the oreo update, but it wasn't coming OTA for some reason. I rooted my phone a year ago when I first got it and had some issues and flashed it back to stock fairly quickly.
So I figured that I could flash the oreo update no big deal. The commands all looked familiar for the first time.
Well I flashed the wrong version. I have tried custom roms such as the pixle but non of them can mouth /oem/ or /vendor.
So do I just need to give up on it?
I have been trying for 5-6 days many hours of frustration.
I'm not developer, but it seems Like there should be a way to get the stock rom back in the box.
I just need to know if its garbage now or not.
Thanks
Did you try to fastboot the device back to stock? There are several guides out there. Unless you cant get into the basic ADB mode, this should be able to be done.
This is the guide I used. Just make you get the Sanders version from stockrom.net
jordanhaughee said:
Did you try to fastboot the device back to stock? There are several guides out there. Unless you cant get into the basic ADB mode, this should be able to be done.
This is the guide I used. Just make you get the Sanders version from stockrom.net
Click to expand...
Click to collapse
Yes, I have tried that. the oem.img always fails and the sparce chunk.0 always fails.
So it doesn't take.
So I am going to answer myself. After much searching and reading.
Due to the phone not allowing downgraded stock firmware ....
It seems that I am stuck.
If Motorola comes out with a new firmware than I can flash that but until than its a brick.
That seem about right?
So With the help of a developer on here, I was able to force oem using a shell command. I than was able to load oreo on and it is running just fine.
Hyde1234 said:
So With the help of a developer on here, I was able to force oem using a shell command. I than was able to load oreo on and it is running just fine.
Click to expand...
Click to collapse
Can you help me? I think I did the same as you..
I tried to install the stock ROM and appears "(bootloader) Validating 'gpt.default.xml' (bootloader) Security version downgrade".
Then I tried to update the OTA through ADB and received this message "This package expects the value "sander" for "ro.product.name"..."