Develop Bugs

Official XIAOMI.EU TWRP

The best recovery for our Mi5, and the only one without any bug now. Believe me.
Just flash the recovery. Forget the boot.IMG if you are not on the xiaomi. Eu rom
https://www.androidfilehost.com/?fid=24499762636006354
Released the 23 April by Jemmini.

nesquix said:
The best recovery for our Mi5, and the only one without any bug now. Believe me.
https://www.androidfilehost.com/?fid=24499762636006354
Released the 23 April by Jemmini.
Click to expand...
Click to collapse
How we can flash it? With fastboot or with recovery?!

i used flashify.. worked fine, but is this the latest recovery? how come its not 3.0.20?

I was not aware Flashify works with Mi5. Good to know

guys can u help me ? after flashing both recovery and boot.img included in the downloaded file, my wifi stopped working, the switch keep turning off. do you know how to fix this ?
thx in advance

vonbraun said:
guys can u help me ? after flashing both recovery and boot.img included in the downloaded file, my wifi stopped working, the switch keep turning off. do you know how to fix this ?
thx in advance
Click to expand...
Click to collapse
I think you shouldn't flash boot.img if you aren't using xiaomi.eu rom. Because It is a modified kernel that disable encryption especially used in xiaomi.eu rom.
To fix it you can try flashing original boot.img from your official version of MIUI of course from fastboot rom.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
nesquix said:
The best recovery for our Mi5, and the only one without any bug now. Believe me.
https://www.androidfilehost.com/?fid=24499762636006354
Released the 23 April by Jemmini.
Click to expand...
Click to collapse
I suggest you to give extra information that only twrp should be flashed if they aren't using xiaomi.eu currently. Because the downloaded file contain twrp and boot.img

pramyhoga said:
I think you shouldn't flash boot.img if you aren't using xiaomi.eu rom. Because It is a modified kernel that disable encryption especially used in xiaomi.eu rom.
To fix it you can try flashing original boot.img from your official version of MIUI of course from fastboot rom.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
I suggest you to give extra information that only twrp should be flashed if they aren't using xiaomi.eu currently. Because the downloaded file contain twrp and boot.img
Click to expand...
Click to collapse
Correct susee, sorry and thank you.
Of course you should just flash the recovery.

same touch not working bug like in the cofface TWRP

I found a workaround but you need your cable and computer.
Just before the TWRP logo comes up, plug in and unplug the USB cable to the phone a few times in succession and touch suddenly magically works.
Still not much we can do without a computer mind you...
Sent from my MI 5 using XDA-Developers mobile app

After flashing a rom , the recovery touchscreen is not working .

Is there any proper fixes for the touchscreen issues in twrp?

waiting some minutes without touch nothing, and then touchscreen works..for me it's ok

zicoxx said:
waiting some minutes without touch nothing, and then touchscreen works..for me it's ok
Click to expand...
Click to collapse
Confirmed. Just let the screen fade out and wait couple minutes.

I also found booting into twrp with the charger connected to my laptop made it work straight away... Weird tho

There is an updated version of twrp and the touch issue seems to be gone. V 6.5.7.
https://www.androidfilehost.com/?fid=24533103863138514
Brief Instructions for fastboot flash.
fastboot flash recovery recovery.img
fastboot boot recovery.img

Can I install that new TWRP by the current TWRP?

If you have the zip, I bet you can.

I download the zip but it doesn't work.

Well, I mean the right zip. This is only the img file compressed.

j2002 said:
Well, I mean the right zip. This is only the img file compressed.
Click to expand...
Click to collapse
Yeahh!! Work.

Pixel XL Uberstock Testing

I am looking for some testers for my rom on Pixel XL, we currently have a build up on https://temp.bbqdroid.org/
It is a flashable zip and you should have a backup from twrp on your pc before flashing.
To keep TWRP you will likely need to flash ROM + Gapps, TWRP zip and then supersu.
Tester hangout: https://hangouts.google.com/group/5Ymr3GHPJdMUcf5j1

