Develop Bugs

Flashing rom, breaking stuff, need some help (twrp bootloop)

Okay, I'm stressed. This is not how I planned it, I'll try to keep it short:
Wanted to do a full clean install of this:
http://forum.xda-developers.com/showthread.php?t=2504016
So what I did:
-Used odin (bootloader) to flash mj5
-Used odin (pda) to flash twrp
-Used twrp to flash rom
-Realised I forgot to wipe, so wiped everything, then wiped media seperate (enter yes to continue) then my N2 rebooted.
Now it's stuck in a boot loop. Teamwin screen keeps flashing every 5 seconds, never going into it.
-Re-flashed twrp via odin, didn't help.
Rom doesn't boot either, bootloop at samsung logo.
**** this is so not good for my stress levels
I have no clue how I broke twrp because I even re-flashed it via odin and still bootloop
Download mode still works thank ****

Okay good news, flashed philz recovery and works! Very happy that I have some sort of recovery back. Now flashing rom, hopefully it boots.
-First boot going on. Very happy now. Sorry for opening this thread, I get REALLY stressed REALLY fast. Once the rom is done booting (which looks like it's going to happen) this thread is not useful anymore, sorry!
-Booting for a few minutes now, stess level is rising...
-Still booting... damn!

Delano.888 said:
Okay good news, flashed philz recovery and works! Very happy that I have some sort of recovery back. Now flashing rom, hopefully it boots.
-First boot going on. Very happy now. Sorry for opening this thread, I get REALLY stressed REALLY fast. Once the rom is done booting (which looks like it's going to happen) this thread is not useful anymore, sorry!
-Booting for a few minutes now, stess level is rising...
-Still booting... damn!
Click to expand...
Click to collapse
Re do the wipes via philz recovery,go under advanced wipe dalvik cache,go and wipe cache partition , then finally "wipe data/factory rest" clean to install new rom,then don't reboot your system cause it won't boot since there's no ROM on it just flash the ROM

singhpratik87 said:
Re do the wipes via philz recovery,go under advanced wipe dalvik cache,go and wipe cache partition , then finally "wipe data/factory rest" clean to install new rom,then don't reboot your system cause it won't boot since there's no ROM on it just flash the ROM
Click to expand...
Click to collapse
I did a full factory reset clean wipe, it does everything for a new rom. Then I flash rom and boot, but booting takes really long. Tried twice, still busy booting second time now 13 minutes...
Didn't do caches last time, I'll try again.

Delano.888 said:
I did a full factory reset clean wipe, it does everything for a new rom. Then I flash rom and boot, but booting takes really long. Tried twice, still busy booting second time now 13 minutes...
Didn't do caches last time, I'll try again.
Click to expand...
Click to collapse
Which philz version are you using?6.25/6.26 is recommended and this other user in DN3 thread couldnt get the rom to boot either by trying latest versions of recovery he used an older version of twrp which is 2.6.3.1/2 and it booted for him.Sometimes recoveries act up for no reason

singhpratik87 said:
Which philz version are you using?6.25/6.26 is recommended and this other user in DN3 thread couldnt get the rom to boot either by trying latest versions of recovery he used an older version of twrp which is 2.6.3.1/2 and it booted for him.Sometimes recoveries act up for no reason
Click to expand...
Click to collapse
philz 5.00, didn't find any newer? that's the problem?
Is this not the latest?:
http://forum.xda-developers.com/showthread.php?t=2028103

Delano.888 said:
philz 5.00, didn't find any newer? that's the problem?
Is this not the latest?:
http://forum.xda-developers.com/showthread.php?t=2028103
Click to expand...
Click to collapse
That's the MAIN culprit my friend i'll link you up with the latest philz
Philz
Download the .tar file put the phone into download mode and flash this recovery via odin using the pda tab

singhpratik87 said:
That's the MAIN culprit my friend i'll link you up with the latest philz
Philz
Download the .tar file put the phone into download mode and flash this recovery via odin using the pda tab
Click to expand...
Click to collapse
Thanks. Got new philz and now installing rom third time.
However I didn't see this anywhere?
8) Now go to choose to install the rom zip file. If you using Philz recovery, make sure to untick "Don't Allow Old update-binary" if this option is avalaible.
Not important? Because didn't see it..

Delano.888 said:
Thanks. Got new philz and now installing rom third time.
However I didn't see this anywhere?
8) Now go to choose to install the rom zip file. If you using Philz recovery, make sure to untick "Don't Allow Old update-binary" if this option is avalaible.
Not important? Because didn't see it..
Click to expand...
Click to collapse
You wont see that line on 6.2.5/6.26 it was only seen on 6.19.2

singhpratik87 said:
You wont see that line on 6.2.5/6.26 it was only seen on 6.19.2
Click to expand...
Click to collapse
Okay thanks. Rom seems to be booting again. Really hope it works now!
edit: still booting, seems to not work again

Delano.888 said:
Okay thanks. Rom seems to be booting again. Really hope it works now!
edit: still booting, seems to not work again
Click to expand...
Click to collapse
Try with twrp 2.6.3.2 ,i know this is annoying that one needs to juggle between recoveries to get a rom to work
Shouldn't take more than 10 minutes for ROM to boot

singhpratik87 said:
Try with twrp 2.6.3.2 ,i know this is annoying that one needs to juggle between recoveries to get a rom to work
Shouldn't take more than 10 minutes for ROM to boot
Click to expand...
Click to collapse
Not 2.7.0.2?

Delano.888 said:
Not 2.7.0.2?
Click to expand...
Click to collapse
You can try like i said it's just trial and error which recovery works,so 2.7.0.2 and then if not work try with 2.6.3.1/2

singhpratik87 said:
You can try like i said it's just trial and error which recovery works,so 2.7.0.2 and then if not work try with 2.6.3.1/2
Click to expand...
Click to collapse
I have NO CLUE what just happened.
I flashed twrp, and it rebooted. Recovery didn't boot, but phone booted right away! Rom is now on. Guess it's okay now.
Thanks for the help!

Delano.888 said:
I have NO CLUE what just happened.
I flashed twrp, and it rebooted. Recovery didn't boot, but phone booted right away! Rom is now on. Guess it's okay now.
Thanks for the help!
Click to expand...
Click to collapse
LOL ,told you ,recoveries can be very annoying at times.Now enjoy the ROM.If you face any issues use the search button in the DN3 thread or read the FAQ in the first page i think it's the 4th post there.Good luck

singhpratik87 said:
LOL ,told you ,recoveries can be very annoying at times.Now enjoy the ROM.If you face any issues use the search button in the DN3 thread or read the FAQ in the first page i think it's the 4th post there.Good luck
Click to expand...
Click to collapse
Very strange how that happened but everything is good now. Thank you very much!

@Delano.888 this is why I NEVER use ODIN, it Just screws your phone up. TWRP FTW for me.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!

Irwenzhao said:
@Delano.888 this is why I NEVER use ODIN, it Just screws your phone up. TWRP FTW for me.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
I don't think it was the fault of odin because I got it working later but the rom has many problems so I guess the rom is just broken. No time today but I'll change my rom soon.

Irwenzhao said:
@Delano.888 this is why I NEVER use ODIN, it Just screws your phone up. TWRP FTW for me.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
Gr8 advice, hope that not too many read this and trust in it. :fingers-crossed:

Delano.888 said:
I don't think it was the fault of odin because I got it working later but the rom has many problems so I guess the rom is just broken. No time today but I'll change my rom soon.
Click to expand...
Click to collapse
Androidwizzard said:
Gr8 advice, hope that not too many read this and trust in it. :fingers-crossed:
Click to expand...
Click to collapse
ODIN is pure unreliable for me. I'm still using a version of TWRP I got last year and it's still more reliable than cwm or any other recovery.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!

Is there a recovery for KitKat

I'm confused from reading posts and such. Is there a recovery for KitKat yet?

Dcm210 said:
I'm confused from reading posts and such. Is there a recovery for KitKat yet?
Click to expand...
Click to collapse
Did you find one?

shahrukhqasim said:
Did you find one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52277504&postcount=29
It comes with its own issues but gets you recovery. Afterwards, freegee works on the E-980 to flash a newer and more stable recovery.

jdk2 said:
http://forum.xda-developers.com/showpost.php?p=52277504&postcount=29
It comes with its own issues but gets you recovery. Afterwards, freegee works on the E-980 to flash a newer and more stable recovery.
Click to expand...
Click to collapse
"Secure booting error so boot success" is this something to be worried about?
And now if I flash some AOSP based ROM, will it work?

shahrukhqasim said:
"Secure booting error so boot success" is this something to be worried about?
And now if I flash some AOSP based ROM, will it work?
Click to expand...
Click to collapse
No, it's supposed to say that.

