Wrong model recognized in PC while recovering with TWRP and other issues - Sony Xperia Z Ultra

Hello, fellas,
I wanted to install TWRP, to have a custom rom in my Z Ultra. I followed the guide showed in https://forum.xda-developers.com/showthread.php?t=2647492 but unfortunatelly, i downloaded the first package, which it seems it was meant for T2 Ultra, and excecuted the .bat file. That file makes me enter in TWRP but as if it was T2, tianchi, so didnt allow me to flash a togari rom. I realized of the mistake, so i downloaded the one meant to Z Ultra, but still the computer recognized it as T2 Ultra.
After that I've tried to flash other images for TWRP, tried adb erase recovery, flash another TWRP.IMG (even 3.0.1 for togari) and still, while recovery, computer says i have a T2 Ultra, the version of TWRP is 2.8, and cant flash any custom rom, so nothing changes. Plus, i cant get into recovery by using the buttons, just via ADB, and still the same happens over and over again. Thanks in advance for any possible help

Yes we are back at the topic of the messy forum.
This thread is over two years old. It don't work on recent firmwares.
To start off.
Is your bootloader unlocked?
Have you ever flashed the last and most recent stock rom? 14.6.A.1.236 is the last firmware when support was ended.

SUPERUSER said:
Yes we are back at the topic of the messy forum.
This thread is over two years old. It don't work on recent firmwares.
To start off.
Is your bootloader unlocked?
Have you ever flashed the last and most recent stock rom? 14.6.A.1.236 is the last firmware when support was ended.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked. I'm trying to see if I can do that flashing u mention, as it's a new thing for me
---------- Post added at 05:09 PM ---------- Previous post was at 04:52 PM ----------
SUPERUSER said:
Yes we are back at the topic of the messy forum.
This thread is over two years old. It don't work on recent firmwares.
To start off.
Is your bootloader unlocked?
Have you ever flashed the last and most recent stock rom? 14.6.A.1.236 is the last firmware when support was ended.
Click to expand...
Click to collapse
Anyways it seems that by doing that flashing, my os will downgrade to KitKat...

Download flashtool here
http://www.flashtool.net/downloads.php
With this you will flash the latest firmware.
Learn how to use flashtool here: http://www.xperiablog.net/2016/03/12/install-xperia-marshmallow-using-flashtool-and-xperifirm-guide/
But in the link above instead in xperiafirm choose "togari" and your model C68xx and the most recent corrensponding to your location or carrier.
Download it and flash it. It will erase everything so backup your storage to a computer.

SUPERUSER said:
Download flashtool here
http://www.flashtool.net/downloads.php
With this you will flash the latest firmware.
Learn how to use flashtool here: http://www.xperiablog.net/2016/03/12/install-xperia-marshmallow-using-flashtool-and-xperifirm-guide/
But in the link above instead in xperiafirm choose "togari" and your model C68xx and the most recent corrensponding to your location or carrier.
Download it and flash it. It will erase everything so backup your storage to a computer.
Click to expand...
Click to collapse
Thanks, I could already do the stock firmware flashing but now there is a situation : bootloader is unlocked, but when trying to root with flashtool, it says "illegal key size or default parameters" I've been searching but not clear info about that...
And about what you just replied...will try it! Thanks a lot

I did it, succesfully...but still lollipop. I guess im back to the same start...

CoderNesty said:
I did it, succesfully...but still lollipop. I guess im back to the same start...
Click to expand...
Click to collapse
Good. Lollipop is the last android version supported for togari.
Why you flashed the stock rom is because there has been changes to bootloader and recovery.
So you need to at least once flash the latest firmware to flash the roms here based on 5.1.1 or later.
Now flash twrp. https://forum.xda-developers.com/xp...ent/twrp-recovery-2-8-7-0-2016-02-03-t3307043
Now remember; starting with twrp 3.0> booting to recovery is done by powering off the device.
And then holding power and volume down until it vibrates. Let go and the phone will soon boot to twrp.
Now you can connect the phone to the computer and transfer any rom you would like to run.
When the cable is connected, in twrp go to mount, and press disable mtp button twice.
And the phone should now be detected on your computer.
Remember. There is no fully stable marshmallow or nougat rom.
These roms here on the forum are for testing purposes not for a daily driver with good battery and working camera for example.
The last remaining active rom is this one: https://forum.xda-developers.com/xp...t/rom-cyanogenmod-12-1-builds-t3066895/page20
Its lollipop based too but with the recent security patches.