I'm getting page cannot be displayed.

pro_b said:
I'm getting page cannot be displayed.
Click to expand...
Click to collapse
Same here brother...I'm guessing we should give it a little more time?

pro_b said:
I'm getting page cannot be displayed.
Click to expand...
Click to collapse
BakedTator said:
Same here brother...I'm guessing we should give it a little more time?
Click to expand...
Click to collapse
sorry correct link is https://temp.bbqdroid.org

Thanks. Downloading now. I've been off the aosp scene for a while. Would anyone have a link to the gapps needed for this rom?

pro_b said:
Thanks. Downloading now. I've been off the aosp scene for a while. Would anyone have a link to the gapps needed for this rom?
Click to expand...
Click to collapse
Try opengapps aroma, 7.1 arm64, you may need to install webview, if you need further assistance there is a hangouts group https://hangouts.google.com/group/5Ymr3GHPJdMUcf5j1

mdalexca said:
Try opengapps aroma, 7.1 arm64, you may need to install webview, if you need further assistance there is a hangouts group https://hangouts.google.com/group/5Ymr3GHPJdMUcf5j1
Click to expand...
Click to collapse
Matt, will that flash in TWRP? Wasn't sure a payload OTA could be recovery flashed. At least not without modification of the script.
---------- Post added at 05:44 AM ---------- Previous post was at 05:26 AM ----------
pro_b said:
Thanks. Downloading now. I've been off the aosp scene for a while. Would anyone have a link to the gapps needed for this rom?
Click to expand...
Click to collapse
Just a heads up. I looked at the script and if you want to flash it , you'll need to adb sideload it as the script needs modification for TWRP.

How well does the build work? OMS Full? As on the 6P?
Or better asked, what does not work? I like the Rome on the N6P and would like to use it here but at the moment much work and no time to test. A short answer would be nice, thanks.

Tylog said:
How well does the build work? OMS Full? As on the 6P?
Or better asked, what does not work? I like the Rome on the N6P and would like to use it here but at the moment much work and no time to test. A short answer would be nice, thanks.
Click to expand...
Click to collapse
flash it and you will see
Sent from my Google Pixel XL using XDA Labs

I am working on a new build right now.

Ok:good:
Sent from my Pixel XL using XDA Labs

Will there be a pixel build?

freddienuxx said:
flash it and you will see
Click to expand...
Click to collapse
Read what I say and understand.

zaksimmermon said:
Will there be a pixel build?
Click to expand...
Click to collapse
Yeah, just getting marlin working first since I have the device

I tried flashing the zip in TWRP RC1 and there were no errors but TWRP says there is no OS installed.
Can't seem to get ADB sideload working on my computer to try that method.
---------- Post added at 03:30 PM ---------- Previous post was at 03:03 PM ----------
No OS installed after doing ADB sideload either.
HTML:
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb devices
List of devices attached
HTxxxxxxxxx sideload
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb sideload uber_marlin-2016-12-20.zip
Total xfer: 1.00x
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>
EDIT: My file size is only 215MB so I probably got a bad download. doh.
EDIT 2: Nope, re-downloaded and got same exact file size.

CZ Eddie said:
I tried flashing the zip in TWRP RC1 and there were no errors but TWRP says there is no OS installed.
Can't seem to get ADB sideload working on my computer to try that method.
---------- Post added at 03:30 PM ---------- Previous post was at 03:03 PM ----------
No OS installed after doing ADB sideload either.
HTML:
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb devices
List of devices attached
HTxxxxxxxxx sideload
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb sideload uber_marlin-2016-12-20.zip
Total xfer: 1.00x
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>
EDIT: My file size is only 215MB so I probably got a bad download. doh.
EDIT 2: Nope, re-downloaded and got same exact file size.
Click to expand...
Click to collapse
That's how TWRP always reads, it even has this problem with DU from what I read, I am working on a new build, I just need to upload it now