Not trying to highjack this thread, but I have 2 relevant questions.
1)
On my E980, I tried using Freegee to install recovery like back on Jelly bean. Every time I do this now, Freegee says an exception was thrown and that E98020g is not supported.
When I use this apk to install the kitkat recovery, everything works fine. Weird thing though is that afterwards, Freegee stops spitting these errors at me.
Any idea what's up with this? Should I stick with the Kitkat recovery, or now use Freegee to install its CWM/TWRP recovery?
2)
(continuing from question 1)
A few hours ago (and all day yesterday too), I did try flashing CWM through Freegee and it worked. I then used that recovery to flash the PhilZ Touch recovery, which I like more. With both the Freegee CWM and the PhilZ recovery, I can do pretty much everything just fine.
But... the problem is that at random times, the PhilZ recovery will cause me to get stuck in a Recovery bootloop. Basically, every bootup forces me into recovery whether I'm holding the proper buttons during bootup or not. (NOTE: I have yet to stick with the Freegee recovery versions long enough to see if they do this too, but some other people are reporting CWM bootloops).
So question 2 is this:
Is this being caused by PhilZ not being fully Kitkat compatible?
Will this Kitkat CWM Recovery not do this? Every time it happens, I must reflash my phone using the tot method and it's getting tiring... been trying to get things working for a day now.

New to this and think I broke my phone.

Well let me explain. I wanted to tether, so I thought I would try and root and install a custom rom. I used Odin to install TWRP, downloaded NobleRom, thinking that it should work, flashed it and all it does it sit at the android screen when I boot up. I did a wipe and tried to install a "stock" rom that is apparently incompatible. My phone is a 920P. Currently lost and looking for direction for a slim, compatible rom that works.
HELP!

mrcookjr said:
Well let me explain. I wanted to tether, so I thought I would try and root and install a custom rom. I used Odin to install TWRP, downloaded NobleRom, thinking that it should work, flashed it and all it does it sit at the android screen when I boot up. I did a wipe and tried to install a "stock" rom that is apparently incompatible. My phone is a 920P. Currently lost and looking for direction for a slim, compatible rom that works.
HELP!
Click to expand...
Click to collapse
im using this with no issues flash in recovery
http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417

I download and give this a try! Thank you!

The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.

1619415 said:
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
Click to expand...
Click to collapse
That's what the post above suggested. Thank you for explaining why. So from what you're saying, each rom is based on a particular Kernel? What other factors must be the same? I'm sorry if this is a dead horse, just new to me.

1619415 said:
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
Click to expand...
Click to collapse
OK, I just installed Renegade and it's sitting on the boot screen with Andy holding a dragonball and a phone. Did I do something wrong?

mrcookjr said:
OK, I just installed Renegade and it's sitting on the boot screen with Andy holding a dragonball and a phone. Did I do something wrong?
Click to expand...
Click to collapse
Wait what?
Upload a screenshot

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers

Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk

I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.

Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.

Thanks a lot guys, that did the trick, and done with flashify

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk

Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.

Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!

HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.

GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...

m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time

http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me

This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!

gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..

After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.

Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse

Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

Failed install of Android 7.1.2 - boot stuck on "Android"

I had CWM Recovery and an older cyanogenmod rom installed and I wanted to upgrade to 7.1.2 from here: https://forum.xda-developers.com/lg.../rom-android-7-0-nougat-20161008-r16-t3476750
I copied the rom to internal memory, rebooted into recovery, selected the rom file to install. It showed some messages about patching, then in a couple of minuted erred with smth like "Erro loki-ifying because of incompatible aboot image".
I then rebooted and now it boots and shows "ANDROID" and is stuck on it - looks like it partially updated the ROM and failed somewhere.
I am not sure what to do now - I tried to boot into recovery (Power off -> Hold Power + Vol down till menu shows) but it doesnt work - it keeps booting onto this stuck boot.
Any ideas?

As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Sent from my XT1254 using Tapatalk
Crap. Sorry. Disregard. Thought this was a Droid Turbo thread.

Einsteindks said:
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Click to expand...
Click to collapse
But how do I flash anything if I can't get into recovery?

andreyl79 said:
But how do I flash anything if I can't get into recovery?
Click to expand...
Click to collapse
You missed my edit update. I got confused as to which thread I was replying to.
Sent from my XT1254 using Tapatalk

Einsteindks said:
You missed my edit update. I got confused as to which thread I was replying to.
Click to expand...
Click to collapse
Nevertheless you gave me the idea to try looking for a similar LG recovery tool and I just found one. Flashing stock at the moment - fingers crossed

Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here

andreyl79 said:
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
Click to expand...
Click to collapse
The reason the flash failed is simply the fact you put the ROM on the internal storage, flashing from there wiped the ROM before it gets written. If you had stored the AOSP on an external SD, it would have worked.
As Lineage is based on AOSP, it should have failed also...