SUPERUSER said:
Good. Lollipop is the last android version supported for togari.
Why you flashed the stock rom is because there has been changes to bootloader and recovery.
So you need to at least once flash the latest firmware to flash the roms here based on 5.1.1 or later.
Now flash twrp. https://forum.xda-developers.com/xp...ent/twrp-recovery-2-8-7-0-2016-02-03-t3307043
Now remember; starting with twrp 3.0> booting to recovery is done by powering off the device.
And then holding power and volume down until it vibrates. Let go and the phone will soon boot to twrp.
Now you can connect the phone to the computer and transfer any rom you would like to run.
When the cable is connected, in twrp go to mount, and press disable mtp button twice.
And the phone should now be detected on your computer.
Remember. There is no fully stable marshmallow or nougat rom.
These roms here on the forum are for testing purposes not for a daily driver with good battery and working camera for example.
The last remaining active rom is this one: https://forum.xda-developers.com/xp...t/rom-cyanogenmod-12-1-builds-t3066895/page20
Its lollipop based too but with the recent security patches.
Click to expand...
Click to collapse
Thanks again for dedicating time to help me the thing is that when this phone was given to me, already had lollipop. So, what I wanted is as always, to try to upgrade it. I know that there are no stable customs roms... But what about porting? Do you recommend me to take some time to study it?

CoderNesty said:
Thanks again for dedicating time to help me the thing is that when this phone was given to me, already had lollipop. So, what I wanted is as always, to try to upgrade it. I know that there are no stable customs roms... But what about porting? Do you recommend me to take some time to study it?
Click to expand...
Click to collapse
If you have the knowledge to port carbon rom or lineage os nougat it would be very welcome.
I own a Honami that has these roms. Honami and togari are very similar to each other and most off the roms here are actually ported from it or the Z1 compact, Z3 or Z5 to Z3 and then to togari.
https://forum.xda-developers.com/xperia-z1/development/rom-carbonrom-weeklies-t3660737
https://forum.xda-developers.com/xperia-z1/development/rom-lineageos-14-1-unofficial-t3628209
It is 100% possible to get a fully stable rom. It is being done on the honami because of larger interest in this phone.
It was mentioned here on the togari forum but no one actually did compile any rom like this.
What you do essentially to get a stable nougat is to keep using the old kernel 3.4 and add the modules and blobs needed and the togari specific drivers.
What you need is basically a powerful linux machine with lots of hard drive space and ram and time to let it compile.

SUPERUSER said:
If you have the knowledge to port carbon rom or lineage os nougat it would be very welcome.
I own a Honami that has these roms. Honami and togari are very similar to each other and most off the roms here are actually ported from it or the Z1 compact, Z3 or Z5 to Z3 and then to togari.
https://forum.xda-developers.com/xperia-z1/development/rom-carbonrom-weeklies-t3660737
https://forum.xda-developers.com/xperia-z1/development/rom-lineageos-14-1-unofficial-t3628209
It is 100% possible to get a fully stable rom. It is being done on the honami because of larger interest in this phone.
It was mentioned here on the togari forum but no one actually did compile any rom like this.
What you do essentially to get a stable nougat is to keep using the old kernel 3.4 and add the modules and blobs needed and the togari specific drivers.
What you need is basically a powerful linux machine with lots of hard drive space and ram and time to let it compile.
Click to expand...
Click to collapse
I dared to flash a MM resurrection ROM, a real shame that works wonderfully except for the camera... Porting sounds like an interesting field for me. Unfortunately I can't count with such powerful machine right now. But I will keep searching, and thanks for your guidance any progression I have I will try to give feed in this thread

Related

Can't flash stock rom

