Hello,
i got a second phone for my GF as i was really happy with this phone and had it flashed without any issues before. This second phone is used and was over a year in use from the guy i've bought it from. It was 100% fine and he always used the shipped Android with it.
So i went on, got the latest TWRP for the phone. Flashed it without any issues and tried to install LineageOS from their website. Flashed it and tried to flash TWRP back as LOS replaces it. I wanted to use TWRP install the backups. But that's where it started to go wrong. Lineage seemed to have been gone from that point on. I couldn't get it to work again, even with reflashing and such. I've downloaded CRDroid and Paranoid and tried them but no luck. Non of them where booting up and TWRP stays showing a warning about "No OS installed".
After some more digging, i've found some posts stating that i would need newest firmware and venders. I've downloaded and flashed them but this made it even worse. The phone started to be stuck in fastboot. I got it working again by flashing latest MIUI version with Xiaomi Flash Tool.
Then i've installed TWRP again but somehow any rom i flash does not boot. The phone starts with the MI logo and flashes once and loads TWRP. There is no message about missing OS or any kind or error when flashing any of these roms.
Anyone able to help me?
Related
Hi
I have been trying for a few days now, but I cant seem to get my WileyFox storm to install OpenGapps (or any Gapps for that matter)
I have flashed the recover to use TWRP and installed [ROM][7.1.2_r17][OFFICIAL] AospExtended ROM V4.3 [OMS/DUI][kipper]
I then tried to install OpenGapps for ARM 7.1.2 Stock using TWRP to flash the zip.
The flash failed saying the device architecture was wrong
I have tried a variety of different types (ARM, ARM64, x86 & so on) with a variety of Android versions as a target.
But nothing works.
I thought the issue may be with the ROM or something so I installed AOKP
This still didnt resolve the issue.
It looks like I have been able to install BeansGapps without any architecture issue, however when I boot the system there is no change.
Am I missing a step, or doing something completely wrong?
Any advice would be appreciated
Its a bit odd replying to myself, but anyway...
OK so I managed to get this working.
It seems to have been an issue with TWRP 3.0.3 and my phone.
The recovery I was using is here:
https://forum.xda-developers.com/wi...t/recovery-team-win-recovery-project-t3367544
I had TWRP installed and then installed AOKP (as mentioned in my first post)
After many many attempts at getting GApps installed with TWRP I finally realised it might be the recovery.
I tried to reflash the recovery with a newer version, and as you can guess...it forced the phone into a bootloader loop
In desperation I went looking for the original twrp recovery and ended finding this page (I'd forgotten where I got the original image):
http://www.androidinfotech.com/2017/03/root-wileyfox-storm-twrp.html
Anyway, I installed that recovery which got me out of the bootloop
It said it was a cyanogenmod recovery...which I thought was odd
I tried to flash GApps and hey presto! It worked
Anyway leaving this here for info.
I hope no-one else runs into such hassle.
Had this exact same issue a few days ago. Searched around for a newer version of TWRP and that sorted it out for me. Couldn't find it on the official TWRP website though.
I hope this works for me to. I will try this tommorow. Breaking my head trying to get my storm to work. Lineage os is making my storm go in an infinite bootloop back to TWRP and every issue you have is relatable. Finding a TWRP for the storm also took me an hour and it doesn't work properly. I hope this works for me but thank you in advance
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
Managed to brick my A1. The only screen its able to go to is either fastbook, or recovery. And even then, doesn't always necessarily boot into recovery, have to plug into computer and go into command prompt (fastboot boot oreo_3.2.2_recovery.img) to get it into TWRP.
Currently can't seem to flash *any* roms, I have a stock rom ("tissot_100108_stock" cant remember where i got it from). Which successfully flashes, but then on reboot gets stuck on the Android One screen. Longest i have waited before giving up is an hour. Even when i flash this rom and reboot, i get a message on TWRP saying "No OS installed"
Tried doing this: [wont let me post link] (MiFlash) method and got an error, basically does not work.
Super frustrated, at my wits end, would just like to flash stock rom and sell this thing or let it sit in a drawer at this point. Thanks in advance.
same problem here...
I have the exact same issue and also came here for that to ask for help.
Xiaomi Mi A1 was running 8.1 OTA updated and then I tried to flash Lineage, but it did not work. I wiped my phone and now it can't install anything, not via TWRP nor with Mi Flash.
I hope we can find a solution.
cantras said:
I have the exact same issue and also came here for that to ask for help.
Xiaomi Mi A1 was running 8.1 OTA updated and then I tried to flash Lineage, but it did not work. I wiped my phone and now it can't install anything, not via TWRP nor with Mi Flash.
I hope we can find a solution.
Click to expand...
Click to collapse
hopefully! i posted on the xiaomi subreddit but no help. i was on 8.0 when i started this whole misadventure.
I got somewhere, I think.
I went into TWRP, switched from B to A booting. It then starts Android but gets stuck in the boot screen of Android one with the colored bar.
I then tried MiFlash again, going directly to the folder which containts the .bat files. It started flashing it finally.
I am back to a working system.
Let me know if it works for you.
you guys should try flashing the latest stock rom 8.1 July running the bat file of your choice located in the factory image through fastboot
the different custom recoveries and miflash are sometimes buggy
run the script directly on fastboot
Sent from my Nexus 6 using Tapatalk
So, to begin with, yesterday Mi A1 got the Android 9 update. As I always do, I went to uptade it with Magisk (it worked with 8.0 to 8.1 and with every security patch, so I, as a newbie, thought, "why the h3ll not?"). Obviously, it didn't work and I got into a boot loop. So, here are the [lot] of things I have tried to do.
-Downloaded MiFlash and the latest OS version from Xiaomi site (8.1 witch november patch). Tried flashing a lot of times, I always get the boot loop after installing it. Wiped all data with TWRP and still didn't work. Always the same problem. Tried with with march security patch and it actually boots. But if I try to uptade via Settings or flash the newest room, I get stuck again.
-Downloaded latest AOSP ROM for the device, flashed it, wiped cache and data, instaled TWRP (3.2.3-0), but the system never initiates. It freezes in the boot animation and nothing happens.
-I've tried the same thing with Lineage 15.1 as well. Checked with MD5 in both roms. Doesn't work at all. Followed every tutorial I could, step by step, don't know what I'm doing wrong.
Can any one please help me? I don't know what to do anymore. Don't wanna get stuck in 8.0 either.
Also, if someone could .zip the Pie update, I would apreciate that. Could try that
Here's the latest flashable pie for you:
https://drive.google.com/file/d/1q9O_F-TB4l3yWthYjw4jkL2prWfh7ClQ/view
Fastboot boot into twrp and clean flash the above latest rom and everything will be fine
thedemon786 said:
Here's the latest flashable pie for you:
https://drive.google.com/file/d/1q9O_F-TB4l3yWthYjw4jkL2prWfh7ClQ/view
Fastboot boot into twrp and clean flash the above latest rom and everything will be fine
Click to expand...
Click to collapse
It worked and it didn't at the same time. The boot animation doesn't freeze anymore, but it's stuck in an infinite loading screen
EDIT: Nevermind, it worked in a second flash. Thank you again
Daniel.meurer said:
It worked and it didn't at the same time. The boot animation doesn't freeze anymore, but it's stuck in an infinite loading screen
EDIT: Nevermind, it worked in a second flash. Thank you again
Click to expand...
Click to collapse
Just hit thanks if it helped. Merry Christmas
Hi,
A few months back I unlocked the bootloader, installed TWRP (I don't know which version, probably letsmakecakes version) and flashed a LOS build from Darkjoker. I ran into a few problems, like asking password on first boot and a Zip Treble compatibility error while trying to flash the rom. I can't recall how I overcome it, I think I deleted something inside the rom zip and then it worked I believe.
But this is an old build, it has a few major bugs (data not working for me, sometimes the phone freezes while connecting to certain networks, etc). I'm dying to change it.
I want to mantain the feel of LOS and stock Android (I don't need costumization), and I've looked into LOS 16 from AmulyaX and Pixel Experience 9.0. Which one would you guys recommend?
Also, with the problems I had when first flashing this phone, I'm a bit afraid of the process. I want to install OrangeFox Recovery and one of these roms. How should I procceed? Can you ELI5 please?
Thank you!
I unlocked my bootloader just yesterday. And before that I made sure that I remove all security locks including screen lock and app lock. This way TWRP did not encrypt my phone. After flashing TWRP I booted into recovery and flashed Orange Fox Recovery zip and it automatically booted into itself. I wanted to stick with MIUI bcz of the battery backup and smoothness so I went for RevOS MIUI. Loving the ROM so far.