Lets start off with telling you i am a newbie and was just following tutorials without really knowing what i was doing.
That said, i tried to install a custom ROM but got an error (7) in TWRP. Decided to reflash my old rom and update TWRP using the official TWRP app.
So i did that but when i wanted to boot into recovery it was stuck on the oneplus screen. I went into fastboot and typed fastboot oem unlock because i thought i could flash TWRP that way if the bootloader was unlocked.
When i tried to restart it gave me nothing but the oneplus screen, even the bootloader wont start. I shut it off completely and now it doesn't give me anything at all - just black.
Can someone help me out?
EDIT:
Issue resolved using THIS. Tyvm
Related
Hello and first of all thank you for reading. I've a strange problem with my redmi note 3 pro.
i was chatting with it but suddenly it starts to have bootloops (mi logo flashes). I tried to restore it with recovery (it was still not unlocked) but nothing to do. So i flashed rom with the miflash and in edl mode (i tried latest stable, latest developer and first developer fastboot roms) but the bootloop was still here. So i tried to unlock bootloader with unoficial method (official says that my phone is linked to another account, absolutely false but i will come to this point later). Tried to flash zip with TWRP but still bootloops. I was tired and i tried cm13. It worked, phone boots and i was absolutely happy but dialer crashes when i receive calls. So i understand that my phone wants the boot.img of android 6.0 to not go into bootloop. I flashed (via TWRP) latest 6.0 based miui rom and it worked but still with dialer problem. I tried to unlock it but still no go. So i decided to try to sign out of my miaccount (yeah it was still there after flash with miflash in EDL mode, don't know why!) becasue it asked me to enter my password to use the phone when i boot miui 6.0 for the first time.
SO i Have absolutely no idea on what i should do. Phone bootloops when i use a 5.1 based rom, and with 6.0 dialer crashes. That's the strangest thing ever.
I tried many fastboot roms in edl and in fastboot, i tried custom recoveries and stock one, tried to unlock and relock bootloader. I tried basically everything (wipes, system-data-cache-internal) EVERYTHING!
please if you hava any idea i will be glad to try!
I've tried to restore a backup from another RN3P but still bootloop. Maybe is somethig related to the boot.img? changing it makes the phone boot.
Go to a Mi service center. They might be able to help you.
Which gapps you installed after you flashed cm13...
When i used stock package, my dialer was also crashing but when i used micro package, the problem was solved....
claudios91 said:
Hello and first of all thank you for reading. I've a strange problem with my redmi note 3 pro.
i was chatting with it but suddenly it starts to have bootloops (mi logo flashes). I tried to restore it with recovery (it was still not unlocked) but nothing to do. So i flashed rom with the miflash and in edl mode (i tried latest stable, latest developer and first developer fastboot roms) but the bootloop was still here. So i tried to unlock bootloader with unoficial method (official says that my phone is linked to another account, absolutely false but i will come to this point later). Tried to flash zip with TWRP but still bootloops. I was tired and i tried cm13. It worked, phone boots and i was absolutely happy but dialer crashes when i receive calls. So i understand that my phone wants the boot.img of android 6.0 to not go into bootloop. I flashed (via TWRP) latest 6.0 based miui rom and it worked but still with dialer problem. I tried to unlock it but still no go. So i decided to try to sign out of my miaccount (yeah it was still there after flash with miflash in EDL mode, don't know why!) becasue it asked me to enter my password to use the phone when i boot miui 6.0 for the first time.
SO i Have absolutely no idea on what i should do. Phone bootloops when i use a 5.1 based rom, and with 6.0 dialer crashes. That's the strangest thing ever.
I tried many fastboot roms in edl and in fastboot, i tried custom recoveries and stock one, tried to unlock and relock bootloader. I tried basically everything (wipes, system-data-cache-internal) EVERYTHING!
please if you hava any idea i will be glad to try!
Click to expand...
Click to collapse
I had a similar issue a while ago with a friend's Samsung. The service center people said that it was a RAM issue..
. If you can return the phone to wherever you bought it from, Do it ASAP and get another model...
Otherwise you might have to go to a service center and tell them exactly what you are facing. Before that i must suggest
Try installing a custom Kernel perhaps and see if it still bootloops
For every worst case software/firmware failure, full rom flash would be the one to solve it. Based on your story, it must be the hardware problem. So if possible, bring it to your nearest service center..
i really thank you for the reply but this phone comes from china and i'm in Italy so I have no warranty at all (including the fact i changed the screen) I think i will use it as an ipod. I've posted a log of the kernel bootloop so maybe someone with skills could help me!
that's the log! http://pastebin.com/b3CVcBAT
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
Hi everybody,
I got my Swift 2 8 months ago and have finally decided to root it using TWRP. So I unlocked my bootloader and then installed TWRP using the official guide at https://twrp.me/devices/wileyfoxswift2.html. I also wiped my cache and dalvik cache.
However, now I have done this, whenever I try to boot, I receive both the amber and red warnings about corruption and then get stuck in a bootloop on the first black and white boot image.
Please can someone help me get back into android; if possible I would like root but in the end just a working phone.
Thanks.
As far as I know it's a dm-verity issue. There might be several ways to fix it but the only one I know is to flash Magisk from TWRP. I still run version 12 because 13.x won't install for me.
From my expierience, unlocking and locking bootloader will wipe your userdata , so backup! How I root mine is, first unlock through fastboot, than fastboot boot twrp, instead of flashing, flash magisk through twrp, than lock the bootloader again through fastboot. This keeps you from getting messages about corruption and has you rooted. Whenever I need twrp I just boot it instead of flashing it. I also made a backup using twrp, just to keep things safe and easy to restore...
Edit: To get out of bootloop you either do a factory reset or flash the image found in this forum using fastboot update...
You should have a look at this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
Hi guys, ive been trying to root my lg k3/lg-k100 now for some time, ive ported a twrp which you can use fastboot to boot into, not to flash tho, anything flashed brings up that stupid device is corrupt softbrick (whats the point in an unlocked bootloader right? haha) ive tried just booting from various bootimgs such as a magisk patched one or a supersu patched one, they boot for about 20 sec then phone shuts down with invalid battery, ill upload the ported twrp, any help for me to complete my mission of rooting this phone would be amazing cheers
Hello,
I have a H830tmobile, have had LineageOS for the past 7 months, but recently figured out I didnt have TWRP when trying to find a system file. While trying to install it, I got dumb and bricked my phone.
Thankfully I unbricked it that time, installed vannila ROM H83020i and downgraded to H83020a. I downgraded because it didnt let me use most fastboot commands and couldn't flash TWRP(flashing,booting,...), keep in mind it didn't let me on LineageOS too.
After that I rooted it using Hard Recovwery Method and flashed TWRP. Everything was going great until now, I found out that my phone doesnt show up on PC while in TWRP, would show up without problems in adb or fastboot. After continuing on through the guide, I formatted data, went back to boot into system and got a message that encryption was unsuccesful. Rebooted back into TWRP, searched for a fix and factory reset the phone, didn't help. I read that I should reformat only the System to ext4, did that and phone is without OS and boots endlessly. While trying to go into recovery mode through fastboot commands, it only sends me into endless boot and I can not get into TWRP and even if I could, I wouldn't be able to flash LineageOS as my phone just doesn't show up on PC.
Is this saveable or not?
ok booted into vanilla os again through uppercut, gonna try flashing lineageos only this time