Hi guys,
I really need help here. I have a SGP312, bootloader unlocked, and I'd like to get back to stock rom 10.7.A.0.228 because I need MHL-Output and this doesn't work with any custom rom I tried. Here's the problem: I can get into fastboot and into flash mode but nothing I try is working. If I use flashtool the and flash latest XperiFirm ROM for SGP312 everything is running fine until I try to boot. The Sony logo appears and then nothing happens. Once I waited for over 30 minutes. Screen stays on but it's not booting.
So back to flashing recovery...in recovery I can flash ALL custom roms I want. LineageOS, crDroid, CyanogenMod, no problem. If I try to flash this: "https://forum.xda-developers.com/xperia-tablet-z/general/stock-10-7-0-228-vmo-t3303365" I have same problem as described before. Sony logo pops up, screen stays on, no boot.
Also I tried different recoveries TWRP, CWM, Phil's and so on and nothing seems to work. With wipes without wipes does not matter...
And I tried Sony flash tool Emma (with rom for SGP11) and I tried with TWRP to flash a backup of 10.7.A.0.228 I made...both with same results
Can anyone help? I just want to go back to Android 5.1.1 (root preferred but if no root it's also okay) or I need a custom rom with working MHL. Does anyone have the one clue that can get me back to stock rom?
Thanks guys!
johneggman said:
Does anyone have the one clue that can get me back to stock rom?
Thanks guys!
Click to expand...
Click to collapse
It's a known issue, especially after coming from android 7.x.x ROMs.
You need to flash ANY stock ROM except 5.1.1. 4.1.2 or 4.4.2 will do. After the ROM boots ok, you can flash 5.1.1 directly via Flashtool 0.9.18.6.
It will work.
Rootk1t said:
It's a known issue, especially after coming from android 7.x.x ROMs.
You need to flash ANY stock ROM except 5.1.1. 4.1.2 or 4.4.2 will do. After the ROM boots ok, you can flash 5.1.1 directly via Flashtool.
It will work.
Click to expand...
Click to collapse
Thank you very much! I'll give that a try. Right now I'm having problems with flashtool 0.9.23.2. It gives me the "Processing of loader.sin finished with errors" and "Error in processHeader : 1" when I try to flash. Drivers are installed correctly, tablet z is recognized as "Sony sa0107". I'm running Windows 10 64bit and flashtool as admin.
Any ideas?
johneggman said:
Thank you very much! I'll give that a try. Right now I'm having problems with flashtool 0.9.23.2. It gives me the "Processing of loader.sin finished with errors" and "Error in processHeader : 1" when I try to flash. Drivers are installed correctly, tablet z is recognized as "Sony sa0107". I'm running Windows 10 64bit and flashtool as admin.
Any ideas?
Click to expand...
Click to collapse
you need version 0.9.18.6.
Rootk1t said:
you need version 0.9.18.6.
Click to expand...
Click to collapse
Thank you! I'll give that a try as soon as I have time. If that also does not work I'll try flashing with my Macbook. Maybe my Windows computer really has some driver issues.
Rootk1t said:
you need version 0.9.18.6.
Click to expand...
Click to collapse
Hi Rootk1t,
thanks for the tip! It worked. I went from 4.4.4 to 5.1.1 prerooted although I had to do this with a Macbook. Even version 0.9.18.6 didn't want to flash my SGP312. I think the drivers on my windows machine are really messed up. But now everything is fine!
Thanks again!
Do you have any hints for me where I can find older stock versions?
schaeaef said:
Do you have any hints for me where I can find older stock versions?
Click to expand...
Click to collapse
Try finding your FTF on http://xperiafirmware.com/
johneggman said:
Hi Rootk1t,
thanks for the tip! It worked. I went from 4.4.4 to 5.1.1 prerooted although I had to do this with a Macbook. Even version 0.9.18.6 didn't want to flash my SGP312. I think the drivers on my windows machine are really messed up. But now everything is fine!
Thanks again!
Click to expand...
Click to collapse
So where did you find the stock 4.4.4 for SGP312? Every single thing I find, links are dead. Thanks
jhcomputerguy said:
So where did you find the stock 4.4.4 for SGP312? Every single thing I find, links are dead. Thanks
Click to expand...
Click to collapse
I'm gonna check as soon as get home. All I remember is, that I was searching a long time because, as you said, all links were dead. Maybe I still have the ROM somewhere in my files. I'll get back to you.
jhcomputerguy said:
So where did you find the stock 4.4.4 for SGP312?
Click to expand...
Click to collapse
I have some tablet firmwares saved.
Rootk1t said:
It's a known issue, especially after coming from android 7.x.x ROMs.
You need to flash ANY stock ROM except 5.1.1. 4.1.2 or 4.4.2 will do. After the ROM boots ok, you can flash 5.1.1 directly via Flashtool 0.9.18.6.
It will work.
Click to expand...
Click to collapse
This was exactly what I needed, thanks! Couldn't flash anything on my SGP311 with the latest Flashtool, but followed your advice and had no issue.
Rootk1t said:
It's a known issue, especially after coming from android 7.x.x ROMs.
You need to flash ANY stock ROM except 5.1.1. 4.1.2 or 4.4.2 will do. After the ROM boots ok, you can flash 5.1.1 directly via Flashtool 0.9.18.6.
It will work.
Click to expand...
Click to collapse
thanks this fixed my SGP311
I flashed 4.4.4 rom
managed to find on 4pda russian website. not sure if pasting link is allow here but just google 4pda and your model number or topic 470240
the page has a complete archive
This saved my SGP311! Thanks for sharing the breadcrumbs to an active download link for 4.4.4 in 2018, found it, downloaded it, flashed it, booted again!
Rootk1t said:
It's a known issue, especially after coming from android 7.x.x ROMs.
You need to flash ANY stock ROM except 5.1.1. 4.1.2 or 4.4.2 will do.
Click to expand...
Click to collapse
Just for the search engine: 5.0.2 didn't work for me either - same symptoms as with 5.1.1. Going back to 4.4.4 worked.
Rootk1t said:
It's a known issue, especially after coming from android 7.x.x ROMs.
You need to flash ANY stock ROM except 5.1.1. 4.1.2 or 4.4.2 will do. After the ROM boots ok, you can flash 5.1.1 directly via Flashtool 0.9.18.6.
It will work.
Click to expand...
Click to collapse
Thank you SO much! I have been flashing umpteen versions with no luck and now with a very ancient "store front" version I'm back up and running! Thanks!
I'm sorry but I can't find any suitable firmware for SGP312.
I'm currently on Android 5.1.1 (Build 10.7.A.0.228, Germany/EU if that matters), and I'd really like to try to upgrade it to LineageOS 15.1 for all kinds of reasons; but in case that I botch anything (or the apps I really need don't work, like the screen time manager, as it's the kids' device), I really want to have a working firmware at hand to at least recover it back.
Kinda-noob question: do I really need a flashable firmware or would a full nandroid backup work for a rollback once I have TWRP installed?
XPUser99 said:
I'm sorry but I can't find any suitable firmware for SGP312.
I'm currently on Android 5.1.1 (Build 10.7.A.0.228, Germany/EU if that matters), and I'd really like to try to upgrade it to LineageOS 15.1 for all kinds of reasons; but in case that I botch anything (or the apps I really need don't work, like the screen time manager, as it's the kids' device), I really want to have a working firmware at hand to at least recover it back.
Kinda-noob question: do I really need a flashable firmware or would a full nandroid backup work for a rollback once I have TWRP installed?
Click to expand...
Click to collapse
For a kids device, i would recommend to stay on sony stock 5.1.1, because games run faster there, also it is already tried and tested with easy root installation and debloating.
To revert back from custom ROM (LOS or RR) to stock you'll need to flash firstly any firmware (like 4.4.4) except the latest 5.1.1, then boot it, and afterwards update to 5.1.1 if you want so. If you revert straight to the latest 5.1.1 stock, you'll get permanent bootloop or black screen issue.
So you need to have at least two stock firmware packages.
As for nandroid backup, you can't revert from custom rom to stock via restoring nandroid backup.
Fresh install is recommended.

Lost recovery and root after installing app for rooted devices, some guidance please?

So I've managed to recover root privileges but dual recovery is lost, I've read in dual recovery Q&A that there's some files I have to erase when you don't want it anymore, so I thought just erase and then flash dual recovery again, but since this happened a lot of factory resets ago there are some concerns about this being the right way, do I just flash it without erasing those files? Also is it realy necessary to flash the latest DR or will my old version do?
I'm on stock KitKat 4.4.4 build 14.4.A.0.118 on a c6833 with LB.
I would also love it if you could recommend the most stable Nougat or MM 6.0.1 rom, I know there's AOSP Nougat, DU and maybe RR for 6.0.1? What would you flash for a daily driver, I don't care about the camera much, but if Wi-Fi and phone radio are working normally, that should do it for me, thanks in advance to anyone that can give me a hand with this.
Sent from my Z Ultra using Tapatalk
i can help!
RealityFails said:
i can help!
Click to expand...
Click to collapse
Awesome, just when I thought no one was gonna answer, so what do u think I should do to get DR back? Do I erase those files and reinstall or just reinstall? My OS is so unstable I'm afraid anything will brick my XZU. Do you need me to provide extra info?
RealityFails said:
i can help!
Click to expand...
Click to collapse
may of missed this part but is your CM based????
No, It's Stock KitKat 4.4.4 build 14.4.A.0.118 with LB. I plan to unlock the bootloader if I get recovery back.
Sent from my C6833 using Tapatalk
9crack said:
No, It's Stock KitKat 4.4.4 build 14.4.A.0.118 with LB. I plan to unlock the bootloader if I get recovery back.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Have you tried to Unlock the bootloader, flash the recovery and root and relock it?
By any chance have you been on official 5.1.1?
No I've never been on any stock LP be it 5.0.2 or 5.1.1, so does it matter if I erase the files in the following howto before reinstalling DR?
How to remove DR:
Delete the following files:
/system/bin/recovery.twrp.cpio.lzma (or .tar)
/system/bin/recovery.cwm.cpio.lzma (or .tar)
/system/bin/recovery.philz.cpio.lzma
/system/bin/charger
/system/bin/dualrecovery.sh
/system/bin/mr
Also is it better to unlock the bootloader first? I don't want relock it afterwards since I want to flash DU or AOSP Nougat, or RR M and have a recovery.
I read a lot of the forums all the time but I'm still pretty much a noob at this, up until now rooted Kitkat is all I've needed, sorry if I'm asking too much.
Sent from my C6833 using Tapatalk
OK so I've been reading, are you suggesting that I unlock the bootloader so when I install DR it stores the recovery on the FOTA kernel partition, instead of /system, so i won't lose DR next time?
I guess that's what I've been looking for if so, last question, is DR compatible with Android M or N roms?
I'm sorry if it's a dumb question, I'm still a noob, hehe.
9crack said:
OK so I've been reading, are you suggesting that I unlock the bootloader so when I install DR it stores the recovery on the FOTA kernel partition, instead of /system, so i won't lose DR next time?
I guess that's what I've been looking for if so, last question, is DR compatible with Android M or N roms?
I'm sorry if it's a dumb question, I'm still a noob, hehe.
Click to expand...
Click to collapse
I could be wrong but it sounds like you wanna be on a cm or asap rom with DR.
If you plan to use any of those roms, yes unlock the bootloader. From this point you should be able to install DR on top of the current recovery, as long as you've had any type of recovery you can flash with an app. Rashr, twrp manager etc.
I've UB now, do I need the new bootloader? Do I get it if I go directly from my Stock KK to RR Lollipop rom? Can I go directly from stock KK to RR Lollipop without bricking it?
Sorry if I'm asking to much but I'm just trying to make sure I don't end up with a bricked phone.
Sent from my Xperia Z Ultra using Tapatalk
Can anyone help please?
So I've managed to get DR working again flashed RR Lollipop but now my phone doesn't see my external SDcard, what should I do?, I've read the whole RR L thread down to the last message but the only solution I've found which is to correctly uninstall Nut's DR doesn't work for me since there's no such files in /system/bin
9crack said:
I've UB now, do I need the new bootloader? Do I get it if I go directly from my Stock KK to RR Lollipop rom? Can I go directly from stock KK to RR Lollipop without bricking it?
Sorry if I'm asking to much but I'm just trying to make sure I don't end up with a bricked phone.
Sent from my Xperia Z Ultra using Tapatalk
Click to expand...
Click to collapse
I believe no. I I'm not to familiar on the new bootloader. Prob have to ask one of the rom devs, but im pretty sure you just need twrp 3.0
Thanks RealityFails, you've been of such help, I did learn from your posts, I flashed DR then RR LL rom then with twrp app and flasher I got my recovery for non-stock since I read somewhere that Nut's DR doesn't work with custom roms.
I'm now trying to learn how to read android's logs to see what's up with this ROM not reading my external SDcard, when I go to storage unmount it then mount again, it reads for a few seconds then it's gone, whatever man! he he crazy rom, otherwise is awesome, and everything else works. If I'm not able to fix the SDcard access do you recommend any other LL rom similar to RR?
Anyhow many thanks for helping this Z Ultra stay unbricked, updated and with a decent recovery.
Sent from my Xperia+Z+Ultra using Tapatalk

Cannot Boot Custom ROMs Anymore. Just Bootloops

Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Clean flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Try without f2fs. Use ext4
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
vistaabalaji said:
Try without f2fs. Use ext4
Click to expand...
Click to collapse
EXT4 had the same issue. Just bootloops forever.
naturist said:
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
Click to expand...
Click to collapse
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
geokilla said:
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
EXT4 had the same issue. Just bootloops forever.
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
Click to expand...
Click to collapse
The one on this thread. Second post.
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Felheipe said:
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Click to expand...
Click to collapse
use latest gapps.outdated or older one causes crashes...
adithyan25 said:
use latest gapps.outdated or older one causes crashes...
Click to expand...
Click to collapse
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Felheipe said:
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Click to expand...
Click to collapse
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
adithyan25 said:
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
Click to expand...
Click to collapse
That's exactly what I did, as I mentioned in OP lol. Except I wasn't flashing MIUI 8 in EDL mode.
adithyan25 said:
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
Click to expand...
Click to collapse
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Felheipe said:
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Click to expand...
Click to collapse
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
edit:- playservices had updated many times after 0303.. so i can say its outdated
adithyan25 said:
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
Click to expand...
Click to collapse
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Felheipe said:
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Click to expand...
Click to collapse
dirty flashing isn't a solution ... theres changes in trees of the rom and kernel..
anyway head back to miui unlocl officially and when coming back to custom rom do wipe everything and give it a shot..probably the crash may be due to over written or exiating files...
happy flashing
~peace
I should mention I clean flashed the ROMs. Updated OP.
Ok trying it again right now and so far, this is what I did:
Used MiFlash to fastboot flash MIUI v7.7.6 Global DEV.
Test the phone to make sure all functions work properly.
Tried to unlock bootloader using Mi Unlock but it said bootloader is already unlocked.
Boot into MIUI again.
Fastboot flashed TWRP 3.1.1.0.
No boot into MIUI.
Flash Kenzo firmware 8.2.4.0 in TWRP
Clean flash LineageOS 13 and Open Gapps 6.0 ARM64 Mini with /data and /cache in EXT4
IT WORKS!
I guess now I'll try Resurrection Remix.

[GUIDE]Rollback/Downgrade firmware from oreo to nougat

.One time use of a computer or laptop is required for booting in to oreo recovery. Your internal storage is going to be wiped in this process so backup your stuff.​
Recovery for oreo firmware OrangeFox-R10.1_O1-Stable-riva.zip
Nougat firmware fw_riva_miui_HM5AGlobal_V10.1.1.0.NCKMIFI_8cb19207b7_7.1.zip
Recovery for nougat firmware OrangeFox-R10.1_N1-Stable-riva.zip
Fix for sensors and ril sensorfix.zip, efsfix.zip
1. Download all above files
2. Boot into oreo recovery through fastboot (you can continue or skip and use the AIO zip below)
3. Flash nougat firmware and nougat recovery
4. Format internal storage
5. Flash given fixes
6. Reboot
[UPDATE: 30/01/2020]
All in one zip is available
Download:
Downgrade (O To N)Firmware.zip
Guide for using this zip
1). Reboot to oreo recovery
2). Flash O to N zip file (from above link)
3). Reboot to recovery again
4). Flash the nougat fw based recovery you want,
or just skip this step.
5). Reboot to recovery again( if u flashed a new recovery)
6). Wipe System, Vendor, Data, Cache, and Dalvik
7). Flash ROM
8). Finally, reboot to system
NaAnBcEhEuL9A8K7 said:
[*]Recovery for nougat firmware download
Click to expand...
Click to collapse
Whoops, we can't find that page.
fix please. Thx)
sjcbank said:
Whoops, we can't find that page.
fix please. Thx)
Click to expand...
Click to collapse
Fixed
My first thought was: why downgrade from Oreo to Nougat??
supergrass said:
My first thought was: why downgrade from Oreo to Nougat??
Click to expand...
Click to collapse
Because custom roms won't boot on stock oreo kernel.
NaAnBcEhEuL9A8K7 said:
Because custom roms won't boot on stock oreo kernel.
Click to expand...
Click to collapse
What custom ROM are you using? I have found them all disappointing, one way or another. I'm currently on rooted MIUI 10 Oreo.
supergrass said:
I have found them all disappointing, one way or another. I'm currently on rooted MIUI 10 Oreo.
Click to expand...
Click to collapse
There is something called personal preference.
Just like you prefer MIUI some others prefer custom ROMs
Firmware taken from the latest global firmware HM5AGlobal-V10.1.1.0.NCKMIFI-7.1 and HM5AGlobal-V10.1.2.0.OCKMIFI-8.1
TWRP in the archives PE-RecoveryProject-3.1 (for the recovery we say thank you Zikiel )
Switch from 7 to 8, Flash Archive Firmware-8.1 RecoveryProject-3.1-Oreo from the recovery; reboot into the recovery; clean up the corresponding sections and install the firmware, root and patches according to your desire; and in the same order from 8 to 7, flash Firmware-7.1 RecoveryProject-3.1-Nougat reboot in recovery cleaning and installing firmware. It is better to stir archives on a memory card and for features and differences in Firmware recovery for 7 does not see the date section from 8
A backup is welcome, for its restoration it is recommended that how it was made !!!
Firmware-7.1+RecoveryProject-3.1-Nougat.zip
Firmware-8.1+RecoveryProject-3.1-Oreo.zip
sjcbank said:
Firmware taken from the latest global firmware HM5AGlobal-V10.1.1.0.NCKMIFI-7.1 and HM5AGlobal-V10.1.2.0.OCKMIFI-8.1
TWRP in the archives PE-RecoveryProject-3.1 (for the recovery we say thank you Zikiel )
Switch from 7 to 8, Flash Archive Firmware-8.1 RecoveryProject-3.1-Oreo from the recovery; reboot into the recovery; clean up the corresponding sections and install the firmware, root and patches according to your desire; and in the same order from 8 to 7, flash Firmware-7.1 RecoveryProject-3.1-Nougat reboot in recovery cleaning and installing firmware. It is better to stir archives on a memory card and for features and differences in Firmware recovery for 7 does not see the date section from 8
A backup is welcome, for its restoration it is recommended that how it was made !!!
Firmware-7.1+RecoveryProject-3.1-Nougat.zip
Firmware-8.1+RecoveryProject-3.1-Oreo.zip
Click to expand...
Click to collapse
Where you got this?
NaAnBcEhEuL9A8K7 said:
Where you got this?
Click to expand...
Click to collapse
Here for you
https://4pda.ru/forum/index.php?showtopic=879215&st=10980#entry82426459
supergrass said:
What custom ROM are you using? I have found them all disappointing, one way or another. I'm currently on rooted MIUI 10 Oreo.
Click to expand...
Click to collapse
How you root your MIUI 10 Oreo,which recovery you flash? thank you
钱八斤 said:
How you root your MIUI 10 Oreo,which recovery you flash? thank you
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-8lZA1zUrur_PT5AvRkd8eKrz8rVTzv7/view?usp=drivesdk
sjcbank said:
Firmware taken from the latest global firmware HM5AGlobal-V10.1.1.0.NCKMIFI-7.1 and HM5AGlobal-V10.1.2.0.OCKMIFI-8.1
TWRP in the archives PE-RecoveryProject-3.1 (for the recovery we say thank you Zikiel )
Switch from 7 to 8, Flash Archive Firmware-8.1 RecoveryProject-3.1-Oreo from the recovery; reboot into the recovery; clean up the corresponding sections and install the firmware, root and patches according to your desire; and in the same order from 8 to 7, flash Firmware-7.1 RecoveryProject-3.1-Nougat reboot in recovery cleaning and installing firmware. It is better to stir archives on a memory card and for features and differences in Firmware recovery for 7 does not see the date section from 8
A backup is welcome, for its restoration it is recommended that how it was made !!!
[drive.google.com/file/d/16DuYSRZIJGy94fcgAnHC3Bp5xgS7PM3L/view?usp=sharing"]Firmware-7.1+RecoveryProject-3.1-Nougat.zip[/URL]
[//drive.google.com/file/d/1FrznxeTnAob-Ai0ye_ZKHHj9Zl1c35wP/view?usp=sharing"]Firmware-8.1+RecoveryProject-3.1-Oreo.zip[/]
Click to expand...
Click to collapse
What is this?
Please, what I must used to downgrade in fastboot? MIUI ROM Flashing Tool? Or can you please send me, how I downgrade it? Thank you.
Why are these custom ROMs not compatible with Oreo Firmware??
Edit: I am planning to compile a ROM for the first time. All I have ever done is to compile recovery(For Redmi 5A) where they are compatible with Oreo firmware(just like other recoveries).
akil777 said:
Why are these custom ROMs not compatible with Oreo Firmware??
Edit: I am planning to compile a ROM for the first time. All I have ever done is to compile recovery(For Redmi 5A) where they are compatible with Oreo firmware(just like other recoveries).
Click to expand...
Click to collapse
Nobody has worked on the oreo sources yet so...
@sunnyraj84348 might be working on it, I don't know, I'm just assuming. Maybe he's focusing on Android 10 ROMs more than Oreo kernel.
NaAnBcEhEuL9A8K7 said:
Nobody has worked on the oreo sources yet so...
@sunnyraj84348 might be working on it, I don't know, I'm just assuming. Maybe he's focusing on Android 10 ROMs more than Oreo kernel.
Click to expand...
Click to collapse
okay, thanks.
Working on a custom rom is very time consuming. Till now I am still trying to create a device tree for my Mi cc9 so that I can make a ROM alongside with the sources provided.(I'm new to things like compiling roms)
akil777 said:
okay, thanks.
Working on a custom rom is very time consuming. Till now I am still trying to create a device tree for my Mi cc9 so that I can make a ROM alongside with the sources provided.(I'm new to things like compiling roms)
Click to expand...
Click to collapse
Good luck with your project ?
[ i'm noob ] Does orange fox recovery working properly on miui 11 ? Unfortunately,i was update my riva to miui 11,succed to unlock bootloader but not with twrp,when i was flash twrp via fastboot,twrp just show up red screen then dim to black screen & only vibrate when touched. I was forgot to add command delete recovery from fastboot,before flashing twrp. Please help,any suggest to proper twrp at stock miui 11 global stable ? Sorry for bed english.
Not work properly when downgrade from MIUI 11 Oreo,now i experience messed up with stock miui rom,try to reverse back with flash full recovery rom from twrp,succed to flash,but when boot into setup wizard,error message appear,eg; "miui daemon has stopped,under that pop up,again error pop up "google service framework has stopped" > "xiaomi service framework has stopped" > "setting has stopped" & bla...bla..bla...! I can't pass setting wizzard,can't continue to normal screen. Then i flash pixel xperience rom 9.0,flawlessly boot until setting wizard done,run smoothly without error. Usually i like to change between custom then stock rom from twrp when i was bored with 1 rom. But now i'm stuck on pixel experience 9.0 (caf) & no twrp working properly when want to flash stock miui oreo.

Need help flashing TWRP onto my rooted SCH-I545 Verizon, 5.0.1, I545VRSGPL1

Can this even be accomplished ?
I am not very phone savvy. I have spent a ton of time reading (apparently) questionable directions/suggestions on what to do.
My ultimate goal was to flash some (any) form of LineageOS on this phone.
I have the USB drivers etc installed (I did manage to root the phone).
I have downloaded Odin (two versions : 3.09 which did not work and 3.14.14 which scared me with warning about deleting my google account...)
I was trying to flash TWRP-3.3.1-0jfltevzw.img.tar (and 3.3.0) obtained from the TWRP website.
I get Write FAIL! (Auth) error very early on.
I have NOT unlocked the bootloader (Is that possible ?). There is no OEM Unlock option in my settings.
I assumed that if the TWRP website published the recovery file that it must be possible to flash it - right ?
I also assume that if I can get ANYTHING flashed to the phone then I should be able to flash some sort of LineageOS. ???
If I ever get this to work, does the TWRP recovery co-exist with LineageOS or does is TWRP wiped when you flash LineageOS ?
Am I using the wrong tool ? Should I be using Odin or something else ?
Sorry for all the questions - but these are a reflection of my mind at this point (quite jumbled).
No LineageOS or TWRP. Verizon prevents the bootloader from being unlocked. You need an unlocked bootloader to install TWRP or an AOSP custom ROM like LineageOS. Some ROMs are possible, but they will all be based on TouchWiz. If you see a ROM with an Android version of 4.x.x, it's not compatible. Only 5.x.x works once you've updated. Here is a guide and list of ROMs: https://forum.xda-developers.com/t/...bricked-de-brick-rom-list-kernel-mod.3395833/
RaspberryPiBen said:
No LineageOS or TWRP. Verizon prevents the bootloader from being unlocked. You need an unlocked bootloader to install TWRP or an AOSP custom ROM like LineageOS. Some ROMs are possible, but they will all be based on TouchWiz. If you see a ROM with an Android version of 4.x.x, it's not compatible. Only 5.x.x works once you've updated. Here is a guide and list of ROMs: https://forum.xda-developers.com/t/...bricked-de-brick-rom-list-kernel-mod.3395833/
Click to expand...
Click to collapse
Hi I have the same problem how do I unlock my bootloader
Mooxxy said:
Hi I have the same problem how do I unlock my bootloader
Click to expand...
Click to collapse
Did you read my comment? It's not possible.
RaspberryPiBen said:
Did you read my comment? It's not possible.
Click to expand...
Click to collapse
i did sorry

Categories

Resources