Develop Bugs

[Q] Won't boot rom or cwm recovery - only download mode

Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?

No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app

Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?

Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?

This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".

vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards

Recovery rebooting without flashing

Hi
While flashing CM13 on my redmi 1s, I did a clean install, meaning wiping everything, and then when I went to flash CM13, TWRP just reboots the moment I swipe to install. This happens with any .zip file.
I installed CWM using fastboot, and that gives me the same problem. The moment I try to flash/install anything using a recovery, that recovery reboots and doesn't flash anything. My device is now useless since it doesn't have an OS installed and no way of doing so..
From what I can tell the system partition is bad because when I boot into recovery it isnt mounted
When I take out the battery now it just goes straight to the fastboot screen. I can take it into recovery but it goes to fastboot by default
Please help

Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!

vbvn said:
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
Click to expand...
Click to collapse
Flashing the fastboot rom doesn't work.. My recovery is broken too, because I can't flash anything.. In either MiRecovery 2.0.1, CWM or twrp.. When I flash the MIUI rom via fastboot it just boots into recovery..
EDIT, I just got it into MIUI but the 4.3 version from china, without Google, and I can't download google via the MI market. So i'm downloading an international version now and will try to flash using MiFlash.
Does anyone know how I can fix the recovery? It still won't flash anything and reboots the moment I try to.

I can't reflash stock recovery

Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one

ICosmin said:
Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one
Click to expand...
Click to collapse
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery

cbendixe84 said:
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery
Click to expand...
Click to collapse
i have already flashed twrp 3.0.2.2 but now I would flash stock recovery but when I try to install it and turn into it op3 show me only op logo and after a few seconds the screen become black.

your phone is bricked I'm assuming. there is a thread for that. that should work for you!

sahed01 said:
your phone is bricked I'm assuming. there is a thread for that. that should work for you!
Click to expand...
Click to collapse
No it isn't. Because I managed to put stock ROM into it via adb with push command and after I have installed it from twrp that works. My only problem is that i can't flash stock recovery.

i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance

varmasagiraju said:
i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance
Click to expand...
Click to collapse
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.

ICosmin said:
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.
Click to expand...
Click to collapse
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?

varmasagiraju said:
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?
Click to expand...
Click to collapse
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)

ICosmin said:
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)
Click to expand...
Click to collapse
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??

If this procedure doesn't you can download an older version of oxygen os and update it via ota. At the first attempt when you will try it will give you an error and at the second attempt It will download all the ROM again and it will reflash by itself

varmasagiraju said:
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??
Click to expand...
Click to collapse
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.

ICosmin said:
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.
Click to expand...
Click to collapse
Thank you.
Will let you know if it worked.

I had that problem.
Solution as follows, worked everytime for me: (I have not tried this method with the newest beta 8)
1. Flash OOS 3.2.6 firmware in twrp.
2. Reboot to fastboot and flash official oxygen os recovery downloaded from the OnePlus website. (This is still the old version for some reason, thus why it won't work)
3. Side load community build with oxygen os recovery, this will flash the new firmware back and update the recovery to be community build compatible.
4. Before rebooting erase everything (factory restore)
5. Reboot to OOS, finish setting up.
6. Turn on advance reboot in developer settings.
7. Reboot to recovery via the reboot menu. First time boot into the recovery may take sometime, but it has always worked for me.
8. After everything looks good, go ahead and OEM lock in fastboot, recovery should work as usual this time and format your phone

OP did you find a solution to this?? Im on the same boat as you

couldn't boot to twrp recovery after flashing cm14

hi'
i have flashed cm14 nightly with aroma (gapps) on cm13 on my oneplus 3
now i couldn't go neither to recovery mode nor to current cm 14 rom to change my rom
i am out of ideas i tried in every possible way to my knowledge pleasee help me ........................

Flash the modified twrp 3.0.2-22 via fastboot.

Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img

I had the same problem. Flashing modified twrp worked for me, thanks! But now if I to flash stock recovery (to install otas), I can't boot to recovery. E: oxygenos otas can be installed with twrp, so no problem anymore

plz send me the link of modified twrp
i coudnt find it on google properly plz

Try the link given by Demian3112. It works

THQ thq soon much.. Its working
Demian3112 said:
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
Yes its working
Thank q very much

THQ thq soon much.. Its working
AJay27 said:
Try the link given by Demian3112. It works
Click to expand...
Click to collapse
THQ for ur valuable suggestion
My killer is back

Demian3112 said:
Get modified twrp here i asume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
Hii,
Still the problem remains same I will explain in detail
I am back to cm14.1 when I flashed twrp from the above link
When I tried to flash some other ROMs they are flashed but screen goes blank after oneplus boot animation,
If I flash 14.1 ROM it is working fine
From cmd non of the recovery where flashed only the above is working
Plz help me
I want to go back to stock soon

It's because of the system partition rewriting issue. People in the cm and other communities are already working on it. Basically the boot partitions get rewritten when we install the cm 14.1 . It happens to some variants while others works fine. Just the issue because of not enough testing. Will be sorted out within time.
What you can do is. Use flashify app or fastboot from your pc and flash your twrp back after installing and booting into the cm 14.1. You can use any twrp no modified versions needed as far as it is supported by your device model. Ciao. Hit thanks if i helped.

sanjumalik720 said:
It's because of the system partition rewriting issue. People in the cm and other communities are already working on it. Basically the boot partitions get rewritten when we install the cm 14.1 . It happens to some variants while others works fine. Just the issue because of not enough testing. Will be sorted out within time.
What you can do is. Use flashify app or fastboot from your pc and flash your twrp back after installing and booting into the cm 14.1. You can use any twrp no modified versions needed as far as it is supported by your device model. Ciao. Hit thanks if i helped.
Click to expand...
Click to collapse
ohhh
then what is the solution ?????

Thank you very much
Demian3112 said:
Get modified twrp here i assume that you know how to flash it?
Boot in fastboot > fastboot flash recovery Recovery filename.img
Click to expand...
Click to collapse
I had the same problem as OP, got stuck with the CM 14 and did not like it (to early, to many bugs)
Wanted to go back to CM 13 but was unable to get into TWRP, and unable to flash CM13 back. Tried with fastboot and adb sideload, nothing worked.
The modified TWRP let me do i full wipe of the phone, (wiped Data, Dalik/ART, and system.) then copied the CM13 Stable release from here onto the phone, together with Gapps, and now everything is back to normal.
Again thank you, and thanks XDA! Somehow you always manage to save my ass after i messed with my device

Balaji Dasari said:
ohhh
then what is the solution ?????
Click to expand...
Click to collapse
Just flash the twrp image file again. The one you used before. Just flash it again. The same way you did back then.

Rooting went fine Flashing rom almost bricked me due to directions??

I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly

Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app

I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?

nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done

Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?

nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good: