Related
I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.
You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.
Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.
If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.
I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?
ostvarivanje said:
I was with Resurrection rom and I took a nandroid backup (as I am doing always when I want to flash a new rom). I flashed the dirty unicorn without knowing that I need to be decrypted (I am encrypted). After being in boot screen for long time I decided to restore nanddroid backup having in otg flash drive. Everything was ok but after some time I had force close to android system, nova launcher and other things I don't remember right now. I decided to flash a new rom (omni) and from that moment and then I can't adjust password for fingerprint. I am aware about /data/system lockscreen.db and other possible files but i had only lockscreen.db. I was removing (I did this procedure for more that 10 times) but when i restarted my phone and set up a new password, after that asked me again to retype the password and every time was incorrect.
I really do not know what else to do. I made a search for long time but I didn't find something else except the guide about data/system I already mentioned and didn't help me.
Can anyone help me because i am right now without any password?
Click to expand...
Click to collapse
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.
preference said:
Back up your app data with swift backup or titanium and wipe every partition except internal. This is assuming you can still get into the rom. I can't tell if you're stuck in TWRP or the rom. If you're stuck in the rom I would wipe all partitions except internal and restore your RR backup then use titanium/swift to back up all your user data then do a clean flash. You can only use encrypted roms from here on out unless you do a format.
Click to expand...
Click to collapse
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close
ostvarivanje said:
Thank you very much for your answer and wiping everything else except internal twrp notify me that there is no os. Actually i found an nandroid backup in my computer from 17th of March (lineage) and i am trying to restore it right now. So... waiting for the results.
Before that i tried to flash again omni rom and in the initial setup i put pattern instead of pin for fingerprint configuration and then it went to the next step without let me configure the fingerprint. When I tried in settings to adjust a lockscreen password or pin or pattern the settings forced close
Click to expand...
Click to collapse
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup
preference said:
When I told you to wipe it was because you had a backup of RR. Do you still have it? Lineage should restore fine if you did the typical default Nandroid backup
Click to expand...
Click to collapse
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.
ostvarivanje said:
I was wrong, the nandroid backup i had was from omni. I finished restoring but again the same thing. I really don't know what to do and in /data/system there is only lockscreen.db file and when i delete it I have the same thing again.
Click to expand...
Click to collapse
Which twrp are you using? Are you on the latest from codeworkx
preference said:
Which twrp are you using? Are you on the latest from codeworkx
Click to expand...
Click to collapse
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem
ostvarivanje said:
Yes, today I put the latest from codeworkx (I think from 9th of March). I even tried official twrp without some changes about my problem
Click to expand...
Click to collapse
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?
preference said:
It sounds like you're locked out permanently. The best bet is restore to RR since that was your last working Nandroid. I have a feeling the lock code will work if you restore to that build.
Did restoring to lineage hell at all?
Click to expand...
Click to collapse
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?
ostvarivanje said:
No, I was wrong and i didn't have linage but omni. Even with RR I couldn't to adjust a password. Now I don't have it anymore.
Is it possible I am the only one with this problem?
Because I have as a secondary device OnePlus 3T I never had a problem like this.
So what's next? Using my phone without lockscreen or there is something to do? Is it a good idea to flash an Oxygene (or oxygene based rom) or there is no any difference?
Click to expand...
Click to collapse
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.
preference said:
You dirty flashed multiple time and tried to hop onto a build that's decrypted by default. You kept trying to save your data and unfortunately you ended up locking yourself out. I'm personally decrypted but have read enough telegram and xda posts to know that the latest codeworkx's recoveries can decrypt the pin. So you basically put yourself into a corner with your actions. Unfortunately you didn't back up your data with titanium or swift. I think you're going to have to fully clean flash (wipe every partition except internal), install a rom and have Google restore your app data. I'm sorry to say this. You can keep trying to avoid it but I think it's your best solution. Don't flash a decrypted rom then try to restore backups without wiping the partitions first. You'll have to start from scratch imo. Maybe someone more experienced can help you.
Click to expand...
Click to collapse
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.
ostvarivanje said:
Let's make things clear. I never flash dirty and always doing wipe everything except internal. Of course i have backup with titanium of all my apps, I don't know how you concluded that I don't have it (maybe it's my fault because english is not my native language). You suggested me to make a fully clean flash (ok, except internal), but this is what i am doing always.
Actually I don't avoid something and i am willing to do everything if i have the result to be able to lock my phone.
Click to expand...
Click to collapse
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.
preference said:
Then I don't understand how the issue is still happening. If you're restoring and doing clean flashed your pin will work. I know this sounds like an attack but it isn't. I'm saying start fresh, and since you have titanium that will only take ten minutes of your time to restore. I'm not trying to say you're stupid or not careful, I'm saying there's likely no solution so why not start over and just use a back up of your app data through titanium? Based on the situation so far, you're making it sound like the pin is essential, so I made assumptions that you didn't have a backup. The solution is to start over. I apologize, your English is very good by the way.
Click to expand...
Click to collapse
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!
ostvarivanje said:
I am flashing roms at least for the 7-8 years (from Samsung Nexus S when it was my first Android phone and earlier from Windows 6). I am always doing a clean flash and always taking titanium backup and nandroid. This is what I did also today. Already I flashed 3-4 roms and restored 2 or 3 times from nandroid with the same result, I can't adjust pin no matter if I am doing that in initial setup for fingerprint or in settings.
About pin I faced the same thing before a month when I tried to flash omni rom. And then I found a guide about not setting up a pin in initial setup but to finish the initial setup and to restart the phone to twrp and with the file manager to remove files related to lockscreen from /data/system. I followed this guide and everything was great, after restarting my phone I could set up a new pin. But today is a nightmare. I am trying to resolve this problem from last night!
Click to expand...
Click to collapse
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.
preference said:
Yeah man the only choice I see is a full format or wipe all partitions. I hate saying that but if your phone is stuck at the pin entry on every rom there is a bug occurring that might need to be completely wet to default, which a format will do. Let me know if someone is more helpful and you figure it out, I've never heard of a pin entry issue across multiple roms.
Click to expand...
Click to collapse
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?
ostvarivanje said:
So we arrived in the end, i mean i need to format internal storage, right? So I will firstly transfer my files to my computer and then i will do that. But is it sure that will resolve the problem. And one more thing. Do i need to make my phone decrypted now when i will remove everhyting from my phone? Some roms have compatibility with encrypted and some others with decrypted. I think somewhere that you can flash to the decrypted phone a rom for encrypted phones with flashing something but i am not sure. For now i thing that mostly rom for oneplus 5t are for encrypted phones, right?
Click to expand...
Click to collapse
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.
preference said:
To stay decrypted flash no verity v2 zip after flashing rom and gapps. Magisk enforces the no encrypt along with the no verity zip.
When you format your phone you will be fully decrypted. If you want to stay decrypted then flash rom, gapps, no verity then boot. Configure your ROM then reboot to recovery after first fill boot. Flash magisk, it should force encrypt.
If you're paranoid about losing decryption then do what u do. - flash no verity after everything. It won't break anything.
I attached the one that works so you don't have to worry about tracking it down. Again you can flash this after flashing any file.
Click to expand...
Click to collapse
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.
ostvarivanje said:
Thank you very much for the instructions. Actually I am confused if I need to stay decrypted or not. That means, if i have a rom for encrypted phones and i want to flash a new one for decrypted the only thing i need to do is to flash in the end the no verity zip? In advance, I need to do the same when i restart to twrp to flash the magisk then again no verity?
Is your file you posted correct? Because its filename is op5 and not op5t, except if it's the same.
Click to expand...
Click to collapse
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)
preference said:
It's the same, works on both devices. There isn't a special one for the 5t.
If you want to try all roms, stay decrypted. All roms appear to work on decrypted phones.
If you want to stay encrypted, then you can only use roms that support force encryption. So you wouldn't be able to flash a rom like DU.
I personally stay decrypted because it's easier to back up and restore roms. It's all a personal choice. If you go encrypted you just might miss out on a couple roms. Most support force encrypt.
Just remember:
Decrypt and first boot = flash rom, gapps, no verity on first flash. Then boot/start the rom and configure rom. Reboot to recovery after finishing first boot and install magisk or superSU. Optionally flash no verity but it's not needed.
Decrypt and any rom update flash = flash rom, no verity, flash gapps if your ROM requires it (ask first, only a few roms like liquid remix require this)
Encrypted and first boot = flash rom, gapps, boot into rom, reboot back into recovery, flash magisk/superSU
Encrypted and update = flash updated rom file, optionally flash gapps if your ROM requires it (again ask in the thread or on telegram for this info)
Click to expand...
Click to collapse
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!
ostvarivanje said:
I just finished with the backup of my files. So if i want to flash a rom like du i need in the end to flash no verity but if it's for encrypted i don't need it. So with this way i can flash every rom i can find.
One more thing, wiping everything (every partition) getting the phone decrypted? I mean that i don't need to do something else?
Your help is more than important for me. I really appreciate it and thank you for that!
Click to expand...
Click to collapse
You can't use normal wipe, go to wipe then choose the option on the right (I think it says wipe device) and then it will tell you to type "yes". If you type yes then hit enter it will format the phone. That's a true format and it will decrypt your device. You can't just wipe all partitions because it's not a complete format.
So if you typed "yes" in TWRP you have a formatted phone. It will stay decrypted until you flash an encrypted rom.
So if you flash DU, you don't need no verity because the rom is decrypted. If you flash RR 6.0 then your phone will encrypt UNLESS you flash no verity. So the file I gave you is a way to stop encryption on encrypted roms.
You flash RR 6.0, gapps, no verity = RR but no encryption.
You flash DU, gapps = decrypted rom so you don't need no verity zip
Most roms are encrypted, so you flash rom, gapps, no verity to stay decrypted. The zip I gave you should be flashed after flashing rom and gapps on every encrypted rom if you want to stay decrypted.
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse
Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?
lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
A Lineage OS rom is still under development and not released yet. Have you tried flashing the stock image (6.2.7.1)? Flash this in recovery, to see if it fixes the update error. You may need to flash Magisk to be rooted again. And this stock image WILL NOT overwrite TWRP. The prerooted roms that are released have Magisk built in so there's nothing different between those and the stock image in which has no root at all. Let me know if you have any questions!
Stock Image for Fire TV Stick 4K: https://drive.google.com/open?id=1LlOFUO8o_8GKm-kQLR9QCMmql2Zyu8W8
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a pre-rooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
From what I have seen, the tutorial for flashing the prerooted is really a dirty flash, and certainly from my experience (where I forgot to reset the device before flashing the image) all my apps were still there.
I'm sure you can wipe your system & data partition from TWRP, and then flash the image.
The only problem I can foresee is that the pre-rooted image might not be a full image which would cause your Firestick not to boot.
I suggest you head over to the pre-rooted image thread and ask if it's ok to wipe those partitions and also what the actual commands are.
I'm curious also - just for future reference....
p.s I just found this
https://twrp.me/faq/openrecoveryscript.html
which lists TWRP's commands, Just check first to see if it's safe to wipe those partitions.
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
I think the system partition would be the important one to wipe, data is mostly user data from what I remember.
If Skel40's link is a full image (as the prerooted one i might be), then maybe do all the wipes and try that one 1st..
Normally when I use TWRP I don't dirty flash, and I wipe system,data,dalvik,cache...
Good luck with whatever you try
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
You need to wipe system, data, dalvik-cache, and cache before flashing. Upon boot up after flashing 6.2.7.1, it skips the updates, I have a backup if needed!
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Retch_100 said:
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Click to expand...
Click to collapse
You wiped everything (data, system, internal, cache, dalvik). There is nothing else, if you are flashing the full stock upgrade image. The device finds remote, connects to bluetooth, then finds Wifi, connects to wifi. Then the device errors (when checking for an update). Since you bought this device used, i highly suspect the device is blacklisted. Firestick 4k's are on sale for $25 again. I would cut my loses and hope someday for a custom (you can ask for a copy of the buggy one diegocr and Rortiz2 over in the tank 12.1 thread. But it is likely unusable at this time.
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Retch_100 said:
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Click to expand...
Click to collapse
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Michajin said:
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Click to expand...
Click to collapse
Okay thanks I will see.
BTW: the Stick does not have any value to me anymore, so bricking it would be okay if I learned something this way
But it'd be better if the Stick could be resurrected to work as a Stick.
Maybe anything of this.
Pass OOBE:
==========
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
pm disable com.amazon.tv.oobe
Your fire stick blacklisted by Amazon.
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Try going into BOOTLOADER to use fastboot instead of fastboot(d), if at all possible.
force reboot to twrp
then wipe cache, select reboot then select system
Raunaksaha2008 said:
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Click to expand...
Click to collapse
I'm glad you posted this, I did the exact same thing yesterday and had the exact same problem. I'm Normally extremely experienced with this stuff I've even made custom roms. This one caught me off guard because I've only had the phone 2 weeks and this was the 2nd custom rom I flashed. Long story short nothing worked and I had to flash miflash stock firmware. Than I tried it again and it did it again. So I flashed the zip before I was already on and everything worked. I don't understand backups with this phone sometimes they backup but I don't believe they will work to restore.
I have never had to say this, there is nothing you can do. You have to flash stock and go back it sucks and I hate it but it is what it is.
hroen_al said:
force reboot to twrp
then wipe cache, select reboot then select system
Click to expand...
Click to collapse
Tried, didn't work
Raunaksaha2008 said:
I was using xiaomi.eu rom V12.5.14.0.RKHCNXM on my Mi 11x (aliothin) installed using the @gogocar62 method using TWRP.
Today i downloaded xiaomi.eu_multi_HMK40_POCOF3_V12.5.18.0.RKHCNXM_v12-11.zip and installed it via permanent twrp 3.5.1 (nebrassy) which was already on my phone.
Since it was just an update, i didn't wipe data. After reboot, phone booted into recovery and there was no sign of my data neither was i being to decrypt data or mount partitions.
Steps I've already done till now -
1. Booted into fastboot, ran temporary twrp 3.5.2. it was able to decrypt data and i could take a backup.
2. Tried changing current slot to a, then to b.
3. Tried wiping data without formatting data.
@gogocar62 can you please tell what's wrong and help me boot into system without data loss?
Also, i downloaded the weekly Android 12 version of xiaomi.eu rom too but i read somewhere that flashing fastboot rom causes critical changes to some partitions and system files and changes it to chinese rom. Is fastboot rom not recommended then?
Thank you.
Click to expand...
Click to collapse
now its not booting into recovery. only fastboot. run twrp bat command file is not working with it anymore.
Raunaksaha2008 said:
now its not booting into recovery. only fastboot. run twrp bat command file is not working with it anymore.
Click to expand...
Click to collapse
could boot into recovery. backed up whatever i could. flashed fastboot xiaomi.eu rom without data wipe (upgrade mode). System was showing issues - permissions stopped working, couldnt find refresh rate settings, apps were misbehaving, general lag. Now trying to flash again with data wipe. If nothing else works, have to go back to original stock rom with mi flash.
Raunaksaha2008 said:
could boot into recovery. backed up whatever i could. flashed fastboot xiaomi.eu rom without data wipe (upgrade mode). System was showing issues - permissions stopped working, couldnt find refresh rate settings, apps were misbehaving, general lag. Now trying to flash again with data wipe. If nothing else works, have to go back to original stock rom with mi flash.
Click to expand...
Click to collapse
Well did it work or did you have to go back to stock? I told you nothing works and I'm not lying I'm extremely experienced with this stuff. I root every device I can get my hands on. This phone is beyond difficult to flash roms with. The problem is you really need to go back to stock everytime you flash a custom rom to make sure it works.
I know when I said my first comment your hoping to god that you don't have to start from scratch but I tried a bunch of stuff to I just didn't feel like explaining it all. I flashed both twrps and tried I reflshed the rom and I did format data and still didn't work. It screws up the system partition layout and nothing reads right.
Went back to stock. Android 12 on xiaomi.eu rom doesn't have refresh rate settings and we are stuck on 60Hz. And also backing up, restoring everytime is a pain and waste of time. Will stick to stock for now.
Raunaksaha2008 said:
Went back to stock. Android 12 on xiaomi.eu rom doesn't have refresh rate settings and we are stuck on 60Hz. And also backing up, restoring everytime is a pain and waste of time. Will stick to stock for now.
Click to expand...
Click to collapse
I told you, I will say it again this phone for custom roms kinda sucks. It can be done but it's always you have to start from scratch Everytime and roll the dice and hope it works. Good luck I would still root stock though
The way everything breaks made me worried that the phone would hard brick if I kept trying stuff. Either that or some how wipe out fastboot and than it would be like a hard brick because nothing would work to fix it. It's a scary phone to mess with. The problem comes from the A/B partitions because XDA developers aren't really developers their just people who read online instructions on putting source code together and don't actually know how to code or fix anything. They get way to much credit. Topjohnwu is a real developer and that's why Google bought him
Facing issues again. Netflix app not showing in Play store. Device is not play protect certified even after flashing official Rom via mi flash.
Techguy777 said:
The way everything breaks made me worried that the phone would hard brick if I kept trying stuff. Either that or some how wipe out fastboot and than it would be like a hard brick because nothing would work to fix it. It's a scary phone to mess with. The problem comes from the A/B partitions because XDA developers aren't really developers their just people who read online instructions on putting source code together and don't actually know how to code or fix anything. They get way to much credit. Topjohnwu is a real developer and that's why Google bought him
Click to expand...
Click to collapse
i agree, flashing stock each time and booting once before flashing each custom rom seems the way to go. i know you're experienced - more than i - but in case you don't know... here's a couple of good apps for backing up apps etc that have worked well when moving from rom to rom (just save/copy whole swiftbackup folder with backed up apps to pc/laptop).
after moving rom, i select 'restore' from google backup but deselect apps (that's all done with seperate app below). that restores a fair bit, including some settings depending on the rom before and after flash. then install swift backup on my rooted device, copy swiftbackup folder back onto phone and restore apps with all data etc (+ anything else you have that didn't restore from google backup). swiftbackup can even backup and restore your wallpaper/screensaver, wifi passwords etc. it's so much better than the outdated titanium backup, which i find unreliable these days.
another alternative is alpha backup pro, another paid app but apparently worth it. sometimes it's on offer or free. i got it when it was free but haven't tried it as swift works well for me. alpha backup
note: i am not affiliated with either of these apps, just making you aware of a backup alternative as TWRP data backups, for me and with this phone, are a no go. also note, i don't backup system stuff when moving to a different rom, only installed apps.
like i say, no doubt you are aware of these options but thought i would post just in case.
reg66 said:
i agree, flashing stock each time and booting once before flashing each custom rom seems the way to go. i know you're experienced - more than i - but in case you don't know... here's a couple of good apps for backing up apps etc that have worked well when moving from rom to rom (just save/copy whole swiftbackup folder with backed up apps to pc/laptop).
after moving rom, i select 'restore' from google backup but deselect apps (that's all done with seperate app below). that restores a fair bit, including some settings depending on the rom before and after flash. then install swift backup on my rooted device, copy swiftbackup folder back onto phone and restore apps with all data etc (+ anything else you have that didn't restore from google backup). swiftbackup can even backup and restore your wallpaper/screensaver, wifi passwords etc. it's so much better than the outdated titanium backup, which i find unreliable these days.
another alternative is alpha backup pro, another paid app but apparently worth it. sometimes it's on offer or free. i got it when it was free but haven't tried it as swift works well for me. alpha backup
note: i am not affiliated with either of these apps, just making you aware of a backup alternative as TWRP data backups, for me and with this phone, are a no go. also note, i don't backup system stuff when moving to a different rom, only installed apps.
like i say, no doubt you are aware of these options but thought i would post just in case.
Click to expand...
Click to collapse
I am using swift backup right now actually as I was reading this and yes I do the same thing copy folder to the USB C drive. It's the only app I've bought in a year. Thank you for at least making a comment of some depth. I get burned out at xda because everyone doesn't say anything they just want answers for their problems and don't contribute to xda.
I did not know about the other app so I will be looking into it. Normally I wouldn't say this but buy Swift back and you get cloud storage. I'm like you I restore apps with an app and I will be using Xiaomi cloud now but also Google. Another app is migrate it's the best for flashing roms it restores your apps and data from twrp well not quite once you reboot.
I thanl you again because maybe I didn't know about Swift back it's important people respond.
Is 120Hz working on your mi11x with xiaomi.eu? It doesn't work on mine.
chratoc said:
Is 120Hz working on your mi11x with xiaomi.eu? It doesn't work on mine.
Click to expand...
Click to collapse
Yes it is, on the latest stable but not on the latest Android 12 beta.