mdalexca said:
That's how TWRP always reads, it even has this problem with DU from what I read, I am working on a new build, I just need to upload it now
Click to expand...
Click to collapse
If you wipe system then flash the rom when you go to reboot it will say no OS installed. When you flash the rom it's flashing to the other partition so no need to wipe system and when you reboot it switches slots. If you just factory reset you won't get the no OS installed message.

Interesting.
Yeah, I did wipe /system.

Guys, its a bit ot but i had the following issue with installing DU on my sailfish:
I wiped System, data, Cache, flashed DU and so on... Then twrp said no OS installed. Ich accidentally rebooted system and did not reboot bootloader.
Screen turned off, hard brick because twrp (or what Else?) swapped boot partition to b (no bootloader installed).
As you can imagine, im pretty frightened to flash anything but weta rom for now on my new pixel (google rma...).
Is this caused by twrp, du or what?

blaze9090 said:
Guys, its a bit ot but i had the following issue with installing DU on my sailfish:
I wiped System, data, Cache, flashed DU and so on... Then twrp said no OS installed. Ich accidentally rebooted system and did not reboot bootloader.
Screen turned off, hard brick because twrp (or what Else?) swapped boot partition to b (no bootloader installed).
As you can imagine, im pretty frightened to flash anything but weta rom for now on my new pixel (google rma...).
Is this caused by twrp, du or what?
Click to expand...
Click to collapse
It's impolite to talk about an issue with DU in the thread dedicated for a totally different ROM.
You may want to post this question over in the TWRP thread.
In the Sailfish forum, btw. You're in the Marlin forum right now. lol

3.2.7 to 4.0.2 direct OTA update for rooted Oneplus 3

I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks

just do a clean flash like any other rom. flash super su immediately after the rom without rebooting to get root access.

jaj473 said:
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
Click to expand...
Click to collapse
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Crazyhat said:
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
Why would you want to sideload the ROM and then perform a wipe to get f2fs, also with the stock recovery. It can be done via twrp itself and the ROM can be flashed normally via twrp.
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Why would you want to sideload the ROM and then perform a wipe to get f2fs, also with the stock recovery. It can be done via twrp itself and the ROM can be flashed normally via twrp.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
I said this is the safest way to avoid the dm-verity message. Theoretically, what you propose is correct but it's not as safer. In fact, this forum is plenty of issues from people who tried to do it like you say.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Crazyhat said:
I said this is the safest way to avoid the dm-verity message. Theoretically, what you propose is correct but it's not as safer. In fact, this forum is plenty of issues from people who tried to do it like you say.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
No there are no issues with it apart from the DM verity splash screen. If you doing a clean install you should not have any issue and if DM verity is such a big deal you can also flash 3.2.8 or 3.5.5 forward to get rid of it.
Sent from my OnePlus3 using XDA Labs

jaj473 said:
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
Click to expand...
Click to collapse
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
Crazyhat said:
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!

bonham1988 said:
No there are no issues with it apart from the DM verity splash screen. If you doing a clean install you should not have any issue and if DM verity is such a big deal you can also flash 3.2.8 or 3.5.5 forward to get rid of it.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Dm-verity is a problem for many people. I won't need to go back to 3.2.8 rom again if previously I did it well so, in my modest opinion, it's much better to ensure that it doesn't happen. Anyway, you can do it whatever you like. It's not my business.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Crazyhat said:
Dm-verity is a problem for many people. I won't need to go back to 3.2.8 rom again if previously I did it well so, in my modest opinion, it's much better to ensure that it doesn't happen. Anyway, you can do it whatever you like. It's not my business.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
You don't actually have to go to 3.2.8 ROM. You just have to flash the firmware and modem. And DM verity is subjective there are many people myself included who don't find that extra splash screen an issue at all.
Sent from my OnePlus3 using XDA Labs

Sir Backe said:
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
Click to expand...
Click to collapse
The safest place for that is the OnePlus site. You have to flash v2 which is the latest version. The OnePlus site will merely show you one link without indicating whether it is for v1 or v2. You can go ahead and download it as it is the v2.

