i thought i was upgrading to 13.1.1 by d/l cm-13.1.1-ZNH2KAS2X1-bacon-signed.zip but after going through the TWRP process and reinstalling my data from the backup i see, from About Phone, that i'm still on Cyanogen OS version 13.1-ZNH2KAS254 instead of the 2KAS2X1 ???!!!
Did i miss something in the install? i had checked the md5s after d/l. i placed the 13.1.1 and gApps on root, ran TWRP, selected the two files and the three basic Wipes. i didn't see any error messages. It rebooted and went through the Android process for 136 apps. i then booted into TWRP again and just reinstalled Data.
Am i missing something here or what?
Have a great evening!
Related
Here I Go
I was on CM11 Snapshot. Then I went to install Lollypop from http://forum.xda-developers.com/nexus-4/development/rom-aosp-build-t2929544. So I go on TWRP and wipe Dalvik Cache, Cache, Internal Storage and System. Then after, I noticed that everything was gone. So I sideload the ROM and my Gaaps. Something went wrong and old system apps like Dialer and Camera were installed and caused problems with the Newer apps and the system. I Wipe again....this time making sure to wipe data. I sideload but....the gaaps did not install. I went into Recover and noticed that TWRP was uninstalled and everytime I installed it VIA Fastboot, it worked but only for the Timebeing. Sideloading was not working and when I tried downloading the GAAPS straight from the browser, it was unsuccessful. Also, everything that I tried to download via browser did not work. Then I connected it to my Computer as an MTP. This was not working either.
Please Help and Thank You
Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.
Hi everyone,
I have been happy with the Marshmellow version the OS since I bought my phone when it came out (Unlocked, Encrypted). I have performed one update since I had the phone. Today, after seeing the latest posts after not being on this site for a year, I decided to make the move to upgrade to OOS 5.1.0!! Why not, nothing else going on this weekend. I upgrade TWRP to 3.2.1-1, I make a full backup, I follow the upgrade instructions... it fails with the continuous spinning balls on reboot. I Do some research... oh, it is "challenging" to upgrade but possible. No big deal, I will just restore my backup and try again at some other time. My backup restore fails Error 255, I try the fixeS I found such as unmounting data... No Luck). Can not restore the data partition. I guess I should have decrypted everything prior to backing up based on what I read later.
I at least backed up my SD card using adb prior to all this, so I decided to just reinstall ANY OS to get my phone running again for tonight. Well I have not had much luck. I downgraded TWRP to 3.2.1-0, I have tried installing:
OnePlus5Oxygen_23_OTA_033_all_1804110400_eb1766 - Originally installed with not errors but phone reboots back into TWRP after a failed 1st reboot. (I do get a "failed to mount /vendor")
lineage-15.1-20180423-nightly-cheeseburger-signed with Gapps (Gapps failed with I think a error 7)
I was messing with the data partition, wiped, formatted, etc. I am sure this is some of the issues. One other thing is that TWRP always boots to the "keep System Read only" I find this strange and had never seen before. I select to allow modification, but it seems like nothing changes on reboot.
At this point I would just like to get a stock OS image on the phone. IS there something I am missing?
https://forum.xda-developers.com/oneplus-5/how-to/guide-mega-unbrick-guide-hard-bricked-t3698370
Sounds good, let me give it a try.
I've been thru this already. Here is the simplest way to get your 1+5 back to work, while having the latest LineageOS installed. It takes a bit of time and patience, but it works:
Using fastboot, reinstall TWRP 3.2.1-1 (or newer, if any)
Wipe all partitions, namely Dalvik/ART cache, Cache, System, Data and Internal storage
Sideload the latest OOS (version 5.10 or later, if any) with Android 8.1. This version will be OK for LineageOS 15.1 and you will no longer have that stupid error 7 when installing LOS 15.1
If OOS boots into recovery and asks for passwords or PIN or schema ... click on the "forgotten" link. OOS Recovery will then remove encryption and wipe out any data that was left.
Reboot phone, and start OOS session. Do not use any security stuff (PIN or schema or whatever) that would encrypt the phone. At least not now - If necessary, you will add it at the end of this whole process.
Once OOS is working, reboot to Bootloader. Since TWRP has been erased with OOS default recovery, you will have to reinstall it.
From TWRP, wipe Dalvik/ART cache, Cache, and Data partitions. This time, do not touch System or Internal storage
Sideload Lineage OS latest version. If you need to use Google Apps (e.g. Open Gapps), sideload it now before rebooting
Reboot (you might have to reboot twice, don't worry about that).
Once booted in LineageOS, do whatever you like - add accounts, root phone, etc.
Enjoy! (you may want to shout "Vive la France!", well ... don't hesitate!)
Sorry for my poor English. If anything here is unclear to you, please let me know.
I Have no idea what happened. I came home to start working on my phone, powered it up, and boom I have Android 8.1. Ok, Whatever...
Now I wonder if I should go for lineage or not.
kuhnto said:
Now I wonder if I should go for lineage or not.
Click to expand...
Click to collapse
It all depends on how important privacy is to you. If you don't care, then stick to the original OnePlus firmware. If you do, then switch to LineageOS.
im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?
I'd wiped out everything off this Nexus 10 tablet. I'd found it in a box of old stuff. Thought I'd start off with a fresh install.
Problem is that now I can't load anything. Every attempt at installing any ROM meets with errors. Using TWRP 2.8.7.0 that was on it. I had used advanced wipe and deleted everything. After each attempt at installing a ROM zip, I did a Dalvik and cache wipe as well.
So, before I end up trashing the old thing, is there some solution that I'm not knowing that would enable me to complete a restore?
Enclosed is a pic of what I'm seeing.
Thanks
Devildoc
Try get a os made for your device if that doesnt help get the latest twrp recovery