Develop Bugs

[please close]Can't flash any other rom after flashing the Android 6.0 gpe rom

Hey guys, hope someone can help me. A few days ago i've flashed the new android m gpe rom and everything was fine. Then somehow i lost root access and tried to fix it. Unfortunately, i'm not even able to flash the fixed rom that was posted a few days later, so i decided to come back to the skydragon sense rom. And for some reason i can't. I try to flash the .zip, it opens in aroma installer, everything goes fine until the installation itself starts. The rom starts to flash, comes to ~20% and then the system just reboots. I've tried both twrp and filz touch, nothing helps.Also supersu doesn't flash properly. I'm not really professional in this, so i might just do somethng wrong, hope someone can help:crying:
Btw i'm s-on.
UPD: I've made an advanced wipe and the everything works now, so if you have the same problem then just try to do the same, see if works.

Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?

redpoint73 said:
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
Click to expand...
Click to collapse
I just flashed the GPE ROM, i'm s-on as i said.

Would this ROM work on Verizon HTC One M8
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help

Are you still able to go into TWRP recovery and are you also rooted?

crispinsaro said:
Are you still able to go into TWRP recovery and are you also rooted?
Click to expand...
Click to collapse
Who was this question adreed to? If you asked me, then i am able to get into recovery, but the supersu doesn't seem to flash, at least i don't get the root.

Miramontes said:
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Click to expand...
Click to collapse
Well, the problem is that i'm s-on, so i hope there is any other solution for this

Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?

paulmartyn said:
I've tried both twrp and filz touch, nothing helps.
Click to expand...
Click to collapse
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
Miramontes said:
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue
Click to expand...
Click to collapse
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.

crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
Will try to erase everything later,maybe tomorrow. Twrp says everything's fine, and aroma doesn't say about any issues, just reboots. Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is. Anyway, thanks for an advice, will try that and tell if it helps or not

redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
I tried filz just to check, because on skydragon everything was fine.
I use twrp 2.8.7.0
hboot 3.19.0.0000
radio 1.25.21331147a1.o6g(if that's what baseband is)
tomorrow i'll try everything you guys advised, see if there is a solution. thanks for the support man

Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!

crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
well, i've tried to make an adwanced wipe as you advised and it worked thanks man, i thought i'll stay on that rom 4ever.
flashing skydragon now:victory:

crispinsaro said:
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
Click to expand...
Click to collapse
guess the problem was caused by different android versions

redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
So i've tried to make a FULL wipe and finally it worked, everithing works fine now, installin' skydragon and waiting for a better 6.0 ROM

Guess i can close the thread now as my problem is resolved.

paulmartyn said:
Guess i can close the thread now as my problem is resolved.
Click to expand...
Click to collapse
Happy that solved your issue, it is normally said that to install a new rom you have to do a full wipe before hand, glad it worked for you though

paulmartyn said:
Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is.
Click to expand...
Click to collapse
You mean flashing SuperSU after Skydragon (you don't specify)? If so, its not necessary, as all custom ROMs are pre-rooted unless explicitly noted.
Also, older versions of SuperSU won't work on Lollipop, so depending on what version SuperSU you tried (again, you don't specify), that may have been the reason for failure.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
crispinsaro said:
I am sure you factory reset through recovery before installing the new ROM
Click to expand...
Click to collapse
I wouldn't be so sure, if the OP didn't state it.
crispinsaro said:
I normally go on advanced wipe and tick all the boxes
Click to expand...
Click to collapse
I would caution users about following this device literally. It is not necessary to wipe internal storage and/or SD card when flashing a ROM (although particular users may have reason to do so for specific reasons). And if the user has their nandroid or ROM.zip on that partition (and they must have the ROM on one of those, unless they intend to sideload it), its going to get wiped out; causing some confusion and probably panic.
The advice I normally give is: Its called "Advanced" for a reason, and don't wipe it unless you know what the result will be; and you have a legitimate reason to do so.
For instance, I've lost count of the times folks have posted that they wiped system, and don't understand why the phone will no longer boot into OS. Or they wiped internal storage or SD card; and didn't know that it would wipe out their nandroids.
The TWRP default wipe (data, cache and Dalvik) says "most of the time, this is the only wipe you will ever need" and it says that for a reason. If one runs into problems flashing a ROM, they might elect to wipe system. So like I said, a legitimate reason to wipe a particular partition.
But on the other hand, I've done a countless number of ROM flashes on a number of devices (including Skydragon), and never wiped any partition outside the "default wipe", and never had any such issues. Even wiping system (which many swear by) I suspect is often a placebo. When you flash a ROM, system will be wiped by definition, so doing it manually is redundant.
I suspect the failure by the OP was not wiping data and/or cache (they never specified they did that originally or not).

Thats true yes, i dont think I made it clear to do the default TWRP wipe first to see if it would solve anything and then try advanced wipe if all fails, but again with caution.

After reading a litte I've got one question...So if I want GPE rom do I need to convert my phone to GPE or just to flash the rom ?!

Would you consider this a clean install?

Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!

ivan.panchev said:
Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!
Click to expand...
Click to collapse
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system

Lowxorx said:
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system
Click to expand...
Click to collapse
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!

ivan.panchev said:
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!
Click to expand...
Click to collapse
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )

Lowxorx said:
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )
Click to expand...
Click to collapse
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!

ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you have the stock 3.2.6 zip file you can follow theses instructions on the official oneplus site. There are both TWRP and stock recovery guide.

ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"

noobtoob said:
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"
Click to expand...
Click to collapse
After the second full charge, I think the things are a lot better - I have only used it for 30 minutes screen on today but is still on 82% (with more than 10 hours idle), which a lot like what I used to have when with 3.2.1. Plus, I am in an area with low network coverage, so that's draining the battery as well. Thanks for all of your answers, if I feel the need, will probably flash the whole stock rom with TWRP.

Need help with Nandroid

Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!

M5devil said:
Hi Guys, I am sorry if I sound ignorant, I am honestly stuck in limbo here and need some assistance...
I was on Freedom OS 2.1 prior to moving to OB3. Before the move, I backed up fully my Freedom OS 2.1. When I flashed OB3, I didn't realize that I didn't have to do full wipe and could just dirty flash OB3. I now want to restore my nandroid backup, but I am running into a problem where it boot loops and when I boot into recovery I don't get to see the pin code unlock to decrypt the phone, therefore can't see my data partition. I was able to get back my partition and reinstall OB3... Please can someone guide me, how to properly restore my nandroid backup, so my data partition doesn't disappear and Freedom OS 2.1 boots up?
Thank you!
Click to expand...
Click to collapse
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.

Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Dazed No More said:
Youll have to wipe the phone completely from stock recovery, flash the full 4.7.4 zip and finally flash twrp Image from fastboot then you'll be able to restore your backup.
https://forum.xda-developers.com/showpost.php?p=75096633&postcount=1
Forgot to mention, be sure to backup your internal storage first because you will he wiping everything.
Click to expand...
Click to collapse
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...

M5devil said:
Thanks for your assistance! I think I missed something somewhere...
I rebooted to stock recovery (on OB3) and wiped the internal storage. Next I tried flash the 4.7.4 zip via adb sideload and after about 10 min recovery screen returned, but I'm still on OB3 after reboot. Please tell me what am I missing. I am not sure how to flash 4.7.4 zip. I will try now to wipe again internal storage, boot into OB3 and copy the 4.7.4 in windows and try to flash it from stock recovery. I read the link you posted and read from post 19 in OP that's downgrading from OB1/2 and I assume OB3 too -- back to OOS 4.7.x is troublesome and WIFI gets lost. I'm hoping that won't be the case where I am simply trying to do a nadroid restore.
Had no idea this is going to be so difficult...
Click to expand...
Click to collapse
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .

Dazed No More said:
- Wipe everything from stock recovery
- Reboot to fastboot from stock recovery
- Run command fastboot boot twrp.img, then transfer the 4.7.4 over mtp
- Flash 4.7.4 zip
- Reboot
Then let it boot and you can re root after that. Have faith that you are one of the luxjy ones whose WiFi is unaffected and works .
Click to expand...
Click to collapse
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!

M5devil said:
Thanks, man! I appreciate it. I was able to successfully get back to my Freedom OS via nandroid restore. Everything is back to normal aside from few hiccups, like no can't view and download images on telegram app for some reason. Uninstalled reinstalled, just see spinning logo but no images.
Other than that. Thank you!
Click to expand...
Click to collapse
Wifi works?

Dazed No More said:
Wifi works?
Click to expand...
Click to collapse
Yes, Wi-Fi works!

M5devil said:
Yes, Wi-Fi works!
Click to expand...
Click to collapse
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.

Dazed No More said:
I wish I was that lucky. I dont know what it is with my device but wifi just will not work when reverting back to Nougat...Ive spent so much time flashing official zips trying to get it back before finding the right combination.
Click to expand...
Click to collapse
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!

M5devil said:
I ended up going back to OB3. I suggest you do the same. Battery life is much much better and phone feels much snappier. Have you tried any 8.1 ROMs? I always preferred the pure vanilla look, so was wondering which 8.1 ROM is good. Thanks!
Click to expand...
Click to collapse
I won't go back to an Oreo OOS until audio controls for wired and wireless headphones work. I've tried codename phoenix, liquid remix, AICP and validus. I personally liked validus the most and aicp second.

Fire TV 4k not possible to set up

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.

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.