bonham1988 said:
You don't actually have to go to 3.2.8 ROM. You just have to flash the firmware and modem. And DM verity is subjective there are many people myself included who don't find that extra splash screen an issue at all.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Ok, great! I have been several months with it too, but only because It never was a trouble for me neither.
---------- Post added at 02:29 PM ---------- Previous post was at 02:13 PM ----------
Sir Backe said:
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
Click to expand...
Click to collapse
Probably, this is not the last version, but it works fine. Right now I'm working and I hope you'll understand that I don't have enough time to look for the last version. Anyway, I leave you this link just in case it is useful for you....
https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img

@Crazyhat
Tks for the link. I just downloaded it from the Oneplus Website according to @tnsmani recommendation. I didn't actually know that it is there, hidden in the depth of the OP Website mess .

Sir Backe said:
@Crazyhat
Tks for the link. I just downloaded it from the Oneplus Website according to @tnsmani recommendation. I didn't actually know that it is there, hidden in the depth of the OP Website mess .
Click to expand...
Click to collapse
Hahaha.... You will have to trust them [emoji4] [emoji106]
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

Pixel XL twrp install

So I just went back to 7.1.2 from O and I tried using the fasboot boot to install tarp but in hanging on the twrp loading screen. I've downgraded all the way to March 7.1.1 and the same issue occurs. Any hel?
Google edition pixel not Verizon
Yes bootloader is unlocked

bennyboy2120 said:
So I just went back to 7.1.2 from O and I tried using the fasboot boot to install tarp but in hanging on the twrp loading screen. I've downgraded all the way to March 7.1.1 and the same issue occurs. Any hel?
Google edition pixel not Verizon
Yes bootloader is unlocked
Click to expand...
Click to collapse
Which version are you trying?
Are you booting to TWRP from fastboot or installing twrp from fastboot?
Try booting to twrp from fastboot and then installing TWRP with the ZIP
Latest version only give me bootloops
twrp-pixel-installer-marlin-3.0.2-0-RC1.zip works for me though.

parakleet said:
Which version are you trying?
Are you booting to TWRP from fastboot or installing twrp from fastboot?
Try booting to twrp from fastboot and then installing TWRP with the ZIP
Latest version only give me bootloops
twrp-pixel-installer-marlin-3.0.2-0-RC1.zip works for me though.
Click to expand...
Click to collapse
I am using the boot command I can't get passed the twrp boot screen unless it takes more then 10 minutes to boot up first time
Sent from my Pixel XL using Tapatalk

bennyboy2120 said:
I am using the boot command I can't get passed the twrp boot screen unless it takes more then 10 minutes to boot up first time
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
I'm just going to leave it on that start screen for 30ish mins see if anything happens.
btw I also reverted from Android O to N

RedBlueGreen said:
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
Click to expand...
Click to collapse
Keep me posted if you get it, I'm trying some other methods
Sent from my Pixel XL using Tapatalk

RedBlueGreen said:
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
I'm just going to leave it on that start screen for 30ish mins see if anything happens.
btw I also reverted from Android O to N
Click to expand...
Click to collapse
I also went from 7.1.2 back to 7.1.1 March update still had the issue
Sent from my Pixel XL using Tapatalk

bennyboy2120 said:
Keep me posted if you get it, I'm trying some other methods
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yeap will do. Might try an older version of twrp.img if nothing happens in 30mins
---------- Post added at 04:52 PM ---------- Previous post was at 04:17 PM ----------
bennyboy2120 said:
I also went from 7.1.2 back to 7.1.1 March update still had the issue
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
nothing.. still on the loading screen

RedBlueGreen said:
Yeap will do. Might try an older version of twrp.img if nothing happens in 30mins
---------- Post added at 04:52 PM ---------- Previous post was at 04:17 PM ----------
nothing.. still on the loading screen
Click to expand...
Click to collapse
Weird. I don't know what could be causing it. I'll check partition chance maybe after going to o?
Sent from my Pixel XL using Tapatalk

