Fire TV 4k not possible to set up - Fire TV Q&A, Help & Troubleshooting

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.

Related

[Q] TWRP asking for encryption password after factory reset?

Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
eris170 said:
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
Click to expand...
Click to collapse
A factory reset from inside TWRP does NOT wipe internal storage/sdcard. If you want to wipe everything you can either do it from inside TWRP with "advanced wipe" or just do a normal factory reset from Settings/Backup and reset. If you fastboot flash the userdata and cache images that would also be like a factory reset. If you wipe/erase the system you will need to fastboot flash the system image or flash a rom BEFORE you try and reboot.
wantabe said:
A factory reset from inside TWRP does NOT wipe internal storage/sdcard.
Click to expand...
Click to collapse
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else. When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things.
Should I just go find the stock OS image and recovery image and flash them over?
eris170 said:
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else.
Click to expand...
Click to collapse
I'm pretty sure that wiping data from inside advanced wipe will have wiped everything, that should have been enough to get rid of your encryption.
eris170 said:
When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
Click to expand...
Click to collapse
No. The system image I was talking about is from the factory image. You have to extract/unzip the factory image a couple times before you can see the zip folder with all the images ( boot (kernel), cache, recovery, system and userdata). You had mentioned in your first post "erasing userdata, system and cache." If you erase system you will need to replace it otherwise your device does not have an os (operating system) anymore. One of many ways to replace it would be to fastboot flash the system image (fastboot flash system system.img) that is extracted from the factory image.
eris170 said:
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things
Click to expand...
Click to collapse
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
eris170 said:
Should I just go find the stock OS image and recovery image and flash them over?
Click to expand...
Click to collapse
I think in your case the easiest thing to do would be to flash the factory image and start over. You will then need to reinstall TWRP and then use TWRP to install/flash the supersu zip. My advice would be to do lots of research before flashing custom roms and custom kernels. After you get back to the factory rom you really need to use TWRP to do a backup (nandroid) BEFORE you flash any custom roms and kernels, with that done it will be easy as hell to get back to stock after experimenting with whatever! Don't rely on toolkits, install the android sdk and learn adb fastboot commands, it's not hard, hell even I can do it!
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
I've never used this but looks interesting. [TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)
wantabe said:
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
Click to expand...
Click to collapse
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
wantabe said:
I think in your case the easiest thing to do would be to flash the factory image and start over.
Click to expand...
Click to collapse
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
eris170 said:
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
Click to expand...
Click to collapse
One of the great things about android is having the ability to change what you don't like and for the most part it isn't hard to do. I did notice with the update to 4.4 better performance and fluidity on both my N5 and N7 so it might be worth checking out at some point. I didn't care for some of the changes like the ui sounds with the 4.4.1 update but it's all easy to modify. Anyway.. glad you got it sorted out.

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​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.

Stuck with Twrp booting

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.

Blank App?

I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
NewbRooter89 said:
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
Click to expand...
Click to collapse
if you flashed anything other than lineage you deserve what you are getting
flash713 said:
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
Click to expand...
Click to collapse
I just ended up deleting everything and flashing a whole new ROM. I was on Lineage 17 but kept having so many bugs that I decided to try a different one. Thanks for the advice though.
sudoxd said:
if you flashed anything other than lineage you deserve what you are getting
Click to expand...
Click to collapse
That's what I was using and I had so many bugs and issues with it.
NewbRooter89 said:
That's what I was using and I had so many bugs and issues with it.
Click to expand...
Click to collapse
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
flash713 said:
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
Click to expand...
Click to collapse
you dont even need to flash the factory image, will work fine flashing from whatever they have now
sudoxd said:
you dont even need to flash the factory image, will work fine flashing from whatever they have now
Click to expand...
Click to collapse
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
flash713 said:
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
Click to expand...
Click to collapse
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
sudoxd said:
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
Click to expand...
Click to collapse
But I love to flash factory image. Jkjk. ?? The reason I had initially posted that on my comment was because I thought if anything wasn't right on his setup it would square it away or if something was left from another past install on sdcard it would clear it all up. Sure a format data in twrp will do same I just thought of that as an easy thing to say that had a zero % chance of being misunderstood. And what if he was on 9.0? ? That's just how I thought at that moment when I commented that. I know Lineage 17 build for Marlin is damn near flawless. I've been using it off and on since it came out. I see you are the dev who makes that kernel. Saw your link to your work. I remember you from long ago (i used to have another user name but had my account deleted a while back) on some Nexus device everyone and their mom owned. Maybe the 5 or 5x or the Gnex idk but I remember your kernel because it was bad ass.
It probably was something on my end. This is the first phone I've rooted with the A/B slots. I also did it through adb sideload because I was having issues with TWRP. I was also stuck in a bootloop when I installed it. Maybe I'll give it another shot. I did really like having Android 10 and my battery life was much better with lineage.

Question Mi 11x (aliothin) not booting after updating xiaomi.eu rom through twrp

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.

Categories

Resources