I'm not new to the ROM world as I've been doing this for about a year. I usually switch between CM (Lineage) or CypherOS and today I went to TWRP to update it from 3.0.2 to 3.1. After flashing it in TWRP and rebooting back into recovery, my PC no longer detects my device. I have no ROM installed (since I was in the process of switching) and now I'm stuck. I can't get files onto my phone.
I have tried reflashing other versions of TWRP using fastboot but they fail every time. I could really use some help
Update: It was the drivers on my PC. I tried on another laptop and it worked fine.
At the beginning, please forgive me the quality of my English.
Me and other friends using c6903 have posted on the forum about trouble with running Nougat ROMs:
- [ROM][7.1.X][27/07/17][STOCK-CAMERA][3.4 KERNEL][TESTING] LineageOS 14.1 - UNOFFICIAL
- [ROM] [7.1.2] [OMS] [OFFICIAL] [Honami] Resurrection Remix Nougat v5.8.3 [01/08/2017]
- [ROM] [7.1.2] [Substratum/OMS] [UNOFFICIAL] [Honami] Android Ice Cold Project 12.1
For example LinageOS 14.1.
I flashed build from 11/07 without any problems.
Everythings worked fine, but when i try to flash newest build I encountered a big problem.
Bootanimation continues 2-3 sec. and phone turn off [check plz video].
Then only the launch button was active.
Everything I do exactly the same as in 11/07 build.
Why rom can't run?
The situation applies to all the above versions.
Resurrection Remix Nougat from 28/06 booted fine too.
Newer versions not...
One of friends - MIcHiJK - suggested that this could be a problem with changing the screen for "fake".
Me and him changed screens probably for counterfeiting.
Maybe someone else did it and have this problem?
....but why build from 11/07 (LinageOS), 26/08 (RR) and 20/06 (ACIP) booted without any problems?? In my case change screen was earlier.
What have I done so far to solve the problem.
- used TWRP 3.0.0 and 3.0.2
- Always full wiped (a few times format internal storage using twrp too)
- flashed roms when using Cyanogenmod 12.1
- flashed roms when using stock .236
- restored software using EMMa and Flashtool, then root (kingroot), flashed twrp by fastboot, full wipe, flash rom - without result
- used others kernels referenced by creators roms (flashed after installation rom).
Nothing worked.
I know I'm not alone. Many guys have problem like me.
Is anyone able to give a solution?
May God bless guy which will solve our problems!
"https://youtu.be/sOBquHNlbzQ"
Hello to all ppl which had this problem.
Since I replace my broken original xperia z1 Display, I wasn´t able to boot any of the new Nougat rom releases.
I solved this problem with a new Kernel.
Super Lamic Posted this Kernel to test the Battery Life but with this Kernel the problem was solved and I was able to run the new Releases on my fake Display.
Kernel Link: https://mega.nz/#!RN1nFYRT!546WMDdM2ToJEeZlleKTjS-TdR54rkYiOGKUDDWQ-t0
Install new LineageOS build on your xperia z1 with TWRP 3.1 (with 3.0 it wasnt able to install the boot.img).
Before you reboot select images, boot and flash the boot.img.
Then the new build should run without problems.
On other roms like Resurrection Remix it endet in invinite boot so I was just able to run normal Lineage.
I hope it helped someone. Im still interested what the devs changed that causes this problem. And I hope there will be improvments in future that this problem wont happen anymore.
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
For those wo will flash AICP maybe this solution will work in RR too.
In normal Lineage it worked when i flashed cm12.1 Nouagt Kernel after flashing LOS 14.1.
But for RR or AICP it ended in infinite boot. Here is how I managed to get it work.
1. Download AICP (Latest Version [2017/08/01]) then download AICP (Version 2017/06/20).
2. Delete 'boot.img' from the Latest Version zip and put the 'boot.img' from the older relase into the Latest
3. Boot into TWRP 3.1 or 3.0, Wipe all and flash your Latest AICP zip with the older boot.img.
4. Boot phone. The z1 will show you just the Sony Logo. I waited some Minutes and powered off with power + volume up.
5. Connect phone in fastboot mode on PC and flashed cm12.1 Nougat Kernel.
6. Type 'Fastboot Reboot', the phone Turns on with the newer Boot screen where xperia stands on the bottom. You will finally see AICP Boot Animation and after some time rom boots.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
Aaskereija said:
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
Click to expand...
Click to collapse
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
MIcHiJK said:
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
Click to expand...
Click to collapse
really funny. sound good, doesn't work
Aaskereija said:
really funny. sound good, doesn't work
Click to expand...
Click to collapse
How did you installed the rom?
From which rom you came and which recovery did you used and how did you installed the recover?
different ways, but mostly with my standard custom-rom Tesla which is on Android 5.1.1. TWRP is on 3.1 which i install via cmd (fastboot flash recovery) cause build in recovery of tesla is broken.
Or i go over latest stock with dualrecovery, flash boot.img of the custom-rom (wich work) and then flash rom. but still recovery is gone after that.
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Guys, you don't have to create threads for this. I'll have an aftermarket display too, so I'll be forced to fix it anyway. And I have an idea what can be wrong...
MIcHiJK said:
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Click to expand...
Click to collapse
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Aaskereija said:
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Click to expand...
Click to collapse
Android Sdk put twrp.img in platform tools folder then open CMD in this foder, fastboot flash recovery TWRP.img.
I asked about twrp cuz in advanced kernel is TWRP 3.1 inbuild but I can't find just the twrp 3.1 IMG without kernel. Strange.
Hello everyone,
I recently wanted to root my galaxy tab s2 and install a custom rom on it to enhance performance, someting i've done before with my old phone where everything worked fine. So i used autoroot to root the tablet which worked fine and choose to install lineageos afterwards. i found a fitting version of lineage on their official website, installed twrp on my tablet and used it to install lineageos and GApps. However i did not unlock my bootloader using adb since i didnt have to do that back when i rooted my phone and i read on a forum that unlocking oem in the developer settings would be enough. This is where the problems start. After i installed the custom rom the tablet would try to boot into the os for a couple of minutes only showing a loading animation just to boot straight into recovery mode afterwards. In an attempt to fix the error i used odin to install a stock rom from sammobile on the tablet. However now it doesnt even boot into recovery anymore. instead it only shows the stock rom loading animation until the battery emptys. Though i can enter download mode from that position and then cancel it in order to reboot the device which enables me to enter recovery mode. Does anyone have an idea how i could boot a normal os again or is the device hard bricked? The only idea i have left is trying to install a new os from an sd card.
I have the same issue. I installed unofficial lineageos 16 to exynos 2015 t810. I have newest odin and twrp. Im wondering if i need to install or unlock the bootloader to get past the logo loop then recovery bootup after 5 minutes. I followed clean tutorials.
Update: i found this to try.
Quote:
Originally Posted by -beluga-
Hi, first of all thanks for the ROM. Unfortunately I am unable to get my T710 running properly with today's packages (it ran 15.1 so far)
- lineage-16.0-20191009-UNOFFICIAL-gts28wifi.zip
- addonsu-16.0-arm-signed.zip
- open_gapps-arm-9.0-pico-20191009.zip (some with nano or stock)
I am doing a full clean install every time (over 10x so far) but only get it to boot using the ROM alone. Any mod, such as addonsu, gapps or even trwp app cause it to show the Lineage boot screen for quite a while until dropping back into TWRP. Since there is a virtually infinite amount of permutations which versions to try - can someone who is successfully installed 16.0 with Gapps on a T710 let me know their version combination please?
Thanks.
pico-20191009 is giving problems with the 1009 build on my T810 too. Pico-20191006 and Magisk 19.4 are doing the trick for me.
Don't know about other combinations
BTW, it's advised not to install the TWRP app as it is known for causing bootloops on this rom.
Don't know for sure, but wiping internal storage before installing rom might be useful too.
I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
RNZL3R said:
I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
Click to expand...
Click to collapse
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
Screwed badly with the systems to the point where I softbricked the phone, and had to revert to stock. Will try going straight to 3.3.1 instead now.
Edit: I used adb to go to fastboot (adb reboot bootloader), from there I tried all the different twrp images I have, including latest Android 10 one using the fastboot boot image.img (replace image by name of image, I name them A8, A9, A10 to match android version).
All of them booted, which means I can flash them without issues. I don't know which version I want to install though for now, and I don't want to be stuck again on a version that I won't be able to upgrade later on... so will probably go straight to A10 and Lineage 17 even if it's quite buggy.
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
did you found a solution? i have the same issue...
Hi
i was trying flash CrDroid ROM on Mi9, unfortunately the system did not wake up despite correctly installing it. I think ok, I will install other ROM. I wipe the data and this is where the problem appeared - I cannot transfer the file to the phone.
PC not detect the phone (before the first flash there was no problem with it), adb fastboot did the same (before 1st flash it did NOT detect it either, nothing changed,). USB OTG is not working. I tried to reinstall the drivers.
TWRP is custom - Orange Fox
Any ideas?