Related
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
BRPW said:
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
Click to expand...
Click to collapse
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Davey126 said:
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Click to expand...
Click to collapse
Hi,
thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Your play store issue is probably Google play services. Download version .99 from the internet or the general thread.
As for your next steps.
It depends on how involved you want to go.
You can use safestrap and run the nexus Rom. Some people feel that is less risky because you are not modifying the system as much or recovery at all. However, if something goes wrong, you have almost no way to fix it (it is possible to brick with safestrap).
Or,
Downgrade to 2.3.2 (you have to do this because the 2.6 bootloader will not load any other recoveries or roms. Then put twrp on and use cm11 or similar. This gives you a working recovery to fix some issues which could go wrong.
Finally, you could rollback and unlock your bootloader. If you do that, it is the most involved, and a little risky. However, if you succeed. You will be able to put more rooms on it and this gives you the most options to recover from an error.
Many people are playing with cm12 after this.
It all depends on how you are willing to take your risks. It will all require a lot of reading on the forums.
Good luck.
Sent from my KFTHWI using Tapatalk
BRPW said:
Hi,thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Click to expand...
Click to collapse
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Davey126 said:
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Click to expand...
Click to collapse
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
BRPW said:
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
Click to expand...
Click to collapse
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Davey126 said:
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Click to expand...
Click to collapse
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
BRPW said:
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
Click to expand...
Click to collapse
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Davey126 said:
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Click to expand...
Click to collapse
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
BRPW said:
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
Click to expand...
Click to collapse
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Davey126 said:
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Click to expand...
Click to collapse
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
BRPW said:
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
Click to expand...
Click to collapse
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Davey126 said:
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Click to expand...
Click to collapse
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
BRPW said:
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
Click to expand...
Click to collapse
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Davey126 said:
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Click to expand...
Click to collapse
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
BRPW said:
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
Click to expand...
Click to collapse
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Davey126 said:
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Click to expand...
Click to collapse
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
BRPW said:
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
Click to expand...
Click to collapse
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Davey126 said:
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Click to expand...
Click to collapse
First option worked. Right, I side-loaded flashify. I'm guessing Im choosing the recovery image option, which then asks me to choose a recovery option; I choose TWRP, which then takes me to a device option. I don't see HDX 8.9 anywhere there. Which device am I choosing?
Edit: Scratch that; figured out what I had to do. Right, everything is done. TWRP's installed and working fine; bootloader is installed (though I don't know how to check it installed correctly). I think I'm ready for ROMs unless there are more checks to do?
Second edit: After some research, I think I've decided on CM11 (That's KitKat, right?). It seems that everything works on that; wifi works nicely, the Kindle app works nicely (had a HD7 that had issues after I flashed an Android ROM), even the camera works nicely. Just need a clear guide on how to flash it, so will wait for you to come back. It's things like "do I wipe dalvik cache, etc" that I'm confused about also. I'd rather not mess it up on the last hurdle trying to rush into it.
To specify, I'm looking at this one: http://forum.xda-developers.com/kin...rom-cm-11-20150228-unofficial-apollo-t3042776
Does it come pre-installed with gapps or no? Can't quite figure that out, since some ROMs specifically mention that they have gapps already loaded in.
Thanks.
Hi all!
I'm new here, so please instruct me if I'm doing anything wrong.
I have a Coolpad Y82-820. It's a Chinese phone, I think.
I'm in the process of getting it rooted. ---- Was rooted before, but an update on their side (to CoolUI V24. [phone model#]. 160407) removed the root and now makes it a bit difficult to root at the moment, though I'm sure it will be done eventually. For those who have this phone, I'd suggest not to update, as this update deletes any rooting applications installed on reboot/restart.
Once rooted, I don't really mind waiting, I would like to put a Custom Rom on this phone, but not sure what options are available. I see posts about the Coolpad Note/Dazen/Shine/Rogues etc. Though nothing about this one, though spec wise it's not too far off from the others.
I'd be grateful if anyone could help with confirmations, information, on how to select a correct custom rom for this device and the steps to do. Also if there's any info on how to root this current version, even better.
Thanks!
Some details of the phone below:
Model Number
Coolpad Y82-820
CPU
Qualcomm Technologies, Inc MSM8916 Quad-core 1.2 GHz
RAM
2G
Internal memory
Total 8G
Resolution
960 * 540
Android version
4.4.4
Kernel version
3.10.28
[email protected] #1
Thu Apr 7 17:01:56 CST 2016
Build number
4.4.005.150730.Y82_820
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Johny2k9 said:
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Click to expand...
Click to collapse
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Røbin said:
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Click to expand...
Click to collapse
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Johny2k9 said:
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Click to expand...
Click to collapse
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Røbin said:
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Click to expand...
Click to collapse
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Johny2k9 said:
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Røbin said:
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Click to expand...
Click to collapse
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿,所以这个汉字我都明白了,如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Johny2k9 said:
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿,所以这个汉字我都明白了,如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Click to expand...
Click to collapse
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Røbin said:
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Click to expand...
Click to collapse
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Johny2k9 said:
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Click to expand...
Click to collapse
There's no available firmware to downgrade. Bad luck for you.
Røbin said:
There's no available firmware to downgrade. Bad luck for you.
Click to expand...
Click to collapse
Is upgrade impossible without rooting?
Johny2k9 said:
Is upgrade impossible without rooting?
Click to expand...
Click to collapse
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Røbin said:
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Click to expand...
Click to collapse
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Johny2k9 said:
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Click to expand...
Click to collapse
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Røbin said:
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Click to expand...
Click to collapse
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Johny2k9 said:
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Click to expand...
Click to collapse
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Røbin said:
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Click to expand...
Click to collapse
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Johny2k9 said:
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Click to expand...
Click to collapse
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Røbin said:
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Click to expand...
Click to collapse
Installed Xposed Installer, but the Download section is empty.
I am in China currently, so a lot of things may be blocked. A VPN should fix this, I believe.
What things I should install. Xposed Installer is new to me.
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
This also what happened to me.
szophiya said:
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
JazzieBoi said:
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
Click to expand...
Click to collapse
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
arda99 said:
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
Click to expand...
Click to collapse
Wow I had no idea metro did that. I knew metro doesn't like unlocked bootloader's and are strict. I will never buy one in my life .
szophiya said:
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Click to expand...
Click to collapse
You could try flashing the stock boot.img via fastboot to see if it finishes installing. https://forum.xda-developers.com/attachments/boot-11-0-1-be88cf-img-zip.5399231/
You'll need to reboot to fastboot and then run: fastboot flash boot_a boot-11-0-1-be88cf-img and then fastboot boot_b (img filename). Try rebooting and performing the update then.
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Misclicked and did a double post, sorry.
szophiya said:
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Click to expand...
Click to collapse
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
JazzieBoi said:
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
Click to expand...
Click to collapse
The MSM you provided is for BE86AA and BE89BA, not for BE88CF which is what they need.
As far as I know, no MSM exists for BE88CF: https://forum.xda-developers.com/t/...8cf-11-0-2-be88cf-rooting-impossible.4367271/
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.