Hello
I hve tried to install Resorrution remix And SlimRom But i have bootloop problems, Once the install is finished the OP5 Goes to continous bootloop. and the only thing i can do is to restore to the OP oxygen OS. since i am doing the whole procedure on Mac and its new to me i was thinking i was doing something wrong but it doesnt seem so. The only problem i get ( i guess its a problem ) It is when i install the Twrp the phone gives a Errorr The the software is not working properly and gives and Adress where to go and check. Htt p: //g. co /abh when it says that the device software can't be checked but i dont belive this is the problem. Does any one had this problem before. If not can you Give me any solution.
Thank you for your attention
That message is OK, it's not an error, it's a warning of your device being unlocked. You should give a little bit of extra info, what steps did you do in twrp? What did you wipe and what files did you flash?
to install custom rom, you have to decrypt the internal stockage with the command "format user data" in fastboot
actupsp said:
to install custom rom, you have to decrypt the internal stockage with the command "format user data" in fastboot
Click to expand...
Click to collapse
Be careful in saying those things, it will completely wipe the phone including pictures and all.
Besides that it's not true, Resurrection remix can be used when encrypted. To me it more sounds like the OP did not wipe enough in twrp, a dirty flash upon Oxygen.
actupsp said:
to install custom rom, you have to decrypt the internal stockage with the command "format user data" in fastboot
Click to expand...
Click to collapse
after i put the Zip in Phone memory i wipe Data, System Cache. and the i go to install The rom and Gapps. it goes everything ok but after is finished the phone wont restart it stays in bootloop. The only thing i can do is to go in fastboot again Recovery and install Oxygen os to Lock The bootloader and after locking the bootloader the phone does a full wipe and it starts.
Related
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Controllerboy said:
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Click to expand...
Click to collapse
I would say the answer lies with issues between f2fs and SuperSU
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my SM-P600 using XDA-Developers Legacy app
And you flash the wrong SuperSU, the one needed is either v.2.79 or v.2.79-R3. try booting back to TWRP and clean Flash Lineage again and flash either one of the SuperSu I Mention before.
I have the same after install unofficial lineage 14.1 'decryption unsuccessful'
On TWRP 3.0.3-1 I go in 'wipe', then 'advanced wipe' and select 'Data', press 'Repair or Change File System' and then 'Change File System' to EXT4
That's work fine on my 2017G
For root
download.lineageos.org/extras
The arm64 zip
After install with TWRP go in deployment options and activated it!
Lineage is running with root
Thanks, everyone. That worked. I was quite worried for a while, I really don't want tot RMA the device a second time due tot me messing things up.
Where do I find the options in Twrp for deployment
jdg007 said:
Where do I find the options in Twrp for deployment
Click to expand...
Click to collapse
Twrp have no deployment option, what won't you to do.
joergwrage said:
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Click to expand...
Click to collapse
Probably it is caused by a known bug in the f2fs implementation in the kernel. Only @Unjustified Dev can solve it. Some people who already was using f2fs with TWRP 3.0.4 and LineageOS 13.1 are not having those issues and they were able to dirty flash the new LOS 14.1.
Updating to TWRP 3.0.3-1 is very recommended. TWRP 3.0.2 has some problems when flashing zips. SuperSU is one of them.
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
crazynitro said:
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
Click to expand...
Click to collapse
I have the same
I tried to flash xXx_NoLimits_4.4_OP5_Oxygen_OB01_full (1) my op5 got into a bootloop. and theres nothing left in the phone. twrp shows nothing. cant copy any file from pc when i try to shows an error that cannot copy item-the device has either stopped respondingor has been disconnected.
You can't reboot into bootloader?
Probably best to factory reset through twrp, flash oxygen is 4.5.14 to go back to stable os.
I don't think this needed a new thread^^
Boot into twrp, wipe using "format data" which will wipe your internal storage (since you've already lost your files, you won't lose any now :3 ). And your phone should boot after that. Switching to oreo from nougat needs a "format data" as of now, afaik. Also NOT using the official twrp is recommended.
What TWRP version did you used?
If you've lost everything then just do a "fastboot -w" from command window, then "fastboot flash recovery TWRP.img" (With whichever TWRP build you want to use), then reboot into TWRP and it should appear on your computer as a mounted drive, then copy your stuff over and flash it using TWRP.
Well, the title is misleading. I didn't expect a query.
P.S.: Best to post in the dedicated thread for the ROM. There are more people that can be of help.
Boot in twrp and go in wipe section on twrp and tap on format data then type yes and your phone recognized back on pc and you will be able to copy files on it :good:
Sent from my OnePlus 5 using XDA Labs
Sevral good replies have been given but no sign of life from the one who asked for help. He is indeed f***ked up.
Yousvel said:
Sevral good replies have been given but no sign of life from the one who asked for help. He is indeed f***ked up.
Click to expand...
Click to collapse
Boot fastboot, flash stock recovery, boot it, erase and wipe every thing, boot fastboot, flash TWRP 3.1.1 , copy your rom and flash your rom.
Sorry for my bad english
Go to TWRP, Wipe then to Advanced wipe, Click Data then choose Repair or Change File System, Change file System. Click EXT3 then Swipe to change. after that choose EXT4 and Swipe to Change. hook phone to pc/mac and tranfer your file zip to your phone and reflash it. *this might or might not work. everything will be deleted from phone*.
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Chrono7x said:
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Click to expand...
Click to collapse
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Choose an username... said:
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Click to expand...
Click to collapse
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Chrono7x said:
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Click to expand...
Click to collapse
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Choose an username... said:
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Click to expand...
Click to collapse
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Chrono7x said:
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Click to expand...
Click to collapse
What? No... That's for normal phones. How did you manage to install LOS without knowing that you need the univ. bootloader and modem?
So, you can't access the internal storage via the file manager on TWRP i'm guessing.
Wipe - Format data, after that flash the Universal bootloader, modem, LOS, Magisk, GApps. Magisk takes care of dm-verity and disables encryption. Don't try to uninstall it though or your internal storage will get encrypted as soon as you do. But if you want to change ROMs you can just fpash it before booting and it won't ger encrypted.
Hey, so I can't decrypt my device anymore. Not in Android itself, and not in the recovery. I've tried sideloading no_verity.zip and formatting the system via fastboot, so far nothing helped. When I try to flash the stock rom via sideload, it says it's not readable. I don't know if thats because I didn't decrypt the device before flashing or because the zip is faulty, but I've tried 3 diffrent roms, including one that has worked before.
Is there anything I can do to get my phone working again?
Device: Onepluss 5 6GB
Rom: Omnirom
Install latest codeworkx twrp or blue spark twrp, skip password menu, format data (not wipe), reboot recovery, now wipe everything, then flash what you want
more_than_hater said:
Install latest codeworkx twrp or blue spark twrp, skip password menu, format data (not wipe), reboot recovery, now wipe everything, then flash what you want
Click to expand...
Click to collapse
Thank you! That worked. I figuered formatting data and wiping data would work quite the same, but thanks for proofing me wrong ^^
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)?