bennyboy2120 said:
Weird. I don't know what could be causing it. I'll check partition chance maybe after going to o?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
came across this..
https://forum.xda-developers.com/showpost.php?p=72452371&postcount=1769
and this is the thread on how to do it.. (dont understand it)
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
not sure if it has anything to do with it.
---------- Post added at 05:41 PM ---------- Previous post was at 05:22 PM ----------
im in a bootloop now..
dont think ill be able to get out of it

RedBlueGreen said:
came across this..
https://forum.xda-developers.com/showpost.php?p=72452371&postcount=1769
and this is the thread on how to do it.. (dont understand it)
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
not sure if it has anything to do with it.
---------- Post added at 05:41 PM ---------- Previous post was at 05:22 PM ----------
im in a bootloop now..
dont think ill be able to get out of it
Click to expand...
Click to collapse
I'm looking into the VBS now, also looking at partition differences because of the O beta
Sent from my Pixel XL using Tapatalk

bennyboy2120 said:
I'm looking into the VBS now, also looking at partition differences because of the O beta
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
fixed my bootloop... thought i messed up really bad.. Gonna leave it for now.. giving me a headache.
Let me know if you find a fix please <3

It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.

mattyb65 said:
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
Click to expand...
Click to collapse
What's the command to swap to the other partition? Thank you!!!
Sent from my Pixel XL using Tapatalk

mattyb65 said:
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
Click to expand...
Click to collapse
any chance you could list all the commands?

bennyboy2120 said:
What's the command to swap to the other partition? Thank you!!!
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
RedBlueGreen said:
any chance you could list all the commands?
Click to expand...
Click to collapse
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata​
switch to the other slot and do the same
fastboot --set-active=_a​
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip​
reboot to welcome screen
fastboot reboot ​
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip​
reboot to welcome screen
fastboot reboot ​
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img​
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot ​
profit

mattyb65 said:
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata​
switch to the other slot and do the same
fastboot --set-active=_a​
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip​
reboot to welcome screen
fastboot reboot ​
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip​
reboot to welcome screen
fastboot reboot ​
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img​
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot ​
profit
Click to expand...
Click to collapse
You the man!!!!
Sent from my Pixel XL using Tapatalk

mattyb65 said:
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata​
switch to the other slot and do the same
fastboot --set-active=_a​
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip​
reboot to welcome screen
fastboot reboot ​
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip​
reboot to welcome screen
fastboot reboot ​
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img​
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot ​
profit
Click to expand...
Click to collapse
Where is the Verified Bootloader?

[/COLOR]
bennyboy2120 said:
Where is the Verified Bootloader?
Click to expand...
Click to collapse
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..

RedBlueGreen said:
[/COLOR]
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
Click to expand...
Click to collapse
how are you trying to root?

RedBlueGreen said:
[/COLOR]
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
Click to expand...
Click to collapse
You need to flash the boot signer zip. This has been covered in many threads.
https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16

[Recovery] TWRP for maple

I want to share you a great twrp who support aroma installer.
Link:https://mega.nz/#!6MQxWIKa!ZuSMnC7DtXxh4R9Vb5hHMjRFFVk6kaCaHiodn5CSN3M

Blackghosthm said:
I want to share you a great twrp who support aroma installer.
Created by @Myself5.
Link:https://mega.nz/#!6MQxWIKa
Click to expand...
Click to collapse
You need a decryption key.
---------- Post added at 05:10 PM ---------- Previous post was at 04:27 PM ----------
Blackghosthm said:
I want to share you a great twrp who support aroma installer.
Created by @Myself5.
Link:https://mega.nz/#!6MQxWIKa!ZuSMnC7DtXxh4R9Vb5hHMjRFFVk6kaCaHiodn5CSN3M
Click to expand...
Click to collapse
What version of twrp is this?

Beetle84 said:
You need a decryption key.
---------- Post added at 05:10 PM ---------- Previous post was at 04:27 PM ----------
What version of twrp is this?
Click to expand...
Click to collapse
3.2.1 but not that version you can find in twrp.me

Blackghosthm said:
3.2.1 but not that version you can find in twrp.me
Click to expand...
Click to collapse
So how about you push your AROMA fix to the official TWRP trees that everyone can profit from it?
Also that image is certainly not created by me. It might be based on the official TWRP, but the way you put it is missleading IMO.

Myself5 said:
So how about you push your AROMA fix to the official TWRP trees that everyone can profit from it?
Also that image is certainly not created by me. It might be based on the official TWRP, but the way you put it is missleading IMO.
Click to expand...
Click to collapse
Ok, I removed your name.

Myself5 said:
So how about you push your AROMA fix to the official TWRP trees that everyone can profit from it?
Also that image is certainly not created by me. It might be based on the official TWRP, but the way you put it is missleading IMO.
Click to expand...
Click to collapse
More than likely from a Chinese site, possibly modified by @machao44

Beetle84 said:
More than likely from a Chinese site, possibly modified by @machao44
Click to expand...
Click to collapse
Yes,now I have the same idea but doesn't matter I didn't write it created by me,I don't think it have matter for developer because he didn't share the recovery in xda.

I still wouldn't mind if _whoever did it_ would push the fix to the TWRP repository.

Myself5 said:
I still wouldn't mind if _whoever did it_ would push the fix to the TWRP repository.
Click to expand...
Click to collapse
Will this affect all Xperias with 4.4 Kernel? Really happy that @Blackghosthm shared that with Me... Can't wait to push out some awesome AROMA Stuff again!
Thanks a lot to everyone who was involved! :angel:

Myself5 said:
I still wouldn't mind if _whoever did it_ would push the fix to the TWRP repository.
Click to expand...
Click to collapse
I believe it created by storm in xperi fix there are 2 twrp versions one of them is this twrp.
Also i heard in some post it created by storm.

heil Aroma!

@sToRm//
Can you shed any light on who made this?

Anyone tried the new official One? https://dl.twrp.me/maple/twrp-3.2.3-0-maple.img.html

Hi I am quite having a hard time figuring out how to install TWRP on my XZP dual global version.
I already flashed the latest firmware last August... I also tried to follow installing it through ADB using command prompt yet nothing did work... Is there someone out here who can help me with flashing TWRP... Thanks

I use in this moment the original 3.2.3-0 version.
Where's is the problem to install TWRP? enable adb, call adb during running phone and accept the PC all time.
If the bootloader unlocked,, boot in Fastmode (hold Volume up during connecting the USB cable with the PC) . Check the driver via fastboot devices, If you see the phone call fastboot flash revovery TWRP. img (if your TWRP version has the name "TWRP. img"). After that you can boot into TWRP

Excappare said:
Hi I am quite having a hard time figuring out how to install TWRP on my XZP dual global version.
I already flashed the latest firmware last August... I also tried to follow installing it through ADB using command prompt yet nothing did work... Is there someone out here who can help me with flashing TWRP... Thanks
Click to expand...
Click to collapse
You need to flash a kernel from a custom ROM first (like CarbonROM) in order to be able to boot from the recovery (FOTAKERNEL) partition. The stock kernels have recovery built-in and would use that instead of TWRP. You can get a CarbonROM kernel image (boot.img) from its flashable zip.
After flashing a custom kernel you can then flash the TWRP image via "fastboot flash recovery <recovery image>". You'll have to reboot the phone and follow the usual button combination (though I don't really know it's holding volume up or down) to access the recovery. Using "fastboot boot" will not work and it'll stuck on the Sony logo with the blue fastboot LED stay on.

I think twrp found from this thread,,you can check TWRP Folder,
,https://forum.xda-developers.com/showpost.php?p=78121448&postcount=4

I've also the Stock Kernel (Pie) on the phone and can reach TWRP without any problems : you must hold Power and Volume (up or down? Not sure in this moment) till you see TWRP on the Screen (around 6 Sec.) Maybe the screen switched off... Switch it on via short press via Power... That's all